BICC IP Resource Allocation Error Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In BICC environments, IP bearer errors during data transmission and reception between Media GateWays lead to inefficient resource management and increased server load due to the inability to detect call errors without managerial intervention.
Innovation Solution
A call monitoring method and apparatus that detect IP resource allocation failures at a Mobile Switching Center, isolate affected routes, and notify a resource manager to manage resources effectively, allowing for error detection and alternative route selection without managerial intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If IP bearer is used for data transmission between MGWs, then resource allocation flexibility is improved, but error detection capability deteriorates
Solution Approach 1:
The patent introduces an intermediary error detection mechanism that operates between the IP bearer layer and the BICC signaling layer. This intermediary monitors IP allocation status and error conditions, translating them into detectable signals without disrupting the flexible IP-based resource allocation. The intermediary layer captures error information from IP resource allocation failures and transmits it through the signaling connection to the calling MSC, thereby maintaining both flexibility and reliability.
2Measurement precision
If manual intervention is required for error detection, then measurement precision is improved, but ease of operation deteriorates
Solution Approach 1:
The system implements self-service error detection where the network automatically monitors and reports IP bearer errors without requiring manual intervention. The MGW autonomously detects IP allocation failures and transmits error information through the signaling connection to the MSC, which then routes the error message to the appropriate resource manager. This automated process maintains high detection accuracy while eliminating the need for manual error checking.
Solution Approach 2:
The patent establishes a feedback mechanism where error information flows back from the MGW through the signaling connection to the MSC and ultimately to the resource manager. This feedback loop enables continuous monitoring and automatic response to IP bearer errors, maintaining precise error detection while operating autonomously without manual intervention.
3Ease of operation
If error detection is implemented without managerial intervention, then ease of operation is improved, but device complexity increases
Solution Approach 1:
The patent leverages the existing BICC signaling connection and H.248 interface between MGW and MSC for multi-purpose use. The same signaling channels used for normal call control and resource management are also utilized for error detection and reporting. This universal use of existing interfaces enables automated error handling without adding separate dedicated error detection infrastructure, thereby limiting the increase in system complexity.
4Productivity
If IP resource allocation failure is not detected, then productivity is maintained, but loss of information increases
Solution Approach 1:
The system performs preliminary error detection at the point of IP resource allocation failure in the MGW, before the error can propagate and cause call processing issues. By detecting and reporting errors at this early stage through the signaling connection, the system prevents information loss while maintaining normal call processing productivity for unaffected calls.
Data Source
AI summary
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.


