JP2009253403A - Log level collecting device and log level collection method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow logs to be left in details, at the occurrence of a fault while reducing the load on a base station, a base station control device, and a CPU of a host server and the capacity of a storage device and to allow logs before the occurrence of the fault, even when the fault cannot be unpredicted, to be preserved and enable analysis of the cause and details of the occurrence of the fault. <P>SOLUTION: A plurality of output levels of log information to be requested to the base station are set, and a table associating output levels of log information with respective types of events reported from the base station due to event occurrence alarms is prepared beforehand; and the output level of log information is obtained from the base station, according to the reception condition of an event-occurrence alarm, a change notification is transmitted to the base station so that log information is output in the obtained output level, and output log information is collected and stored. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a radio communication technology, and more particularly, to an apparatus and method for performing maintenance operation of a radio base station.

  In wireless communication systems, base stations (BSs) that transmit and receive radio signals to and from mobile terminals are arranged in large numbers every several hundreds to several tens of kilometers depending on the coverage of the base station. Each of these base stations is connected to a plurality of base station controllers (Base Station Controllers: BSCs), which control the base stations and assign and switch radio channels to mobile terminals. Yes. The base station control device is further connected to the Internet or a wired telephone network via a core network.

  The number of base stations connected to the base station controller is several tens or more. In order for the base station control device to control the base station, it is necessary to grasp the operation status and failure status of the connected base station. In the base station and the base control device, information on the operation status and failure status is collected and temporarily stored in each device. This stored information is usually called a log. This log is divided into a system operation information log, which is a normal operation status log of the apparatus, and a failure information log related to the situation when some kind of failure occurs. These logs are output minute by minute and are extremely large. For this reason, if all logs are transferred from the base station to the base station controller in real time, a load is imposed on the dedicated line between the base station and the base controller, which affects basic functions such as calls and user data transfer. For this reason, conventionally, only a small part of the system operation information log and the failure information log are transferred to the host server in real time and stored.

  The system operation information log transferred to the upper server is transmitted from the upper server to a monitoring terminal (not shown) in a predetermined manner and displayed. Most other system operation information logs and failure information logs that have not been sent to the host server have limited storage capacity, so they are temporarily saved in each device and then overwritten by new logs. .

The log stored in this way is used to identify the failure occurrence by the operator of the monitoring terminal when a failure occurs in each device or system, and to identify the failure occurrence device. An operator went to the installation site and collected manually. As such a system, for example, in Patent Document 1, when each device can determine the occurrence of a failure by itself, a failure information log at that time is automatically stored in the device, and then analysis is necessary. Has been disclosed to manually output the failure information log stored inside each device when a failure occurs
JP 2007-60092 A

  In the system described in the background section above, the log at that time is automatically saved only when it is determined that a failure has occurred in the base station or base station controller, so it cannot be determined that a failure has occurred. In this case, the log is overwritten immediately after it is temporarily saved, and cannot be collected even if analysis is required later.

  In addition, if the base station device is in a state that can only be restored by a sudden reset, or if a human reset is performed for some reason, the log before the reset will be almost cleared, so A situation occurs where the situation cannot be analyzed.

  As a method for avoiding such a situation, consider a case in which logs are stored in detail in a host server. The base station communicates with the base station control device and the host server via a dedicated line. One base station control apparatus is connected to one hundred or more base stations in some cases. Therefore, an enormous storage area is required to store the logs of the hundred or more base stations. In addition, as described above, the transfer of a huge amount of logs may increase the burden on the dedicated line and affect the normal call processing function. Therefore, it is impossible for the upper server to collect logs in real time over a long period of time.

  Log collection is required to output and save as few essential logs as possible in consideration of the load on the CPU of the device and the capacity of the storage device. On the other hand, once a failure occurs and analysis becomes necessary, the more information that is stored in the log, the more detailed it is, and the logs before the failure point are also saved. It is easier to analyze the reason for the failure and how it occurred.

  The present invention was made to solve these problems, satisfying the above conflicting requirements, reducing the load on the CPU of the base station and the base station control device and the capacity of the storage device, at the time of failure occurrence An object of the present invention is to provide a log collection device and a log collection method capable of leaving a log in detail.

  It is another object of the present invention to be able to save a log before the occurrence of a failure and analyze the cause and background of the occurrence of the failure even when an unexpected failure occurs.

In order to solve the above problems, in the present invention, the log information output level requested to the base station is set in a plurality of stages, and the log information is set for each event type notified by the event occurrence alarm from the base station. A table in which the output levels are associated with each other is prepared in advance, and when no event occurrence alarm is received from the base station, the base station is designated to output log information at a predetermined output level of the table. Collect and store log information output at the output level specified by the base station,
On the other hand, when an event occurrence alarm is received from the base station, the base is configured to obtain an output level corresponding to the event type notified by the event occurrence alarm by referring to the table and to output log information at the obtained output level. A change notification is transmitted to the station, and log information output at the output level changed from the base station is collected and stored.

  According to the present invention, a log collection device and a log collection method capable of leaving a log in detail when a failure occurs while reducing the load on the CPU and the storage device capacity of the base station, the base station control device, and the host server Can be provided.

  In addition, even when an unforeseen failure occurs, a log before the failure can be saved, and the cause and background of the failure can be analyzed.

  Hereinafter, embodiments of the present invention will be described with reference to examples.

  First, a general configuration of a wireless communication system to which the present invention is applied and log collection when a failure occurs will be described with reference to FIGS.

FIG. 1 is a diagram illustrating a configuration of a current wireless communication system.
In the current wireless communication system, the base station (BS1) 15-1 to base station (BSn) 15-n that communicates with the mobile terminal 16 through a wireless line is from several hundred meters depending on the area covered by the base station. It is arranged every several tens km. These base stations (BS 1) 15-1 to base stations (BSn) 15 -n are connected to the base station control device 11 and the upper server 13 via the connection router 12. The base station control device 11 is also connected to the Internet 14 or a wired telephone network (not shown) via the connection router 12. The base station control device 11 is also connected to the upper server 13 via the connection router 12.
In FIG. 1, all the base stations are connected to one base station control device. However, in the wireless communication system, a plurality of base stations and a plurality of base station control devices are not shown here. Is present.

FIG. 2 is a diagram illustrating a sequence of a failure information log collection operation when a failure occurs in the current wireless communication system.
As shown in FIG. 2, the base station has a main function unit and an internal log collection unit. In the current wireless communication system, when a failure occurs in the base station, the main function unit detects this and sends a failure occurrence alarm to the internal log collection unit. When notified to the main function unit, the main function unit sends a failure information log to the internal log collection unit, and the failure information log is stored in the internal log collection unit. When the collection of the failure information log is completed, the internal log collection unit notifies the completion of the collection of the failure information log.

  In the current system as described above, Only the failure information log is stored because the memory capacity of the internal log collection unit is limited. 2. Logs cannot be collected automatically for faults that cannot be identified as faults. 3. The person in charge looks at the alarm displayed on the monitoring terminal based on the information sent to the host server, confirms which device has a fault, and the operator goes to the device location to manually collect the logs Since it started, it took a considerable amount of time to determine the situation and collect logs after the failure occurred, and it was not possible to collect logs at the time of failure occurrence and immediately before the failure occurrence.

  The present embodiment solves such a problem, and can reduce the load on the CPU of the base station and the base station control device and the capacity of the storage device while leaving a log in detail when a problem occurs. In addition, even when an unpredictable problem occurs, a log before the problem occurs can be saved and the problem can be analyzed. This will be described below with reference to FIGS.

FIG. 3 is a diagram for explaining the configuration of a wireless communication system in an embodiment of the present invention.
In this embodiment, log collection devices 17-1 to 17-n are connected to the base station (BS1) 15-1 to the base station (BSn) 15-n, respectively. In the present embodiment, the log output from the base station includes a lot of information that can be obtained by the base station in a very detailed manner depending on the level of detail (information amount). Set multiple levels to as few as possible. Then, the log collection device connected to each base station always collects the base station log at any level. The log collection device monitors an event notification such as a failure occurrence notification output from the base station, and upon receiving the event notification, transmits a command to the base station to change the log output level according to the content. Hereinafter, the configuration of the log level collection device, the operation flow, and an example of the log level will be described in detail.

First, the configuration of the log collection device will be described.
FIG. 4 is a diagram showing the configuration of the log collection device in one embodiment of the present invention.
In the present embodiment, the log collection device 17 is connected to a base station and has an interface for transmitting and receiving information to and from the base station. The interface 174 is connected to the base station 15 and has an interface 175 for transmitting / receiving information to / from a host server. In addition, the log collection device 17 includes a memory 171 for temporarily storing event information, logs, and programs received from the base station. The log received from the base station is stored in the hard disk (HD) 173. The CPU 172 executes a program to perform log collection, log level control for the base station, control of the log level collection device, and the like.

Next, a processing sequence between the base station and the log collection device when collecting logs will be described.
FIG. 5 is a diagram for explaining the sequence of log collection processing in one embodiment of the present invention.
In this embodiment, when the log collection device is installed, a log collection start notification is transmitted from the log collection device to the base station. Receiving this, the base station outputs a log at a preset log level. In the case of the present embodiment, the log level in the normal state where no event such as a failure has occurred is set as a constant level, and the log is output at the constant level (S21). The log collection device collects and stores this output log in real time. Since the log collecting apparatus according to the present embodiment always saves the log as described above, even if an event or failure that cannot be detected occurs, the log is secured, and the cause and background can be analyzed.

Thereafter, when any event occurs in the base station 15 (S22), the base station outputs an event occurrence alarm (S23). When the event occurrence alarm output from the base station 15 is received, the log collection device 17 determines the event type, and selects a log level with reference to a preset log level change determination table. Here, the case where the log level m is selected will be described. The log level change judgment table and the log level and the log type level correspondence table inside the base station described later are set in advance by analyzing the urgency level, importance level, impact range, and log collection level of each event. Keep it.
When the log level is selected, the log collection device transmits a change command so as to change the log level of the log output to the base station from the constant level to the log level m.
The base station that has received the change command for changing the log level to m changes the log level to be output in accordance with the command.

In this embodiment, the log level collection device 17 has a timer (not shown), and when the preset time has elapsed and the timer expires, the log level collection device 17 notifies the base station to return the log level to the constant level.
The base station that has received this changes the level of the log to be output to a constant level.
As the time set in the timer, another value can be set according to the event type or log level in FIG.
The logs collected and stored in this way are stored in the log collection device for a certain period of time. The log collection device has a sufficiently large storage area for storing log information so that the storage period can be set sufficiently long. In this embodiment, there is no need to send the log to the upper server at all times, so no load is applied to the line.

FIG. 6 shows a processing flow in the log collection device when the above-described log collection processing sequence is executed.
In the log collection device, first, when log collection is started, logs are always collected at a constant level from the base station (S21). When the event occurrence alarm is received from the base station (S22), the type of the received event is determined, the log level is determined according to the event type by referring to the preset log level change determination table, and the base A log level change command is transmitted to the station so as to change the level of the output log to the log level (S23). Then, the logs transmitted from the base station are collected at the changed log level according to the change command (S24). When the log collection timer expires after a lapse of a certain time (S25), a command to return the log level to the constant level is transmitted to the base station (S26).

FIG. 7 shows an example of a log level change determination table of the log collection device.
Event types include unknown cause reset, artificial reset, abnormal call processing, congestion occurrence, memory usage rate higher than preset usage rate, CPU usage rate higher than preset usage rate, etc. There is a special event.
Log level 1 is associated with each of the above events, for example, in the case of an unknown reset or an artificial reset. Further, when abnormal call processing or congestion occurs, log level 2 is associated, and when memory or CPU usage is high, log level 3 is associated.

As described above, the information output from the log is roughly divided into system operation information and failure information. Depending on the event, information regarding the event is output in detail in a certain type of log, but information regarding the event is not output much in another type of log. Therefore, the log level associated with each event needs to be able to set the level of detail for each type of log information.
FIG. 8 shows an example of a table in which each log level is associated with a level for each type of base station internal log. The table shown in FIG. 8 exists in the base station 15. The base station acquires a plurality of types of logs simultaneously as operation information logs and failure information logs. FIG. 8 shows an example in which the log types are divided into a plurality of types from the internal log a to the internal log x. The log level 1 is a level in which the internal log a outputs the log with the level 1 content which is the most detailed and the most information amount, and the internal log b and the internal log x are also the most detailed and the most information level. This indicates that the log is output with the content of 1.
In addition, the log level 2 is the level 2 in which the internal log a is the second most detailed and the most information amount, and the internal log b is the level 1 in the most detailed and most information level. The log is output with the contents, and the internal log x indicates that the log is specified to be output with the contents of level 2 which is the second most detailed and information-rich level. In the example shown in FIG. 8, the log level 5 is associated with the constant level. Therefore, in the state of S21 in FIG. 6 (in particular, when no event has occurred), the internal log a is output at level 6, the internal log b is output at level 4, and the internal log x is at level In this way, the log is output and sent to the log collector and saved. By setting the log level for each type of log in this way, it is possible to secure sufficient information and reduce unnecessary information. The load can be reduced.

  Although an example in which the table of FIG. 8 exists in the base station 15 is shown, this table can be similarly implemented even if it exists in the log collection device 17.

  In the above embodiments, the case where the present invention is implemented in the base station has been described as an example. However, the present invention can be similarly implemented in the base station control apparatus.

It is a figure explaining the structure of the present radio | wireless communications system. It is a figure explaining the sequence of the failure information log collection operation | movement at the time of failure occurrence in the present wireless communication system. It is a figure explaining the structure of the radio | wireless communications system in one Example of this invention. It is a block diagram of the log collection apparatus in one Example of this invention. It is a sequence diagram of the log collection process in one Example of this invention. It is an operation | movement flowchart of the log collection apparatus in one Example of this invention. It is an example of the log level change judgment table of a log collection device. It is an example of the table which matched each log level of a log collection apparatus, and the level according to the kind of base station internal log.

Explanation of symbols

11 Base station controller 12 Linked router 13 Host server 14 Internet 15-1 to 15-n Base stations 1 to n
16 Mobile terminal 17 Log collection device 171 Memory 172 CPU
173 HD
174 I / F1
175 I / F2

Claims (6)

A log collection device connected to a radio base station, receiving log information output from the radio base station, collecting and storing the log information,
An interface with the base station, a storage unit, and a control unit;
In the storage unit, a plurality of log information output levels requested to the base station are set, and the log information output level is associated with each event type notified by the event occurrence alarm from the base station. Have a table attached,
The controller is
In a state where no event occurrence alarm is received from the base station, the base station is designated to output log information at a predetermined output level of the table and is output at the output level designated by the base station. Log information is collected and stored in the storage unit,
When receiving an event occurrence alert from the base station, the base is configured to obtain an output level corresponding to the event type notified by the event occurrence alert with reference to the table and to output log information at the obtained output level. A log collection device that transmits a change notification to a station, collects log information output at the output level changed from the base station, and stores the collected log information in the storage unit. The log collection device according to claim 1,
And have a timer,
After a notification of changing the output level of log information to the base station, when the timer expires after a certain time elapses, the base level is set so that the output level of the log information is returned to the output level where no event occurrence alarm has been received. A log collection device that transmits a change notification to a station. The log collection device according to claim 1 or 2,
There are multiple types of log information,
In addition to the table in which the event type and the output level are associated with each other, a table in which the detail level of log information output is set for each of the plurality of types of log information for each output level is prepared.
A log information collection apparatus, wherein a change notification is transmitted to the base station so that log information is output at a level of detail obtained by referring to the table for each of the plurality of types of log information. A log collection method for connecting to a radio base station, receiving log information output from the radio base station, collecting and storing the log information,
A table in which the output level of log information requested to the base station is set in a plurality of stages, and the output level of the log information is associated in advance for each event type notified by an event occurrence alert from the base station. Prepare it,
In a state where no event occurrence alarm is received from the base station, the base station is designated to output log information at a predetermined output level of the table and is output at the output level designated by the base station. Collect and store log information,
When receiving an event occurrence alert from the base station, the base is configured to obtain an output level corresponding to the event type notified by the event occurrence alert with reference to the table and to output log information at the obtained output level. A log collection method characterized by transmitting a change notification to a station and collecting and storing log information output at the output level changed from the base station. The log collection method according to claim 4,
After the log information output level change notification is sent to the base station, when a certain time has passed, the base station is notified to change the log information output level back to the output level when no event occurrence alarm has been received. A log collection method characterized by transmitting a message. The log collection method according to claim 4 or 5,
There are multiple types of log information,
In addition to the table in which the event type and the output level are associated with each other, a table in which the detail level of log information output is set for each of the plurality of types of log information for each output level is prepared.
A log information collecting method, wherein a change notification is transmitted to the base station so that log information is output at a level of detail obtained by referring to the table for each of the plurality of types of log information.

Images