A-Interface Circuit Sharing in the MSC Pool

benjamin.omeke
benjamin.omeke  Diamond  (1)
7 years 10 months ago  View: 2127  Reply: 1
1F


This feature enables the media gateway (MGW), UMG8900, to assign A-interface circuit resources configured at the local office (adopting the MSC pool networking) to terminals upon receiving A-interface circuit assignment requests from the mobile switching center (MSC) server. In the traditional networking mode, each base station controller (BSC) are connected only to its corresponding MSC server. Therefore, A-interface circuits of a BSC are managed by only one MSC server. In the MSC Pool networking mode, each BSC are connected to multiple MSC servers in the resource pool. Therefore, A-interface circuits of a BSC are able to be managed by multiple MSC servers. Each MSC server, however, can manage only the circuit resources allocated to it. As a result, circuit resources cannot be dynamically adjusted among multiple MSC servers, leading to low usage of A-interface circuit resources and complexity in maintenance work.

To tackle this issue, management of A-interface circuits is transferred from the MSC server to the MGW.


Benefits for Carriers:

  • Increased usage of A-interface circuit resources and reduced investment on A-interface circuit devices
  • Simplified maintenance work and capacity expansion

Node requirements:

UAWEI UMG8900 V200R007C03 and later
HUAWEI MSOFTX3000 V100R006C02(CPCI) and later;
HUAWEI MSOFTX3000 V200R008C02(ATCA) and later



Impact on the System

This feature has no adverse impact on the system.


Application Limitations

The feature can be applied only when the BSCs in the MSC Pool are provided from Huawei if the A-Flex function is implemented by the BSC.


Interaction with Other Features

Feature Interaction

WUFD-071100 Support A-Flex Networking (MGW Agent)

The MGW can provide the MSC pool networking with the MGW proxy A-Flex feature, that is, the MGW supports the NAS node selection function (NNSF) feature, only when this feature and the A-Flex networking (MGW agent) feature are enabled.

Application Scenario

  • This feature and the A-Flex networking (MGW agent) are used together to build 2G MSC Pool networking.
  • This feature and the A-Flex feature are used together to build the 2G part of 2G/3G hybrid MSC Pool networking.

Implementation Principle

The MGW manages the A-interface circuit resources, including circuit selection, preemption, dialing tests, reseting, blocking, and unblocking. To improve the TDM resource usage and facilitate TDM resource management, the MGW manages the TDM resources by trunk groups. Each BSC can have a maximum of eight trunk groups.

The mappings between BSCs and trunk groups are determined by the destination signaling points (DSPs) and network identifications (NIs). A DSP and an NI uniquely identify a BSC. In addition, if several trunk groups have the same DSP and NI as that of a BSC, the trunk groups map the BSC.

Management of A-interface circuit resources are classified into the following types by specific operations:
  • Circuit preemption, selection and dialing test, which are originated by MSC server and performed by the MGW
  • Circuit reset, which is originated by the MGW or the BSC and the MSC server forwards the reset messages exchanged between the MGW and the BSC
  • Circuit or circuit group blocking and unblocking, which are originated by the BSC and performed by the MGW and the MSC server forwards the reset messages exchanged between the MGW and the BSC
The implementation of the A-interface circuit resource management is as follows:
  • Upon receiving a circuit preemption or selection from the MSC server, the MGW determines the corresponding BSC based on the DSP and NI contained in the request. It also determines the A-interface trunk group based on the bearer capability. Then, it performs the corresponding operation on all the A-interface circuits of the trunk group based on certain algorithms.
  • Upon receiving a request from the MSC server for resetting or blocking a specified circuit, the MGW determines the TDM termination corresponding to the circuit based on the DSP, NI, bearer capability, and circuit identification code (CIC) contained in the request. Then, it performs the corresponding operation on the TDM termination.
  • Upon receiving a request from the MSC server for blocking or unblocking all the A-interface circuits of a specified BSC, the MGW determines the corresponding BSC based on the DSP and NI contained in the request. It also selects the A-interface trunk group based on the bearer capability. Then, it performs the corresponding operation on all the TDM terminations of the trunk group.

user_2837311
user_2837311  Diamond 
3 years 11 months ago
2F
useful document, thanks