A network fault analysis method based on RESET message

Abstract

A method for analyzing network failures based on RESET messages, including: when a base station has a failure alarm, the core network analyzes the type of failure that occurs in the base station, and forwards the failure type to the ACS, and the ACS determines whether the failure alarm that occurs in the base station is a false alarm or a real alarm and feeds back the judgment information to a historical database; when a core network has a failure alarm, the base station analyzes the type of failure that occurs in the core network, and forwards the failure type to the ACS, and the ACS determines whether the failure alarm that occurs in the core network is a false alarm or a real alarm and feeds back the judgment information to a historical database; the database regularly analyzes the probability of subsequent base stations and core networks having false alarms based on the collected information. Through the above scheme, possible false alarms of base stations or core networks can be discovered in a timely manner and handled in a timely manner.

Description

Technical Field

[0001] The present invention relates to the technical field of fault analysis, and in particular to a method for analyzing network faults based on RESET messages. Background Art

[0002] Operators that develop 5G technology to support 4G terminals, realize the early use of 5G, and promote the research and practice of transition solutions from 4G to 5G have a first-mover advantage. They are also the first to carry out innovative research on "4G and 5G interoperability based on application perception" in 3GPP, giving full play to the advantages of 5G technology and making rational use of existing 4G investments. And through the core network interoperability solution, the synergy of 4G and 5G networks is achieved. Therefore, operators have a leading and pioneering role in this technology.

[0003] Fault alarms often occur between the core network and the base station. What is needed now is how to determine whether the fault alarm is a false alarm or a real alarm, and how to collect this data to calculate the possible subsequent false alarms of related equipment. Summary of the invention

[0004] The present invention aims at the deficiencies in the prior art and provides a method for analyzing network failures based on RESET messages.

[0005] To achieve the above object, the present invention adopts the following technical solutions:

[0006] A method for analyzing network failure based on a RESET message, comprising:

[0007] When a base station fault alarm occurs, the core network analyzes the fault type of the base station and forwards the fault type to the ACS, which determines whether the fault alarm of the base station is a false alarm or a real alarm and feeds the judgment information back to the history database;

[0008] When a fault alarm occurs in the core network, the base station analyzes the fault type of the core network and forwards the fault type to the ACS. The ACS determines whether the fault alarm of the core network is a false alarm or a real alarm and feeds the judgment information back to the history database;

[0009] The database regularly analyzes the probability of false alarms in subsequent base stations and core networks based on the collected information.

[0010] To optimize the above technical solutions, the specific measures taken also include:

[0011] Furthermore, when a fault alarm occurs in the base station, the core network analyzes the fault type of the base station and forwards the fault type to the ACS, and the ACS determines whether the fault alarm of the base station is a false alarm or a real alarm and feeds back the judgment information to the history database. The specific contents are:

[0012] When a fault alarm occurs in a base station, the base station sends a RESET message carrying its own fault alarm identifier to the core network. The core network obtains the fault alarm identifier in the RESET message and uses it as a query condition to obtain the fault type corresponding to the fault alarm identifier from the alarm database, and then forwards it to the ACS.

[0013] The ACS packages the data information of the fault type into a configuration file request and sends it to the base station; the base station parses the configuration file request and obtains the real-time monitoring indicator data of the corresponding fault type, and then forwards it to the ACS; the ACS compares the real-time monitoring indicator data with the indicators in the threshold database to determine whether the fault occurring in the base station is a false alarm or a real alarm, and feeds back the judgment result to the historical database.

[0014] Furthermore, when a fault alarm occurs in the core network, the base station analyzes the fault type of the core network and forwards the fault type to the ACS, and the ACS determines whether the fault alarm in the core network is a false alarm or a real alarm and feeds back the judgment information to the history database. The specific contents are:

[0015] When a fault alarm occurs in the core network, the core network sends a RESET message carrying its own fault alarm identifier to the base station. The base station obtains the fault alarm identifier in the RESET message and uses it as a query condition to obtain the fault type corresponding to the fault alarm identifier from the alarm database, and then forwards it to the ACS.

[0016] ACS packages the data information of the fault type into a configuration file request and sends it to the core network; the core network parses the configuration file request and obtains the real-time monitoring indicator data of the corresponding fault type, and then forwards it to the ACS; ACS compares the real-time monitoring indicator data with the indicators in the threshold database to determine whether the fault occurring in the core network is a false alarm or a real alarm, and feeds back the judgment result to the historical database.

[0017] Furthermore, the database periodically analyzes the probability of false alarms in subsequent base stations and core networks based on the collected information, and the specific contents are:

[0018] The historical database is analyzed to obtain the probability a of a false alarm occurring in the base station or core network in the previous period, the probability b of a true alarm occurring, the probability c of a false alarm occurring and being transferred to a true alarm in the next period, the probability d of a false alarm occurring and being transferred to a false alarm in the next period, the probability e of a true alarm occurring and being transferred to a false alarm in the next period, and the probability f of a true alarm occurring and being transferred to a true alarm in the next period; where a+b=1, c+d=1, e+f=1;

[0019] Calculate the probability of a false alarm in the base station or core network in the next period g = a*d+b*e.

[0020] The beneficial effects of the present invention are:

[0021] 1. When an alarm occurs in a base station, the core network will check the fault type and use the ACS to determine whether it is a false alarm or a real alarm. The historical database will analyze the possibility of subsequent false alarms in related equipment, and then improve the related equipment in a timely manner.

[0022] 2. When an alarm occurs in the core network, the base station will check the fault type and use the ACS to determine whether it is a false alarm or a real alarm. The historical database will analyze the possibility of subsequent false alarms in related equipment, and then improve the related equipment in a timely manner.

[0023] 3. The probability of false alarms in subsequent base stations or core networks is calculated through the database, so that relevant equipment can be improved in advance to achieve a preventive effect.

[0024] 4. Through the cooperation between the base station and the core network, related fault types can be checked on each other to maximize resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 It is a schematic diagram of calculating the probability of false alarm occurring in the next period in an embodiment of the present invention. DETAILED DESCRIPTION

[0026] The present invention will now be described in further detail with reference to the accompanying drawings.

[0027] The present invention belongs to a network communication environment, and mainly includes: in a 5G network, when a network failure occurs between a core network and a base station, the faulty party will actively initiate a RESET message carrying its own identification to notify the other end. The fault type corresponding to the fault is obtained from the real-time alarm database through the core network or base station identification in the RESET message as a query condition. And report it to the ACS. The ACS receives the fault type identification and collects real-time monitoring index values ​​from the faulty core network or base station through the TR069 protocol. And compare the fault type trigger threshold with the threshold database to realize the implementation process of secondary confirmation of the fault through TR069 after the fault occurs. This method can greatly reduce the false alarms caused by threshold setting sensitive alarms and network jitter when a fault occurs between the base station and the core network, and improve the 5G network operation and maintenance guarantee capability.

[0028] Step 1: When a network failure occurs between the core network and the base station in the 5G network, the faulty party will actively initiate a RESET message with its own identifier to notify the other end. The core network or base station identifier in the RESET message is used as a query condition to obtain the fault type corresponding to the fault from the real-time alarm database and report it to the ACS.

[0029] Step 2: The ACS and CPE (the core network and base station in this patent are referred to as CPE) interoperate through the RPC method unique to the TR069 protocol to complete the secondary active monitoring fault confirmation process for the CPE.

[0030] Specific description: First, after receiving the fault type identifier, the ACS initiates a TR069 protocol-compliant call to the faulty core network or base station (referred to as: faulty CPE) through the TR069 protocol. <rpc>After the CPE parses the configuration file to obtain the fault type request message, it sends it to the ACS again. The ACS parses the configuration file to obtain the real-time monitoring indicator value of the fault type of the CPE. The value is compared with the trigger threshold of the fault type in the threshold database. If it is greater than the threshold, it is a real alarm, otherwise it is a false alarm. The secondary confirmation data of the fault is stored in the historical fault database.

[0031] Step 3: Reference Figure 1 . The database regularly calculates the collected data. Taking the situation of the base station as an example, the historical database analyzes and obtains the probability a of a false alarm in the base station or core network in the previous period, the probability b of a real alarm, the probability c of a false alarm being transferred to a real alarm in the next period, the probability d of a false alarm being transferred to a false alarm in the next period, the probability e of a real alarm being transferred to a false alarm in the next period, and the probability f of a real alarm being transferred to a real alarm in the next period; among which a+b=1, c+d=1, e+f=1;

[0032] Calculate the probability of a false alarm in the base station or core network in the next period g = a*d+b*e.

[0033] The probability a of a false alarm occurring in the previous period is calculated as follows: the database obtains the number of false alarms occurring in the previous period, and divides the number by the total number of alarms in the previous period to obtain the probability a.

[0034] The probability b of a real alarm occurring in the previous period is calculated as follows: the database obtains the number of real alarms occurring in the previous period, and divides the number by the total number of alarms in the previous period to obtain the probability b.

[0035] Among them, the probability a of a false alarm occurring in the previous period that will be transferred to a true alarm in the next period (the transfer probability of the next period) is calculated as follows: the total false alarm rate x (total number of false alarms / total number of alarms) in history (previous period and previous periods) is obtained through the historical database; the false alarm probability a in the previous period (number of false alarms in the previous period / total number of alarms in the previous period) is obtained through the historical database; the probability c of a false alarm occurring in the previous period that will be transferred to a true alarm in the next period is calculated, c=s+(xa); wherein s is the threshold value, and since c+d=1, d can be obtained.

[0036] For example, the total historical false alarm rate x = 30% = 0.3, the false alarm rate a = 28% = 0.28 in the previous period, which means that 2% = 0.02 of the transfers are real alarms. The transfer probability c = 22% = 0.22 in the next period is obtained by adding 2% of the transfers (threshold s), and further d = 1-22% = 0.78. The threshold s is set in advance, and a specific threshold is selected for the real transfer difference in different intervals (the difference in this example is 2%) to ensure that the transfer probability is less than 1 and greater than 0.

[0037] Among them, the probability e of the probability b of a real alarm occurring in the previous period turning into a false alarm in the next period (the transition probability of the next period) is calculated as follows: the total real alarm rate x' (total number of real alarms / total number of alarms) in history (previous period and previous periods) is obtained through the historical database; the probability b of the real alarm in the previous period (number of real alarms in the previous period / total number of alarms in the previous period) is obtained through the historical database; the probability e of the probability b of a real alarm occurring in the previous period turning into a false alarm in the next period is calculated, e=s'+(x'-b); wherein, s' is the threshold value, and since e+f=1, f can be obtained.

[0038] For example, the total historical true alarm rate x'=70%=0.7, the previous period true alarm rate b=72%=0.72, which means that 2%=0.02 of the transfers are false alarms. The transfer of 2%+30% (threshold s') is used to obtain the transfer probability e=32%=0.32 in the next period, and further f=1-32%=0.68. The threshold s' is set in advance, and a specific threshold is selected for the transfer difference in different intervals (the difference in this example is 2%) to ensure that the transfer probability is less than 1 and greater than 0.

[0039] In summary, in the next period, the false alarm probability of the base station is g=0.28*0.78+0.72*0.32=0.4488. This probability may not exceed the red line of 60%, and manual repair and improvement of the base station is not necessary for the time being.

[0040] This application adopts the idea of ​​Markov chain algorithm. The Markov transfer matrix method model formula is: X(k+1)=X(k)×P; X(k) represents the state vector of the trend analysis and prediction object at time t=k, P represents the one-step transfer probability matrix, and X(k+1) represents the state vector of the trend analysis and prediction object at time t=k+1.

[0041] This application is mainly to calculate the probability g of false alarm in the next period, because a true alarm indicates that the entire system is operating normally and there is no problem with the alarm. If the probability of false alarm is high, it means that the relevant equipment (base station or core network) is aging or has other problems and needs to be replaced or repaired in time.

[0042] It should be noted that the terms such as "upper", "lower", "left", "right", "front", "back", etc. cited in the invention are only for the convenience of description and are not used to limit the scope of implementation of the present invention. Changes or adjustments in their relative relationships should be regarded as the scope of implementation of the present invention without substantially changing the technical content.

[0043] The above are only preferred embodiments of the present invention, and the protection scope of the present invention is not limited to the above embodiments. All technical solutions under the concept of the present invention belong to the protection scope of the present invention. It should be pointed out that for ordinary technicians in this technical field, some improvements and modifications without departing from the principle of the present invention should be regarded as the protection scope of the present invention.< / rpc>

Claims

1. A method for analyzing network failure based on RESET message, characterized in that: include: When a base station fault alarm occurs, the core network analyzes the fault type of the base station and forwards the fault type to the ACS, which determines whether the fault alarm of the base station is a false alarm or a real alarm and feeds the judgment information back to the history database; When a fault alarm occurs in the core network, the base station analyzes the fault type of the core network and forwards the fault type to the ACS. The ACS determines whether the fault alarm of the core network is a false alarm or a real alarm and feeds the judgment information back to the history database; The database regularly analyzes the probability of false alarms in subsequent base stations and core networks based on the collected information, including: The historical database is analyzed to obtain the probability a of a false alarm occurring in the base station or core network in the previous period, the probability b of a true alarm occurring, the probability c of a false alarm occurring and being converted to a true alarm in the next period, the probability d of a false alarm occurring and being converted to a false alarm in the next period, the probability e of a true alarm occurring and being converted to a false alarm in the next period, and the probability f of a true alarm occurring and being converted to a true alarm in the next period; where a+b=1, c+d=1, e+f=1; Calculate the probability of false alarm in the base station or core network in the next period g=a*d+b*e.

2. A method for analyzing network failure based on RESET message according to claim 1, characterized in that: When a fault alarm occurs in the base station, the core network analyzes the fault type of the base station and forwards the fault type to the ACS, and the ACS determines whether the fault alarm of the base station is a false alarm or a real alarm and feeds back the judgment information to the history database. The specific content is as follows: when a fault alarm occurs in the base station, the base station initiates a RESET message carrying its own fault alarm identifier to the core network, the core network obtains the fault alarm identifier in the RESET message, and uses this as a query condition to obtain the fault type corresponding to the fault alarm identifier from the alarm database, and then forwards it to the ACS; The ACS packages the data information of the fault type into a configuration file request and sends it to the base station; the base station parses the configuration file request and obtains the real-time monitoring indicator data of the corresponding fault type, and then forwards it to the ACS; the ACS compares the real-time monitoring indicator data with the indicators in the threshold database to determine whether the fault occurring in the base station is a false alarm or a real alarm, and feeds back the judgment result to the historical database.

3. A method for analyzing network failure based on RESET message according to claim 1, characterized in that: When a fault alarm occurs in the core network, the base station analyzes the fault type of the core network and forwards the fault type to the ACS, and the ACS determines whether the fault alarm of the core network is a false alarm or a real alarm and feeds back the judgment information to the history database. The specific content is as follows: when a fault alarm occurs in the core network, the core network initiates a RESET message carrying its own fault alarm identifier to the base station, and the base station obtains the fault alarm identifier in the RESET message, and uses it as a query condition to obtain the fault type corresponding to the fault alarm identifier from the alarm database, and then forwards it to the ACS; The ACS packages the data information of the fault type into a configuration file request and sends it to the core network; The core network parses the configuration file request and obtains the real-time monitoring indicator data of the corresponding fault type, and then forwards it to the ACS; the ACS compares the real-time monitoring indicator data with the indicators in the threshold database to determine whether the fault occurring in the core network is a false alarm or a real alarm, and feeds the judgment result back to the historical database.

Images