KR102077125B1 - Apparatus and method for restoring call fail - Google Patents

Abstract

Call failure recovery apparatus according to the present invention, the log collection unit for collecting log records of the terminal; A log analyzer extracting a call failure log from the collected log records, and filtering only a call failure log based on a specific cause for which a connection failure of the call failure log is preset; And a control unit controlling to recover from a call failure by disconnecting and reconnecting a call when the call failure log based on the filtered specific cause occurs more than a reference number within a predetermined reference time.

Description

Device and method for recovering call failure in mobile communication system {APPARATUS AND METHOD FOR RESTORING CALL FAIL}

The present invention relates to an apparatus and method for recovering a call failure in a mobile communication system. More particularly, when data transmission is impossible due to a call failure between a terminal and an exchange, the cause of the call failure is diagnosed, An apparatus and method for recovering a call failure that can be automatically recovered.

Since an LTE network is an all-IP network between entities, all the traffic flows from a radio link connecting a user terminal to a base station to a packet data network (PDN) connecting to a service entity is based on IP.

In such an LTE network, due to various reasons, a call connection fails or is disconnected, and thus a state in which data transmission is impossible is generated. For example, an error of a mobile communication module of a terminal, a problem in a wireless environment, hardware equipment on a base station or a core network For example, the problem.

In the conventional mobile communication system, if the data connection is impossible due to a call connection failure, the operator of the exchange directly checks the call failure status and delivers it directly to the terminal user to manually reconnect or the terminal to 3G in LTE. We used CSFB (Circuit Switch-Fallback) to disconnect from LTE switch and reconnect.

However, despite the fact that call failure based on a certain cause may occur repeatedly among the causes causing such a call failure, the conventional system has a disadvantage in that real-time recognition and action cannot be made for a call failure based on such a specific cause.

SUMMARY OF THE INVENTION An object of the present invention for solving the above problems is to provide an apparatus and method for recovering a call failure of a mobile communication system that can automatically reconnect a call on a system with respect to a terminal where call failure frequently occurs based on a specific cause. There is.

According to an aspect of the present invention, there is provided a call failure recovery apparatus, comprising: a log collecting unit for collecting log records on call processing of a terminal; A log analyzer extracting a call failure log from the collected log records, and filtering only a call failure log based on a specific cause for which a connection failure of the call failure log is preset; And a control unit controlling to recover from a call failure by disconnecting and reconnecting a call if the call failure log based on the filtered specific cause occurs more than a reference number within a predetermined reference time. By a recovery device.

Here, the log analyzer may filter the call failure based on the reason that the call failure can be recovered upon reconnection after the call connection release by the controller in the call failure log.

Here, the log analyzer may filter only a call failure log in which the cause of the call connection failure among the call failure logs is Transport Resource Unavailable.

In addition, the above object is, according to the present invention, a call failure recovery method comprising the steps of: collecting log records on the call processing of the terminal; Extracting a call failure log from the collected log records; Filtering only a call failure log based on a specific cause in which the cause of the call connection failure in the extracted call failure log is preset; Determining whether a call failure log based on the filtered specific cause has occurred more than a reference number within a predetermined reference time; And reestablishing a call connection with the terminal and recovering a call failure.

The filtering may include filtering only a call failure log in which a connection failure of the call failure log is a transport resource unavailable.

Accordingly, an apparatus and method for recovering a call failure of a mobile communication system capable of automatically reconnecting a call to a system for a terminal frequently causing a call failure based on a specific cause can be provided.

1 is a block diagram of a mobile communication system according to the present invention.
2 is a block diagram of a call failure recovery apparatus according to the present invention.
3 illustrates a call reconnection procedure of a mobile communication system according to the present invention.
4 is a flowchart of a call failure recovery method according to the present invention.

It is to be noted that the technical terms used herein are merely used to describe particular embodiments and are not intended to limit the present invention. In addition, the technical terms used in the present specification should be interpreted as meanings generally understood by those skilled in the art to which the present invention belongs, unless specifically defined otherwise in the present specification, and are overly inclusive. It shall not be construed in the sense of or in the sense of being excessively reduced. In addition, when the technical terms used herein are incorrect technical terms that do not accurately express the spirit of the present invention, they should be replaced with technical terms that can be properly understood by those skilled in the art. In addition, the general terms used in the present invention should be interpreted as defined in the dictionary or according to the context before and after, and should not be interpreted in an excessively reduced sense.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings, and the same or similar components will be given the same reference numerals regardless of the reference numerals and redundant description thereof will be omitted. In addition, in describing the present invention, when it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, it should be noted that the accompanying drawings are only for easily understanding the spirit of the present invention and should not be construed as being limited to the spirit of the present invention by the accompanying drawings. The spirit of the invention should be construed to extend to all changes, equivalents, and substitutes in addition to the accompanying drawings.

1 is a block diagram of a mobile communication system according to the present invention.

As shown, the mobile communication system according to the present invention is a terminal 200, eNB 310, S-GW 320, P-GW 330, PDN 400, MME 340, ESM 350 ), The call failure recovery apparatus 100 may be included.

In the present specification, a description of specific components for constituting a mobile communication system that can be understood by those skilled in the art will be omitted, and a call failure, which may be referred to as a specific idea of the present invention, will be omitted. The recovery operation will be described in detail.

The terminal 200 is a mobile communication module (not shown), a Wi-Fi (Wireless LAN), a Wimax (World Interoperability for Microwave Access), and HSDPA (High Speed) for transmitting and receiving wireless signals with a base station, an exchange, and another terminal in a mobile communication network. A wireless internet module (not shown) for wireless internet access, a user input module (not shown), a display module (not shown), etc. for receiving a user's key input for the operation of the terminal 200 based on downlink packet access) It may include, in a specific embodiment is not limited thereto.

Among the components illustrated in FIG. 1, an evolved Node B (eNB) 310, a Serving Gateway 320 (S-GW), a Packet Data Network Gateway (P-GW) 330, a Mobile Mobility Entity (MME) 340, and the like may be used. Each entity may be defined in an Evolved Packed Core network architecture defined in 3GPP.

Evolved Packed Core (EPC) is a set of network nodes for 3GPP LTE system. Evolved Core Network of the existing 3GPP system architecture, Evolved RAN, E-UTRAN (Evolved-UMTS) Terrestrial Radio Access Network), and has an efficient network structure that simplifies the network node to improve the efficiency of the packet network.

Briefly describing each entity, the eNB 310 is a base station of the LTE system, plays a role of relaying traffic between the network and the terminal 200, and measures signal strength and quality, baseband signal processing, and channel card. (channel card) Can perform functions such as resource management.

The S-GW 320 is a session control and user plane node that processes payload traffic according to an established session. The S-GW 320 interworks with an eNB 310 through an S1-U interface and performs an Inter LTE / 3GPP hand. It supports the over, configures the P-GW 330 and the EPS bearer (Evolved Packet System bearer) and delivers a packet data unit (PDU) using tunneling (Tunneling).

The P-GW 330 allocates IP of the terminal 200 and maintains routing information with the S-GW 320 and the external network for the packet service as a session control and user plane that interworks with an external Internet network and a non-3GPP network. It has tunneling and IP routing functions.

The MME 340 sets an EPS bearer (Evolved Packed System bearer) to control the call connection between the terminal 200 and the core network.

More specifically, as a node managing subscriber information and mobility of the terminal 200, the node manages session management, idle subscriber management, paging, and subscriber authentication functions.

That is, the MME 340 processes the control signal when there is a join request or a radio bearer setup request from the terminal 200 or another network node such as the P-GW 330 or the S-GW 320. It may be responsible for various functions of a control plane such as a control plane, and performs functions such as setting up the EPS bearer or setting up an IP tunnel and mobility management.

The EPS Session Management (ESM 350) manages a session including a default bearer as a protocol stack of a control plane in an Evolved Packed System (EPS), and includes a terminal 200, an eNB 310, and an MME in an EPC. 340, a log record on the call processing of the terminal 200 generated through the ESM 350 may be collected and stored.

Here, the log record collected by the ESM 350 includes a destination IP and a source IP transmitted in a call processing process between the terminal 200 and the eNB 310, the eNB 310, and the S-GW 320. (Source IP), Tunnel Endpoint Identifier (TEID), and the like, and may include information on the occurrence of call failure and the cause of call failure coming from the MME 340, S-GW 320, and the EPS stage. May be included.

The call failure recovery apparatus 100 analyzes the logs collected by the ESM 350 and controls to automatically recover the call failure.

The call failure recovery apparatus 100 analyzes a log record of the terminal 200, extracts a call fail log, and based on a specific cause in which the cause of the call connection failure is extracted from the extracted call failure log. Only the call failure log may be filtered, and if the call failure log based on the filtered cause occurs more than the reference number within a predetermined reference time, the failed call may be automatically recovered.

In this case, the call failure recovery apparatus 100 may request a reconnection with the terminal 200 to the MME 340 processing a control signal of the terminal 200 and another node, and the MME 340 according to the request, The call failure may be recovered by detaching and reattaching the call connection with the terminal 200 to form a default bearer.

In the present specification, the call failure recovery apparatus 100 performs some functions of the MME 340 and the ESM 350, or transmits a control command to the MME 340 and the ESM 350 to perform a specific operation. In this case, the call can be automatically recovered.

Hereinafter, the configuration of the call failure recovery apparatus 100 will be described with reference to FIG. 2.

As shown in FIG. 2, the call failure recovery apparatus 100 according to the present invention may include a log collector 110, a log analyzer 120, and a controller 130.

The log collector 110 collects log records on the call processing of the terminal 200.

Here, the log record of the terminal 200 is not a log record related to the processing inside the terminal 200, but the terminal 200, the eNB 310, the S-GW 320, and the P on the mobile communication system during the call processing. It may include a log record collected between each entity including the GW 330, MME (340).

The log collector 110 may refer to the log records collected by the ESM 350, and the collected log records may be related to the occurrence of call failures and the causes of call failures that may occur between respective entities on the mobile communication system. Information may be included.

The log analyzer 120 extracts a call fail log from the collected log records, and filters only the call failure log based on a specific cause in which the cause of the call connection failure is preset in the extracted call failure log.

As a cause of the call failure, an error in the mobile communication module of the terminal 200, a problem in the wireless environment, a missing Naver list, a delay in handover, the absence of a dominant pilot, the absence of a serving pilot, the hardware equipment of a base station or a core network system For example, the problem of, cell mismatch and lack of uplink coverage.

Here, the preset specific cause is registered in advance by the operator of the MME or ESM, and when the cause occurs and a call failure occurs, when the call failure recovery apparatus 100 disconnects the call and reconnects, the recovery is performed. Only possible causes may be included.

For example, a case in which a call failure recovery apparatus 100 may recover when a call is disconnected and then reconnects, and a call failure occurs due to a transport resource unavailable, for example. It is not.

Transport resource unavailable (Traffic Resource Unavailable), specifically, when trying to transmit data due to the call connection attempt or handover of the terminal 200 generates a Tunnel Endpoint Identifier (TEID), the TEID already in use to a new call In case of allocation, call transmission may fail due to such transmission resource allocation failure.

The transmission resource allocation failure may have a great effect on the service since the actual frequency of occurrence is high. When the call failure is automatically recovered through the call failure recovery apparatus 100 as in the present invention, the effect is great.

The controller 130 checks whether a call failure log based on the filtered specific cause has occurred more than a reference number within a predetermined reference time.

As a result of the check, if a call failure log based on a specific cause occurs more than the reference number within a predetermined reference time, the controller 130 detaches the call connection with the terminal 200 and then reattaches the call failure. Control to recover.

In this case, the controller 130 requests reconnection to the MME 340, and the MME 340 reattaches after detaching a call connection with the terminal 200 according to the request of the controller 130. Call failure can be recovered by forming a default bearer.

The call failure recovery apparatus 100 of the mobile communication system according to the present invention described above frequently generates call failures based on a specific cause such as transport resource unavailable through collecting and analyzing call failure logs. Since the terminal 200 is configured to automatically reconnect the call on the system, it is possible to minimize the data service interruption time due to the call failure.

3 illustrates a call reconnection procedure of a mobile communication system according to the present invention.

When the terminal 200 transmits a service request message to the eNB 310 for initial call connection (S110), the eNB 310 transmits an initial context setup message to the MME 340 (S120).

In this case, when a call failure occurs, the call failure recovery apparatus 100 performs a process for automatic recovery.

Specifically, by analyzing the log records of the terminal 200, extracting the call failure log, and filtering only the call failure log based on a specific cause of the cause of the call connection failure from the extracted call failure log, the filtered If the call failure log based on the cause occurs more than the reference number within a predetermined reference time, the MME 340 requests the recovery of the call failure (S130).

In this case, when a call failure occurs due to a specific cause, such as transmission resource allocation failure, it is confirmed that normal data service is possible through the following call reconnection process, and the call failure recovery apparatus 100 is thus capable of reconnection. The occurrence of specific causes of call failures can be filtered through log records.

The MME 340 transmits a detach request message to the terminal 200 in order to reconnect with the terminal 200 (S140), and the terminal 200 sends a detach accept message to the MME 340 via the eNB 310. By transmitting (S150), the connection is released.

After transmitting the detach accept message, the terminal 200 transmits an attach request message to the MME 340 and requests reconnection of the call (S160).

The MME 340 transmits an attach accept message to the terminal 200 (S170), and a default bearer is formed between the MME 340 and the terminal 200, thereby completing the reconnection of the call (S180).

4 is a flowchart of a call failure recovery method according to the present invention.

The call failure recovery apparatus 100 collects log records on call processing of the terminal 200 (S210).

At this time, in the call processing collected by the ESM 350, it is possible to refer to a log record collected between each entity including a terminal, eNB, S-GW, P-GW, and MME on the mobile communication system. May include information regarding the occurrence of a call failure and the cause of the call failure that may occur between each entity.

The call failure recovery apparatus 100 extracts a call failure log from the collected log records (S220).

As a cause of the call failure, an error in the mobile communication module of the terminal 200, a problem in the wireless environment, a missing Naver list, a delay in handover, the absence of a dominant pilot, the absence of a serving pilot, the hardware equipment of a base station or a core network system For example, the problem of, cell mismatch and lack of uplink coverage.

When the call failure log is extracted, only the call failure log is filtered based on a specific cause in which the cause of the call connection failure is preset (S230).

Here, the predetermined specific cause is registered in advance by the operator, and when the cause occurs and the call failure occurs, the call failure recovery apparatus 100 includes only the cause that can be recovered by reconnecting after disconnecting the call. can do.

For example, a case in which a call failure recovery apparatus 100 may recover when a call is disconnected and then reconnects, and a call failure occurs due to a transport resource unavailable, for example. It is not.

In particular, the transmission resource allocation failure generates a Tunnel Endpoint Identifier (TEID) when attempting to transmit data due to a call connection attempt or handover of the terminal 200. When a TEID that is already in use is allocated to a new call, The same connection resource allocation failure may occur and call connection may fail.

On the other hand, the call failure recovery apparatus 100 checks whether the call failure log based on the specific cause has occurred more than the reference number within the reference time (S240).

As a result of the check, when a call failure log based on a specific cause occurs more than a reference number within a predetermined reference time, the call failure recovery apparatus 100 detaches and reattaches the call connection with the terminal 200. Recover call failure (S250).

In this case, the call failure recovery apparatus 100 requests reconnection to the MME, and according to the request, the MME detaches and then reattaches the call connection with the terminal 200, thereby resetting the default bearer. ), Call failure can be recovered.

In the above-described call failure recovery method of the mobile communication system according to the present invention, through the collection and analysis of the call failure log, the terminal 200 frequently occurs a call failure based on a specific cause, such as transport resource unavailable ), It is configured to automatically reconnect the call on the system, thereby minimizing data service downtime due to the call failure.

As mentioned above, although embodiment of this invention was described, those of ordinary skill in the art should add, change, delete, add, etc. the component within the range which does not deviate from the idea of this invention described in the claim. The present invention may be modified and changed in various ways, which will also be included within the scope of the present invention.

100: call failure recovery device 110: log collection unit
120: log analysis unit 130: control unit
200: terminal 310: eNB
320: S-GW 330: P-GW
340: MME 350: ESM
400: PDN

Claims (5)

In the call failure recovery apparatus,
A log collecting unit collecting log records on call processing of the terminal;
A log analyzer extracting a call failure log from the collected log records, and filtering only a call failure log based on a specific cause for which a connection failure of the call failure log is preset; And
If the call failure log based on the filtered specific cause occurs more than the reference number within a predetermined reference time, and disconnects the call connection with the terminal and reconnect, and includes a control unit for controlling to recover the call failure,
The log analysis unit,
The call failure recovery device of the call failure log to filter the call failure log based on the cause of the recovery of call failure when reconnection after call disconnection by the control unit to the call failure log based on the specific cause. delete The method of claim 1,
The log analysis unit,
The call failure recovery apparatus for filtering only the call failure log of the cause of the call connection failure of the call failure log is Transport Resource Unavailable. In a call failure recovery method,
Collecting, by the call failure recovery apparatus, log records on call processing of the terminal;
The call failure recovery apparatus extracting a call failure log from the collected log records;
Filtering, by the call failure recovery apparatus, only a call failure log based on a specific cause in which the cause of the call connection failure is preset in the extracted call failure log;
Determining, by the call failure recovery apparatus, whether a call failure log based on the filtered specific cause has occurred more than a reference number within a predetermined reference time; And
The call failure recovery apparatus releases the call connection with the terminal and reconnects to recover the call failure.
The filtering step,
The call failure recovery method of the call failure log, the call failure log based on the cause that can recover the call failure when reconnection after call disconnection to the call failure log based on the specific cause. The method of claim 4, wherein
The filtering step,
The call failure recovery method for filtering only the call failure log of the cause of the call connection failure of the call failure log (Transport Resource Unavailable).

Images