BSC-MSC Connectivity Check via A-Interface Loopback Signaling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for checking connectivity between a BSC and an MSC during a calling process are cumbersome and inefficient, leading to increased maintenance costs due to the difficulty in quickly locating circuit errors.

Innovation Solution

A method involving the MSC sending a Connectivity Check command to the BSC, with the BSC performing a connectivity check and responding with a success identifier or Clear Request message to cancel the self-loop, allowing for quick identification of connection issues without altering the calling process flow.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional methods (loopback, pulling E1, specifying circuit for Call-Testing) are used to check connectivity, then circuit errors can be detected, but the process is troublesome and time-consuming, increasing maintenance cost

Engineering Contradiction:
Improvecircuit error detection capabilityVSAvoidmaintenance time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by performing connectivity check during the calling process establishment phase, before actual service delivery. The network element inserts a connectivity check identifier in the setup message, and the called side performs loopback and returns the identifier in the answer message, completing the connectivity verification before the call is fully established, thus avoiding separate maintenance testing time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies self-service by enabling the network elements themselves to perform connectivity verification during normal calling operations. The called network element automatically performs loopback and returns the connectivity check identifier without requiring external maintenance personnel intervention, making the system self-diagnosing during operational phases

Inventive Principle:
Principle #25Self-service

2Reliability

If traditional methods are used to check E1 connections, then connection correctness can be verified, but the process is cumbersome requiring manual intervention at both ends, increasing maintenance complexity

Engineering Contradiction:
Improveconnection verification accuracyVSAvoidmaintenance operation simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent enables self-service by having the called network element automatically perform the loopback operation and return the connectivity check identifier to the calling element. This eliminates the need for maintenance personnel to manually configure loopback at both ends, reducing operational complexity while maintaining verification accuracy through automated identifier matching

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback by having the called network element return the connectivity check identifier in the answer message to the calling element. This closed-loop feedback mechanism automatically confirms connection correctness without manual intervention, simplifying the maintenance operation while ensuring accurate verification through identifier matching

Inventive Principle:
Principle #23Feedback

3Productivity

If connectivity check is integrated into calling process, then error detection efficiency is improved, but the calling process flow must be modified

Engineering Contradiction:
Improveerror detection efficiencyVSAvoidcalling process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies universality by making the calling process serve dual functions: both establishing service connections and performing connectivity verification. The setup and answer messages are used for both their original calling functions and as carriers for connectivity check identifiers, eliminating the need for separate verification procedures and improving error detection efficiency without significantly increasing process complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system merges connectivity verification functionality into the existing calling process flow. The connectivity check identifier is embedded within the standard setup and answer messages, combining the service establishment and connectivity verification functions into a single integrated process, thereby improving efficiency while maintaining relatively simple process structure

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS7974594B2Method for checking connectivity between base station controller and mobile switching center
Publication Date: 2011.07.05 HUAWEI TECH CO LTD
  • US7974594B2 patent drawing
  • US7974594B2 patent drawing
  • US7974594B2 patent drawing

AI summary

The present invention relates to a method for checking connectivity between a BSC (Base Station Controller) and an MSC (Mobile Switching Center), including: the MSC loopbacking a circuit and sending a connectivity check command to the BSC to instruct the BSC to perform the connectivity check; the BSC performing the connectivity check according to the connectivity check command; if the connectivity check is successful, the BSC sends a Connectivity Check Success identifier to the MSC to instruct the MSC to cancel the self-loop of the circuit; if the connectivity check fails, the BSC sends a Clear Request message to the MSC to release the communication connection and cancel the self-loop of the circuit. Embodiments of the present invention implement quick and convenient locating of connection errors by adding a Connectivity Check command in the messages for A-interface.