Method and apparatus for detecting error in an IP-based bearer independent call control environment

• US 9,247,442 B2
• Filed: 01/24/2013
• Issued: 01/26/2016
• Est. Priority Date: 01/26/2012
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Lee, Kisun, Lee, Jounghwa
• Primary Examiner(s): Mesfin, Yemane
• Assistant Examiner(s): Chen, Peter
• Application Number:
  US13/749,300
• Publication Number:
  US 20130194909A1
• Time in Patent Office: 1,097 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04W 24/04 Arrangements for maintaining operational condition
• CPC Class Codes: H04W 24/08 Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 76/12 Setup of transport tunnels

Abstract

A call monitoring method for detecting an error in a Bearer-Independent Call Control (BICC) environment using an Internet Protocol (IP) as a bearer is provided, in which an MSC receives connection information about a called exchange from another MSC, requests IP resource allocation for configuring a termination to a Media GateWay (MGW) controlled by the MSC based on the received connection information about the called exchange, determines, upon receipt of a resource allocation failure message from the MGW, whether a cause of a resource allocation failure is an IP allocation error, and transmits the resource allocation failure message to a resource manager, if the cause of the resource allocation failure is an IP allocation error.

Claims

1. A call monitoring method for detecting an error at a Mobile Switching Center (MSC) in a Bearer-Independent Call Control (BICC) environment using an Internet Protocol (IP) as a bearer, the method comprising:

receiving connection information about a called exchange from an other MSC;

requesting IP resource allocation for configuring a termination to a Media GateWay (MGW) controlled by the MSC based on the received connection information about the called exchange;

determining, upon receipt of a resource allocation failure message from the MGW, whether a cause of a resource allocation failure is an IP allocation error;

setting associated IP resources as having an IP allocation error, if an IP resource allocation failure rate received from the resource manager exceeds a predetermined threshold;

isolating a BICC route including the IP resources from a service, if the IP resources are associated as having the IP allocation error; and

transmitting the resource allocation failure message to a resource manager, if the cause of the resource allocation failure is the IP allocation error,

wherein the isolating of the BICC route comprises transmitting error information about the IP resources associated as having the IP allocation error to the other MSC.

2. The method of claim 1, wherein the connection information about the called exchange includes a Codec negotiation result with the called exchange and a backbone network connection Identifier (ID).

3. The method of claim 1, wherein the resource allocation failure message is a predetermined error code value in an <

ADD REPLY>

Megaco message.

4. The method of claim 1, further comprising:

transmitting a recovery message for call recovery to the other MSC, upon receipt of the resource allocation failure message.

5. The method of claim 4, wherein the recovery message is a predetermined cause value in a Release (REL) message.

6. The method of claim 4, further comprising:

receiving a modify message from the other MSC to which the recovery message has been transmitted; and

requesting IP resource allocation for configuring a termination based on the received modify message to the MGW by the modify message.

7. The method of claim 1, further comprising:

receiving an error message indicating an IP bearer error in a connection to an other MGW connected to the MGW controlled by the MSC from the MGW controlled by the MSC; and

isolating a route directed to an MSC connected to the other MGW based on the received error message.

8. The method of claim 7, wherein the error message is transmitted in a <

NOTIFY>

Megaco message.

9. A call monitoring method for detecting an error at a Mobile Switching Center (MSC) in a Bearer-Independent Call Control (BICC) environment using an Internet Protocol (IP) as a bearer, the method comprising:

receiving an error message indicating an IP bearer error in a connection to an other Media GateWay (MGW) connected to an MGW controlled by the MSC from the MGW controlled by the MSC;

setting associated IP resources as having an IP allocation error, if an IP resource allocation failure rate received from a resource manager exceeds a predetermined threshold;

isolating a BICC route including the IP resources from a service, if the IP resources are associated as having the IP allocation error; and

isolating a route directed to an MSC connected to the other MGW based on the received error message,

wherein the isolating of the BICC route comprises transmitting error information about the IP resources associated as having the IP allocation error to the other MSC.

10. The method of claim 9, wherein the error message is transmitted in a <

NOTIFY>

Megaco message.

11. A call monitoring apparatus for detecting an error at a Mobile Switching Center (MSC) in a Bearer-Independent Call Control (BICC) environment using an Internet Protocol (IP) as a bearer, the apparatus comprising:

a first transceiver for transmitting and receiving connection information about a called exchange from an other MSC;

a second transceiver for transmitting and receiving an IP resource allocation request for configuring a termination and information indicating whether an IP resource allocation has been successful to and from a Media GateWay (MGW) controlled by the MSC based on data transmitted and received through the first transceiver;

a resource manager for storing the information indicating whether the IP resource allocation has been successful, transmitted and received through the second transceiver; and

a controller for determining whether an IP error has occurred based on data stored in the resource manager, the controller being configured to;

set associated IP resources as having an IP allocation error, if an IP resource allocation failure rate received from the resource manager exceeds a predetermined threshold; and

isolate a BICC route including the IP resources from a service, if the IP resources are associated as having the IP allocation error,

wherein the isolating of the BICC route comprises transmitting error information about the IP resources associated as having the IP allocation error to the other MSC.

12. The apparatus of claim 11, wherein the controller detects an IP resource allocation failure of an other MGW controlled by the other MSC based on data transmitted and received through the first transceiver.

13. The apparatus of claim 11, wherein, if an IP resource allocation failure rate is equal to or greater than a threshold, the resource manager determines that associated IP resources have an IP error.