KR100459762B1 - Call Failure Message Surveillance Apparatus and Method for Mobile Network of CDMA - Google Patents

Abstract

The present invention relates to a call failure message monitoring apparatus and method for a code division multiple access mobile communication network, comprising: a message receiving unit for receiving a call failure message from a code division multiple access mobile communication network; A message classifier that classifies the call failure message received by the message receiver; And a message generation number management unit that outputs an alarm generation message to generate an alarm when a message classified from the message classification unit is received more than a predetermined number of times.

According to the present invention configured as described above, the F3000 message generated by the system, the BSC, the BTS, or the cause can be classified and managed to monitor the call failure of the code division multiple access mobile communication network. According to the present invention, the number of occurrences of the classified F3000 message is managed to notify the operator when more than the set number is generated so that the user can take action as soon as possible. Further, according to the present invention, the generated F3000 message is classified and stored, and the operator can inquire as needed to effectively manage hardware and software of the mobile communication network.

Description

Call Failure Message Surveillance Apparatus and Method for Mobile Network of CDMA}

The present invention relates to the management of a call failure message of a mobile communication network, and more specifically, to classify and store a call failure message generated in a mobile communication network by the cause of occurrence and to generate a set value abnormality by counting the number of occurrences for each classified call failure message. The present invention relates to a call failure message monitoring device and a call failure message management method of a code division multiple access mobile communication network capable of generating an alarm when an action can be taken.

The F3000 displays the cause information of the call failure of the system in operation for the call related failure analysis on the base station system (BSS) of the CDMA2000 system in the Fault Message 3000. Device is referred to collectively as F3000.

The F3000 is a real-time call to identify the causes of failures related to calls and other services (eg, mobility management services and supplementary services) generated in the mobile communication system and to overcome the problems. It is a function to collect related problems. That is, the F3000 is a function of reporting the call failure reason and the location of the hardware (H / W) or software (S / W) that occurred.

However, the F3000-related messages collected by the BSM are difficult to be easily identified by the operator of the mobile communication network and monitored for each cause. However, there are various needs to easily identify the F3000 message.

The first is a case where a large number of call failures are caused by a problem in the system software (S / W). As described above, when a large number of call failures occur due to a problem in the system software S / W, the operator does not know the problem because the BSM does not output an alarm (alarm message). Therefore, the operator cannot discover the problem of the system software until the subscriber's request is raised due to the poor call processing. Moreover, the operator of the mobile communication network wants to preempt the occurrence of the problem by testing the system software (S / W) in advance, but there is a problem that the BSM does not provide an alarm service.

The second is a case where a large number of call failures occur due to system hardware (H / W) problems. As such, when a large number of call failures are caused by the system hardware (H / W), the conventional BSM does not provide information on how seriously a call failure is occurring. Therefore, the operator may not know how seriously the call processing failure due to the system hardware (H / W) problem occurs, so there is a problem that can not be quickly acted.

The third is when a large number of call failures occur before a system problem occurs. In such a case, since the occurrence of a failure by the system hardware (H / W) or software (S / W) cannot be known in advance by the conventional BSM, there is a problem that cannot be prevented in advance. Therefore, it is necessary to notify the operator in advance of a large number of call failures occurring as a preliminary sign of system failure so that the operator can prevent the failure in advance.

The fourth case is a case where a large number of call failures are caused by a wireless environment. In this case, conventionally, a large number of call failures are generated in a specific area due to a wireless environment, and the cause cannot be known until the subscriber complains. Moreover, call failure caused by this wireless environment is difficult to detect until the operator performs a field test. Therefore, when a large number of call failures occur in a specific area due to the wireless environment, it is necessary to quickly analyze the location and cause and take action.

Therefore, the present invention has been proposed to solve the above-mentioned problems, and notifies the operator when abnormally more call failures occur than the number of occurrences in a stable state that is normally generated while monitoring call failures occurring in the system in real time. An object of the present invention is to provide a call failure message monitoring apparatus and a call failure message management method of a code division multiple access mobile communication network.

1 is a diagram schematically illustrating a connection state between a code division multiple access mobile communication network and a call failure message monitoring apparatus according to an embodiment of the present invention;

2 is a view showing in detail the configuration of the call failure message monitoring apparatus shown in FIG.

3 is a flowchart showing an example of the operation of the call failure message monitoring apparatus shown in FIG.

4 is a flowchart showing another example of the operation of the call failure message monitoring device shown in FIG. 1;

<Explanation of symbols for the main parts of the drawings>

110, 120: BTS (Base Station Transceiver System)

130: BSC (Base Station Controller) 140: DCN (Data Core Network)

150: BSM (Base Station Manager) 160: IWF (Inter Working Function)

170: MSC (Mobile Switching Center)

300: call failure message monitoring device

310: F3000 message receiving unit 320: F3000 message classification unit

330: F3000 message storage unit 340: F3000 message search unit

350: operator matching unit 360: F3000 message analysis unit

370: F3000 message occurrence number management unit

380: alarm generation and control unit

According to a feature of the present invention proposed to achieve the above object, a call failure message monitoring apparatus of a code division multiple access mobile communication network is a device for monitoring a call failure message generated in a code division multiple access mobile communication network, A message receiving unit which receives a call failure message generated from a code division multiple access mobile communication network; A message classifier classifying a call failure message received by the message receiver; And a message generation number management unit that outputs an alarm generation message to generate an alarm when a message classified from the message classification unit is generated a predetermined number of times or more.

According to another aspect of the present invention, a call failure message monitoring apparatus of a code division multiple access mobile communication network is a device for monitoring a call failure message generated in a code division multiple access mobile communication network, generated from the code division multiple access mobile communication network. A message receiver for receiving a failed call failure message; A message classifier classifying a call failure message received by the message receiver; A message storage unit storing a call failure message classified from the message classification unit; A message retrieval unit for retrieving and outputting a call failure message stored in the message storage unit by a retrieval condition; And an operator matching unit which transmits a search condition to the message retrieval unit and displays a result detected by the message detection unit.

According to still another aspect of the present invention, there is provided a method for monitoring a call failure message in a code division multiple access mobile communication network, the method for monitoring a call failure message generated in a code division multiple access mobile communication network, wherein the call failure message is generated from the code division multiple access mobile communication network. Receiving a failed call failure message; Classifying a call failure message received from the step of receiving the message; And counting call failure messages classified from the classifying step, and generating an alarm if the counted value is equal to or greater than a predetermined value within a predetermined time.

According to still another aspect of the present invention, a method for monitoring a call failure message of a code division multiple access mobile communication network is provided in the method for monitoring a call failure message generated in a code division multiple access mobile communication network. Receiving a generated call failure message; Classifying a call failure message received from the step of receiving the message; Classifying and storing each call failure message classified in the classifying step; And inquiring and storing the stored call failure message in the storing step according to a predetermined inquiry condition.

Hereinafter, embodiments of the present invention will be described in detail with reference to FIGS. 1 to 4.

1 is a diagram schematically illustrating a connection state between a code division multiple access mobile communication network and a call failure message monitoring apparatus according to an embodiment of the present invention. Here, reference numeral 100 denotes the Internet, 180 denotes a PSTN, 190 denotes a mobile telephone company network, and 200 denotes another exchange and an additional system.

In the figure, the MSC (Mobile Switching Center) is a system for performing a switching function in a network, and performs a function of connecting a mobile subscriber in a network with subscribers of other networks, and is connected with various additional systems to provide additional services. The base station controller (BSC) connects voice calls and line data calls between the base station transceiver system (BTS) and the mobile switching center (MSC), and packets between the base station transceiver system (BTS) and the data core network (DCN). It connects data calls and performs vocoding for voice calls.

The base station controller (BSC) operates and maintains a base station transceiver system (BTS) under the control of a base station manager (BSM). In addition, the BTS (Base Station Transceiver System) is wirelessly matched with the mobile terminal to provide a mobile communication service to the mobile subscriber. The base station manager (BSM) is a device for operating and maintaining a base station controller (BSC) and a base station transceiver system (BTS). And a DCN (Data Core Network) is a device for providing a packet data communication service of the mobile communication, for example to the mobile subscriber. Finally, the Inter Working Function (IWF) provides mobile subscribers with line data communication services in fax or modem communication.

The call failure message monitoring apparatus 300 is connected to the BSM 150 and receives a call failure message generated from a mobile communication network (for example, BTS or BSC).

2 is a diagram illustrating in detail the configuration of the call failure message monitoring apparatus shown in FIG. In the drawing, reference numeral 310 denotes an F3000 message receiver, 320 an F3000 message indexer, 330 an F3000 message storage, 340 an F3000 message query, and 350 an operator. A user interface, 360 denotes an F3000 message analyzer, 370 denotes an F3000 message occurrence number management unit, and 380 denotes an alarm generation and a control unit, respectively.

First, the F3000 message receiving unit 310 receives the F3000 message reported to the BSM 150 from the BSC 130 or the BTSs 110 and 120 in real time. When the F3000 message is not received by the BSM 150, the F3000 message receiver 310 restarts the software block or generates an alarm to the operator.

The F3000 message classifier 320 classifies the F3000 message received by the F3000 message receiver 310. The F3000 message classification unit 320 includes a monitoring target exclusion setting function and a classification function of BSC and BTS. The monitoring target exclusion setting function is set to be excluded from monitoring because the generated F3000 message is not a system problem, for example, due to a busy, absent, power off, missing, or suspended use. In addition, in the case where the importance is low among the F300 messages, a monitoring target which is not necessary for monitoring may be excluded. Subsequently, the BSC classification function is to classify in which position the received F3000 message is generated. In addition, the BTS classification function classifies whether the received F3000 message is generated at the BTS at which position belonging to the BSC at which position.

Subsequently, the F3000 message generation number management unit 370 manages the number of occurrences of the classified F3000 message output from the F3000 message classification unit 320 for each BSC and BTS. First, the F3000 message generation number management unit 370 manages the number of generation of F3000 messages for each BSC. That is, when the F3000 message is generated, the F3000 message generation number management unit 370 accumulates and stores the number of occurrences of the F3000 message for each BSC. The number of occurrences of the F3000 message for each BSC is the sum of all the F3000 messages generated in the BTS accommodated in the corresponding BSC.

The F3000 message occurrence number management unit 370 manages the number of occurrences of the F3000 message for each BTS. That is, when an F3000 message is generated, the F3000 message generation number management unit 370 accumulates and stores the number of occurrences of the F3000 message for each BTS.

In addition, the F3000 message occurrence number management unit 370 performs a function of resetting the number of occurrences of the counted F3000 message. For example, if you manage the number of F3000 message occurrences by hour, reset the number to '0' every hour (or daily reset if you manage by day).

Subsequently, when the F3000 message occurs more than the set number of times, the alarm generation and control unit 380 performs a function of outputting an audible or visual (eg, text or picture) alarm to the operator. Such alarm generation and control unit 380 performs an alarm generation timer function. That is, the number of occurrences of the F3000 message to be managed for a set time for each BSC or BTS is set, and an alarm generation command is output to generate an alarm when more than the set number is generated. When the alarm generation and control unit 380 reaches the set time, the alarm generation and control unit 380 initializes the number of managed F3000 messages to '0' and starts counting again (for example, 10 F3000 messages are generated for 1 minute). If it is set to trigger an alarm, it will generate an alarm if 10 F3000 messages occur within one minute and reset the count to '0' every minute. At this time, the alarm generation and the control unit 380 may enable the operator to check by outputting an alarm to the operator when the F3000 message is not received for a predetermined time or more.

And alarm generation and the control unit 380 generates an audible alarm. That is, when an alarm generation command is output from the alarm generation timer, a specific sound is generated for the operator to recognize. At this time, the alarm generation and control unit 380 allows the operator to recognize and determine according to the priority by causing the alarm from the BSC and the alarm sound from the BTS to be generated differently. In addition, the alarm generation and the control unit 380 generates a visible alarm. That is, when an alarm generation command is output from the alarm generation timer, a specific character string is output on the screen so that an operator can recognize it (the character string may include the position and the number of occurrences of the BSC or BTS). The visible alarm string is displayed in a cumulative manner in the program window, and can be deleted by the operator as necessary. Furthermore, the alarm generation and control unit 380 displays the identification display list and the current status list of BSC and BTS on the screen in the form of a GUI (Graphic User Interface), and then the alarm generation command is transmitted from the alarm generation timer. If necessary, the color of the location and status of the relevant BSC or BTS may be changed (for example, blue in normal times, red in case of an alarm) so that an operator can recognize it. Finally, the alarm generation and control unit 380 includes various alarm generation setting functions. The operator may set the F3000 monitoring period necessary to generate an alarm through the alarm generation and the control unit 380, and set how many alarms are to be generated when the number of events occurs within the corresponding period (for example, 100 for 1 minute in the BSC). Alarm output when 1 F3000 message is generated, alarm output when 10 F3000 messages occur for 1 minute in BTS). The alarm generation and control unit 380 includes a function that allows the operator to select the type and size of the audible sound, and a function that can set / release the audible sound.

In the figure, the F3000 message storage unit 330 classifies the F3000 message output from the F3000 message classification unit 320 by date, time or, if necessary, the system, and then designates and stores a directory. In this case, the F3000 message excluded from the monitoring target in the F3000 message classification unit 320 is stored separately.

The F3000 message interpreter 360 provides a function of interpreting and outputting the F3000 message so that the operator can easily understand the raw data of the F3000 message. That is, the F3000 message interpreter 360 interprets and outputs the F3000 message (for example, USRDATA) consisting of numbers so that the operator can easily understand what the corresponding numbers mean. In addition, the F3000 message analyzer 360 arranges the F3000 message thus interpreted in such a manner as to be easily displayed by the operator in the order of the system, hardware, software, and cause. In addition, the F3000 message interpreter 360 includes a function of storing or printing the interpreted F3000 message.

Subsequently, the F3000 message retrieval unit 340 extracts the data stored in the F3000 message storage unit 330, classifies the data into F3000 messages corresponding to a BSC or BTS desired by the operator, and then transfers the data to the F3000 message interpreter 360. Perform the function. That is, the F3000 message retrieval unit 340 reads F3000 message data stored in a specific directory of the F3000 message storage unit 330 by a current time or a desired time, classifies the B3000 and BTSs, and then classifies the F3000 message analysis unit 360. To pass on.

Finally, the operator matching unit 350 serves as a matching function with the operator providing various setting menus of the call failure message monitoring apparatus 300 to the operator. The operator matching unit 350 displays the display function of the graphical user interface (GUI) for the convenience of the operator. to provide. The operator matching unit 350 provides a reception and monitoring start control menu of the F3000 message, provides an alarm setting and control menu, provides a menu for interpreting the stored F3000 message, and an operator in the other transmission line monitoring device. Provide menus or status screens required by the user.

3 is a flowchart showing an example of the operation of the call failure message monitoring apparatus 300 shown in FIG.

First, when a monitoring start command is input, the call failure message monitoring apparatus 300 starts a monitoring operation (S110). The call failure message monitoring apparatus 300 determines whether an F3000 message has been received through the F3000 message receiving unit 310 (S120). At this time, if the F3000 message is not received, for example, for 5 minutes, the call failure monitoring apparatus 300 restarts the F3000 message receiving unit 310 (S140), and notifies the operator (S150).

When the F3000 message is received from the F3000 message receiving unit 310, the call failure message monitoring apparatus 300 determines whether the received F3000 message corresponds to the monitoring target through the F3000 message classifying unit 320 (S160). ). When the received F3000 message corresponds to the monitoring target, the F3000 message classification unit 320 of the call failure message monitoring apparatus 300 classifies the received message by system, BSC, or BTS (S180). If the received F3000 message is not to be monitored, the F3000 message classifier 320 deletes the received message (S170).

Subsequently, the call failure message monitoring apparatus 300 determines whether the number management time of the F3000 message occurrence number management unit 370 has changed (S190). In this case, when the number management time is changed, the call failure message monitoring apparatus 300 resets the management number set for each BSC or BTS to be 0 (S200).

If the set number management time is not changed, the F3000 message generation number management unit 370 increments the corresponding number management counter for each BSC or BTS by 1 (S210). And update the corresponding management number of the operator's screen through the GUI (S220).

Subsequently, the call failure message monitoring apparatus 300 increases the number of monitoring of the corresponding BSC or BTS by 1 based on the F3000 message (S230). The call failure message monitoring apparatus 300 determines whether the F3000 message generation number management unit 370 exceeds the set number of F3000 messages (S240). In this case, when the number of occurrences of the F3000 message is greater than or equal to the set value, the call failure message monitoring apparatus 300 generates an audible alarm and a visible alarm (S250 and S260).

Subsequently, the call failure message monitoring apparatus 300 determines whether the set time has been exceeded for each set monitoring target message through the F3000 message occurrence number management unit 370 (S270). If the time set for each monitoring target is exceeded, the number of monitoring of the corresponding counter is reset to zero (S280). Finally, the call failure message monitoring apparatus 300 stores the F3000 message through the F3000 message storage unit 330 (S290), and if the end command is not input, the call failure message monitoring apparatus 300 performs the process again from the step S120.

4 is a flowchart illustrating another example of an operation of the call failure message monitoring apparatus 300 illustrated in FIG. 1.

First, the call failure message monitoring apparatus 300 receives the F3000 analysis command from the operator through the operator matching unit 350 (S410).

Then, the operator matching unit 350 transmits the F3000 analysis command to the F3000 message search unit 340. When the F3000 analysis command is received, the F3000 message retrieval unit 340 determines whether the number of F3000 message management cases of the corresponding BSC or BTS exceeds 0 through the F3000 message storage unit 330 (S420). If the number of F3000 message management exceeds 0, the F3000 message retrieval unit 340 extracts the corresponding F3000 message from the F3000 message storage unit 330 (S430).

Subsequently, the F3000 message search unit 340 classifies the extracted F3000 message by BSC or BTS (S440) and outputs the F3000 message to the F3000 message analyzer 360. Then, the F3000 message analysis unit 360 interprets the F3000 message so that the operator can easily identify (S450) and outputs the message to the operator matching unit 350.

Finally, when the interpreted F3000 message is received from the F3000 message interpreter 360, the operator matching unit 350 generates a window in an operator terminal (for example, a monitor) (S460) and displays the interpreted F3000 message (S460). S470).

As such, those skilled in the art will appreciate that the present invention can be implemented in other specific forms without changing the technical spirit or essential features thereof. Therefore, the above-described embodiments are to be understood as illustrative in all respects and not as restrictive. The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

The present invention can classify and manage F3000 messages generated by system, BSC, BTS, or cause so as to monitor call failure of a code division multiple access mobile communication network. According to the present invention, the number of occurrences of the classified F3000 message is managed to notify the operator when more than the set number is generated so that the user can take action as soon as possible.

Further, according to the present invention, the generated F3000 message is classified and stored, and the operator can inquire as needed to effectively manage hardware and software of the mobile communication network.

Claims (19)

An apparatus for monitoring a call failure message generated in a code division multiple access mobile communication network, A message receiving unit which receives a call failure message generated from the code division multiple access mobile communication network; A message classifying unit classifying the call failure message received by the message receiving unit; A message storage unit for storing a call failure message classified from the message classification unit; A message generation number management unit that outputs an alarm generation message to generate an alarm when a message classified from the message classification unit is received a predetermined number of times or more; And An alarm generation and control unit for generating an audible or visible alarm when an alarm generation message is output from the message occurrence number management unit; Call failure message monitoring apparatus of a code division multiple access mobile communication network, characterized in that consisting of. delete delete The method of claim 1, The message generation number management unit distinguishes the BSC or BTS to be monitored to set the number of call failure message generation call failure message monitoring device, characterized in that the multi-connection mobile communication network. The method of claim 1, And the message classifier deletes the received call failure message when the call failure message is not to be monitored. An apparatus for monitoring a call failure message generated in a code division multiple access mobile communication network, A message receiving unit which receives a call failure message generated from the code division multiple access mobile communication network; A message classifier classifying a call failure message received by the message receiver; A message generation number management unit that outputs an alarm generation message to generate an alarm when a message classified from the message classification unit is generated more than a predetermined number of times; A message storage unit storing a call failure message classified from the message classification unit; A message retrieval unit for retrieving and outputting a call failure message stored in the message storage unit by a retrieval condition; A message analyzing unit for interpreting and outputting a call failure message output from the message searching unit; And An operator matching unit for transmitting a search condition to the message retrieval unit and displaying a result retrieved from the message retrieval unit; Call failure message monitoring apparatus of a code division multiple access mobile communication network, characterized in that consisting of. delete delete The method of claim 6, The call failure message monitoring device is configured to include an alarm generation and a control unit for generating an audible or visual alert when an alarm generation message is output from the number of message occurrence management unit, wherein the call failure message monitoring device of a code division multiple access mobile communication network is provided. . A method for monitoring a call failure message generated in a code division multiple access mobile communication network, A method for monitoring a call failure message generated in a code division multiple access mobile communication network, Receiving a call failure message generated from the code division multiple access mobile communication network; Classifying the call failure message received from the step of receiving the message, and storing the classified call failure message for each classified call failure message; And Counting each classified call failure message from the classifying step and generating an alarm if the counted value is greater than or equal to a predetermined value within a predetermined time; Call failure message monitoring method of a code division multiple access mobile communication network, characterized in that consisting of. The method of claim 10, The generating of the alert comprises: setting a time for counting a call failure message, wherein the call failure message monitoring method of a code division multiple access mobile communication network. The method of claim 10, The generating of the alert comprises: setting a count to zero when a set time is reached. The method of claim 10, The generating of the alert comprises: setting a value for counting a call failure message, wherein the call failure message monitoring method of a code division multiple access mobile communication network. delete The method of claim 10, The classifying the message may include deleting the call failure message when the call failure message is not a management target, the call failure message monitoring method of a code division multiple access mobile communication network. A method for monitoring a call failure message generated in a code division multiple access mobile communication network, Receiving a call failure message generated from the code division multiple access mobile communication network; Classifying a call failure message received from the step of receiving the message, counting each classified call failure message and generating an alarm if the counted value is greater than or equal to a predetermined value within a predetermined time; Classifying and storing the classified call failure messages; And Querying the stored call failure message in the storing step according to a predetermined inquiry condition, interpreting and outputting a call failure message; Call failure message monitoring method of a code division multiple access mobile communication network, characterized in that consisting of. delete The method of claim 16, And inquiring and outputting the message comprises outputting a call failure message through a graphical user interface. delete