Security Level: for

3G sites creation customer

3G sites creation For Tunisiana

Prepared by Ibraheem Fawzy Date 2012-09-05

Updated by Date
Updated by Date
Approved by Date
Authorized by Date

2023-03-25 HUAWEI Confidential Page1, Total10

 Security Level: for
3G sites creation customer

Contents
Introduction.................................................................................................................................2
Configuration on RNC side:.......................................................................................................3
Configuration on NodeB side:....................................................................................................7

Introduction

The 3G site creation means how to configure the site so that after the physical
connection is done all the communication interfaces should perform well to carry the data
between the end user (mobile subscriber) and the RNC. The procedure is quite simple
and yet needs two parts, one part on the RNC and the other on the NodeB. Unlike the
Abis interface in GSM, the IUB interface is a standard one i.e. NodeBs from different
vendor can communicate and integrated to RNC from other vendor. That’s the
configuration should be run separately on both RNC and NodeB. Hereafter I will
introduce how to prepare both of them.

2023-03-25 HUAWEI Confidential Page2, Total10

 Security Level: for
3G sites creation customer

Before starting in the data creation I would like to point to another important interface
which is the operation and maintenance interface (O&M) this interface connects the
NodeB to the M2000 (huawei server responsible for supervision, operation and
maintenance for huawei’s Nodes) as shown in the below picture.

Now let`s go through the RNC configuration

Configuration on RNC side:

The configuration on RNC side contains two parts:

Transmission part:

Contain the IUB configuration depending on the protocol stack of IUB as follow:

2023-03-25 HUAWEI Confidential Page3, Total10

 Security Level: for
3G sites creation customer

In the IP protocol stack that shown below the framing protocols are carried on IP paths
and the NBAP carried on the Stream Control Transmission Protocol (SCTP) links. The ip
layer configuration should be done by adding the IP addresses on the RNC port and
NodeB…

Now it`s look easy and simple so first we will add the NodeB as following command
ADD UNODEB: NodeBName="MON2602", NodeBId=32602, SRN=1, SN=2, TnlBearerType=IP_TRANS,
IPTRANSAPARTIND=NOT_SUPPORT, HostType=SINGLEHOST, SharingType=DEDICATED,
CnOpIndex=0;
Note: the subrack and slot number are pointing to the SPU boards in RNC

then the following commands to activate the LDR and OLC algorithms
ADD UNODEBALGOPARA: NodeBName="MON2602", NodeBLdcAlgoSwitch=IUB_LDR-
0&NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR-0&IUB_OLC-0;
ADD UNODEBLDR: NodeBName="MON2602";
ADD UNODEBOLC: NodeBName="MON2602";

Then we will add two SCTP links one for the NCP and the other for the CCP. The SCTP
link is identified by the quaternary “local port and ip address and destination port and IP
address” Like the following example:
ADD SCTPLNK: SRN=1, SN=2, SCTPLNKN=534, MODE=SERVER, APP=NBAP, LOCIP1="10.204.13.246",
PEERIP1="10.98.14.72", PEERPN=58081, LOGPORTFLAG=NO, VLANFLAG1=DISABLE,

2023-03-25 HUAWEI Confidential Page4, Total10

 Security Level: for
3G sites creation customer

VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
ADD SCTPLNK: SRN=1, SN=2, SCTPLNKN=535, MODE=SERVER, APP=NBAP, LOCIP1="10.204.13.246",
PEERIP1="10.98.14.72", PEERPN=58082, LOGPORTFLAG=NO, VLANFLAG1=DISABLE,
VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;

Then we should add the NBAP entities on the added SCTP links:

ADD UNCP: NodeBName="MON2602", CARRYLNKT=SCTP, SCTPLNKN=534;

ADD UCCP: NodeBName="MON2602", PN=0, CARRYLNKT=SCTP, SCTPLNKN=535;

As now the CP part of the IUB is done we will move to the UP part
The first step is to add adjacent Node to link it to the IP Paths:
ADD ADJNODE: ANI=317, NAME="MON2602", NODET=IUB, NODEBID=32602, TRANST=IP;
Then we will map the added node to a quality of service map:
ADD ADJMAP: ANI=317, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=100, TMISLV=100,
TMIBRZ=100, FTI=0;
The standard traffic map required four IP Paths with different QOS so a four IP Paths will
be added:
ADD IPPATH: ANI=317, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=EF, IPADDR="10.204.13.246",
PEERIPADDR="10.98.14.72", TXBW=100000, RXBW=100000, CARRYFLAG=NULL,
VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.98.14.72";
ADD IPPATH: ANI=317, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=AF41, IPADDR="10.204.13.246",
PEERIPADDR="10.98.14.72", TXBW=100000, RXBW=100000, CARRYFLAG=NULL,
VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.98.14.72";
ADD IPPATH: ANI=317, PATHID=3, ITFT=IUB, TRANST=IP, PATHT=AF31, IPADDR="10.204.13.246",
PEERIPADDR="10.98.14.72", TXBW=100000, RXBW=100000, CARRYFLAG=NULL,
VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.98.14.72";
ADD IPPATH: ANI=317, PATHID=4, ITFT=IUB, TRANST=IP, PATHT=AF11, IPADDR="10.204.13.246",
PEERIPADDR="10.98.14.72", TXBW=100000, RXBW=100000, CARRYFLAG=NULL,
VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.98.14.72";
For transmission reason we will map a vlan to the IP address of the NodeB:
ADD VLANID: SRN=1, SN=18, IPADDR="10.98.14.72", VLANID=3495;
Dd IF the routing to the NodeB subnet is not included in the RNC then we should add the
routes:
ADD IPRT: SRN=1, SN=18, DSTIP="10.98.14.72", DSTMASK="255.255.255.255",
NEXTHOP="10.204.13.81", PRIORITY=HIGH, REMARK="IUB_MON2602";
ADD IPRT: SRN=1, SN=18, DSTIP="10.98.14.65", DSTMASK="255.255.255.255",
NEXTHOP="10.204.13.81", PRIORITY=HIGH, REMARK="IUB_MON2602_gw";
For M2000 to know the NodeB IP (in case of NodeB to be maintained by NMS through
BSC6900) we should Run the following command:
ADD UNODEBIP: NODEBID=32602, NBTRANTP=IPTRANS_IP, NBIPOAMIP="10.97.14.19",
NBIPOAMMASK="255.255.255.0", IPSRN=0, IPSN=22, IPLOGPORTFLAG=NO, VLANFLAG=ENABLE,
VLANID=930, VLANPRI=0;

2023-03-25 HUAWEI Confidential Page5, Total10

 Security Level: for
3G sites creation customer

Radio Part

Radio part deals with Cell setup part

Note: the configuration should be matched on both NodeB and RNC for Cell to be setup
successfully
First step is to add the Local cell (the name of the cell on the NodeB side. For detail
descriptions about this part please refer to 3GPP TS 25.401.) which is unique per NodeB
ADD ULOCELL: NodeBName="MON2602", LoCell=3260201;
ADD ULOCELL: NodeBName="MON2602", LoCell=3260211;
ADD ULOCELL: NodeBName="MON2602", LoCell=3260221;

Then we add the location and service area codes LAC and SAC:

ADD USAC: CnOpIndex=0, LAC=2322, SAC=63020;

ADD USAC: CnOpIndex=0, LAC=2322, SAC=63021;
ADD USAC: CnOpIndex=0, LAC=2322, SAC=63022;

Then we add the cells with its parameters:

ADD UCELLQUICKSETUP: CellId=63020, CellName="MON2602F01", PeerIsValid=INVALID,

CnOpGrpIndex=0, BandInd=Band8, UARFCNUplink=2862, UARFCNDownlink=3087,
PScrambCode=228, TCell=CHIP1024, LAC=2322, SAC=63020, CfgRacInd=REQUIRE, RAC=132,
SpgId=1, URANUM=D1, URA1=1, NodeBName="MON2602", LoCell=3260201, SupBmc=FALSE,
PCPICHPOWER=340,MaxTxPower=460;
ADD UCELLQUICKSETUP: CellId=63021, CellName="MON2602F11", PeerIsValid=INVALID,
CnOpGrpIndex=0, BandInd=Band1, UARFCNUplink=9663, UARFCNDownlink=10613,
PScrambCode=228, TCell=CHIP0, LAC=2322, SAC=63021, CfgRacInd=REQUIRE, RAC=132, SpgId=2,
URANUM=D1, URA1=1, NodeBName="MON2602", LoCell=3260211, SupBmc=FALSE,
PCPICHPOWER=310,MaxTxPower=447;
ADD UCELLQUICKSETUP: CellId=63022, CellName="MON2602F21", PeerIsValid=INVALID,
CnOpGrpIndex=0, BandInd=Band1, UARFCNUplink=9638, UARFCNDownlink=10588,
PScrambCode=228, TCell=CHIP0, LAC=2322, SAC=63022, CfgRacInd=REQUIRE, RAC=132, SpgId=3,
URANUM=D1, URA1=1, NodeBName="MON2602", LoCell=3260221, SupBmc=FALSE,
PCPICHPOWER=310,MaxTxPower=447;
To add the HSDPA capability we will run the following:

ADD UCELLHSDPA: CellId=63020, AllocCodeMode=Automatic, HsPdschMaxCodeNum=15,

HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON;
ADD UCELLHSDPA: CellId=63022, AllocCodeMode=Automatic, HsPdschMaxCodeNum=15,
HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON;

2023-03-25 HUAWEI Confidential Page6, Total10

 Security Level: for
3G sites creation customer

ADD UCELLHSDPA: CellId=63021, AllocCodeMode=Automatic, HsPdschMaxCodeNum=15,

HsPdschMinCodeNum=1, CodeAdjForHsdpaSwitch=ON;

To add the HSUPA capability:

ADD UCELLHSUPA: CellId=63020;

ADD UCELLHSUPA: CellId=63021;
ADD UCELLHSUPA: CellId=63022;

After adding the Cells it is not active by default, that we need to activate everything we added:

ACT UCELLHSDPA: CellId=63020;

ACT UCELLHSDPA: CellId=63021;
ACT UCELLHSDPA: CellId=63022;
ACT UCELLHSUPA: CellId=63020;
ACT UCELLHSUPA: CellId=63021;
ACT UCELLHSUPA: CellId=63022;

ACT UCELL: CellId=63020;

ACT UCELL: CellId=63021;
ACT UCELL: CellId=63022;

Configuration on NodeB side:

The configuration on the NodeB side contain two steps because the way used for
commissioning is the (remote commissioning using DHCP) the overall procedure is to allow
the M2000 or RNC to work as a DHCP server, the DHCP server has a table to map the MAC
address represented by ESN (electronic serial number) which could be found on the WMPT
card in the BBU to the (IP address + subnet mask + gateway), For complying with DHCP
principal the ports on any L3 device between the NodeB and the DHCP server which will strip
off the VLAN tag must be configured as DHCP relay through the IP forwarding (the port will
detect the Broadcast DHCP Discover message, then it will change the giaddr field in the
message to the IP address of the port that receives the DHCPDISCOVER message, then
send this message to the DHCP server). After the DHCP process completed the O&M
interface will be up and the NodeB will be accessible though the M2000 but it will work without
any data, that’s the DHCP mode. Like the bootb mode in ATM the DHCP mode will not allow
any data configuration by MML but only allow the “list” commands…

2023-03-25 HUAWEI Confidential Page7, Total10

 Security Level: for
3G sites creation customer

To add the data to the NodeB we will have to use the XML script generated by CME. For
convenient a template of XML could be prepared for the hardware part then the MML will be
allowed to be run on the NodeB so the rest of configuration could be done using the MML.
How to prepare both parts?? As follow:

XML part

The XML template for hardware can be prepared using the CME however I will include here the
templates to be modified according to each site`s data

After opening the XML file matching the hardware of the target NodeB, use a txt editor program
to change data related to communication, other data can be modified later, those data contains the
IP addresses and VLANs related to the O&M part.

MML part

The MML part is used as it is easier especially for the bulk modification. By MML we should first
remove the default data added by the XML then configure the desired data:

RMV LOCELL: LOCELL=0;

RMV SEC: STN=9999, SECN=0;
RMV IUBCP: CPPT=NCP;
RMV IUBCP: CPPT=CCP;
RMV SCTPLNK: SCTPNO=0;
RMV SCTPLNK: SCTPNO=1;
RMV IPPATH: PATHID=0;
RMV SITE: STN=9999;
RMV DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="1.1.1.1";

Then the actual data should be added we will start with the IUB IP defined by the following
command:

ADD DEVIP: SRN=0, SN=4, SBT=ETH_COVERBOARD, PT=ETH, PN=0, IP="10.98.14.72",

MASK="255.255.255.224";

Then the VLAN mapping and the IP route:

ADD VLANMAP: NEXTHOPIP="10.98.14.65", VLANMODE=SINGLEVLAN, INSTAG=ENABLE,

2023-03-25 HUAWEI Confidential Page8, Total10

 Security Level: for
3G sites creation customer

VLANID=931, SETPRIO=ENABLE;
ADD IPRT: SRN=0, SN=4, SBT=ETH_COVERBOARD, DSTIP="10.204.13.246",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="10.98.14.65";

Then like the RNC we will configure the IUB data to match that data on RNC and follow the IUB
protocol stack that’s (SCTP, NBAP and IP PATH):

ADD SCTPLNK: SCTPNO=0, CN=0, SRN=0, SN=4, LOCIP="10.98.14.72", LOCPORT=58081,

PEERIP="10.204.13.246", PEERPORT=58080;
ADD SCTPLNK: SCTPNO=1, CN=0, SRN=0, SN=4, LOCIP="10.98.14.72", LOCPORT=58082,
PEERIP="10.204.13.246", PEERPORT=58080;
ADD IUBCP: CPPT=NCP, BEAR=IPV4, BELONG=MASTER, FLAG=MASTER;
ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=1, BELONG=MASTER, FLAG=MASTER;

Like the RNC four IP PATHs are required with different QOS in the NodeB side the DSCP is used
the mapping between DSCP and PHB is used:

ADD IPPATH: PATHID=0, SN=4, SBT=ETH_COVERBOARD, PT=ETH, JNRSCGRP=DISABLE,

LOCALIP="10.98.14.72", PEERIP="10.204.13.246", DSCP=46, RXBW=100000, TXBW=100000,
TXCBS=50000000, TXEBS=0, FPMUXSWITCH=DISABLE;
ADD IPPATH: PATHID=1, SN=4, SBT=ETH_COVERBOARD, PT=ETH, JNRSCGRP=DISABLE,
LOCALIP="10.98.14.72", PEERIP="10.204.13.246", DSCP=34, RXBW=100000, TXBW=100000,
TXCBS=50000000, TXEBS=0, FPMUXSWITCH=DISABLE;
ADD IPPATH: PATHID=2, SN=4, SBT=ETH_COVERBOARD, PT=ETH, JNRSCGRP=DISABLE,
LOCALIP="10.98.14.72", PEERIP="10.204.13.246", DSCP=26, RXBW=100000, TXBW=100000,
TXCBS=50000000, TXEBS=0, FPMUXSWITCH=DISABLE;
ADD IPPATH: PATHID=3, SN=4, SBT=ETH_COVERBOARD, PT=ETH, JNRSCGRP=DISABLE,
LOCALIP="10.98.14.72", PEERIP="10.204.13.246", DSCP=10, RXBW=100000, TXBW=100000,
TXCBS=50000000, TXEBS=0, FPMUXSWITCH=DISABLE;

Then we start with the radio part by add the site name to which a sector will be related:

SET NODEBNAME: NAME="MON2602";

ADD SITE: STN=900, STNAME="MON2602";
ADD SITE: STN=2100, STNAME="MON2602";

Then the sectors are added to the sites and to the physical RF boards as to be one SEC per one
board:

ADD SEC: STN=900, SECN=0, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE,

ANT1CN=0, ANT1SRN=60, ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2N=R0B;
ADD SEC: STN=900, SECN=1, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE,
ANT1CN=0, ANT1SRN=62, ANT1N=R0A, ANT2CN=0, ANT2SRN=62, ANT2N=R0B;

2023-03-25 HUAWEI Confidential Page9, Total10

 Security Level: for
3G sites creation customer

ADD SEC: STN=2100, SECN=0, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE,

ANT1CN=0, ANT1SRN=80, ANT1N=R0A, ANT2CN=0, ANT2SRN=80, ANT2N=R0B;
ADD SEC: STN=2100, SECN=1, SECT=REMOTE_SECTOR, ANTM=2, DIVM=COMMON_MODE,
ANT1CN=0, ANT1SRN=81, ANT1N=R0A, ANT2CN=0, ANT2SRN=81, ANT2N=R0B;

The local cells are added to the sector, the local cells identified by Cell parameters and must match
the configuration on RNC:

ADD LOCELL: LOCELL=3260201, STN=900, SECN=0, SECT=REMOTE_SECTOR,

ULGROUPNO=0,DLGROUPNO=0, CN1=0, SRN1=60, SN1=0, ANT1N=ANTB, ULFREQ=2862,
DLFREQ=3087, MXPWR=460, HISPM=FALSE, RMTCM=FALSE;
ADD LOCELL: LOCELL=3260211, STN=2100, SECN=0, SECT=REMOTE_SECTOR, CN1=0, SRN1=80,
SN1=0, ULFREQ=9663, DLFREQ=10613, MXPWR=447, HISPM=FALSE, RMTCM=FALSE;
ADD LOCELL: LOCELL=3260221, STN=2100, SECN=0, SECT=REMOTE_SECTOR, CN1=0, SRN1=80,
SN1=0, ULFREQ=9638, DLFREQ=10588, MXPWR=447, HISPM=FALSE, RMTCM=FALSE;

For dual Cell configuration we need to run this command:

ADD DUALCELLGRP: FIRSTLOCELL=3260211, SECONDLOCELL=3260221;

To set the VSWR alarm and the post-processing threshold we can use the following commands:

MOD RRU: CN=0,SRN=60,SN=0,ALMPROCSW=ON,ALMPROCTHRHLD=18,ALMTHRHLD=15;

MOD RRU: CN=0,SRN=62,SN=0,ALMPROCSW=ON,ALMPROCTHRHLD=18,ALMTHRHLD=15;
MOD RRU: CN=0,SRN=80,SN=0,ALMPROCSW=ON,ALMPROCTHRHLD=18,ALMTHRHLD=15;
MOD RRU: CN=0,SRN=81,SN=0,ALMPROCSW=ON,ALMPROCTHRHLD=18,ALMTHRHLD=15;

The command DSP UCELL on RNC can be used to check the Cell setup status

For any enquiries please don’t hesitate to contact me:

[email protected]

2023-03-25 HUAWEI Confidential Page10, Total10