IuCS Configuration Based on ATM

Internal

CATALOG
Scene I One RNC Connects One MGW Which Connects One MSC Server ........... 2 Scene II One RNC Connects One MGW And One MSC Server ......................... 3 Scene III One RNC Connects One MGW Which Connects One MSC Server Pool ... 4 Scene IV One RNC Connects One MGW Which Connects Two MSC Servers ....... 5 Scene V One RNC Connects One MSC ..................................................... 7

2009-2-25

1 , 7

IuCS Configuration Based on ATM

Internal

Scene I One RNC Connects One MGW Which Connects One MSC Server
This scene is based on R4 or later version. Figure I:

Figure I In this situatioin, two N7DPCs are considered to configure. One is for MGW, another one is for MSC Server. In detail, DSP type of the N7DPC of MGW is ALCAP. Considering that control-plane signaling messages to the MSC Server will be routed by the MGW, the STP function switch have to be turned on. And the adjcent flag is direct-connect. After the MGW, the other N7DPC for MSC Server is RANAP, which STP fuction switch is off and adjcent flag is no-direct-connect. In order to bear the signaling messages, one MTP3B link set is needed for MGW. Example commands:
ADD N7DPC: DPX=0, DPC=10, NEIGHBOR=YES, NAME="MGW", DPCT=IUCS_ALCAP, STP=ON, BEARTYPE=MTP3B; ADD N7DPC: DPX=1, DPC=11, NEIGHBOR=NO, NAME="MSC Server", DPCT=IUCS_RANAP, STP=OFF, BEARTYPE=MTP3B; ADD MTP3BLKS: SIGLKSX=0, DPX=0, NAME="MGW"; ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="MGW"; ADD MTP3BLNK: ;

2009-2-25

2 , 7

IuCS Configuration Based on ATM

Internal

Scene II One RNC Connects One MGW And One MSC Server
This scene is based on R4 or later version. Figure II:

MSC Server

RNC Figure II

MGW

In this consideration, there are two N7DPCs for MGW and MSC Server respectively. For MGW, the DSP type is choosed to ALCAP, adjcent flag is direct-connect, and STP fuction switch is off. For MSC Server, the DSP type will be RANAP, and other parameters are same with MGW. In this case, two MTP3B link sets have to be configured. Example commands:
ADD N7DPC: DPX=0, DPC=10, NAME="MGW", DPCT=IUCS_ALCAP, BEARTYPE=MTP3B; ADD N7DPC: DPX=1, DPC=11, NAME="MSC Server", DPCT=IUCS_RANAP, BEARTYPE=MTP3B; ADD MTP3BLKS: SIGLKSX=0, DPX=0, NAME="MGW"; ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="MGW"; ADD MTP3BLNK: ; ADD MTP3BLKS: SIGLKSX=1, DPX=1, NAME="MSC Server"; ADD MTP3BRT: DPX=1, SIGLKSX=1, NAME="MSC Server"; ADD MTP3BLNK: ;

2009-2-25

3 , 7

IuCS Configuration Based on ATM

Internal

Scene III One RNC Connects One MGW Which Connects One MSC Server Pool
This scene is based on R4 or later version. Figure III:

Figure III Considering this network structure, only one N7DPC is available. The MGW will decide which MSC Server will be used to process the signaling messages, so just one N7DPC is needed to add from RNC to MGW. In detail, DSP type of the N7DPC is IUCS, adjcent flag is direct-connect, STP fuction switch is off. Below this N7DPC, there is one MTP3B link set. Example commands:
ADD N7DPC: DPX=0, DPC=10, NAME="IUCS", DPCT=IUCS, BEARTYPE=MTP3B; ADD MTP3BLKS: SIGLKSX=0, DPX=0, NAME="IUCS"; ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="IUCS"; ADD MTP3BLNK: ;

2009-2-25

4 , 7

IuCS Configuration Based on ATM

Internal

Scene IV One RNC Connects One MGW Which Connects Two MSC Servers
This scene is based on R4 or later version. Figure IV:

Figure IV In this case, there are three N7DPCs, two for the MGWs and one for the MSC Server. The configuration of the N7DPCs of the MGWs are same within scene I, except that the signaling route mask should be B1000 as two routes to MSC Server. And the parameters of MSC Servers N7DPC are also same within scene I. The signaling link mask of MTP3B that used to bear the signaling messages is B01111. Example commands:
ADD N7DPC: DPX=0, DPC=10, NEIGHBOR=YES, NAME="MGW 1", DPCT=IUCS_ALCAP, STP=ON, BEARTYPE=MTP3B; ADD N7DPC: DPX=1, DPC=11, NEIGHBOR=YES, NAME="MGW 2", DPCT=IUCS_ALCAP, STP=ON, BEARTYPE=MTP3B; ADD N7DPC: DPX=2, DPC=12, NEIGHBOR=NO, NAME="MSC Server", DPCT=IUCS_RANAP, STP=OFF, BEARTYPE=MTP3B; ADD MTP3BLKS: SIGLKSX=0, DPX=0, NAME="MGW 1"; ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="MGW 1"; ADD MTP3BLNK: ; ADD MTP3BLKS: SIGLKSX=1, DPX=1, NAME="MGW 2"; 2009-2-25 5 , 7

IuCS Configuration Based on ATM ADD MTP3BRT: DPX=1, SIGLKSX=1, NAME="MGW 2"; ADD MTP3BLNK: ;

Internal

2009-2-25

6 , 7

IuCS Configuration Based on ATM

Internal

Scene V One RNC Connects One MSC

This scene is based on R99 version. Figure V:

Figure V In the R99 version, the MSC isnt divided into MGW and MSC Server. Therefore, just only one N7DPC is enough. DSP type of the N7DPC is IUCS, adjcent flag is direct-connect, and STP fuction switch is off. Then one MTP3B link set is used to bear the messages. Example commands:
ADD N7DPC: DPX=0, DPC=1, NAME="IUCS", DPCT=IUCS, BEARTYPE=MTP3B; ADD MTP3BLKS: SIGLKSX=0, DPX=0, NAME="IUCS"; ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="IUCS"; ADD MTP3BLNK: ;

2009-2-25

7 , 7