Generally, when the MSOFTX3000 is connected to an RNC, the RNC can belong to only one MGW. When the MGW of the RNC is faulty or the bearer between the RNC and the MGW is faulty, all the services of the RNC may be interrupted. To prevent the service interruption due to the MGW upgrade, MGW failure, or the failure of bearer between the MGW and RNC, the Mini_Iu_FLEX is introduced to implement the load sharing of the service management by  allowing one RNC to connect to multiple MGWs.

 

Therefore, when one MGW is faulty or the bearer between the MGW and the RNC is faulty, the MSC server can interact with another MGW connecting to the RNC to avoid the service interruption. In addition, to save TC resources to the maximum extent and reduce the traffic connection between the MGWs in an MSC, the system can preferentially select the circuit resources of the same MGW if the RNC of a calling party and the RNC of a called party are connected to the same MGW.

 

The following functions are implemented through the Mini_Iu_FLEX networking:

 

• When one RNC is connected to multiple MGWs, the MSOFTX3000 can select the circuit resource of the corresponding MGW according to actual requirements. 
• When the RNC of a calling party and the RNC of a called party are connected to the same MGW, the system can preferentially select the circuit resources of the same MGW to avoid the waste of the circuit resources between the MGWs.
• When the bearer between the RNC and the MGW is faulty, the MSC server can efficiently detect the change of the current bearer. For example, when Bearer1 is faulty, if a call passes RNC2, the MSC server can select Bearer2 instead of Bearer1, and select MGW2 for service interaction.

New Functions in the R7C1 Version:

 

In the Mini_Iu_FLEX networking or MINI-A-FLEX networking (using the IP based A interface), if the bearer type of an endpoint at the access side is ATM or IP, the MSC can select another MGW connecting to the RNC or BSC (using the IP based A interface) to establish the bearer when the bearer over the MGW fails. The reselection may prolong the connection duration; therefore, the reselection can be performed only once. The reselection of the MGW can greatly increase the call connection ratio and decrease the call loss ratio due to the failure of bearer establishment.

 

Implemented node : VMSC/VLR

 

Served network: UMTS

 

Benifits for carriers:

 

This function enhances the network security. The MSC server can detect not only the status of an MGW but also the status of the bearer between the MGW and the RNC. When an MGW is faulty, the interruption of all services may be prevented, saving the transmission resources. When the bearer between the RNC and the MGW is faulty, the MSC server can select another bearer channel to the RNC, efficiently avoiding the call loss. The reselection of the MGW after the failure of the bearer establishment at the access side greatly increases the call connection ratio and decreases the call loss ratio due to the failure of the bearer establishment.

 

Requirements for peripheral network entities:

None

 

This document is very well done

very useful info.

Wow! Its a great concept. We can use it without MSC pool function.

Important thing: To prevent the service interruption due to the MGW upgrade, MGW failure, or the failure of bearer between the MGW and RNC, the Mini_Iu_FLEX is introduced to implement the load sharing of the service management by  allowing one RNC to connect to multiple MGWs.

Very good document

useful document, thanks