01-01 Introduction to RNC Initial Configuration

RNC Initial Configuration Guide

1

1 Introduction to RNC Initial Configuration

Introduction to RNC Initial Configuration

About This Chapter RNC initial configuration is described in terms of its definition, configuration scenario, configuration method, and scripts for configuration. 1.1 Definition Definition of RNC Initial Configuration RNC initial configuration refers to the process after which the RNC becomes functional. The process of R NC initial configuration involves the writing and execution of the configuration script. 1.2 RNC Initial Configuration Tool The RNC initial initial configuration tool refers to the text editor through which you can obtain a new initial configuration configuration script by adding, deleting, and modifying MML commands in an existing MML script. 1.3 Components of the RNC Initial Configuration Script An integrate initial initial configuration script consists of the global data script, equipment data script, interface data script, and cell data script. 1.4 Conventions Conventions in Parameter Relationship Diagrams This part describes the conventions between the parameters of MML commands.

Issue 01 (2007-05-15)

Huawei Technologies Proprietary

1-1



1.1 Definition of RNC Initial Configuration RNC initial configuration refers to the process after which the RNC becomes functional. The process of RNC initial configuration involves the writing and execution of the configuration script. After the RNC is initially installed, prepare and configure the data on the basis of the hardware, network planning, and negotiation with other devices. Then, you can obtain an MML script in .txt format. The data in the MML script that is obtained after RNC initial configuration must be complete, consistent, and valid. After the script is executed, a data file is generated and then is loaded to the RNC, which enables the system to work properly. The correct initial configuration data is a prerequisite for the proper running of the RNC. RNC initial configuration does not include the case where data is modified after the RNC enter the service state. For details about modifying the data, refer to the RAN Reconfiguration Guide. NOTE

During the execution and modification of the script, a data file is generated and then is loa ded to the RNC before the data takes effect. For details, refer to Loading RNC Software and Data Files.

1.2 RNC Initial Configuration Tool The RNC initial configuration tool refers to the text editor through which you can obtain a new initial configuration script by adding, deleting, and modifying MML commands in an existing MML script.

1.3 Components of the RNC Initial Configuration Script An integrate initial configuration script consists of the global data script, equipment data script, interface data script, and cell data script. 1.3.1 Example: Global Data in the RNC Initial Configuration Script This part describes global data in the RNC initial configuration script. The global data includes RNC basic data, OSP data, license file, number of internal subnet, and global location data. 1.3.2 Example: Equipment Data in the RNC Initial Configuration Script This part describes equipment data in the RNC initial configuration script. The data consists of equipment data, RNC clock source, RNC time, NodeB clock source, RSS data, and RB S data. 1.3.3 Example: Interface Data in the RNC Initial Configuration Script This part describes interface data in the RNC initial configuration script. The data includes the configuration data of Iub, Iu-CS, Iu-PS, Iu-BC, and Iur interfaces. 1.3.4 Example: Cell Data in the RNC Initial Configuration Script This part describes cell data in the RNC initial configuration script. The cell data includes the local cell data, logical cell data, intra-frequency neighboring cell data, inter-frequency neighboring cell data, and neighboring GSM cell data.

1-2


Issue 01 (2007-05-15)



1.3.1 Example: Global Data in the RNC Initial Configuration Script This part describes global data in the RNC initial configuration script. The global data includes RNC basic data, OSP data, license file, number of internal subnet, and global location data. //Set the RNC to offline mode. SET OFFLINE: SRN=ALL, BULKT=OFF; //Add basic data to the RNC. //Add basic data to the local office. ADD RNCBASIC: RncId=1, SharingSupport=NO; //Add the operator ID. ADD CNOPERATOR: CnOpIndex=0, CnOperatorName="Operator", PrimaryOperatorFlag=YES, MCC="460", MNC="00"; //Add OSP to the RNC. ADD OPC: NI=NATB, SPCBITS=BIT24, SPC=H'000A31, NSAP="H'45000086100101008F0000000000000000000000", NAME="RNC-1"; //Activate the license file. ACT LICENSE: CNOPERATORINDEX=0, ISPRIMARYPLMN=YES, FN="license.lic"; //Set the number of the internal subnet. SET SUBNET: SUBNET=90; //Add the global location data. ADD LAC: CnOpIndex=0, LAC=100, PlmnValTagMin=1, PlmnValTagMax=64; ADD SAC: CnOpIndex=0, LAC=100, SAC=100; ADD RAC: CnOpIndex=0, LAC=100, RAC=0, PlmnValTagMin=65, PlmnValTagMax=128; ADD URA: URAId=0, CnOpIndex=0; ADD URA: URAId=1, CnOpIndex=0;

1.3.2 Example: Equipment Data in the RNC Initial Configuration Script This part describes equipment data in the RNC initial configuration script. The data consists of equipment data, RNC clock source, RNC time, NodeB clock source, RSS data, and RB S data. //Set the RNC time. //Set the time zone and daylight saving time. SET TZ: ZONET=GMT_E_8_00, DST=NO; //Modify the RSS. MOD SUBRACK: SRT=RSS, SRName="RSS", PIUT14=AEU, REDT14=Backup_binding, PIUT16=AOU, REDT16=Backup_apart, PIUT18=UOI_IUPS, REDT18=Backup_apart, PIUT24=FG2_OTHER, REDT24=Backup_binding, PIUT26=AEU, REDT26=Backup_binding; //Add an RBS. ADD SUBRACK: SRN=1, SRName="RBS", PIUT14=AEU, REDT14=Backup_binding, PIUT16=UOI_OTHER, REDT16=Backup_apart, PIUT18=FG2_IUPS, REDT18=Backup_binding, PIUT20=UOI_OTHER, REDT20=Backup_apart, PIUT22=FG2_OTHER, REDT22=Backup_binding; //Configure the RNC clock. //Add the clock source. ADD CLKSRC:SRCGRD=1, SRCT=BITS1-2MHZ; ADD CLKSRC:SRCGRD=2, SRCT=LINE1_8KHZ; ADD CLKSRC:SRCGRD=3, SRCT=LINE2_8KHZ; //Set the clock switching policy.

Issue 01 (2007-05-15)


1-3



SET CLKMODE:CLKWMODE=AUTO; //Set the clock source of the board. SET CLK:SRT=RSS, SN=14, BT=AEU, REF2MCLKSRC=31, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=OFF, BACK8KCLKSW2=OFF; SET CLK:SRT=RSS, SN=16, BT=AOU, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=ON, BACK8KCLKSW2=OFF; SET CLK:SRT=RSS, SN=18, BT=UOI, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=OFF, BACK8KCLKSW2 =OFF; SET CLK:SRT= RSS, SN=19, BT=UOI, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1 =OFF, BACK8KCLKSW2 =OFF; SET CLK:SRT= RSS, SN=22, BT=PEU, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MC LKSW2=OFF, BACK8KCLKSW1=OFF, BACK8KCLKSW2 =OFF; SET CLK: SRT =RBS, SRN=1, SN=14, BT=AEU, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2= OFF; SET CLK: SRT =RBS, SRN=1, SN=16, BT=UOI, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2= OFF; SET CLK: SRT=RBS, SRN=1, SN=20, BT=UOI, REF2MCLKSRC=1, REF2MCLKSW1=OFF, REF2MCLKSW2= OFF; //Configure a NodeB clock source. SET SNTPSRVP ARA: SP=60, SW=off;

1.3.3 Example: Interface Data in the RNC Initial Configuration Script This part describes interface data in the RNC initial configuration script. The data includes the configuration data of Iub, Iu-CS, Iu-PS, Iu-BC, and Iur interfaces. 1.3.3.1 Exam ple: Iub Data in the RNC Initial Configuration Script This part describes an example of Iub data in the RNC initial configuration script. The Iub data consists of the physical layer data of Iub, ATM traffic resource data, transmission and service mapping data, factor table data, Iub control plane data, Iub user plane data, and Iub management data. 1.3.3.2 Example: Iu-CS Data in the RNC Initial Configuration Script This part describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS data consists of the physical layer data of Iu-CS, transmission and service mapping data, factor table data, Iu-CS control plane data, and Iu-CS user plane data. 1.3.3.3 Example: Iu-PS Data in the RNC Initial Configuration Script This part describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS data consists of the physical layer data of Iu-PS, transmission and service mapping data, factor table data, Iu-PS control plane data, and Iu-PS user plane data. 1.3.3.4 Example: Iu-BC Data in the RNC Initial Configuration Script This part describes an example of Iu-BC data in the RNC initial configuration script. The Iu-BC data consists of the physical layer data of Iu-BC, transmission and service mapping data, factor table data, transmission port data, IPoA data, and SABP data. 1.3.3.5 Example: Iur Data in the RNC Initial Configuration Script This part describes an example of Iur data in the RNC initial configuration script. The Iur data consists of the physical layer data of Iur, t ransmission and service mapping data, factor table data, Iur control plane data, and Iur user plane data.

1-4


Issue 01 (2007-05-15)



Example: Iub Data in the RNC Initial Configuration Script This part describes an example of Iub data in t he RNC initial configuration script. The Iub data consists of the physical layer data of Iub, ATM traffic resource data, transmission and service mapping data, factor table data, Iub control plane data, Iub user plane data, and Iub management data. //Apply ATM transport to the Iub. //Set the E1T1 parameters. Set all the links on the AEUa in slot 14 in subrack 1: Link select: ALL; //Frame Structure: E1_CRC4_MULTI_FRAME; Line code: HDB3; Scramble switch: ON. SET E1T1: SRN=1, SN=14, BT=AEU, LS=ALL, LNKT=E1_CRC4_MULTI_FRAME, LNKCODE=HDB3, SCRAMBLESW=ON; //Add UNI links. Add a UNI link 0 to the AEUa in slot 14 in subrack 1. ADD UNILNK: SRN=1, SN=14, UNILNKN=0; //Add an IMA link group and an IMA link. Add an IMA link group with link 1 and link 2 to the AEUa in //slot 14 in subrack 1. ADD IMAGRP: SRN=1, SN=14, IMAGRPN=0; ADD IMALNK: SRN=1, SN=14, IMALNKN=1, IMAGRPN=0; ADD IMALNK: SRN=1, SN=14, IMALNKN=2, IMAGRPN=0;

//Add ATM traffic resources. Add an ATM traffic record. The index is 101. The service type is CBR and //the peak rate is 1000 cell/s. ADD ATMTRF: TRFX=101, ST=CBR, UT=CELL/S, PCR=1000, CDVT=102400; //Add the transmission and service mapping data. Add a transmission and service mapping record. //The TRMMAP ID is 0. The interface type is Iub. The transport type is ATM transport. Other parameters //use default values. ADD TRMMAP: TMI=0, ITFT=IUB_IUR_IUCS, TRANST=ATM; //Add a factor table. The factor table index is 0. The table name is Iub. Other parameters use the //default value. ADD FACTORTABLE: FTI=0, NAME="IUB";

//Add Iub control plane data. //Add SAAL links. The SAAL links are terminated at SPU subsystem 0 in slot 2 in RBS 1. The link //numbers range from 10 to 13. //Add the SAAL link bearing the NCP. ADD SAALLNK: SRN=1, SN=2, SSN=0, SAALLNKN=10, CARRYT=UNI, CARRYSN=14, CARRYUNILNKN=0, CARRYVPI=10, CARRYVCI=33, TXTRFX=101, RXTRFX=101, SAALLNKT=UNI; //Add the SAAL link bearing the CCP. ADD SAALLNK: SRN=1, SN=2, SSN=0, SAALLNKN=11, CARRYT=UNI, CARRYSN=14, CARRYUNILNKN=0, CARRYVPI=10, CARRYVCI=34, TXTRFX=101, RXTRFX=101, SAALLNKT=UNI; ADD SAALLNK: SRN=1, SN=2, SSN=0, SAALLNKN=12, CARRYT=UNI, CARRYSN=14, CARRYUNILNKN=0, CARRYVPI=10, CARRYVCI=35, TXTRFX=101, RXTRFX=101, SAALLNKT=UNI; //Add the SAAL link bearing the ALCAP. ADD SAALLNK: SRN=1, SN=2, SSN=0, SAALLNKN=13, CARRYT=UNI, CARRYSN=14, CARRYUNILNKN=0, CARRYVPI=10, CARRYVCI=36, TXTRFX=101, RXTRFX=101, SAALLNKT=UNI; //Add the NodeB and the algorithm. ADD NODEB: NodeBName="NODEB1", NodeBId=1, SRN=1, SN=2, SSN=0, TnlBearerType=ATM_TRANS, Nsap="H'3901010101010101010101010101011101011111", NodeBProtclVer=R6; ADD NODEBALGOPARA:

Issue 01 (2007-05-15)


1-5



NodeBName="NODEB1", IubCongCtrlSwitch=OFF; //Add the Iub port data. //Add an NCP. ADD NCP: NODEBNAME="NODEB1", CARRYLNKT=SAAL, SAALLNKN=10; //Add the CCP 0 and CCP 1. ADD CCP: NODEBNAME="NODEB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=11; ADD CCP: NODEBNAME="NODEB1", PN=1, CARRYLNKT=SAAL, SAALLNKN=12;

//Add Iub user plane data. //Add a port controller. ADD PORTCTRLER: SRN=1, SN=14, PT=IMA, CARRYIMAGRPN=0, CTRLSN=2, CTRLSSN=0; //Add a transmission adjacent node on the Iub interface, that is, NodeB1. The adjacent node ID is 0. //The interface type is Iub. ADD ADJNODE: ANI=0, NAME="NODEB1", NODET=IUB, NODEBID=1, TRANST=ATM, IsROOTNODE=YES, SRN=1, SN=2, SSN=0, SAALLNKN=13, TMI=0, FTI=0; //Add an AAL2 path to NodeB1. The AAL2 path ID is 1. ADD AAL2PATH: ANI=0, PATHID=1, PT=RT, CARRYF=1, CARRYT=IMA, CARRYSN=14, CARRYIMAGRPN=0, CARRYVPI=10, CARRYVCI=37, TXTRFX=101, RXTRFX=101, OWNERSHIP=LOCAL; //Add an AAL2 route that reaches NodeB1. ADD AAL2RT: NSAP="H'3901010101010101010101010101011101011111", ANI=1, RTX=0, OWNERSHIP=YES;

//Add the Iub management plane data. //Add the IP address of the boards. Th e local IP address is 18.18.18.18 . The subnet mask is 255.255.255.0. ADD DEVIP: SRN=1, SN=14, IPADDR="18.18.18.18", MASK="255.255.255.0"; //Add an IPoA PVC. The local IP address is 18.18.18.18. The peer IP address is 18.18.18.200. //The IPoA PVC is carried over the IMA group 0. ADD IPOAPVC: IPADDR="18.18.18.18", PEERIPADDR="18.18.18.200", CARRYT=IMA, CARRYIMAGRPN=0, CARRYVPI=10, CARRYVCI=37, TXTRFX=101, RXTRFX=101, PEERT=NODEB; //Add the OM IP address of the NodeB. The NodeB OM IP address is 10.12.12.13. The gateway address on //the RNC side, or the peer IP address of IPoA PVC is 18.18.18.200. ADD NODEBIP: NODEBID=1, NBOAMIP="10.12.12.13", NBOAMMASK="255.255.255.0", GATEWAYIP="18.18.18.200"; //Add the IP attribute of the NE management system. The IP address of the NE management system is 129.168.150.111. The network segment mask is 255.255.255.0. ADD EMSIP: EMSIP="129.168.150.111", MASK="255.255.255.0";

Example: Iu-CS Data in the RNC Initial Configuration Script This part describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS data consists of the physical layer data of Iu-CS, transmission and service mapping data, factor table data, Iu-CS control plane data, and Iu-CS user plane data. //Take the ATM transport over Iu-CS mode as an example. //Add physical layer data of the RNC external interface. //Set attributes of the optical port on the UOIa board in slot 16 in subrack 1. SET OPT: SRN=1, SN=16, BT=UOI, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16byte, J0TXVALUE="SBS HuaWei 155", J0RXT=16byte, J0RXVALUE="SBS HuaWei 155",

1-6


Issue 01 (2007-05-15)



J1TXT=16byte, J1TXVALUE="SBS HuaWei 155", J1RXT=16byte, J1RXVALUE="SBS HuaWei 155";

//Add ATM traffic resources. //Add two ATM traffic records. One is for the control plane. The index is 102. The service type is //CBR. The peak cell rate is 1000 cell/s. The other one is for the user plane. The index is 103. //The service type is CBR. The peak cell rate is 1500 cell/s. ADD ATMTRF: TRFX=102, ST=CBR, TRFD=NOCLPNOSCR, UT=CELL/S, PCR=1000; ADD ATMTRF: TRFX=103, ST=CBR, TRFD=NOCLPNOSCR, UT=CELL/S, PCR=1500;

//Add the transmission resour ce mapping data. Add the mapping table with the TRMMAP ID as 1. ADD TRMMAP: TMI=1, ITFT=IUB_IUR_IUCS, TRANST=ATM;

//Add a factor table. The factor table index is 1. The table name is Iu-CS. ADD FACTORTABLE: FTI=1, NAME="IUCS";

//Add the Iu-CS control plane data. //Add SAAL links. ADD SAALLNK: SRN=1, SN=2, SSN=1, SAALLNKN=4, CARRYT=NCOPT, CARRYSN=16, CARRYNCOPTN=0, CARRYVPI=11, CARRYVCI=35, TXTRFX=102, RXTRFX=102, SAALLNKT=NNI; ADD SAALLNK: SRN=1, SN=2, SSN=1, SAALLNKN=5, CARRYT=NCOPT, CARRYSN=16, CARRYNCOPTN=0, CARRYVPI=22, CARRYVCI=35, TXTRFX=102, RXTRFX=102, SAALLNKT=NNI; //Add RNC DSPs. //The index of DSP on the Iu-CS control plane is 0. The signaling route mask is B0111, indicating there are at most eight routes for load sharing. ADD N7DPC: DPX=0, DPC=H'000B50, SLSMASK=B0111, NEIGHBOR=YES, NAME="TO-UMGW", DPCT=IUCS_ALCAP, STP=ON, PROT=ITUT, BEARTYPE=MTP3B; //The index of DSP on the Iu-CS control plane is 3. The signaling route mask is B0111, indicating there are at most eight routes for load sharing. ADD N7DPC: DPX=3, DPC=H'000A85, SLSMASK=B0111, NEIGHBOR=NO, NAME="TO-MSOFT3000", DPCT=IUCS_RANAP, STP=OFF, PROT=ITUT, BEARTYPE=MTP3B; //Add the MTP3-B data. Add the signaling linkset connecting the MGW. The linkset index is 0. The //signaling link mask is B1000, indicating there are at most two links for load sharing. The link set //has two routes connecting to the MGW and MSC SERVER respectively. ADD MTP3BLKS: SIGLKSX=0, DPX=0, LNKSLSMASK=B1000, NAME="TO-UMGW"; ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="TO-UMGW"; ADD MTP3BRT: DPX=3, SIGLKSX=0, NAME="TO-MSOFT3000"; ADD MTP3BLNK: SIGLKSX=0, SIGSLC=0, SRN=1, SN=2, SSN=1, SAALLNKN=4, NAME="TOUMGW"; ADD MTP3BLNK: SIGLKSX=0, SIGSLC=1, SRN=1, SN=2, SSN=1, SAALLNKN=5, NAME="TOMSOFT3000";

//Add the adjacent node of the Iu-CS. ADD ADJNODE: ANI=1, NAME="IUCS", NODET=IUCS, DPX=0, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS1, TMI=1, FTI=1; //Add the CN domain and CN node. ADD CNDOMAIN: CNDomainId=CS_DOMAIN; ADD CNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=3, CNProtclVer=R5, SupportCRType=CR529_SUPPORT, OffLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=ATM_TRANS;

Issue 01 (2007-05-15)


1-7



//Set the Iu-Flex information. The CN domain does not support the Iu-Flex. SET IUFLEX: CnOpIndex=0,CsIuFlexFlag=OFF, PsIuFlexFlag=OFF;

//Add the Iu-CS user plane data. //Add the SPU subsystem managing transmission resources to the Iu-CS port. ADD PORTCTRLER: SRN=1, SN=16, PT=NCOPT, CARRYNCOPTN=0, CTRLSN=2, CTRLSSN=1; //Add the AAL2 path and AAL2 route to the Iu-CS. ADD AAL2PATH: ANI=1, PATHID=1, PT=RT, CARRYF=1, CARRYT=NCOPT, CARRYSN=16, CARRYNCOPTN=0, CARRYVPI=33, CARRYVCI=55, TXTRFX=103, RXTRFX=103; ADD AAL2RT: NSAP="H'4506060606060606060606060606060606060606", ANI=1, RTX=1;

Example: Iu-PS Data in the RNC Initial Configuration Script This part describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS data consists of the physical layer data of Iu-PS, transmission and service mapping data, factor table data, Iu-PS control plane data, and Iu-PS user plane data. //Take the IP transport over Iu-PS mode as an example. //Add physical layer data. //Set the attributes of Ethernet ports on the FG2a board. Set the type of the port 0 on the FG2a in //slot 18 in subrack 1 to FE. SET ETHPORT: SRN=1, SN=18, PN=0, PTYPE=FE, MTU=1500, AUTO=ENABLE; //Add the IP address of the Ethernet port. The IP address of the port 0 in slot 18 in subrack 0 is //10.161.204.201. The subnet mask is 255.255.255.0. ADD ETHIP: SRN=1, SN=18, PN=0, IPADDR="10.161.204.201", MASK="255.255.255.0"; //Add the Iu-PS transmission resource mapping data. The TRMMAP ID is 3. The interface type is Iu-PS. //Other parameters use the default values. ADD TRMMAP: TMI=3, ITFT=IUPS;

//Add an Iu-PS factor table. The factor table index is 3. The table name is IuPS. ADD FACTORTABLE: FTI=3, NAME="IUPS ";

//Add Iu-PS control plane data. //Add SCTP links. ADD SCTPLNK: SRN=1, SN=2, SSN=0, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, LOCIPADDR1="10.161.204.201", PEERIPADDR1="10.161.193.201", PEERPORTNO=2905; //Add an Iu-PS DSP. ADD N7DPC: DPX=4, DPC=H'000A93, SLSMASK=B1000, NEIGHBOR=YES, NAME="TO IU-PS IP", DPCT=IUPS, STP=OFF, PROT=ITUT, BEARTYPE=M3UA; //Add the M3UA data. //Add the M3UA local entity. ADD M3LE: LENO=0, ENTITYT=M3UA_ADP_IPSP, RTCONTEXT=1, NAME="RNC"; //Add M3UA destination entity. ADD M3DE: DENO=10, LENO=0, DPX=4, RTCONTEXT=5, ENTITYT=M3UA_ADP_IPSP, NAME="IU-IPSGSN" //Add the M3UA signaling linkset. The link set index is 0 with at most eight links for load sharing. ADD M3LKS: SIGLKSX=0, DENO=0, LNKSLSMASK=B0111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, NAME="IU IP TO SGSN";

1-8


Issue 01 (2007-05-15)



//Add an M3UA route. ADD M3RT: DENO=10, SIGLKSX=0, NAME="IU-PS-IP-SGSN"; //Add the M3UA signaling link. ADD M3LNK: SIGLNKID=1, SIGLKSX=0, SRN=1, SN=2, SSN=0, SCTPLNKN=1, NAME="IU-PS-IP"; //Add an adjacent node. ADD ADJNODE: ANI=3, NAME="IU-PS IP", NODET=IUPS, DPX=4, TMI=3; //Add the CN domain information and node data. ADD CNDOMAIN: CNDomainId=PS_DOMAIN; ADD CNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=4, CNProtclVer=R5, SupportCRType=CR529_SUPPORT, OffLoadStatus=NORMAL, AvailCap=1000, TnlBearerType=IP_TRANS; //Set the Iu-Flex information. The CN domain does not support the Iu-Flex. SET IUFLEX: CnOpIndex=0,CsIuFlexFlag=OFF, PsIuFlexFlag=OFF;

//Add the Iu-PS user plane data. //Add the SPU subsystem managing the transmission resources to the Iu-PS. ADD PORTCTRLER: SRN=1, SN=18, PT=ETHER, CARRYEN=0, CTRLSN=2, CTRLSSN=0; //Add an IP path. ADD IPPATH: ANI=3, PATHID=1, PATHT=RT, IPADDR="10.161.204.201", PEERIPADDR="10.161.193.201", PEERMASK="255.255.255.0", TXBW=10000, RXBW=10000, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.161.193.202"; //Add an IP route. ADD IPRT: SRN=1, SN=18, DESTIP="10.161.193.0", MASK="255.255.255.0", NEXTHOP="10.161.204.1";

Example: Iu-BC Data in the RNC Initial Configuration Script This part describes an example of Iu-BC data in the RNC initial configuration script. The Iu-BC data consists of the physical layer data of Iu-BC, transmission and service mapping data, factor table data, transmission port data, IPoA data, and SABP data. //Take the ATM transport over Iu-BC mode as an example. //Add physical layer data. //Set the attributes of electrical ports on the UOIa board in slot 20 in subrack 1. SET OPT: SRN=1, SN=20, BT=UOI, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=64byte, J0TXVALUE="SBS 155", J0RXT=64byte, J0RXVALUE="SBS 155", J1TXT=64byte, J1TXVALUE="SBS 155", J1RXT=64byte, J1RXVALUE="SBS 155";

//Add ATM traffic resources. ADD ATMTRF: TRFX=104, ST=NRTVBR, UT=KBIT/S, PCR=10000, SCR=8000, REMARK="IU-BC";

//Add the Iu-BC transmission resource mapping data. ADD TRMMAP: TMI=4, ITFT=IUB_IUR_IUCS, TRANST=ATM;

//Add the Iu-BC factor table. ADD FACTORTABLE: FTI=4, NAME="IUBC";

//Add the SPU subsystem managing transmission resources to the Iu-BC port. ADD PORTCTRLER: SRN=1, SN=20, PT=NCOPT, CARRYNCOPTN=0, CTRLSN=2, CTRLSSN=0;

//Add the IPoA data to the Iu-BC interface. //Add the IP address of the boards. ADD DEVIP: SRN=1, SN=20, IPADDR="172.22.21.50", MASK="255.255.255.0";

Issue 01 (2007-05-15)


1-9



//Add an IPoA PVC. ADD IPOAPVC: IPADDR="172.22.21.50", PEERIPADDR="172.22.21.254", CARRYT=NCOPT, CARRYPN=0, CARRYVPI=14, CARRYVCI=126, TXTRFX=104, RXTRFX=104,PEERT=OTHER; //Add an IP route. ADD IPRT: SRN=1, SN=20, DESTIP="172.22.5.0", MASK="255.255.255.0", NEXTHOP="172.22.21.254"; //Add SABP data. ADD CBSADDR: SRN=1, SN=2, SSN=0,CnOpIndex=0,RNCIPADDR="172.22.21.50", CBCIPADDR="172.22.5.0", CBCMASK="255.255.0.0";

Example: Iur Data in the RNC Initial Configuration Script This part describes an example of Iur data in the RNC initial configuration script. The Iur data consists of the physical layer data of Iur, t ransmission and service mapping data, factor table data, Iur control plane data, and Iur user plane data. //Take the IP transport over Iur mode as an example. //Add physical layer data. //Set the attributes of Ethernet ports on the FG2a board in slot 22 in subrack 1. SET ETHPORT: SRN=1, SN=22, PN=1, PTYPE=FE, MTU=1500, AUTO=EN ABLE; ADD ETHIP: SRN=1, SN=22, PN=1, IPADDR="22.22.22.21", MASK="255.255.255.0";

//Add the Iur transmission resource mapping data. ADD TRMMAP: TMI=5, ITFT=IUB_IUR_IUCS, TRANST=IP;

//Add an Iur factor table. ADD FACTORTABLE: FTI=5, NAME="IUR";

//Add the Iur control plane data. //Add an SCTP link. ADD SCTPLNK: SRN=1, SN=2, SSN=0, SCTPLNKN=3, MODE=SERVER, APP=M3UA, LOCIPADDR1="22.22.22.21", PEERIPADDR1="22.22.22.22", PEERPORTNO=1026; //Add DSPs. ADD N7DPC: DPX=5, DPC=H'000A21, SLSMASK=B1000, NAME="IUR", DPCT=IUR; //Add basic data to a neighboring RNC. ADD NRNC: NRncId=115, SHOTRIG=OFF, HHOTRIG=OFF, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, Dpx=5, RncProtclVer=R5, TnlBearerType=IP_TRANS; //Add the M3UA data. //Add an M3UA destination entity. ADD M3DE: DENO=11, LENO=0, DPX=5, RTCONTEXT=1, ENTITYT=M3UA_ADP_IPSP, NAME="RNC-2"; //Add the M3UA signaling link set. The link set index is 0 with at most eight links for load sharing. ADD M3LKS: SIGLKSX=1, DENO=11, LNKSLSMASK=B0111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, NAME="TO-RNC-2"; //Add an M3UA route. ADD M3RT: DENO=11, SIGLKSX=1, PRIORITY=10, NAME="TO-RNC-2"; //Add an M3UA signaling link. ADD M3LNK: SIGLNKID=5, SIGLKSX=1, SRN=1, SN=2, SSN=0, SCTPLNKN=3, PRIORITY=10, LNKREDFLAG=M3UA_ADP_MASTER_MOD, NAME="TO-RNC-2"; //Add an adjacent node.

1-10


Issue 01 (2007-05-15)



ADD ADJNODE: ANI=5, NAME="TO-RNC-2", NODET=IUR, DPX=5, TRANST=IP, TMI=5, FTI=5;

//Add the Iur user plane data. //Add the SPU subsystem managing the transmission resources to the Iur. ADD PORTCTRLER: SRN=1, SN=22, PT=ETHER, CARRYEN=1, CTRLSN=2, CTRLSSN=0; //Add an IP path and an IP route. ADD IPPATH: ANI=5, PATHID=1, PATHT=RT, IPADDR="22.22.22.21", PEERIPADDR="22.22.22.22", PEERMASK="255.255.255.0", TXBW=1000, RXBW=1000; ADD IPRT: SRN=1, SN=22, DESTIP="16.16.16.16", MASK="255.255.255.0", NEXTHOP="22.22.22.21";

1.3.4 Example: Cell Data in the RNC Initial Configuration Script This part describes cell data in the RNC initial configuration script. The cell data includes the local cell data, logical cell data, intra-frequency neighboring cell data, inter-frequency neighboring cell data, and neighboring GSM cell data. //Set up cells quickly. //Add basic data of local cells. ADD LOCELL: NODEBNAME="NodeB1", LOCELL=0; ADD LOCELL: NODEBNAME="NodeB1", LOCELL=1; ADD LOCELL: NODEBNAME="NodeB1", LOCELL=2; //Add logical cell data quickly. ADD QUICKCELLSETUP: CellId=0, CellName="CELL 0",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, UARFCNDownlink=10563, PScrambCode=0, TCell=CHIP0, LAC=100, SAC=100, CfgRacInd=REQUIRE, RAC=0, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=0, SupBmc=FALSE; ADD QUICKCELLSETUP: CellId=1, CellName="CELL 1",CnOpIndex=0,BandInd=Band1, UARFCNUplink=9613, UARFCNDownlink=10563, PScrambCode=1, TCell=CHIP256, LAC=100, SAC=100, CfgRacInd=REQUIRE, RAC=0, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=1, SupBmc=FALSE; ADD QUICKCELLSETUP: CellId=2, CellName="CELL 2",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, UARFCNDownlink=10563, PScrambCode=2, TCell=CHIP512, LAC=100, SAC=100, CfgRacInd=REQUIRE, RAC=0, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=2, SupBmc=FALSE; //Activate a logical cell. ACT CELL: CELLID=0; ACT CELL: CELLID=1; ACT CELL: CELLID=2; //Add an intra-frequency neighboring cell. //Add an inter-frequency neighboring cell. ... ... //Add a neighboring GSM cell. ... ... //Set the RNC to online mode. The initial configuration ends. SET ONLINE:;

1.4 Conventions in Parameter Relationship Diagrams This part describes the conventions between the parameters of MML commands. The example of a parameter relationship diagram is shown in Figure 1-1. Issue 01 (2007-05-15)


1-11



Figure 1-1 Example of the parameter relationship diagram

The elements in are explained as follows: l

The parameters in a box marked in solid or dotted lines belong to the command above the box. For example, parameter 3 belongs to command 2.

l

Boxes 1 and 2 list only the parameters related to both commands.

l

The command above box 2 in solid lines is executed to perform the current task, and the command above box 1 in dotted li nes is executed to perform a related task.

l

The parameters at both ends of the solid arrow are the same. This parameter is configured through the command at the arrowhead and invoked through the command at the arrow tail. For example, parameter 2 is configured through command 1 and invoked through command 2.

l

The parameters at both ends of the dotted arrow are different. The one at the arrowhead must be predefined, and the one at the arrow tail must be consistent with it. For example, parameter 3 must be consistent with parameter 1.

l

The parameter marked with *, such as parameter 3, is a conditional parameter. It is configured only in some conditions. NOTE

The parameter relationship between the commands to add, modify, and remove a configured object is obvious. This guide does not describe such relationships.

1-12


Issue 01 (2007-05-15)

01-01 Introduction to RNC Initial Configuration

Recommend Documents