BSC6900V900R011 GO Data Configuration ISSUE1.0-20091130-B

www.huawei.com

Security Level: Internal Use

HUAWEI TECHNOLOGIES Co., Ltd. HUAWEI Confidential

Dual-mode BSC6900

Data Configuration—GSM Only

TSD wireless product service department-GBSS

ISSUE2.0

2009-11

HUAWEI TECHNOLOGIES Co., Ltd. Page 2HUAWEI Confidential

This slide describes the process of creating the script of the

BSC6900 initial configuration depend on the WebLMT.


Be familiar with the data configuration steps

Know the method of data effective

Know how to create a new CELL and a new BTS quickly


BSC6900 Intial Configuration Guide(V900R011C00)

BSC6900 Commissioning Guide(V900R011C00)

BSC6900 MML Command Reference (V900R011C00)

Typical Configuration Scripts (in Intial Configuration Guide)


Chapter 1 Summarize of Data ConfigurationChapter 1 Summarize of Data Configuration

Chapter 2 Data Configuration


The Evolution of Data Configuration Client

We can use GUI and MML to complete the data configuration for BSC6000,

one for Graphic User Interface, another for Man Machine Language which can

run batch script. For BSC6900, we use WebLMT and CME to do the data configuration. No

need to install the server software on your PC, and we can login by Web

anywhere to do the data configuration by MML command.

GUI LMT MML LMT

M2000 CME

Web LMT

M2000 CME

BSC6000 BSC6900


WebLMT Login

Enter the external virtual IP address of the OMU in the address bar on the IE. Press Enter

on the keyboard, or click Go next to the address bar to display the login window of the

BSC6900. Enter the Name, Password, and Verify Code. Select the User Type. You can select Local

User or EMS. If the verify code is illegible, click Change the verify code for a new code.


Data Configuration Interface of MML

Navigation Tree

Command Display

Running

Failed

Running Successful

Input Command


Run Batch Interface


Data Configuration Modes

Principle of Effective Mode Configuration The process of effective mode configuration is as follows:

The BSC6900 is switched to effective mode.

The configuration console (LMT or M2000) sends MML commands to the configuration

management module of the OMU.

The configuration management module of the OMU sends the configuration data to the

database of the related host board and writes the data to the OMU database.

Realize We can use SET CFGDATAINEFFECTIVE to switch between effective and ineffective

mode.

One command just for one subrack.

This mode used in modifying data dynamic.


Data Configuration Modes

Principle of Ineffective Mode Configuration The process of ineffective mode configuration is as follows:

The BSC6900 is switched to ineffective mode.

The configuration console (LMT or M2000) sends MML commands to the configuration

management module of the OMU.

The configuration management module sends only the configuration data to the OMU database.

When a subrack or the BSC6900 is reset, the OMU formats the configuration data in the

database into a .dat file, loads the file onto the related host boards, and then activates the

configuration data.

Realize We can use SET CFGDATAINEFFECTIVE to switch between effective and ineffective mode.

One command just for one subrack.

This mode used in Initial data Configuration .


Data Configuration Take Effect

Begin

Generating the Data File for the Loading

Setting the Loading Mode

Resetting the BSC6900 Boards

Checking the Consistency of the Data and the Version

Finish

Set the subrack as ineffective mode

SET CFGDATAINEFFECTIVE

Initialize the BSC6900 configuration Data

RST DATA

Run MML batch RUN BATCHFILE

Format the data files

FMT DATA

Set the subrack work mode

SET LODCTRL

Reset subrack RST SUBRACK

Check the consistency

ACT CRC

Set the subrack as effective mode

SET CFGDATAEFFECTIVE

Updating the OMU Database


Change in MML Data configuration of BSC6900

Equipment and logical data are separated in site and cell data configuration. Equipment data, logical data, bind.

SRAN sites ： 3900 sites of 2G and 3G unify to SRAN sites （ 3900 sites with 9.0

software version） Types of sites supported SRANMODE:

BTS3900,BTS3900A,DBS3900,BTS3036,BTS3036A,DBS3036A,BTS3900L ； Select SRANMODE when add bts; Select actual cabinets when add bts cabinets, such as APM30, RFC etc. Designate the cabinet, subrack and slot information when add RXU board; Designate the cabinet, subrack and slot information of main control board which transmission

is connected to in BTS when add bts connect. The data of the site unsupported SRANMODE and cannot be changed to the site supported

SRANMODE by MML data configuration. Others

OPC is binded to cells, not to the BSC subrack; Clock source is configured for interface boards, not for BSC subrack; Signaling links set is need to add; GSM CN node is need to configure.


PC OMU

FunctionsThe PC OMU is auxiliary software developed on the basis of the OMU software of

Windows version. The PC OMU enables Huawei engineers to operate the OMU software on their PCs.

Data configuration through MML commands Verify the data configuration through the license file Panel display on the LMT (optional)

Methods of Obtaining the Software and Documents Software： http://support.huawei.com

Software -> Version Software -> Wireless Product Line -> Single RAN -> MBSC -> BSC6900 -> BSC6900 V900R011 -> BSC6900 V900R011C00SPC300 or later version. Windows version (windows is in the software name) should be used.

Documents ： BSC6900 PC OMU Operation Guide in Version Documents

Method of Starting and Stopping PC OMU net start omud net stop omud

Default functions setting Device panel display, FTP tool, alarm, tracing, and monitoring are disabled by default Built-in OMU board mode, not the external BAM server mode


Chapter 1 Summarize of Data Configuration

Chapter 2 Data ConfigurationChapter 2 Data Configuration


The Chat Flow of Data Configuration

Configuring the

system information

Configuring a cabinet

Configuring a subrack

Configuring a board

Configuring a

communication patch

between subracks

Configuring the time

Configuring the

system information

Configuring a cabinet

Configuring a subrack

Configuring a board

Configuring a

communication patch

between subracks

Configuring the time

The Equipment Data

The Equipment Data

Configuring the

basic data

Configuring the

OPC

Configuring the

basic data

Configuring the

OPC

Global Information

Global Information

Configuring Ater

interface

Configuring A

interface

Configuring Gb

interface

Configuring Ater

interface

Configuring A

interface

Configuring Gb

interface

Interface Data

Interface Data

Set the Clock

source of

Interface board

Add the Clock

source of the

system

Set the work

mode of the

system Clock

source

Set the Clock

source of

Interface board

Add the Clock

source of the

system

Set the work

mode of the

system Clock

source

The Clocks Data

The Clocks Data

Configuring the

BTS device data

Configuring the

logic data of the cell

Configuring the

transmission data

Activating BTS

data

Configuring the

BTS device data

Configuring the

logic data of the cell

Configuring the

transmission data

Activating BTS

data

GBTS and Cells

GBTS and Cells

Data configuration scene BM/TC Separated.

A, Ater, Abis Over TDM Transmission.

Inner PCU, Gb over FR.


Step 1: Configuring the Global Information

Finish

Begin

Configuring the Equipment Data


Configuring the Clocks

Configuring the Global Information

Configuring a GSM BTS and Its Cells

Configuring the Basic Data

SET BSCBASIC1

2 ADD GCNOPERATEOR

Configuring OPCADD OPC3

4 ADD N7DPC



Configuring the Basic Data: SET BSCBASIC: <Name>, <AreaCode>, <CC>, <AVer>, <UmVer>, <AbisVer>,

<HiFreqBandSupport>, <ServiceMode>, <SptRanSharing><IsSupportTcPool><IsMainBSC><ATERTRANSMODE>;

Aver, Umver, AbisVer: Phase tag for GSM protocols supported by the A interface. The value of

this parameter is chosen according to the A interface phase tag provided by the

MSC.Recommended Value: "GSM_PHASE_2" is recommended in common scenarios. If the

BSC needs to support GPRS services, EDGE services, AMR services, eMLPP services, inter-

RAT handover, and A over IP mode, "GSM_PHASE_2Plus" is recommended. ServiceMode: Service mode of the BSC,GUI Value Range: SEPARATE(Separate),

TOGETHER(Together), AIP(AIP). SptRanSharing: Whether to support RAN Sharing . IsMainBSC: Whether the BSC is a primary BSC . ATERTRANSMODE: Transport mode of the Ater interface. The Ater interface can be in TDM

or in IP transport mode. Example: SET BSCBASIC: AreaCode=021, CC=86, AVer=GSM_PHASE_2Plus,

UmVer=GSM_PHASE_2Plus, AbisVer=GSM_PHASE_2Plus, HiFreqBandSupport=DCS1800, ServiceMode=SEPARATE, ATERTRANSMODE=TDM;



Configuring the Basic Data: ADD GCNOPERATOR: <OperatorType>, <OPNAME> ， <MCC>, <MNC>,

<MSCPOOLALLOW>, <SGSNPOOLALLOW>; OperatorType: Primary operator or secondary operator, GUI Value Range: PRIM(Primary

Operator), SEC(Secondary Operator). OPNAME: Name of the operator. This parameter uniquely identifies an operator. MCC: Mobile country code. This parameter identifies the country where a

mobile .subscriber is located, for example, the Chinese MCC is 460. MNC: Mobile network code. This parameter identifies the public land mobile network

(PLMN) where a mobile subscriber is homed. Example: ADD GCNOPERATOR: OperatorType=PRIM, OPINDEX=0,

OPNAME="TEST", MCC="460", MNC="04", MSCPOOLALLOW=NO,

SGSNPOOLALLOW=NO;



Configuring the OPC ADD OPC: <NAME>, <SPX>, <NI>, <SPCBITS>, <SPC>

NAME: OSP name.

SPX: OSP Index, To identify an OSP uniquely.

NI ： Network ID. GUI Value Range: INT(INT), INTB(INTB), NAT(NAT), NATB(NATB).

SPCBITS ： OSP code bits. GUI Value Range: BIT14(BIT14), BIT16(BIT16), BIT24(BIT24).

SPC ： Hexadecimal OSP code.

Example: ADD OPC: NAME="BSC130", SPX=0, NI=NATB, SPCBITS=BIT14,

SPC=H'0A03;



Configuring DPC ADD N7DPC: <NAME>, <DPX>, <SPX>, <SPDF>, <DPC>, <DPCT>;

NAME ： DSP name.

DPX ： The DSP index uniquely indicates the corresponding relationship of an DSP and

OSP.

SPX ： To identify an OSP uniquely.

DPC ： The DSP code is in the hexadecimal format and cannot be 0. The value is unique

in the SS7 signaling network. The number of DSP bits is the same as that of the SPC. If

the designated bit is Bit14 in the adding of the SPC, the value range of the parameter is

H'1~H'3FFF(1~16383). If the designated bit is Bit16 in the adding of the SPC, the value

range of the parameter is H'1~H'FFFF(1~65535). If the designated bit is Bit24 in the

adding of the SPC, the value range of the parameter is H'1~H'FFFFFF(1~16777215).

DPCT ： DSP type. GSM only mode configured as A.

Example: ADD N7DPC: NAME="MSC", DPX=0, SPX=0, SPDF=WNF, DPC=H'0910,

DPCT=A;


Step 2: Configuring the Equipment Data

Finish

Begin

Configuring the Interfaces


Configuring the Clocks



Configuring the System

InformationSET SYS1

Configuring a Cabinet

ADD CAB2

Configuring a Subrack

ADD SUBRACK3

Configuring a Board

ADD BRD5

Configuring a Communication Path Between

Subrack

ADD SRCONPATH6

Configuring the Time

SET TZ7

8 ADD SNTPSRVINFO

4 SET SCUPORT



Configuring the System Information SET SYS: <SYSDESC>, <SYSOBJECTID>, <SYSCONTACT>,

<SYSLOCATION>, <SYSSERVICES>; SYSDESC ： Description of the Base Station Controller. SYSOBJECTID ： Identifier of the Base Station Controller. SYSCONTACT ： Contact way of the Base Station Controller supplier. SYSLOCATION ： Location of the Base Station Controller. SYSSERVICES ： Services provided by the Base Station Controller. Example: SET SYS: SYSDESC="LAB", SYSOBJECTID="001",

SYSLOCATION="XINTIANXIA";



Configuring a Cabinet ADD CAB: <CN>, <CABT>；

CN ： Number of the cabinet . CABT ： Whether the added cabinet is a remote cabinet. Example ： ADD CAB: CN=1, CABT=YES;

Note The MPR is configured by default. You cannot add or remove this cabinet by running the

MML command. The cabinets consist of the Main Processing Rack (MPR), Extended

Processing Rack (EPR), and TransCoder Rack (TCR).

If the TC subrack is configured in the local cabinet, the remote TCR cannot be configured.

Configuring a Subrack ADD SUBRACK: <SRN>, <SRName>, <TYPE>;

SRN ： Number of the subrack. SRName ： Name of the subrack to be added. TYPE ： Type of the subrack. ISTCCENTR ： Whether the subrack is a remote main TC subrack. Example ： ADD SUBRACK: SRN=3, SRName="TC1", TYPE=TCS, ISTCCENTRAL=YES; ADD SUBRACK: SRN=1, SRName="EPR1", TYPE=EPS, WORKMODE=GO;



Configuring a Subrack ， enable the panel port of the SCUa board in the main subrack

SET SCUPORT: <SRN>, <PN>, <Switch >; SRN ： Subrack No. PN ： Port No. Switch ：端口开关。 GUI Value Range: CLOSE, OPEN 。 Example：

SET SCUPORT: SRN=0, PN=0, Switch=OPEN;SET SCUPORT: SRN=0, PN=2, Switch=OPEN;

Note For the active and standby SCUa boards, if you set the attributes of the port on one SCUa

board, those of the corresponding port on the other SCUa boards are also set. Except for port 10 and 11 on the SCUa board in subrack 0 when the external OMU is used,

this command modifies the attributes of both an odd numbered port and an even numbered

port. For example, if the attributes of port 2 on the SCUa board are modified, the attributes of

port 3 are also modified. When the external OMU is used, only one of port 10 and port 11 on

the SCUa board in subrack 0 can be enabled.



Configuring a Board ADD BRD ： <SRN>, <BRDCLASS>, <BRDTYPE>, <LGCAPPTYPE>, <SN>,

<MPUSUBRACK>, <MPUSLOT>; BRDCLASS ： Classes of boards classified according to function modules, GUI Value

Range: INT, DPU, XPU, TNU, OMU. BRDTYPE ： Type of the board.

LGCAPPTYPE ： Logic function type of the board, GUI Value Range: OAM,

TDM_Switching, GCP, UCP, RGCP, RUCP, IBCA, GTC, GPCU, UUP, ATM, IP, FR,

HDLC, TDM, GbIP, Abis_TDM, Ater_TDM, Pb_TDM, A_TDM, Abis_IP.

MPUSUBRACK ： Number of the subrack where the MPU is located. MPUSLOT ： Number of the slot where the MPU is located. Example: ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=XPUa,

LGCAPPTYPE=RGCP, SN=0;

ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=XPUa, LGCAPPTYPE=GCP,

SN=8, MPUSUBRACK=0, MPUSLOT=0;



Configuring a Communication Path ADD SRCONPATH: <SRN1>, <SRN2>, <TDMN1>, <TDMN2>;

SRN1 ： Number of the subrack of one end of the inter-subrack connection channel. SRN2 ： Number of the subrack of the other end of the inter-subrack connection channel

TDMN1 ： Each subrack has six TDM numbers, ranging from 0 to 5. Subrack 1 TDM Port

No. refers to the TDM number on subrack 1 of the inter-subrack connection. TDMN1 ： Each subrack has six TDM numbers, ranging from 0 to 5. Subrack 1 TDM Port

No. refers to the TDM number on subrack 1 of the inter-subrack connection. Example ： ADD SRCONPATH: SRN1=0, SRN2=1, TDMN1=0, TDMN2=0;

Note Two different inter-subrack connection paths cannot be connected to the same TDM in an

identical subrack.

The two ports of one inter-subrack connection path cannot be connected to the same

subrack.

The inter-subrack connection path can only be connected to the subracks of the same

types.

At most three inter-subrack connection paths can be configured between two subracks of

the same type.



Configuring the Time Zone SET TZ: <ZONET>,< DST>;

ZONET ： Time zone. DST:Whether daylight saving time starts. Example ： SET TZ: ZONET=GMT-0800 ， DST=NO;

Configuring the SNTP Server ADD SNTPSRVINFO: <IP>, <PT>;

IP ： IP address of the server. PT ： Number of the port that provides the time information on the SNTP server. Example: ADD SNTPSRVINFO: IP="192.168.88.200", PT=123;

Note: The number of SNTP servers cannot exceed 16.

If multiple SNTP servers are configured, the OMU selects the best SNTP server as the

clock source according to the algorithm defined in the Network Time Protocol (NTP).

The IP address is the IP address of the SNTP server. The SNTP client in the active OMU

receives the time information from the SNTP server. The IP address cannot be set to a

special address such as 0.0.0.0 or 127.0.0.1.


Step 3: Configuring the Interfaces

Finish

Begin



Configuring Clock

Configuring the Interface


Configuring the A interface

Configuring the physic Layer over A interface

ADD AE1T1

5

Configuring the control plane Over A interface

ADD MTP3LKS

ADD MTP3LNK

ADD MTP3RT

6

Configuring the Ater Interface

Configuring an Ater Connection Path

ADD ATERCONPATH1

Configuring an Ater OML

ADD ATEROML2

Configuring an Ater Signaling Link

ADD ATERSL3

Configuring the GB Interface

Configuring PCU typeSET BSCPCUTYPE

7

Configuring SGSN nodeADD SGSNNODE

8

Configuring NSEADD NSE

9

Configuring BCADD BC

10

Configuring NSVCADD NSVC

11

Configuring PTPBVCADD PTPBVC

12

4 Configuring the CN node

ADD GCNNODE


Step 3: Configuring the Interface—Ater Interface

Configuring an Ater connection path ADD ATERCONPATH ： <ATERIDX>, <BMSRN>, <BMSN>, <BMPN>,

<TCSRN>, <TCSN>, <TCPN>; ATERIDX ： Index of an Ater connection path. BMSRN 、 BMSN 、 BMPN ： BM Subrack NO, Slot NO, Port NO. TCSRN 、 TCSN 、 TCPN ： TC Subrack NO, Slot NO, Port NO. Example: ADD ATERCONPATH: ATERIDX=0, BMSRN=0, BMSN=14, BMPN=0,

TCSRN=3, TCSN=14, TCPN=0;

Note This command applies only in BM/TC separated configuration mode.

If the TC pool function is enabled, this command applies to only the active BSC. For the

standby BSCs, you need to run the ADD ATERE1T1 command to add the Ater

connection path.


Step 3: Configuring the Interface—Ater Interface Configuring Ater OML

ADD ATEROML: <ATEROMLINX>, <ATERPIDX>, <TSMASK>; ATEROMLINX ： Ater maintenance link index. ATERPIDX ： Ater connection path index. TSMASK ： Time slots for Ater operation and maintenance. These time slots are provided by

the ports connected to the Ater connection path. Example ： ADD ATEROML: ATEROMLINX=0, ATERPIDX=0, TSMASK=TS1-1&TS2-

1&TS3-1&TS4-1&TS5-1&TS6-0&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-

0&TS14-0&TS15-0&TS16-0&TS17-0&TS18-0&TS19-0&TS20-0&TS21-0&TS22-0&TS23-

0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0; Note

Only the remote TCS can be configured with the OML on the Ater interface. Before configuring the OML on the Ater interface, you must configure the Ater connection

path. The Ater OML only configured between the local switching subrack and the remote main

subrack. The BM and TC subracks used for the OML on the Ater interface must be main

subracks. Besides timeslot 1, the OML on the Ater interface must contain four consecutive timeslots. At most two OMLs on the Ater interface can be configured in the entire system.


Step 3: Configuring the Interface—Ater Interface

Configuring an Ater Signaling Link ADD ATERSL: <BTCFLAG>, <ATERIDX>, <ATERMASK>, <TNMODE>;

BTCFLAG ： GUI Value Range: CFGBM(BM), CFGTC(TC). CFGBM indicates that the signaling link is

from XPU to Ater interface board in BM, and CFGTC indicates the signaling link from Ater interface board

in TC to the A interface board. To configure a whole AterRSL from A interface board to XPU board, two

MML commands are needed.

TNMODE ： The Ater signaling link operates in the terrestrial transmission or satellite

transmission mode. In the areas such as desert and lake where the terrestrial transmission

is difficult, the satellite transmission can be used. Example ： ADD ATERSL: BTCFLAG=CFGBM, ATERIDX=0, ATERMASK=TS1-0&TS2-0&TS3-0&TS4-0&TS5-0&TS6-

0&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-1&TS17-0&TS18-0&TS19-0&TS20-

0&TS21-0&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, TNMODE=TRRS;

ADD ATERSL: BTCFLAG=CFGTC, BSCTID=0, ATERIDX=0, ATERMASK=TS1-0&TS2-0&TS3-0&TS4-0&TS5-0&TS6-

0&TS7-0&TS8-0&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-1&TS17-0&TS18-0&TS19-0&TS20-

0&TS21-0&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, TNMODE=TRRS;

Note

Each BSC can be configured with a maximum of 64 Ater connection links; Each A interface

board can be configured with a maximum of 64 signaling links; Each ATER interface board

can be configured with a maximum of 64 timeslots used for Ater signaling link.


Step 3: Configuring the Interface—A Interface

Configuring GSM CN Node ADD GCNNODE: <CNNODEIDX>, <DPC>, <DPCGIDX>, <OPNAME>,

<CNID><DFDPC>; CNNODEIDX ： Node index of an MSC. DPC ： Code of a destination signaling point (DSP) in a signaling network. In a signaling

network, each signaling point has a corresponding signaling point code (SPC).

DPCGIDX ： Signaling group of a DSP.

If multiple DSPs or one DSP serves as a logical entity, this logical entity is a DSP group.

OPNAME ： Name of the operator. This parameter uniquely identifies an operator.

CNID ： Used to uniquely identify an MSC.



DFDPC: For the default DPC corresponds to the CN of the primary operator: when only

one DPC is configured, this parameter must be set to "YES", indicating that all the calls

for the operator are accessed through the CN identified by the DPC. When multiple DPCs

are configured, this parameter also determines the DPC that allows the generation of

ESN. In this case, the parameter is set to "YES" for this DPC while the value for other

DPCs is "NO".

For the CN of a secondary operator, this parameter must be set to “Yes" when only one

DPC is configured. This indicates that all the calls for the secondary operator are

accessed through the CN. When multiple DPCs are configured, this parameter is invalid.

Example: ADD GCNNODE: CNNODEIDX=0, DPX=0, DPCGIDX=0, OPNAME="TEST",

CNID=0, DFDPC=YES;



Configuring the Physical Layer ADD AE1T1: <SRN>, <SN>, <PN>, <STCIC>, <DPCGIDX>, <OPCIDX>,

<BSCFLAG>; STCIC ： Number of the start CIC. The C/C of each E1/T1 timeslot can be calculated on

the basis of this parameter. Assume that the start CIC is 100, the CIC of the E1 timeslots on the A interface will automatically be set to 100, 101, 102, 103, and so on. Assume that the CIC of an E1 timeslot is 65535, the CICs of all successive E1 timeslots are all 65535.

BSCFLAG ： It indicates whether the A interface E1/T1 is the primary BSC or secondary BSC.

Example: ADD AE1T1: SRN=0, SN=16, PN=0, STCIC=0, DPCGIDX=0, OPCIDX=0, BSCFLAG=MAINBSC;

Note You can configure up to 512 E1/T1 links on the A interface board. The CICs of the two E1/T1 timeslots on the A interface with the same OSP index and

DPC Group Index must be different. In practice, however, running this command always

fails due to the same CIC of the two timeslots. In this case, you need to adjust the Start

CIC to ensure that the CIC of an E1/T1 timeslot on the A interface differs from that of

another timeslot.



Configuring the Control Plane ADD MTP3LKS: <SIGLKSX>, <DPX>, <NAME>;

SIGLKSX ： To identify an signaling link set uniquely. DPX ： The DSP index uniquely indicates the corresponding relationship of an DSP and

NAME ： Signaling link set name. Example: ADD MTP3LKS: SIGLKSX=0, DPX=0, NAME="LINK1";

Note The DSP specified by DSP index must exist, and it must be an adjacent DSP. One adjacent DSP can be configured with only one signaling link set.



Configuring the Control Plane ADD MTP3LNK: <SIGLKSX>, <SIGSLC>, <BEARTYPE>, <TCMODE>, <ATERIDX>,

<ATERTSMASK>, <ASRN>, <ASN>, <MTP2LNKN>, <APN>, <ATSMASK>; SIGLKSX ： To identify an signaling link set uniquely. SIGSLC ： M3UA link ID of the specified link set.

BEARTYPE ： Link bearer type. GUI Value Range: MTP2(MTP2), SAAL(SAAL).

TCMODE ： To specify the mode of TC. GUI Value Range:

SEPERATE_PRINCIPAL(Principal BSC), SEPERATE_SUBORDINATE(Subordinate

BSC), TOGETHER(BSC/TC Together). ATERIDX ： Index of an Ater connection path. ATERTSMASK ： Ater interface timeslot mask. MTP2LNKN ： To identify an MTP2 link. APN ： A interface port No.. ATSMASK ： A interface timeslot mask.



Configuring the Control Plane Example: ADD MTP3LNK: SIGLKSX=0, SIGSLC=0, BEARTYPE=MTP2,

TCMODE=SEPERATE_PRINCIPAL, ATERIDX=0, ATERMASK=TS1-0&TS2-0&TS3-



0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, ASRN=3,

ASN=16, MTP2LNKN=0, APN=0, ATSMASK=TS1-0&TS2-0&TS3-0&TS4-0&TS5-0&TS6-



0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, NAME="mtp3link0";



Note The link set to be used must exist.

Signalling Link Code must be set to the same value at the two ends of the signaling link.

The total number of MTP3 signaling links cannot exceed 1904.

The number of MTP3 links controlled by the same CPUS subsystem cannot exceed 50.

ADD MTP3RT: <DPX>, <SIGLKSX>, < NAME>; DPX ： The DSP index uniquely indicates the corresponding relationship of an DSP and

OSP. SIGLKSX ： To identify an signaling link set uniquely. NAME ： One MTP3 route name. Example: ADD MTP3RT: DPX=0, SIGLKSX=0, NAME="RT1";

Note DSP index and Signalling link set index must exist.

If the DSP specified by DSP index is inconsistent with that specified by Signalling link

set index, you need to check whether the DSP specified by Signalling link set index

has a transfer function.

In addition to a direct route, it is recommended to add an alternative route as a backup.

At most 238 MTP3 routes can be configured for the BSC.


Step 3: Configuring the Interface—Gb Interface

Configuring the PCU Type SET BSCPCUTYPE: <TYPE>;

TYPE ： Type of the PCU.

GUI Value Range: OUTER(Outer PCU), INNER(Inner PCU).

Example: SET BSCPCUTYPE: TYPE=INNER;

Configuring the SGSN Node ADD SGSNNODE: <CNOPNAME>, <CNID>;

OPNAME ： Name of the operator. This parameter uniquely identifies an operator. CNID ： Identifies a service provider. Example: ADD SGSNNODE: OPNAME="TEST", CNID=0;



Configuring an NSE ADD NSE: <NSEI>, <SRN>, <SN>, <PT>, <CNOPNAME>, <CNID>;

NSEI ： Identifies a unique NSE. SRN 、 SN ： Subrack number and slot number of the XPU bound to the.

PT ： Subnet protocol type. GUI Value Range: GB_OVER_FR(Gb over FR),

GB_OVER_IP(Gb over IP). OPNAME ： Name of the operator. This parameter uniquely identifies an operator. CNID ： Identifies a service provider. Example: ADD NSE: NSEI=0, SRN=0, SN=0, PT=GB_OVER_FR, OPNAME="TEST",

CNID=0;

Note The NSE must be configured in the MPS or EPS.

A BSC can be configured with up to 128 NSEs.

When Protocol type is set to GB_OVER_IP and Subnetwork Configure Mode is set to

DYNAMIC, then Server IP and Server Port are determined by the serving GPRS support

node (SGSN). If Subnetwork Configure Mode is set to STATIC, then Server IP and Server

Port need not be set.

NSE identifier must be consistent with that on the SGSN side.



Configuring a BC ADD BC: <SRN>, <SN>, <PN>, <BCID>, <TS>;

SRN 、 SN 、 PN: Subrack number, Slot number, Port number. BCID ： Identifies one BC at the same port. The BCID's value range of PEUa board is

0~255 and that of POUc board is 0~511. TS ： Timesolt of bearing channels. Example: ADD BC: SRN=0, SN=24, PN=0, BCID=0, TS=TS1-1&TS2-1&TS3-1&TS4-


1&TS15-1&TS16-1;

Note Bearing timeslot and Protocol type must be consistent with those on the Serving GPRS

Support Node (SGSN) side.



Add NSVC ADD NSVC: <NSVCIDX>, <NSVCI>, <NSEI>, <SRN>, <SN>, <BCID>, <DLCI>;

NSVCIDX ： NSVC index, identifying a unique NSVC. NSVCI ： NSVC ID, identifying a unique NSE. This ID must be negotiated with the peer

SGSN. NSEI ： Identifies a unique NSE. BCID ： Identifies one BC at the same port. The BCID's value range of PEUa board is

0~255 and that of POUc board is 0~511. DLCI ： ID of the data link connection of the NSVC. It is an interworking parameter which

must be consistent on the BSC and the peer. Example: ADD NSVC: NSVCIDX=0, NSVCI=0, NSEI=0, SRN=0, SN=24, BCID=0,

DLCI=16;

Note An NSVC is carried on a bearer channel (BC) on the E1/T1 link. A BC can be configured

with several NSVCs (differentiated by The identifier of Data Link Connection). An

NSVC can belong to only one BC and only one NSE, whereas an NSE can correspond to

several NSVCs.

NSE identifier, NSVC identifier, and The identifier of Data Link Connection must be

consistent with those on the SGSN side.



Configuring a PTPBVC ADD PTPBVC: <NSEI>, <BVCI>, <IDTYPE>, <CELLNAME>;

NSEI ： Identifies a unique NSE. BVCI ： Identifies one PTP BVC.

IDTYPE ： Subscribers can specify the cell according to the index or the name.

GUI Value Range: BYNAME(By Name), BYID(By Index).

Example: ADD PTPBVC: NSEI=0, BVCI=2, IDTYPE=BYNAME, CELLNAME="CELL1";

Note When the SGSN pool function is disabled, a cell can be configured with only one PTP

BVC. When the SGSN pool function is enabled, a cell can be configured with up to 32

PTP BVCs.

An NSE can support up to 2048 PTP BVCs.

This command can be used only in built-in PCU mode.


Step4: Configuring the Clocks

Finish

Begin




Configuring Clock


set the clock source

SET CLK1

add the clock source of the

system ADD CLKSRC2

set the work mode of the system clock source

SET CLKMODE3



Set Board Clock Source SET CLK: < SRT>, <SRN>, <SN>, <BT>, <REF2MCLKSR>,

<BACK8KCLKSW1>; SRT: Type of the subrack. GUI Value Range: MPS, EPS, TCS.

SRN: Number of the subrack.

BT: Type of the board. GUI Value Range: AEUa, PEUa, AOUa, POUa, UOIa, EIUa, OIUa,

AOUc, POUc, UOIc.

REF2MCLKSR: Clock source link No. of output clock 1. GUI Value Range: 0~31. BACK8KCLKSW1 ： Switch of 8K output clock 1 on the backplane board. Example: SET CLK: SRT=TCS, SRN=3, SN=16, BT=EIUa, REF2MCLKSRC=0,

BACK8KCLKSW1=ON; SET CLK: SRT=MPS, SN=14, BT=EIUa, REF2MCLKSRC=0, BACK8KCLKSW1=ON;

Note The clock source of the interface board in the EPS cannot be set to the 8 kHz output

clock source.

Each 8 kHz clock of the backplane has only one clock source. The output switch cannot

be set for multiple interface boards at the same time.



Add Clock Source ADD CLKSRC: <SRCGRD>, <SRCT>;

SRCGRD ： Priority of the clock source. GUI Value Range: 1~4.

SRCT ： Type of the clock source. GUI Value Range: BITS1-2MHZ(2MHZ Building

Integrated Timing Supply system 1), BITS2-2MHZ(2MHZ Building Integrated Timing

Supply system 2), BITS1-2MBPS(2MBPS Building Integrated Timing Supply system 1),

BITS2-2MBPS(2MBPS Building Integrated Timing Supply system 2), 8KHZ(8KHZ),

GPS(Globe Positioning System), LINE1_8KHZ(8KHZ line1), LINE2_8KHZ(8KHZ line2),

BITS1-T1BPS(T1BPS Building Integrated Timing Supply system 1), BITS2-

T1BPS(T1BPS Building Integrated Timing Supply system.

Example: ADD CLKSRC: SRCGRD=1, SRCT=LINE1_8KHZ ；



Set Clock Working Mode SET CLKMODE: <MODE> ， <SRCGRD>;

MODE ： Working mode of the system clock. Working modes of the system clock are as

follows:

(1) MANUAL: In this mode, you must specify a clock source and prevent the switching of

the clock source.

(2) AUTO: In this mode, you do not need to specify a clock source and the system

automatically selects the clock source with the highest priority.

(3) FREE: In this mode, the clock source of GCGa or GCUa is used.

GUI Value Range: MANUAL, AUTO, FREE Example: SET CLKMODE: MODE=AUTO;

Note If the manually-set clock source is unavailable, the switchover fails. Then, the current

clock source remains unchanged.


Step 5: Configuring a GSM BTS and Its Cells

Finish

Begin



Configuring Clock




Configure BTS

ADD BTS1

Configure BTS subrack

ADD BTSCABINET2

Configuring the Logical Data

Configure Cell data

ADD CELL

ADD GCELLOSPMAP

ADD GCELLFREQ

4

Configure TRX data

ADD BTSTRXBRD

ADD BTSRXUCHAIN

ADD BTSRXUBRD

5

Bind a Cell to a BTS

ADD CELLBIND2BTS6

Configure BTS board

ADD BTSBRD3

Bind a physical board to

a logic TRX

ADD TRXBIND2PHYBRD

7

Configuring the Transmission Data

ADD BTSCONNECT8

Activating the BTS Configuration

ACT BTS9



Configuring a GSM BTS ADD BTS: < BTSID>, <BTSNAME>, <BTSTYPE>,

<SEPERATEMODE> ， <SERVICEMODE> ， <SRANMODE>; SEPERATEMODE ： Whether to enable the BTS to support the separation between the

physical and logical. GUI Value Range: SUPPORT(Support), UNSUPPORT(Not Support).

SERVICEMODE ： Service bearer mode of the BTS. GUI Value Range: TDM, HDLC,

HDLC_HubBTS, IP.

SRANMODE ： Whether to enable the BTS to identify an object in the BTS in normalized

mode, for example, to identify a board by the slot No., subrack No., and cabinet No. and

to identify a transmission port by the port No. in a board. GUI Value Range:

SUPPORT(Support), NOT_SUPPORT(Not Support).

Example: ADD BTS: BTSID=0, BTSNAME="BTS3900", BTSTYPE=BTS3900_GSM,

SEPERATEMODE=SUPPORT, SERVICEMODE=TDM, SRANMODE=SUPPORT;



Add BTS Cabinet ADD BTSCABINET: <IDTYPE>, <BTSID>,<CN>, <TYPE>;

IDTYPE ： Index type of the BTS. BYNAME: query by BTS name; BYID: query by BTS

index. GUI Value Range: BYNAME(By Name), BYID(By Index).

BTSID ： ID of the BTS. The BTS ID must not conflict with other BTS IDs in the BSC.

CN ： Number of the cabinet.

TYPE ： Type of a cabinet.

Example: ADD BTSCABINET: IDTYPE=BYID, BTSID=1, CN=0, TYPE=BTS3012;

Add BTS Board ADD BTSBRD:<IDTYPE>, <BTSID>, <CN>, <SRN>, <SN>;

Example: ADD BTSBRD: IDTYPE=BYID, BTSID=0, CN=0, SRN=11, SN=0, BT=FMU;



3900 Series Base Stations ADD BTSRXUCHAIN: <IDTYPE>, <BTSID>, <RCN>, <TT>, <HCN>, <HSRN>,

<HSN>, <HPN>; Number of the RXU chain or ring. The value scope is 0~11 for Non-SRAN BTS and 0~249 for

SRAN BTS. The RXU chain No. is unique in the same BTS. A maximum of 12 RXU chains

can be configured in one BTS.

RXU topology type, that is, RXU ring topology or RXU chain topology. In the case of the ring

topology, the optical ports of the head and tail boards must be specified. In the case of the

chain topology, only the optical port of the head board must be specified.

Number of the cabinet where the head board of the RXU chain or ring is located.

HSRN:Number of the subrack where the head board of the RXU chain or ring is located. The

subrack No. is unique in the same BTS.

HSN: Number of the slot where the head board of the RXU chain or ring is located. The slot

No. is unique in the same BTS.

HPN:The number of the optical port of the head board in the RXU chain or ring.

Example: ADD BTSRXUCHAIN: IDTYPE=BYID, BTSID=0, RCN=0, TT=CHAIN, HCN=0,

HSRN=0, HSN=6, HPN=0;



3900 Series Base Stations ADD BTSRXUBRD: <IDTYPE>, <BTSID>, <BT>, <CN>, <SRN>, <SN>,

<RXUNAME>, <RXUCHAINNO>, <RXUPOS>; BT:Type of the newly added RXU board. GUI Value Range: DRRU(DRRU),

DRFU(DRFU), MRRU(MRRU), XRRU(XRRU), MRFU(MRFU), GRFU(GRFU),

GRRU(GRRU), XRFU(XRFU), BTS3900E(BTS3900E).

RXUCHAINNO: Number of the RXU chain where the board is located.

RXUPOS: Position of the RXU board on an RXU chain.

Example: ADD BTSRXUBRD: IDTYPE=BYID, BTSID=0, BT=DRFU, CN=0, SRN=4,

SN=0, RXUNAME="drfu0", RXUCHAINNO=0, RXUPOS=1;



Set the Send/Receive Mode and Work Mode of the RXU Board SET BTSRXUBP: <IDTYPE>, <BTSID>, <RXUIDTYPE>, <RXUNAME>,

<RXUTYPE>, <SndRcvMode3>; RXUIDTYPE: Type of the RXU board index.

RXUNAME: Name of the RXU board. The RXU name is unique in one BTS.

RXUTYPE: Type of the RXU board. GUI Value Range: DRRU(DRRU), DRFU(DRFU),

MRRU(MRRU), MRFU(MRFU), GRFU(GRFU), GRRU(GRRU), BTS3900E(BTS3900E).

SndRcvMode3: Sending and receiving mode of the MRFU/GRFU board. GUI Value

Range: SGL_ANTENNA(Single Feeder[1TX + 1RX]), SGLDOUBLE_ANTENNA(Single

Feeder[1TX + 2RX]), DOUBLE_ANTENNA(Double Feeder[2TX + 2RX]),

DOUBLEFOUR_ANTENNA(Double Feeder[2TX + 4RX]),

DOUBLESINGLE_ANTENNA(Double Feeder[1TX + 1RX]),

DOUBLEDOUBLE_ANTENNA(Double Feeder[1TX + 2RX]). Actual Value Range:

SGL_ANTENNA, SGLDOUBLE_ANTENNA, DOUBLE_ANTENNA,

DOUBLEFOUR_ANTENNA, DOUBLESINGLE_ANTENNA,

DOUBLEDOUBLE_ANTENNA;


Step 5: Configuring the Logical Data

Add BSC Cell ADD GCELL: <CELLID>, <CELLNAME>, <TYPE>, <MCC>, <MNC>, <LAC>,

<CI>; CELLID ： Index of a cell, uniquely identifying a cell in a BSC. CELLNAME ： Name of a cell, uniquely identifying a cell in a BSC. TYPE ： This parameter specifies the frequency band of new cells. Each new cell can be

allocated frequencies of only one frequency band. Once the frequency band is selected, it

cannot be changed. MCC ： Mobile country code. This parameter identifies the country where a mobile

subscriber is located, for example, the Chinese MCC is 460. MNC: Mobile network code. This parameter identifies the public land mobile network

(PLMN) where a mobile subscriber is homed. LAC ： Location area code (LAC). MSs can freely move in the local location area with no

need of location update. Reasonable local allocation can effectively lighten the signaling

load and improve the call completion rate. CI ： Identity code of a cell. Example ： ADD GCELL: CELLID=0, CELLNAME="cell0", TYPE=GSM900, MCC="460",

MNC="10", LAC=10, CI=11;



The Relation Between Cell And OSP ADD GCELLOSPMAP: <IDTYPE>, <CELLID>, <OPC>;

IDTYPE ： Type of an index. GUI Value Range: BYNAME(By Name), BYID(By Index). CELLID ： Index of a cell, uniquely identifying a cell in a BSC. OPC: Code of the original signaling point (OSP) in the signaling network. In the signaling

network, each signaling point is identified by a signaling point code. Example: ADD GCELLOSPMAP: IDTYPE=BYID, CELLID=0, OPC=H'A03;

Configure the logic Data-Add Cell Frequency ADD GCELLFRQ: <IDTYPE>, <CELLID>, <FREQ1>;

FREQ1: Frequency 1 Example: ADD GCELLFREQ: IDTYPE=BYID, CELLID=0, FREQ2=2;

Configure the logic Data-Add GSM TRX ADD GTRX: < IDTYPE>, <CELLID>, <TRXID>, <FREQ> ， <ISMAINBCCH>;

FREQ: Frequency of the TRX. ISMAINBCCH ： Whether to enable the TRX to carry the main BCCH in the cell. GUI

Value Range: NO(No), YES(Yes). Example: ADD GTRX: IDTYPE=BYID, CELLID=0, TRXID=0, FREQ=2,

ISMAINBCCH=YES;



Bind a Cell to a BTS ADD CELLBIND2BT: <IDTYPE>, <CELLID>, <BTSID>;

Example: ADD CELLBIND2BTS: IDTYPE=BYID, CELLID=0, BTSID=0 ； Configuring the Binding Between a Logical TRX and a Physical TRX Board

ADD TRXBIND2PHYBRD: <TRXID>, <TRXTP>, <TRXPN>, <SRN>, <SN>; TRXID ： ID of the TRX. The TRX ID must be globally unique. TRXTP ： Type of the TRX board bound to the TRX. GUI Value Range: TRX(TRX),

TRU(TRU/DTRU), QTRU(QTRU), DRRU(DRRU), DRFU(DRFU), MRRU(MRRU),

MRFU(MRFU), GRFU(GRFU), GRRU(GRRU), BTS3900B(BTS3900B),

BTS3900E(BTS3900E). TRXPN ： Number of the channel bound to the TRX on the TRX board. Example: ADD TRXBIND2PHYBRD: TRXID=0, TRXTP=DRFU, TRXPN=0,

RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0;

Note For TRX boards of the DBS3900 GSM, BTS3900 GSM, BTS3900A GSM, DBS3036,

BTS3036, BTS3036A, BTS3900B GSM and BTS3900E GSM, you need to specify the

attributes of the RXU link.


Step 5: Configuring the Transmission Data

Add BTS Connect ADD BTSCONNECT: <IDTYPE>, <BTSID>, <INPN>, <DESTNODE>, <SRN>,

<SN>, <PN>; IDTYPE ： Index type of the BTS. BYNAME: query by BTS name; BYID: query by BTS

index. GUI Value Range: BYNAME(By Name), BYID(By Index). BTSID ： ID of the BTS. The BTS ID must not conflict with other BTS IDs in the BSC. INPN ： Number of a BTS port. DESTNODE ： Type of the object the BTS is connected to. Value range: BTS, BSC, and

DXX. GUI Value Range: BTS, BSC, DXX, OTHER. Example: ADD BTSCONNECT: IDTYPE=BYID, BTSID=0, INPN=0, INCN=0, INSRN=0,

INSN=6, DESTNODE=BSC, SRN=0, SN=18, PN=0;

Note The connection between the BSC and the BTS is not required for the IP-based BTS that

supports IP over FE/GE transmission.


Step 5: Activating the BTS Configuration

Act BTS ACT BTS: <IDTYPE>, <BTSID>;

IDTYPE ： Type of an index. GUI Value Range: BYNAME(By Name), BYID(By Index).

BTSID ： ID of the BTS. Example: ACT BTS: IDTYPE=BYID, BTSID=0;

Note After this command is run, the BTS is initialized. This command can also be used to

check the BTS data as some data check is not done when BTS is not active in BSC6900.


Step 5: Configuring a GSM BTS and Its CELL

Quickly Configuring a GSM Cell ADD GCELLQUICKSETUP: <CELLID>, <CELLNAME>, <TYPE>, <MCC>,

<MNC>, <LAC>, <CI>, <OPC>, <BCCHFREQ>, <OTHERFREQ>; CELLID: Index of a cell, uniquely identifying a cell in a BSC. CELLNAME: Name of a cell, uniquely identifying a cell in a BSC. TYPE ： Cell type. Currently, the fast BTS construction is available for only GSM900 and

DCS1800 cells. GUI Value Range: GSM900(GSM900), DCS1800(DCS1800). MCC 、 MNC 、 LAC 、 CI ： Mobile country code. Mobile network code. Location area

code (LAC). Identity code of a cell. BCCHFREQ ： Frequency of the BCCH TRX. OTHERFREQ ： Ordinary frequency. Multiple frequencies are separated by "&". For

example, "22&33&44&55" are allocated to TRXs in ascending order. Example: ADD GCELLQUICKSETUP: CELLID=1, CELLNAME="CELLA",

TYPE=GSM900, MCC="460", MNC="04", LAC=10, CI=3, OPC=H'A03, BCCHFREQ=12,

OTHERFREQ="33&55";

Thank You

www.huawei.com

BSC6900V900R011 GO Data Configuration ISSUE1.0-20091130-B

Documents

1tx 2rx

base station

1tx 1rx

sran sites3900

configuration

ater connection

signaling

sends mml