MSC Pool: About This Chapter
MSC Pool: About This Chapter
41 MSC Pool
41.1 Overview
This describes the advantages of the MSC pool. The MSC pool implements resource sharing
and load balancing for even distribution of traffic in the MSC pool; thus reducing inter-MSC
handovers and realizing redundancy backup.
41.2 Availability
This lists the NEs, software, and other conditions required for the implementation of the MSC
pool.
41.3 Technical Description
This describes the technical aspects of the MSC pool. Through the MSC pool, the NAS node
can be selected according to the load balancing algorithm. For example, new MSs are assigned
to different MSCs in the MSC pool according to this algorithm; thus implementing the load
balancing between MSCs in the MSC pool.
41.4 Capabilities
This describes the capabilities of the MSC pool.
41.5 Implementation
This describes how to configure and verify the MSC pool.
41.6 Maintenance Information
This lists the alarms related to the MSC pool.
41.7 References
41.1 Overview
This describes the advantages of the MSC pool. The MSC pool implements resource sharing
and load balancing for even distribution of traffic in the MSC pool; thus reducing inter-MSC
handovers and realizing redundancy backup.
Definition
Multiple MSCs constitute an MSC pool. The BSC connects to each MSC in the MSC pool.
Purposes
Based on the 3GPP 23.236-630 protocol, the MSC pool features the following:
l The load balancing and resource sharing between MSCs in the MSC pool can increase the
network capacity and reduce the investment in equipment.
l The even allocation of resources between the MSCs in the MSC pool realizes the
redundancy backup.
l The reduced handovers between the MSCs in the MSC pool improve the network quality.
Terms
Terms Definition
Terms Definition
CN Core Network
41.2 Availability
This lists the NEs, software, and other conditions required for the implementation of the MSC
pool.
NEs Involved
Table 41-1 lists the NEs involved in the MSC pool.
√ - √ √ √ - - √
NOTE
l -: not involved
l √: involved
Software Releases
Table 41-2 describes the versions of GBSS products that support the MSC pool.
Miscellaneous
The precautions for using the MSC pool are as follows:
l To implement the MSC pool, licenses are required and the MSC pool Function
Enabled must be configured at the BSC side.
l In actual networking, the interconnected MSCs must support the MSC pool. At present,
only the MSCs that are interconnected to Huawei core network devices can use the MSC
pool.
l After the MSC pool is enabled at the BSC side, the TMSI re-allocation function must be
enabled at the MSC side.
l If the BSC supports the MSC pool, the following data of the BSC must be the same as that
of the MSC:
– NRI length and NRI and DPC Route
– NULL_NRI and NULL_NRI and DPC Route
– MSC Available Capacity, MNC, CN ID, and MSC Administration State
l In the BSC6000V900R003, the MSC pool in the CS domain rather than the PS domain is
implemented.
CS pool-area 1 CS pool-area 2
PS pool-area 1 PS pool-area 2
SGSN3 SGSN6
SGSN4
SGSN5
NOTE
The NRI is a binary digit of 0 to 10 bits. It is used to identify each CN node in the MSC pool.
On the BSC, the NRI is placed in a specified segment in the TMSI of the CN node. The NRI
begins at the twenty-third bit, as shown in Figure 41-2.
31 30 29 28 27 26 25 24 23 22 21 20 19 18 …… 1 0
The NRIs in a MSC pool must be equal in length. If two MSC pools overlap, the NRIs in the
two MSC pools must be equal in length.
The load balancing algorithm consists of the algorithm defined by protocols and random number
algorithm.
The (V, MSC) relation table is generated by the BSC based on the status and available capacity of
each MSC in the MSC pool. According to this algorithm, the loads of the MSC relate to the
distribution of the IMSI, which cannot fully implement the load balancing function.
l Random number algorithm
When the NAS message of the MS carries IMSI/IMEI/NULL_NRI, the BSC chooses a
random number from 0 to 999 to be the value V. Then, the BSC queries the (V, MSC)
relation table to determine the MSC for the current service.
The two algorithms differ in the way of generating the value V but share the same way of
choosing the MSC.
CAUTION
To use the random algorithm, ensure that the TMSI re-allocation function is enabled at the MSC
side.
If the random number algorithm is used, the mapping between the IMSI and MSC are uncertain.
l If the TMSI re-allocation function is not enabled on the MSC, the MS initiates a call carrying
an IMSI and the BSC assigns the MS to other MSCs at random. The VLR of the other
MSCs does not contain the user data; thus, the call fails.
l If the TMSI re-allocation function is enabled on the MSC, the MS can use the TMSI to
initiate a call; the call thus succeeds.
The mapping between the NRI and MSC is defined in data configuration. An NRI corresponds
to only one MSC while an MSC can correspond to multiple NRIs.
When an MS uses the TMSI to update the location or initiate a call, the BSC can determine the
office by parsing the NRI value in the TMSI and querying the mapping between the NRI and
the MSC.
l If the BSC cannot find the corresponding MSC, or the MSC is in the unavailable state, or
the MSC Administration State is inhibited, the BSC uses the random number algorithm
to select an MSC from the MSCs that are normal and available.
l If the value of the NRI is NULL_NRI, the BSC uses the random number algorithm to select
an MSC from the MSCs that are normal and available.
NOTE
The NULL_NRI is defined in the data configuration. It must be the same as that in the MSC configuration.
If only one operator is in the PLMN network, the NULL_NRI is unique. When more than one operator is
in the PLMN network, each operator has a NULL_NRI. A BSC can be configured with up to five
NULL_NRIs.
After the offload, you must set the administration state of MSC1 to normal; otherwise, MSC1
cannot receive the information about the newly registered users.
NOTE
By default, the period for broadcasting the private message is one hour. The period can be set on the NSS.
If the available capacity in the private message is directly used as a load balancing parameter,
the MSC Available Capacity set at the BSC side is invalid and unavailable for later use. To
solve the problem that the BSC configuration data does not take effect, the following formula
is adopted:
MSC available capacity = MSC Available Capacity configured by the BSC - (total MSC
capacity in the private message - MSC available capacity in the private message)
When the MSC Available Capacity configured by the BSC is of great difference from the total
MSC capacity in the private message, the result may be equal to or smaller than 0. In this case,
the capacity is considered to be 0.
The MSC sends the configuration message to notify the BSC of the current MSC status. In this
way, the MSC is offloaded.
The MSC can query the current MSC status saved on the BSC. If the MSC considers that the
query result is abnormal, it can send the configuration message to the BSC to re-set the MSC
status.
The changes of the BSC message processing on the A interface are as follows:
41.4 Capabilities
This describes the capabilities of the MSC pool.
l Each MSC/VLR can have up to eight NRI values at the same time.
l Each BSC can be configured with 1024 NRI values.
l Each BSC can be configured with five NULL_NRI values and each NULL_NRI value can
be configured with 32 MSCs.
41.5 Implementation
This describes how to configure and verify the MSC pool.
Prerequisite
l The BSC and MSC are Huawei devices.
l The MSC version supports the MSC pool.
l The BSC connects to the core network correctly.
l The MSC server interconnects to the MGW and the relevant data is configured correctly.
Context
This describes the application of the MSC pool on the BSC.
Procedure
Step 1 Configure the data of the MSC server and the MGW.
1. For Huawei core network devices, enable the MSC pool on the MSC.
2. Set A-Flex to Yes.
3. Plan the following configuration data of the MSC related to the MSC pool: NRI,
NULL_NRI, MSC Available Capacity, MNC, and CN ID.
For details of setting parameters, refer to the user manuals related to the MSC products.
3. The BSC supports the MSC pool after the license is activated. Set the attributes of related
objects and parameters on the BSC6000 Local Maintenance Terminal.
Step 3 Add a DSP
1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-
click BSC6000, and then choose Configure SS7 Signaling Point on the shortcut menu. A
dialog box is displayed, as shown in Figure 41-3.
In Figure 41-3, click the DSP tab.
CAUTION
The DPCGIndex maps the Port No.. Configure the Start CIC of this port.
The start CICs of different ports within a DPC group cannot be duplicate.
2. Configure the parameters displayed in Figure 41-7 and then click Finish. The configuration
of the MSC pool parameters is complete.
Step 6 Configuring the NRI and DCP route
1. Click the NRI and DPC Route tab in Figure 41-7. A tab page is displayed, as shown in
Figure 41-8.
----End
Prerequisite
l The BSC and MSC are Huawei devices.
l The MSC version supports the MSC pool.
l The BSC connects to the core network correctly.
l The MSC server interconnects to the MGW and the relevant data is configured correctly.
l The MSC pool is configured correctly.
Context
The MSC pool is verified with the load balancing algorithm.
Procedure
l Select Random Algorithm in the MSC Pool Load Balancing Algorithm Selection table.
1. After the MS is switched on, its location is updated.
– Use the IMSI to update the location.
The MS is assigned to the MSC in the MSC pool at random. The MSC with higher
available capacity is more probable to be chosen.
– Use the TMSI to update the location.
The MS is assigned to the DPC (MSC) mapping the NRI in the TMSI.
2. After the location of the MS is updated, the MSC assigns the TMSI to the MS. This
MSC provides later service for the MS.
3. When the MS initiates a call or other services again, it is assigned to the MSC.
l Select Based on MSC ID Algorithm in the MSC Pool Load Balancing Algorithm
Selection table.
1. Each time the location of the MS is updated through the IMSI or a call is initiated, the
BSC assigns the MS to a specified MSC.
----End
Alarms
If multiple DSPs are supported, the DPC information is added to the alarms related to the MSC
for distinguishing different MSCs. Table 41-3 lists the alarms related to the MSC pool.
Performances
None.
41.7 References