Call exception analysis method and device, call exception prevention method and device

Abstract

The embodiment of the invention discloses a nethod for analysing abnormal call, at first, according to the call historical record (CHR) data, the method ascertains the cell of the user when the abnormal call happens; then processes the alarm analysis for the alarm data which is generated by an interface allocation object of the base station in the adjacent time sections or abnormal call happens, positions the reason of abnormal call. The embodiment of the invention discloses a abnormal call analysing device, two methods of preventing the abnormal call and two devices thereof. The invention can improve analysis efficiency of analysing abnormal call.

Description

technical field [0001] The invention relates to a call processing technology in wireless communication, in particular to a method for analyzing abnormal calls, a device for analyzing abnormal calls, a method for preventing abnormal calls and a device for preventing abnormal calls. Background technique [0002] Mobile network users will complain to the operator when encountering abnormal situations such as call drop or access failure during the use of mobile services. In order to improve the service quality, operators always respond to users' complaints in the first time, inform users of the reasons for abnormalities, and solve problems existing in the network according to the reasons, so as to avoid abnormalities from occurring again. In the prior art, there is a technical solution for abnormal call analysis based on call history records (CHR), which roughly includes the following steps: [0003] Step 1: Record the terminal number of the complaining user, the time when the ...

AI Technical Summary

Problems solved by technology

[0010] 1. The above-mentioned existing technical solutions can only locate the call abnormality caused by the wireless network, but when the cause of the call abnormality is the failure of the equipment in the network, the above-mentioned technical solution cannot locate the real problem

For example: when the air interface signal is not good or the success rate of access is low due to the failure of the equipment transmission or the equipment flashing off, the above technical solution cannot locate the cause of the abnormality according to the CHR. At this time, it will consume a lot of manpower and material resources Drive test to locate the problem

However, the final positioning results found that it was not the problem of the wireless network, but the problem of the equipment. On the one hand, it required a lot of manpower and material resources. On the other hand, it made it difficult for users to respond to complaints in a timely manner, resulting in low analysis efficiency.

[0011] 2. The signaling trace started during the drive test will generate a large amount of data. The analysis of these data is complex and time-consuming, and most of the data is useless, which also makes the analysis efficiency low

[0012] 3. Due to post-event analysis, the cause of the user’s abnormal call may have been automatically recovered, making it impossible or difficult to reproduce the abnormal call during drive testing, and then unable to locate the real cause of the abnormal call

[0013] 4. The above technical solution is a passive analysis based on user complaints. When there are hidden dangers in the network that lead to abnormal calls, the hidden dangers cannot be actively prevented, which may lead to a large number of abnormal outbreaks and affect customer satisfaction.

Images