JP5624954B2 - Fault detection device, fault detection method, and fault detection program - Google Patents

Description

  The present invention relates to a failure detection device, a failure detection method, and a failure detection program.

  In recent years, the use of IP (Internet Protocol) telephones has been increasing mainly in communication carrier networks. In many cases, outgoing calls and incoming calls between users in an IP telephone service are realized using SIP (Session Initiation Protocol), and the role of the SIP server responsible for relaying calls is important. In addition, many communication carriers are interconnected not only with general users but also with other communication carriers. Based on SLA (Service Level Agreement), the normality of SIP signaling propagation is maintained, and deterioration factors are caused during abnormal conditions. It has become very important to identify locations early and restore service.

Regarding the failure monitoring of SIP servers distributed over a wide area that provide IP telephone services such as communication carriers, there is a system that captures all SIP packets flowing into or out of a SIP server and monitors traffic between the SIP servers in real time. It is known (Non-Patent Document 1).
Further, in Patent Document 1, a server failure is detected based on the number of SIP messages transmitted and received by each SIP server, and the failure occurs on either the user side or the non-user side based on the SIP server to which the terminal is connected. And a monitoring device that detects a logical failure between SIP servers is disclosed.

JP 2009-239343 A

NetCall Monitor, http://www.softfront.co.jp/products/applience/netcall/netcall_monitor.html

However, the system disclosed in Non-Patent Document 1 needs to individually confirm the captured data of SIP packets when monitoring a failure in a SIP signal network composed of a plurality of SIP servers. Therefore, when the number of SIP packets increases due to an increase in subscribers in the future, there is a problem that the analysis load of the system shown in Non-Patent Document 1 increases.
To solve this problem, Patent Document 1 solves the problem by monitoring a failure in the SIP signal network based on the number of SIP signals transmitted and received by each SIP server instead of individual SIP packets.

  However, since the monitoring apparatus disclosed in Patent Document 1 simply determines the server where the SIP signal has not been transferred normally (where an error has occurred) as the failure location, an abnormal SIP signal is generated due to a failure or the like. There is a problem that the failure location cannot be accurately identified in the case of transfer. In addition, the monitoring device disclosed in Patent Document 1 has a problem that a failure location cannot be specified when three or more SIP servers are routed between terminals.

  Therefore, the present invention has been made in view of the above problems, and a failure detection device, a failure detection method, and a failure that can accurately identify a failure location in a SIP signal network without analyzing individual SIP packets. It is an object to provide a detection program.

  The present invention has been made to solve the above-described problem, and one aspect of the present invention is an occurrence error in which the number of occurrence errors for each path between SIP servers is estimated based on statistical information related to SIP signal communication. A failure detection apparatus comprising: a number estimation unit; and a failure location identification unit that identifies a failure location based on the number of paths transmitting or receiving the estimated occurrence error.

  Further, according to one aspect of the present invention, in the above-described failure detection apparatus, the generated error number estimation unit includes the number of errors received and transmitted by a certain SIP server for each path, and the normal received by the SIP server for each path. Based on the number of calls, the number of transfer errors transmitted by the SIP server for each path is calculated, and based on the calculated number of transfer errors and the number of errors transmitted by the SIP server for each path, the SIP server The number of generated errors transmitted by the server is estimated for each path.

  Further, according to one aspect of the present invention, in the above-described failure detection apparatus, the failure location specifying unit may determine the number of paths that transmit or receive the generated error and the number of transmissions or receptions for each path of the generated error. Based on the above, the failure location is specified.

  Further, according to another aspect of the present invention, the failure detection apparatus further includes a failure occurrence detection unit that detects failure occurrence in the SIP signal network based on the estimated number of occurrence errors for each path. To do.

  Further, according to one aspect of the present invention, in the above-described failure detection apparatus, the failure occurrence detection unit acquires the number of past occurrence errors for each item related to the occurrence error, and the failure occurrence detection unit generates a failure occurrence. The detection is performed by totaling the number of generated errors at the current time for each item and comparing the total number of generated errors for each item with the number of past generated errors for each corresponding item. .

  Another embodiment of the present invention is a failure detection method executed by a failure detection apparatus, and estimates the number of generated errors for each path between SIP servers based on statistical information related to SIP signal communication. A failure detection method comprising: a procedure; and a failure occurrence detection procedure for detecting failure occurrence in a SIP signal network based on the estimated number of occurrence errors for each path.

  Further, according to one aspect of the present invention, a computer is configured to estimate a number of generated errors for each path between SIP servers based on statistical information related to SIP signal communication. A failure detection program for executing a failure occurrence detection step for detecting occurrence of a failure in a SIP signal network based on the number of occurrence errors.

  According to the present invention, it is possible to accurately identify a failure location in a SIP signal network without analyzing individual SIP packets.

It is a figure for demonstrating an error, a generation | occurrence | production error, and a transfer error. It is a schematic block diagram of the failure location detection system in this embodiment. It is an example of the data structure of the statistical information of a normal call, and the statistical information at the time of an error. It is a schematic block diagram of the failure detection apparatus in this embodiment. It is a figure for demonstrating the calculation method of the number T (i) of the transfer error which the SIP server transmitted with respect to the path | route i. It is an example of the statistical information relevant to the SIP server X extracted by the generation | occurrence | production error number estimation part. This is the statistical information after the one with the called number band of “03” is extracted from the statistical information of FIG. The statistical information after the error number “400” is extracted from the statistical information of FIG. It is an example of the statistical information after generation | occurrence | production error was estimated. FIG. 10 is a diagram showing the number of generated errors totaled for each transmission address / error number combination in the example of FIG. 9. It is an example of the average number of occurrence errors in the past fixed period stored in the statistical information storage unit. It is an example of the number of generated errors after being divided for each path from statistical information. It is a flowchart which shows the flow of the whole process of the failure detection apparatus in this embodiment. It is a flowchart which shows the detail of a process of the generated error number estimation part in step S103 of FIG. It is a flowchart which shows the detail of a process of the failure generation detection part in step S104 of FIG. It is a flowchart which shows the detail of a process of the failure location specific | specification part in step S105 of FIG.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. First, the meaning of the words used in this embodiment will be described. In this embodiment, “call” means a SIP INVITE message (hereinafter also referred to as INVITE). “Called number band” means a specific upper digit in a number representing the destination of a call.

  FIG. 1 is a diagram for explaining errors, occurrence errors, and transfer errors. In the figure, a terminal 10, a SIP server 20, a SIP server 30, and a SIP server 40 are shown. The terminal 10 transmits INVITE to the SIP server 20. When receiving the INVITE from the terminal 10, the SIP server 20 transfers the received INVITE to the SIP server 30. When receiving the INVITE from the SIP server 20, the SIP server 30 transfers the received INVITE to the SIP server 40.

  If the SIP server 40 receives an INVITE from the SIP server 30 and a failure has occurred in the SIP server 40, the SIP server 40 transmits an error message to the SIP server 30. When receiving an error message from the SIP server 40, the SIP server 30 transfers it to the SIP server 20. When receiving the error message from the SIP server 30, the SIP server 20 transfers it to the terminal 10.

  That is, an error that has occurred in the SIP server 40 is transferred to the terminal 10 through the SIP server through which INVITE has passed. At this time, the error message transmitted by the originating SIP server 40 is referred to as “occurrence error”, and the error message transferred by the intermediate SIP server (20, 30) is referred to as “transfer error”. Further, when simply referred to as “error”, it means an error message including an occurrence error and a transfer error.

  “Route” means a communication route through which calls and errors are transmitted / transferred. “Sender server / receiver server” means a SIP server on each side of a call or error sender / receiver on a certain route. The IP addresses of devices that transmit / receive calls and errors in a certain route are referred to as “transmitting address” and “receiving address”.

  In general, an error occurrence mechanism can be roughly classified into two in a SIP signal. One is referred to as a “server type error”, which is an error caused by the SIP server that received the call. The other is called a “client-type error”, which is an error caused by the SIP server that sent the call. Specifically, the server type error is an error when an error is transmitted in response to a normal call received by a SIP server in which a failure or the like has occurred. On the other hand, the client type error is an error when an error is returned from a normal SIP server as a transmission destination because a certain SIP server has transmitted an abnormal INVITE.

FIG. 2 is a schematic block diagram of the failure location detection system 1 in the present embodiment. The failure location detection system 1 includes a SIP signal network 100, a SIP signal collection device 200, and a failure detection device 300.
The SIP signal network 100 is a network that is a target for isolating a fault location.
The SIP signaling network 100 includes eight SIP servers up to SIP servers 101,. Each SIP server is connected to other SIP servers. For example, the SIP server 101 is connected to the SIP servers 102, 104, 105 and 107.

  Each SIP server performs the following processing as an example. Each SIP server stores call transfer information in which a transfer destination is set for each called party number band in a storage unit included in the SIP server. When each SIP server receives a call from another SIP server, it refers to the call transfer information and transfers the call to a transfer destination that matches the called number band of the received call. If an error occurs, each SIP server transfers the error by going back the route through which the call has been transferred. Each SIP server records all call and error transfer processes in its SIP server in the SIP log.

  In the present embodiment, the SIP signal network 100 includes eight SIP servers. However, the present invention is not limited to this, and it is only necessary to include two or more SIP servers.

  The SIP signal collection device 200 performs the following processing as an example. The SIP signal collection device 200 is connected to all the SIP servers (101 to 108) constituting the SIP signal network through a communication network, and periodically collects SIP logs from each SIP server. The SIP signal collection device 200 generates statistical information related to communication per unit time for each SIP server based on the collected SIP log information. Here, the statistical information related to communication refers to the number of calls that are normally answered (hereinafter referred to as the number of normal calls), the number of calls that have an error during call transfer, and the transmission and reception of error messages. It means a number (hereinafter referred to as error number).

  The SIP signal collection device 200 in this embodiment counts the number of normal calls and the number of errors. Specifically, the SIP signal collection device 200 counts the number of transmission / reception for each combination of “route” / “numbered number band” for normal calls. On the other hand, the SIP signal collection device 200 counts the number of transmission / reception for each combination of “route” / “called number band” / “error number” regarding errors. Then, the SIP signal collection device 200 transmits the generated statistical information to the failure detection device 300.

  The failure detection apparatus 300 identifies a failure location based on the statistical information of the SIP signal. The failure detection device 300 estimates the number of generated errors, detects the failure occurrence, and identifies the failure location based on the SIP signal statistical information received from the SIP signal collection device 200. In addition, the failure detection apparatus 300 holds SIP signal statistical information for a predetermined period in the past in order to detect the occurrence of a failure.

  Here, an example of a data structure of statistical information related to communication in the present embodiment will be described. The statistical information is roughly divided into two pieces of information that respectively count the number of normal calls and the number of errors, and these are represented by the data structure of FIG.

FIG. 3 shows an example of the data structure of statistical information on normal calls and statistical information on errors. FIG. 3A is an example of a data structure of statistical information of normal calls. In FIG. 3A, normal call statistical information data is represented by a set of start time, end time, transmission side address, reception side address, called number band, and number of calls.
FIG. 3B is an example of the data structure of error statistical information. In FIG. 3B, data of statistical information at the time of error is represented by a set of start time, end time, transmission side address, reception side address, called number band, error number, and number of errors.

Here, the statistical information is generated by the SIP log collection device 200 every unit time. The “start time” / “end time” in FIG. 3 indicates the start time and end time of the unit time for which the statistical information is generated. Represents the time.
The statistical information of normal calls shown in FIG. 3 (A) is the total number of calls for each unit time, for each route, and for each called number band. At this time, the call with an error is not counted. The error statistical information shown in FIG. 3B is obtained by counting the number of errors for each unit time, for each route, for each called number band, and for each error number. The direction of error transmission / reception is opposite to the direction of call transmission / reception.

  This data structure will be used in the explanation of the specific processing method described later. However, some columns are omitted as necessary, and the “number of calls” and “number of errors” are specified for specific grouping conditions. Each of them is expressed as a total number. Further, the “number of errors” is the total number of transfer errors and generated errors when it is received from the SIP log collection device 200, but is estimated after the number of generated errors is estimated in the failure detection device 300. It shall be expressed as the number of generated errors.

FIG. 4 is a schematic block diagram of the failure detection apparatus 300 in the present embodiment. The failure detection apparatus 300 includes a statistical information reception unit 301, a statistical information storage unit 302, an occurrence error number estimation unit 303, a failure occurrence detection unit 304, and a failure location identification unit 305.
The statistical information receiving unit 301 receives statistical information from the SIP log collection device 200 and stores the received statistical information in the statistical information storage unit 302. Further, the statistical information receiving unit 301 outputs the received statistical information to the generated error number estimating unit 303.

  The statistical information storage unit 302 holds the statistical information of the SIP signal received from the SIP log collection device 200. In addition, the statistical information storage unit 302 holds the past occurrence error number information indicating the past occurrence error number calculated by the occurrence error number estimation unit 303 for a certain period required by the failure occurrence detection unit 304.

Based on the statistical information received from the statistical information receiving unit 301, the generated error number estimating unit 303 estimates the number of generated errors in each SIP server (hereinafter also referred to as a generated error number estimating process). Details of the generated error number estimation process will be described later.
The generated error number estimation unit 303 calculates the generated error number for each combination of “route” / “error number” / “called number band”. The generated error number estimating unit 303 adds generated error number information indicating the calculated generated error number to past generated error number information stored in the statistical information storage unit 302. Further, the generated error number estimation unit 303 outputs the generated error number information to the failure occurrence detection unit 304.

  The failure occurrence detection unit 304 determines the occurrence error number indicated by the occurrence error number information input from the occurrence error number estimation unit 303 as a combination of “transmission side address” / “error number” or “reception side address” / “error number”. "For each combination. Then, the failure occurrence detection unit 304 compares the total number of occurrence errors with the average number of occurrence errors in the past certain period held in the statistical information storage unit 302 (hereinafter referred to as the average number of occurrence errors), Detection of failure occurrence (hereinafter also referred to as failure occurrence detection processing) is performed. Details of the failure occurrence detection process will be described later.

  The failure occurrence detection unit 304 outputs failure occurrence information indicating the occurrence of the failure obtained by the detection to the failure location specifying unit 305. As a result, the fault location is identified by the fault location identification unit 305 for those detected as the occurrence of the fault.

  The fault location identifying unit 305 determines the path in which the occurrence error has been transmitted (or received) and the number of transmissions (or the number of receptions) of the occurrence error of the fault detected by the fault occurrence detection unit 304. Based on this, the failure location is identified (hereinafter also referred to as failure location identification processing). Details of the fault location specifying process in the fault location specifying unit 305 will be described later. The failure location specifying unit 305 outputs failure location information indicating the specified failure location to the outside of the own device.

<Principle of generated error number estimation processing>
Next, the principle of the generated error number estimation process will be described. Hereinafter, the following definitions are used for explanation. The normal call and error transmission / reception directions are opposite. The number of normal calls received from a path i by a certain SIP server X is NI (i). In addition, the number of errors received from a path i by a certain SIP server X is EI (i). The number of errors transmitted from a certain SIP server X to route i is EO (i). Of the errors transmitted from a certain SIP server X to the path i, the number of transfer errors is T (i). In addition, among errors transmitted from a certain SIP server X to the route i, the number of generated errors is G (i). Among the above, the number of normal calls NI (i), the number of received errors EI (i), and the number of transmitted errors EO (i) are included in the statistical information received from the SIP log collection device 200.

The number of occurrence errors T (i) of the generated error number estimation unit 303 transmitted from a certain SIP server X to the route i is calculated based on the number of errors received from all routes by a certain SIP server X per predetermined unit time. By multiplying the total number by the ratio of the number of normal calls received by the SIP server X from the path i per unit time to the total number of normal calls received by the SIP server X from the entire path per unit time. calculate.
Specifically, the generated error number estimation unit 303 calculates the number T (i) of transfer errors transmitted from a certain SIP server X to the route i according to the following equation (1) for each route.

Here, ΣEI (X) and ΣNI (X) are the total number of errors received by the SIP server X from all paths and the total number of normal calls received by the SIP server X from all paths, respectively.
Since Equation (1) is calculated as a probabilistic value, depending on the statistical information, the number of transfer errors in the calculation result of Equation (1) is greater than the number of transmission errors (ie, T (i)). > EO (i)) may occur. In this case, the generated error number estimation unit 303 sets the value of T (i) to EO (i) in the route.

At this time, since a difference occurs between the total number of received errors and the total number of transfer errors, the generated error number estimation unit 303 distributes the difference to a path where T (i) is smaller than EO (i). .
Specifically, for example, the generated error number estimation unit 303 calculates T ′ (i) according to the following equation, where T ′ (i) is the number of transfer errors distributed to each path.

  Here, ΣNI (y) is the total number of normal calls in a route where T (i) in the SIP server X is smaller than EO (i). The generated error number estimating unit 303 newly sets T (i) obtained by adding T ′ (i) obtained by this equation to T (i). In addition, when a route whose T (i) is larger than EO (i) is generated again by this, the generated error number estimation unit 303 eliminates all routes whose T (i) is larger than EO (i) (ΣT ( x) = ΣEI (x) until the above processing is repeated.

  Subsequently, since the number of generated errors G (i) is obtained by subtracting the number of transmission errors T (i) from the number of transmission errors EO (i), the generated error number estimating unit 303 performs the following for each path. The number of occurrence errors G (i) is calculated according to the following equation (3).

  As described above, the generated error number estimation unit 303 transmits, based on the number of errors received by a certain SIP server for each route and the number of normal calls received by the SIP server for each route, for each route. The number of generated transfer errors is calculated, and the number of generated errors transmitted by the SIP server is estimated based on the calculated number of transfer errors and the number of errors transmitted by the SIP server for each path.

Next, a method for calculating the number T (i) of transfer errors by the generated error number estimation unit 303 will be described with reference to the example of FIG.
FIG. 5 is a diagram for explaining a method for calculating the number T (i) of transfer errors transmitted from the SIP server 54 to the route i. In the figure, seven SIP servers 51, 52, 53, 54, 55, 56 and 57 are shown. Here, a solid line represents a normal call, and a broken line represents an error. Hereinafter, the route from the SIP server X to the SIP server Z is described as route X → Z.

In the figure, the error number EI (51 → 54) of the path 51 → 54 is 5, the error number EI (52 → 54) of the path 52 → 54 is 5, and the error of the path 53 → 54. It is shown that the number EI (53 → 54) of the number is 10 in the same figure. In addition, the number of normal calls NI (55 → 54) of the route 55 → 54 is four, and the route 56 → 54. It is shown that the number of normal calls NI (56 → 54) is 4 and the number of normal calls NI (57 → 54) of the path 57 → 54 is 12.

  In the figure, the number of errors EO (54 → 55) in the path 54 → 55 is 20, the number of errors EO (54 → 56) in the path 54 → 56 is 20, and the path 54 → 57. It is shown that the number of errors EO (54 → 57) is 10.

  Here, the total number of errors received by the SIP server 54 from other SIP servers is 20 (= 5 + 5 + 10). The total number of normal calls received by the SIP server 54 from other SIP servers is 20 (= 4 + 4 + 12). Therefore, in the example of FIG. 5, the generated error number estimation unit 303 calculates the transfer error number T (54 → 55) of the path 54 → 55 as 4 (= 20 × 4/20). Similarly, the generated error number estimation unit 303 calculates the transfer error number T (54 → 56) of the route 54 → 56 as 4 (= 20 × 4/20). Similarly, the generated error number estimation unit 303 calculates the transfer error number T (54 → 57) of the route 54 → 57 as 12 (= 20 × 12/20).

Since the transfer error number T (54 → 57) of the route 54 → 57 is larger than the transmission error number EO (54 → 57) of the same route, the transfer error number T (54 → 57) of the route 54 → 57 is calculated as the route. It is assumed that the transmission error number EO (54 → 57) of 54 → 57 is 10.
The generated error number estimating unit 303 generates a difference 2 between the total number 20 of errors received by the SIP server 54 and the total number 18 of transfer errors transmitted by the SIP server 54. 2 is distributed to routes 54 → 55 and routes 54 → 56, which are routes in which T (i) is smaller than EO (i).

Here, in the SIP server X, the total number of normal calls ΣNI (y) on the route where T (i) is smaller than EO (i) is the number of normal calls 4 on the route 54 → 55 and the normal calls on the route 54 → 56. It is the sum of Equation 4 and its value is 8.
Therefore, the generated error number estimation unit 303 calculates the number T ′ (54 → 55) of transfer errors distributed to the route 54 → 55 as 1 (= (20−18) × 4/8). The generated error number estimation unit 303 has a value 4 of the transfer error number T ′ (54 → 55) distributed to the route 54 → 55 to the value 4 of the transfer error number T (54 → 55) of the route 54 → 55. The value 5 obtained by adding 1 is newly set as the value of the number T (54 → 55) of transfer errors on the path 54 → 55.

  Similarly, the generated error number estimation unit 303 calculates the number T ′ (54 → 56) of transfer errors distributed to the route 54 → 56 as 1 (= (20−18) × 4/8). The generated error number estimation unit 303 has a transfer error number T ′ (54 → 56) value distributed to the route 54 → 56 to a value 4 of the transfer error number T (54 → 56) of the route 54 → 56. The value 5 obtained by adding 1 is newly set as the value of the number T (54 → 56) of transfer errors in the path 54 → 56.

  Subsequently, the generated error number estimation unit 303 subtracts 5 which is the transfer error number T (54 → 55) of the path 54 → 55 from 20 which is the error number EO (54 → 55) of the path 54 → 55, and Fifteen is calculated as the number of generated errors G (54 → 55) on the route 54 → 55.

  Further, the generated error number estimation unit 303 subtracts 5 which is the transfer error number T (54 → 56) of the route 54 → 56 from 20 which is the error number EO (54 → 56) of the route 54 → 56, and S Fifteen is calculated as the number of generated errors G (54 → 56) on the route 54 → 56.

  Further, the generated error number estimation unit 303 subtracts 10 which is the transfer error number T (54 → 57) of the route 54 → 57 from 10 which is the error number EO (54 → 57) of the route 54 → 57, and 0 is calculated as the number of generated errors G (54 → 57) from 54 → 57. That is, the occurrence error number estimation unit 303 determines that the occurrence error number G (54 → 57) of the route 54 → 57 does not exist.

<Specific example of the process for estimating the number of generated errors>
Next, the generated error number estimation process will be described using a specific example. The generated error number estimation unit 303 repeatedly performs the following processing for all SIP servers existing in the SIP signal network 100, respectively. First, the generated error number estimation unit 303 extracts statistical information related to the SIP server X, which is a certain SIP server in the SIP signal network 100, every predetermined unit time. Specifically, the generated error number estimation unit 303 extracts statistical information in which either the transmission side address or the reception side address is “X”. In that case, for example, the statistical information shown in FIG. 6 is extracted. Here, the unit time in which the statistical information being processed by the failure detection apparatus 300 is generated is referred to as the current time.

  FIG. 6 is an example of statistical information related to the SIP server X extracted by the generated error number estimation unit 303. FIG. 6A is an example of normal call statistical information in a predetermined unit time. In the figure, a set of a transmission side address, a reception side address, a called number band, and the number of calls (number of normal calls) is shown. For example, the first line of the figure shows that the sender address is “A”, the receiver address is “X”, the called party number band is “02”, and the number of calls is “120”. ing.

  FIG. 6B is an example of statistical information on errors in a predetermined unit time. In the figure, a set of a transmission side address, a reception side address, a called number band, an error number, and the number of errors is shown. For example, in the first line of the figure, the transmission side address is “X”, the reception side address is “A”, the called number band is “02”, the error number is “400”, and the number of errors is “ 21 ". The error number uniquely represents an internal server error, an incorrect request, an authentication failure, and the like.

  Subsequently, the generated error number estimation unit 303 extracts all the called number bands included in the statistical information related to the SIP server X. In the case of the example in FIG. 6, since three types “02”, “03”, and “04” are extracted as the called party number bands, the generated error number estimation unit 303 repeats the subsequent processing for all these called party number bands. For each. Here, the following processing will be described by taking the case where the called number band is “03” as an example.

The generated error number estimation unit 303 extracts the statistical information whose called number band is “03” from the statistical information related to the SIP server X (FIG. 6). In that case, the statistical information shown in FIG. 7 is extracted.
FIG. 7 shows the statistical information after the one with the called number band “03” is extracted from the statistical information of FIG. FIG. 7A is an example of statistical information of a normal call whose called number band is “03” in a predetermined unit time. In the figure, a set of a transmission side address, a reception side address, a called number band, and the number of calls (number of normal calls) is shown. For example, the first line in the figure shows that the sender address is “C”, the receiver address is “X”, the called party number band is “03”, and the number of calls is “300”. ing.

  FIG. 7B shows an example of statistical information of an error in which the called number band in a predetermined unit time is “03”. In the figure, a set of a transmission side address, a reception side address, a called number band, an error number, and the number of errors is shown. For example, in the first line of the figure, the transmission side address is “X”, the reception side address is “C”, the called number band is “03”, the error number is “400”, and the number of errors is “ 16 ".

  Subsequently, the generated error number estimation unit 303 extracts all error numbers included in the statistical information extracted above. In this example, since two types of error numbers “400” and “401” are extracted, the generated error number estimation unit 303 repeatedly performs the subsequent processing for all of these error numbers. Here, the following processing will be described by taking the case where the error number is “400” as an example.

The generated error number estimation unit 303 extracts statistical information whose error number is “400” from the statistical information extracted above (FIG. 7). In that case, the statistical information shown in FIG. 8 is extracted.
FIG. 8 shows statistical information after the error number “400” is extracted from the statistical information of FIG. FIG. 8A is an example of statistical information of a normal call with an error number “400” in a predetermined unit time. FIG. 8A is the same as FIG.

  FIG. 8B is an example of statistical information of an error whose error number is “400” in a predetermined unit time. In the figure, a set of a transmission side address, a reception side address, a called number band, an error number, and the number of errors is shown. For example, in the first line of the figure, the transmission side address is “X”, the reception side address is “C”, the called number band is “03”, the error number is “400”, and the number of errors is “ 16 ".

The generated error number estimation unit 303 estimates the number of generated errors for each path in the combination of the called number band “03” and the error number “400” in the SIP server X using the statistical information extracted as described above. To do.
In the example of FIG. 8, the SIP server X has received 35 errors from the SIP server A and has transmitted a total of 55 errors to the SIP server C, SIP server D, and SIP server E. The error number estimation unit 303 calculates the total number of transfer errors as 35 and the total number of generated errors as 20.

The generated error number estimation unit 303 estimates the number of generated errors for each path based on the above-described processing. First, the generated error number estimation unit 303 calculates the number of normal calls and errors in each route received by the SIP server X from the statistical information in FIG. 8 and the number of errors transmitted by the SIP server X to each route. Set.
Specifically, the generated error number estimation unit 303 sets the number of normal calls NI (C → X) of the route C → X to 300 and the normal call number of the route D → X from the statistical information of FIG. The number NI (D → X) is set to 240, and the number NI (E → X) of normal calls on the route E → X is set to 160. Further, the generated error number estimation unit 303 sets the error number EI (A → X) of the route A → X to 35 and the number EO (X → C) of the error of the route X → C from the statistical information of FIG. C) is set to 16, the error number EO (X → D) of the route X → D is set to 10, and the error number EO (X → E) of the route X → E is set to 29.

    The generated error number estimation unit 303 calculates the number of transfer errors for each path from these values using Equation (1) as follows. The generated error number estimation unit 303 sets 15 (= 35 × 300 / (300 + 240 + 160)) of transfer errors T (X → C) on the route X → C, and T (X → D) of transfer errors on the route X → D. ) Is calculated as 12 (= 35 × 240 / (300 + 240 + 160)), and the number T (X → E) of transfer errors on the route X → E is calculated as 8 (= 35 × 160 / (300 + 240 + 160)).

  Here, in the route X → D, the number T (X → D) of transfer errors in the route X → D is larger than the number of errors EO (X → D) in the route X → D. The unit 303 sets the number T (X → D) of transfer errors on the route X → D to 10. As a result, the total number of transfer errors ΣT (X) transmitted by the SIP server X becomes 33, and a difference 2 from the total number ΣEI (X) = 35 of the number of errors transmitted by the SIP server X occurs. The number estimation unit 303 distributes the difference 2 to the remaining routes.

  The generated error number estimation unit 303 calculates the number of transfer errors distributed for each path using the equation (2) as follows. Note that the calculation result here is rounded off to a whole number because a decimal point occurs. Specifically, the generated error number estimation unit 303 distributes the transfer error number T ′ (X → C) distributed to the route X → C to 1 (≈2 × 300 / (300 + 160)) and the route X → E. The transfer error number T ′ (X → E) to be calculated is calculated as 1 (≈2 × 160 / (300 + 160)).

  Thereby, the generated error number estimation unit 303 calculates the number of transfer errors for each path as follows. The generated error number estimation unit 303 sets the transfer error number T (X → C) of the route X → C to 16 (= 15 + 1) and the transfer error number T (X → E) of the route X → E to 9 (= 8 + 1). And calculate.

  Therefore, the generated error number estimation unit 303 calculates the number of generated errors for each path using Equation (3) as follows. The generated error number estimation unit 303 sets the generated error number G (X → C) of the route X → C to 0 (= 16-16) and the generated error number G (X → D) of the route X → D to 0 (= 10-10) and the number of occurrence errors G (X → E) of the route X → E is calculated as 20 (= 29−9).

<Specific example of failure detection processing>
The failure occurrence detection process will be described by taking as an example a case where the occurrence error shown in FIG. 9 is estimated by the occurrence error number estimation by the occurrence error number estimation unit 303.
FIG. 9 is an example of statistical information after the occurrence error is estimated. In the figure, a set of a transmission side address, a reception side address, a called number band, an error number, and the number of generated errors is shown. For example, in the first line of the figure, the transmission side address is “X”, the reception side address is “A”, the called number band is “02”, the error number is “400”, and the number of generated errors Is "20".

The failure occurrence detection unit 304 adds up the number of occurrence errors for each transmission address / error number combination in the estimated occurrence error. In the case of the example of FIG. 9, the totaled result is as shown in FIG.
FIG. 10 is a diagram showing the number of generated errors counted for each transmission address / error number combination in the example of FIG. In the figure, a set of a transmission side address, an error number, and the number of generated errors is shown. For example, the first line in the figure shows that the transmission side address is “X”, the error number is “400”, and the number of generated errors is “61”.

The failure occurrence detection unit 304 repeatedly performs the subsequent processing for all of these combinations of sender addresses / error numbers. Here, the following processing will be described by taking the case where the combination of the transmission side address / error number is “X” / “400” as an example.
The failure occurrence detection unit 304 acquires, from the statistical information storage unit 302, the average number of occurrence errors for a certain past period for each transmission address / error number combination. Then, the failure occurrence detection unit 304 calculates the ratio of the number of generated errors at the current time with respect to the average number of generated errors in the past certain period for each combination of the transmission side address / error number.

  FIG. 11 is an example of the average number of errors that have been stored in the statistical information storage unit 302 in the past certain period. In the figure, the average number of errors generated in a past fixed period is shown for each transmission address / error number combination. For example, the first line of the figure shows that the transmission side address is “X” and the error number is “400”, and the average number of errors generated in the past certain period is “8”.

Hereinafter, a case will be described as an example where the average number of errors generated in the past certain period for each combination of the sender address / error number acquired from the statistical information storage unit 302 shows the value shown in FIG.
For example, the failure occurrence detection unit 304 uses the number of errors generated in the first row in FIG. 10 and the average number of errors generated in the past certain period in the first row in FIG. For the occurrence error “X” / “400”, the ratio of the occurrence error number at the current time to the average occurrence error number in the past certain period of 7.625 (= 61/8) is calculated.

The failure occurrence detection unit 304 determines whether a failure has occurred for each “transmission side address” / error number combination based on the calculated ratio. Specifically, for example, the failure occurrence detection unit 304 determines that a failure has occurred when the calculated ratio is equal to or greater than a predetermined threshold. On the other hand, when the calculated ratio is less than a predetermined threshold, the failure occurrence detection unit 304 does not determine that a failure has occurred in the transmission address / error number combination.
Here, for example, when the threshold is 3.0, the occurrence error with the combination of the transmission side address / error number “X” / “400” is the ratio of the occurrence error number at the current time to the average occurrence error number in the past certain period. Since 7.625 exceeds the threshold value 3.0, the failure occurrence detection unit 304 determines that a failure has occurred.

Supplementing the other combinations in the above example, since the above-mentioned ratio is less than 3.0 for the error in which the combination of the transmission side address / error number is “A” / “400”, the failure occurrence detection unit 304 The combination of the transmission side address / error number (“A” / “400”) does not determine that a failure has occurred.
In addition, since the average of the past fixed period is 0 for the error in which the combination of the transmission side address / error number is “A” / “500”, the failure occurrence detection unit 304 cannot calculate the above-mentioned ratio (the ratio is + ∞). In this case, the failure occurrence detection unit 304 determines that a failure has occurred when the number of occurrence errors at the current time is equal to or greater than a predetermined number.

  Note that the failure occurrence detection unit 304 may determine that a failure has occurred uniformly when the average of the past certain period is zero.

  The failure occurrence detection unit 304 performs the same processing as described above by replacing the “transmission side address” in the above example with a “reception side address”. Specifically, the failure occurrence detection unit 304 calculates the ratio of the number of generated errors at the current time with respect to the average number of generated errors in a past fixed period for each “reception-side address” / error number combination. The failure occurrence detection unit 304 determines whether a failure has occurred for each “reception-side address” / error number combination based on the calculated ratio.

  The failure occurrence detection unit 304 determines a combination of all transmission side addresses / error numbers determined to have a failure, and all combinations of reception side address / error numbers determined to have a failure, to the failure location identification unit 305. Output to.

<Specific example of failure location identification processing>
Next, details of the failure location specifying process will be described using a specific example.
The failure location identifying unit 305 repeats the following processing by recognizing that a failure has been detected by the failure occurrence detection unit 304 and all combinations of sender addresses / error numbers determined to have failed by the failure occurrence detection unit 304. This is performed for each of the determined combinations of the receiving address / error number. Here, the subsequent processing will be described by taking the case where the transmission side address / error number is “X” / “400” as an example.
First, the failure location identifying unit 305 generates an error for each combination of “transmission side address” and “error number” determined to have occurred, or “reception side address” and “error number” determined to have occurred. Count the number for each route.

  FIG. 12 is an example of the number of generated errors after being divided for each path from the statistical information. In the figure, a set of a transmission side address, a reception side address, an error number, and the number of generated errors is shown. For example, the first line in the figure shows that the transmission side address is “X”, the reception side address is “A”, the error number is “400”, and the number of generated errors is “20”. ing.

  Subsequently, the failure location identifying unit 305 transmits the number of paths that transmit (or receive) the occurrence error for the specific error number and the number of transmissions (or the number of receptions) for each path of the generated error for the specific error number. Based on the above, the fault location is identified. Specifically, for example, the failure location specifying unit 305 calculates the number of paths in which the total number of generated errors is equal to or greater than a predetermined error threshold. For example, when the occurrence error threshold is 10, the number of routes is three routes of route X → A, route X → B, and route X → E.

  Note that the occurrence error threshold may be determined based on a ratio to the total number of errors that a certain server X transmits in a predetermined unit time. Specifically, for example, in the example of FIG. 12, the total number of generated errors in the combination of the transmission side address X and the error number 400 is 61, but the generated error threshold is 10 of the total number of generated errors. 6 which is% may be sufficient.

  When the calculated number of routes is greater than or equal to a predetermined route threshold, the failure location specifying unit 305 specifies the SIP server having the transmission side address as the failure location of the server type error. For example, when the above-described route threshold is 3, the failure location identifying unit 305 identifies the SIP server having the transmission side address “X” as the failure location of the server type error related to the error number “400”. On the other hand, if the calculated number of routes is less than a predetermined route threshold, the failure location specifying unit 305 does not specify the SIP server having the transmission side address as the failure location of the server type error.

  In addition to setting a uniform error threshold value for the entire system, the error error threshold value may be set individually for each SIP server or error number. Thereby, the fault location specifying unit 305 can flexibly specify the fault location even when the characteristics of the number of error occurrences are different.

  The fault location identifying unit 305 performs the same processing by replacing “transmission side address” in the above example with “reception side address”. However, the failure location detected by the failure location specifying unit 305 at this time is a failure location of a client type error. Specifically, if the calculated number of routes is greater than or equal to a predetermined route threshold, the failure location specifying unit 305 specifies the SIP server having the receiving address as the failure location of the client type error. On the other hand, if the calculated number of routes is less than a predetermined route threshold, the failure location identifying unit 305 does not identify the SIP server having the receiving address as the failure location of the client type error.

  In this embodiment, the failure location identifying unit 305 generates the number of errors for each combination of “transmission side address” and “error number” or combination of “reception side address” and “error number” detected as a failure occurrence. However, it is not limited to this. The failure location specifying unit 305 may divide the number of generated errors for each path for each “transmission side address” or “reception side address” detected as the occurrence of a failure.

  In other words, the fault location specified by the fault location specifying unit 305 is an error that occurs in the transmitting server in which the fault occurrence is detected by the fault occurrence detection unit 304 or in the receiving server in which the fault occurrence is detected by the fault occurrence detection unit 304. The number may be divided for each route, and may be performed based on the number of generated errors divided for each route.

In the present embodiment, the failure location identifying unit 305 identifies the failure location based on the number of paths in which the total number of generated errors is greater than or equal to a predetermined occurrence error threshold. However, the present invention is not limited to this. Absent.
The failure location identifying unit 305 includes a transmission server in which a failure occurrence is detected by the failure occurrence detection unit 304, a path including an occurrence error transmitted by the transmission side server, or a failure occurrence detected by the failure occurrence detection unit 304. What is necessary is just to identify a failure location based on the path | route containing the generation | occurrence | production error which the receiving server receives and this receiving server.

  FIG. 13 is a flowchart showing the overall processing flow of the failure detection apparatus 300 in the present embodiment. The failure detection apparatus 300 repeats the following processing every predetermined unit time (step S101). First, the statistical information receiving unit 301 receives statistical information (step S102). Next, the generated error number estimation unit 303 estimates the number of generated errors (step S103). Next, the failure occurrence detection unit 304 detects the failure occurrence (step S104). Next, the fault location identifying unit 305 identifies the fault location (step S105). Above, the process of this flowchart is complete | finished.

  FIG. 14 is a flowchart showing details of processing of the generated error number estimation unit 303 in step S103 of FIG. The generated error number estimation unit 303 performs the processing from step S302 to step S307 for all SIP servers (step S301). First, the generated error number estimation unit 303 extracts information related to the currently targeted SIP server from the statistical information (step S302).

  The generated error number estimation unit 303 performs the processes from step S304 to step S307 on the “numbered number band” included in the statistical information for the statistical information extracted in step S302 (step S303). The generated error number estimation unit 303 extracts the currently included “incoming number band” from the extracted statistical information (step S304).

  Next, the generated error number estimation unit 303 performs the following processing on all the “error numbers” included in the statistical information with respect to the statistical information extracted in step S304 (step S305). First, the generated error number estimation unit 303 extracts the “error number” including the “error number” that is the current target from the extracted statistical information (step S306). Next, the generated error number estimation unit 303 is a process of estimating the number of generated errors for each route in the combination of the “arrival number band” and the “error number” that are currently targeted in the currently targeted SIP server. Is performed (step S307). The generated error number estimation unit 303 terminates the generated error number estimation process in step S103 of FIG. 13 when the above process is performed for all the SIP servers with all combinations of the “numbered number” and “error number”. To do.

  FIG. 15 is a flowchart showing details of the processing of the failure occurrence detection unit 304 in step S104 of FIG. The failure occurrence detection unit 304 counts the number of occurrence errors for each combination of “transmission side address” and “error number” of occurrence errors (step S401). Next, the failure occurrence detection unit 304 performs the processing from step S403 to step S405 on the combinations of “transmission side address” and “error number” of all occurrence errors (step S402).

  The failure occurrence detection unit 304 calculates the ratio of the number of generated errors at the current time to the average number of generated errors during a past fixed period (step S403). Next, the failure occurrence detection unit 304 determines whether or not the calculated ratio is greater than or equal to a threshold value (step S404). If the ratio is greater than or equal to the threshold (YES in step S404), the failure occurrence detection unit 304 determines that a failure has occurred (step S405). Then, when there is a next “transmission side address” and “error number” combination, the failure occurrence detection unit 304 returns to the process of step S403.

  On the other hand, when the ratio is less than the threshold (NO in step S404), the failure occurrence detection unit 304 returns to the process of step S403 when there is a next combination of “transmission side address” and “error number”. The failure occurrence detection unit 304 proceeds to the process of step S406 when the process from step S403 to step S405 is performed on the combinations of “transmission side address” and “error number” of all occurrence errors.

  Next, the failure occurrence detection unit 304 counts the number of occurrence errors for each combination of the “reception side address” and “error number” of the occurrence error (step S406). Next, the failure occurrence detection unit 304 performs the processing from step S408 to step S410 on the combinations of “reception side address” and “error number” of all occurrence errors (step S407). The failure occurrence detection unit 304 calculates the ratio of the number of generated errors at the current time to the average number of errors generated in a certain past period (step S408).

  Next, the failure occurrence detection unit 304 determines whether or not the calculated ratio is greater than or equal to a threshold value (step S409). If the ratio is greater than or equal to the threshold (YES in step S409), the failure occurrence detection unit 304 determines that a failure has occurred (step S410). Then, when there is a next combination of “reception side address” and “error number”, the failure occurrence detection unit 304 proceeds to the process of step S408.

  On the other hand, when the ratio is less than the threshold (NO in step S409), the failure occurrence detection unit 304 proceeds to the process of step S408 if there is a next combination of “reception side address” and “error number”. When the failure occurrence detection unit 304 performs the processing from step S408 to step S410 on the combinations of “reception side address” and “error number” of all occurrence errors, the failure occurrence detection unit in step S104 of FIG. The process 304 is terminated.

  FIG. 16 is a flowchart showing details of the processing of the fault location identifying unit 305 in step S105 of FIG. First, the failure location identification unit 305 performs the processing from step S502 to step S505 for all combinations of “transmission side address” and “error number” determined to have failed (step S501). First, the failure location specifying unit 305 calculates the number of generated errors for each route (step S502).

  Next, the failure location identifying unit 305 calculates the number of paths in which the total number of generated errors is equal to or greater than a predetermined error threshold (step S503). Next, the failure location identifying unit 305 determines whether or not the calculated number of routes is greater than or equal to a predetermined route threshold value (step S504). When the number of routes is equal to or greater than the route threshold (YES in step S504), the failure location specifying unit 305 specifies the SIP server having the transmission side address as the failure location of the server type error (step S505). Then, when there is a next combination of “transmission side address” and “error number”, the fault location identifying unit 305 returns to the process of step S502.

  On the other hand, if the number of routes is less than the route threshold value (NO in step S504), the failure location identifying unit 305 returns to the process of step S502 if there is a next combination of “transmission side address” and “error number”. When the processing from step S502 to step S505 is performed on the combinations of “transmission side address” and “error number” of all occurrence errors, the failure location specifying unit 305 proceeds to the processing of step S506.

  Next, the failure location identification unit 305 performs the processing from step S507 to step S510 for all combinations of “reception side address” and “error number” determined to have failed (step S506). . First, the failure location specifying unit 305 calculates the number of generated errors for each route (step S507).

  Next, the failure location specifying unit 305 calculates the number of paths where the total number of generated errors is equal to or greater than a predetermined error threshold (step S508). Next, the fault location identifying unit 305 determines whether or not the calculated number of routes is greater than or equal to a predetermined route threshold value (step S509). If the number of routes is equal to or greater than the route threshold (YES in step S509), the failure location identifying unit 305 identifies the SIP server having the receiving address as the failure location of the client type error (step S510). Then, when there is a next combination of “reception side address” and “error number”, the fault location identifying unit 305 returns to the process of step S507.

  On the other hand, if the number of routes is less than the route threshold (NO in step S509), if there is a next combination of “reception side address” and “error number”, the process returns to step S507. If the processing from step S507 to step S510 is performed on the combination of “reception side address” and “error number” of all occurrence errors, the failure location specifying unit 305 performs the failure location specifying unit in step S105 of FIG. The process of 305 ends.

<Effect>
As described above, since the failure detection apparatus 300 according to the present embodiment detects a failure in the SIP signal network using the statistical information, it is possible to monitor the large-scale network in real time while reducing the amount of data to be analyzed.
In addition, since the failure detection apparatus 300 according to the present embodiment excludes personal information from data to be analyzed and detects a failure based only on statistical information, it can be safely operated in terms of security.

The failure detection apparatus 300 according to the present embodiment performs a combination of a sender address / error number pair determined to have a failure and a receiver address / error number pair determined to have a failure. Aggregate the number of errors that occurred. That is, the failure detection apparatus 300 separates transmission and reception, and totals the number of generated errors for each error number and for each path. Then, the failure detection apparatus 300 determines whether a certain SIP server is a server type error based on the number of routes in which a certain SIP server transmits an error in which a specific error number is generated exceeds a predetermined threshold. Judge whether or not. Further, in the failure detection apparatus 300, a certain SIP server is a client-type error based on the number of routes in which a certain SIP server has received a specific error number occurrence error exceeds a predetermined threshold. It is determined whether or not.
Thereby, the failure detection apparatus 300 not only detects the SIP server in which an error has occurred, but also identifies the failure location by classifying the failure location of the server type error or the failure location of the client type error. it can.

In addition, the failure detection apparatus 300 according to the present embodiment estimates the number of generated errors for each route for each combination of “destination number band” and “error number” with respect to the statistical information. It is determined whether a failure has occurred for each combination of “side address” and “error number” or each combination of “reception side address” and “error number”.
Therefore, even when there are various characteristics of the number of generated errors depending on the SIP server, error number, etc., the failure detection apparatus 300 can detect the occurrence of the failure with high accuracy.

Further, the failure detection apparatus 300 according to the present embodiment is a combination of “transmission side address” and “error number” determined to have failed, or “reception side address” and “error number” determined to have failed. The number of generated errors for each combination is divided for each route, and the fault location is specified based on the number of generated errors.
Therefore, even when there are various characteristics of the number of generated errors depending on the SIP server, error number, etc., the failure detection device 300 can specify the failure location with high accuracy.

  Further, the failure detection apparatus 300 according to the present embodiment can be realized using only an in-service call in actual operation due to the characteristics of the failure detection method and the failure location specifying method. And the like need not be separately sent to the SIP signal network, and the provision of the existing service is not affected.

  Note that the detection of the failure occurrence by the failure occurrence detection unit 304 of the present embodiment is performed based on the ratio of the number of generated errors at the current time to the average number of errors generated in a certain period in the past. This may be performed by comparing the number of generated errors with the number of past generated errors.

  In the failure detection apparatus 300 of the present embodiment, the number of past occurrence errors is stored in the statistical information storage unit 302. However, the present invention is not limited to this, and the number of past occurrence errors is stored in an external database (not shown). May be. In that case, the failure occurrence detection unit 304 may read the number of past occurrence errors from an external database. That is, the failure occurrence detection unit 304 may acquire the number of past occurrence errors from the statistical information storage unit 302 or an external database (not shown).

  The failure occurrence detection unit 304 detects the occurrence of the failure by counting the number of occurrence errors at the current time for each combination of the transmission address and error number of the occurrence error or for each combination of the reception address and error number of the occurrence error. However, although it was performed by comparing the total number of generated errors with the corresponding number of past generated errors, it is not limited to such totaling.

The failure occurrence detection unit 304 detects the occurrence of a failure by counting the number of errors generated at the current time for each error number of the generated error, and calculating the number of generated errors for each error number in the past for each error number. It may be done by comparing with a number. In that case, the failure occurrence detection unit 304 may acquire the number of past occurrence errors for each error number.
According to this, even when the number of generated errors in which error numbers are mixed does not change with time, the failure occurrence detection unit 304 can detect the occurrence of a failure by counting the number of generated errors for each error number. .

In addition, the failure occurrence detection unit 304 detects the occurrence of a failure by adding up the number of generated errors at the current time for each incoming number of the generated errors, and calculating the number of generated errors for each of the received incoming numbers for each corresponding incoming number. It may be performed by comparing with the number of generated errors. In that case, the failure occurrence detection unit 304 may acquire the number of past occurrence errors for each called number.
According to this, the failure occurrence detection unit 304 can detect the occurrence of a failure by counting the number of occurrence errors for each called number even when the number of generated errors in which the called numbers are mixed does not change with time. .

That is, the detection of the failure occurrence by the failure occurrence detection unit 304 is performed for each item related to the occurrence error (for example, the transmission side address, the reception side address, the error number, the called number, and a combination of two or more thereof). This may be performed by counting the number of generated errors and comparing the total number of generated errors for each item with the number of past generated errors for each corresponding item. In that case, the failure occurrence detection unit 304 may acquire the number of past occurrence errors for each item related to the occurrence error.
Accordingly, the failure occurrence detection unit 304 can detect the occurrence of a failure by counting the number of occurrence errors for each item even when the number of occurrence errors in which the items are mixed does not change with time.

  In the present embodiment, the failure location identifying unit 305 transmits the number of paths that have transmitted (or received) the occurrence error for the specific error number and the number of transmissions of the generated error for each path of the specific error number ( Or, the location of the failure is specified based on the received number), but is not limited thereto. The failure location identifying unit 305 transmits the number of paths for which error occurrences for all error numbers are transmitted (or received), and the number of transmissions for each path of occurrence errors for all error numbers (not for each specific error number). Alternatively, the failure location may be specified based on the received number).

  In addition, the failure location specifying unit 305 is not based on the number of transmission (or reception) paths of occurrence errors and the number of transmissions (or receptions) for each path, but only on the number of paths that transmit (or receive) occurrence errors. The fault location may be specified. Specifically, for example, the failure location specifying unit 305 determines in advance that the number of paths that transmit (or receive) an error with respect to a specific error number or all error numbers among paths that a certain SIP server X has is in advance. If the threshold is equal to or greater than the predetermined threshold, the SIP server may be specified as a failure location of the server type error (or client type error).

  Further, a program for executing each process of the failure detection apparatus 300 of the present embodiment is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed. The various processes described above related to the failure detection apparatus 300 may be performed.

  Here, the “computer system” may include an OS and hardware such as peripheral devices. Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used. The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

  Further, the “computer-readable recording medium” refers to a volatile memory (for example, DRAM (Dynamic) in a computer system serving as a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. Random Access Memory)) that holds a program for a certain period of time is also included. The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

  As mentioned above, although embodiment of this invention was explained in full detail with reference to drawings, the concrete structure is not restricted to this embodiment, The design etc. of the range which does not deviate from the summary of this invention are included.

DESCRIPTION OF SYMBOLS 1 Failure location detection system 100 SIP signal network 200 SIP signal collection device 300 Failure detection device 301 Statistical information receiving part 302 Statistical information storage part 303 Occurrence error number estimation part 304 Failure occurrence detection part 305 Fault location identification part

Claims (6)

Based on the statistical information related to the communication of the SIP signal, based on the number of errors received and transmitted by a certain SIP server for each path and the number of normal calls received by the SIP server for each path, the SIP server The number of transfer errors transmitted for each path is calculated, and the number of generated errors transmitted by the SIP server is estimated for each path based on the calculated number of transfer errors and the number of errors transmitted by the SIP server for each path. A generation error number estimation unit that estimates the number of generation errors for each path between SIP servers,
Based on the number of paths that are transmitting or receiving the estimated occurrence error, a failure location identifying unit that identifies a failure location,
A failure detection apparatus comprising: The failure point identification unit, based on the number of transmissions or reception number for each route path number and emitting raw error that is sending or receiving the generation error, claim 1, wherein the identifying a failure location fault detection apparatus according to. On the basis of the occurrence number of errors for each estimated path failure detecting apparatus according to claim 1 or claim 2, further comprising a failure detector for detecting a failure in the SIP signaling network. The failure occurrence detection unit obtains the number of past occurrence errors for each item related to the occurrence error,
In the detection of the occurrence of a failure by the failure occurrence detection unit, the number of generated errors at the current time is totaled for each item, and the total number of generated errors for each item is compared with the corresponding number of past generated errors for each item. The fault detection apparatus according to claim 3 , wherein the fault detection apparatus is performed. A failure detection method executed by a failure detection apparatus,
Based on the statistical information related to the communication of the SIP signal, based on the number of errors received and transmitted by a certain SIP server for each path and the number of normal calls received by the SIP server for each path, the SIP server The number of transfer errors transmitted for each path is calculated, and the number of generated errors transmitted by the SIP server is estimated for each path based on the calculated number of transfer errors and the number of errors transmitted by the SIP server for each path. A generation error number estimation procedure for estimating the number of generation errors for each path between SIP servers,
A failure occurrence detection procedure for detecting a failure occurrence in the SIP signal network based on the estimated number of occurrence errors for each path;
A failure detection method comprising: On the computer,
Based on the statistical information related to the communication of the SIP signal, based on the number of errors received and transmitted by a certain SIP server for each path and the number of normal calls received by the SIP server for each path, the SIP server The number of transfer errors transmitted for each path is calculated, and the number of generated errors transmitted by the SIP server is estimated for each path based on the calculated number of transfer errors and the number of errors transmitted by the SIP server for each path. and generating an error number estimation step of estimating the number of occurrences errors for each path between SIP servers by,
A failure occurrence detection step of detecting a failure occurrence in the SIP signaling network based on the estimated number of occurrence errors for each path;
A fault detection program characterized by causing

Images