bsc6900v900r012 uo global and equipment data configuration-20101218-b-v1.0

HUAWEI TECHNOLOGIES CO., LTD. All rights reserved

www.huawei.com

Internal

Global and Equipment Data Configuration

------Based on MML Commands

BSC6900V900R012


Upon completion this course, you will be able to:

Master the procedure and methods of data

configuration of BSC6900

Master global and equipment data configuration


《 (For Customer)BSC6900 UMTS Product

Documentation(V900R012C00_01)-EN 》

《 BSC6900 UMTS Initial Configuration

Guide(V900R012C00_01) 》


Chapter 1 Data Configuration Overview

Chapter 2 Global Data Configuration

Chapter 3 Equipment Data Configuration


Web Local Maintenance Terminal ( MML Client )

The local maintenance terminal is an item of the LMT software.

The local maintenance terminal adopts the GUI and the MML

(Man Machine Language) to operate and maintain the system.

Note: Data configuration is realized by the MML commands.


Application Scenarios of MML

Deployment

During the deployment, engineers should configure BSC6900 data

configuration script according to the negotiation data for stand alone

RNC during initial setup and run the script by MML commands in

batches.

Modify a few configuration data

When a few configuration data need to be modified, every single MML

command can be run to execute the function.

Data Preparation for Initial Configuration

In the BSC6900 initial configuration, some data is obtained from the

data sheets after negotiation with other network elements.

data preparation


Open Web LMT Enter the external virtual IP address of the OMU in the address bar

on the IE


Data Configuration Methods

1. Effective data configuration mode

2. Ineffective data configuration mode


Data Configuration Overview

Configuration Command Action Description

Action Meaning

ADD Add an object

SET Set an object

LST Query BAM database configuration information

DSP Query FAM object state or BAM running state

MOD Modify an object

RMV Remove an object

ACT Activate an object

DEA Deactivate an object

RST Reset an object

What is different between LST and DSP ?



Data Configuration Control

BSC6900 controls whether LMT or M2000 has the permission

to configure the data at a time to avoid the data conflict

Check the status of CMC (REQ CMCTRL)

Procedure of obtaining CMC in different cases

Lock CMC

If … Then …

M2000 communicates with BSC6900

normally

Use the REQ CMCTRL command to request the CMC.

If M2000 approves, LMT will get it

M2000 cannot communicate with BSC6900 or

BSC6900 is not equipped with M2000

Use the FOC CMCTRL command to obtain the CMC

forcibly



Configuration procedures of initial setup RNC

Global dataconfiguration

Equipment data configuration

Interface dataconfiguration

Cell data configuration

Start

End

BSC6900

BSC6900

NodeB

NodeB

NodeB

MSC Server

MGW

SGSN

UE UTRAN CNUu Iu

Iu-CS

Iu-PS

Iur

Iub

Iub

Iub


Global Data Configuration Procedure

End

Start

Adding RNC basic data

Configuring the OPC and DPC

Configuring the Area Information

Adding M3UA local and destination entities

Global parameter is used to identify the

RNC in a network.

This is the first step of RNC initial

configuration, use SET CFGDATAINEFFECTIVE

command switch RNC all

subrack to ineffective mode.

During the RNC initial configuration,

global data include several necessary

steps as shown in right procedure flow.


Configure RNC Basic Data Information

ADD URNCBASIC :

ADD UCNOPERATOR ：

ADD UCNOPERGROUP:

SET UOPERATORCFGPARA ： optional

SET UOPERATORSHARINGMODE ： optional

SET SUBNET : optional

SET SCTPSVRPORT: optional

End

Start






What is IU-FLEXIUFLEX features:

All CN node connecting to the RNC belongs to one operator

Why IUFLEX:

To enable load share in one CN domain, in a case when RNC

has more capacity then CN, by connecting to CN pool, RNC

resource could be more efficiently used

One CN node serves more RNC, this decrease CN switch and

roaming, and thus less CN signaling

CS3

RNC

NodeB

PS2

One Operator

CS2CS1PS1 PS3


What is MRNC (ran sharing)

MRNC （ Multi-logical RNC ） is to configure one physical RNC to be

several logical RNC, the logical RNC belongs to different operators

Operator has its own CN, CN is not shared

Radio resource is not shared among operators

The feature RAN SHARING supported in V1.8 is MRNC

CS2

RNC

CS1

Operator_A

PS1

Operator_B

PS2

Cell1

Cell2

Cell3

Cell4


What is MOCN

MOCN features:

Each operator has its own CN, CN is not shared

Radio resource is shared among operators, i.e. the cell is shared

among operators

Each operator may deploy Iu-flex

RNC is responsible to route the UE to its subscribing operator

CS2

RNC

NodeB

CS1

Operator_A

PS1

Operator_B

PS2


RNC id range is 0-4096 and used to uniquely identifying an RNC in same

operator network.

ATM address: use to distinguish equipment in ATM transmission network.


Paramters of ADD URNCBASIC command



Paramters of ADD UCNOPERATOR command

Cn Operator Name: Value range: String long 1 ~ 31

Mobile country code: MCC Value range: 000 to 999

Mobile network code: MNC Value range: 00 to 99 or 000 to 999

Cn Operator index: Value range: 5-31


PRIM: Primary operator, determines functions to be supported the entire RAN system

and allocates licenses to secondary operators. The primary operator permits registration

and access the UE.

SEC: Secondary operator, functions to be supported the entire RAN system and the

license of the secondary operators are controlled by primary operator. Secondary

operator permit access UE.

OUTER: Outer operator, In mobility management, UEs need to be hand over from the

operator of the source RNC to the operator of the target RNC. If the operator is not the

primary operator and secondary operator of the source RNC, you need to specify the

operator as an outer operator so that the operator support the mobility management.

COMM: operator that supports non-support UEs, The PLMN ID indicated in the

system broadcast information as defined for conversational networks, which non-support

UEs understand as the serving opertaor.




ADD CNOperator correlative concept

MCC: Mobile country code MNC: Mobile network code MSIN: To identify the MS in one PLMN IMSI: To identify the MS in one Country

MCC MNC MSIN

3 digits 2/3 digits

Not more than 15 digits

IMSI (International Mobile Subscriber Identity)

NMSI



Paramters of ADD UCNOPERGROUP command

In one operator group, can be configure 1-4 real operator index

In one operator group, can choose to configure one common operator index.

CNOPERATORGROUP is to facilitate maintenance and management.



Paramters of SET UOPERATORCFGPARA command

If the RNC system support IU-FLEX and MOCN ， this command use to configure

NRI parameter.

NRI (network recourse identifier) is part of the temporary indentity TMSI (CS

domain) or P-TMSI (PS domain), which is assigned by the serving CN node to the

UE.


Paramters of SET UOPERATORSHARINGMODE command

RAN Sharing Support: Multiple operators to share a set of

RAN equipment that covers the same area.

MOCN: Multi-operator share frequency resource mode.

Intra RAT Inter Plmn Ho Allowed: Intra Plmn handover.

Inter RAT Inter Plmn Ho Allowed: Inter Plmn handover.


RNC1

Operator 2

RNC2

RNC3

Operator 1


Set RNC Internal Subnet No.

EPS

SCU

80.x.x.x


EPS

BAMExternal

BAMInternal


Parameter of SET SCTPSRVPORT command.


The default parameter:

NBAP port No. is 58085.

M3UA port No. is 2910.



ADD OPC:

ADD N7DPC ：

End

Start






Parameter of ADD OPC command


OSP name: <NAME> 1~31 characters. OSP code bits: <SPCBITS> Value range: BIT14, BIT16, BIT24.

Network ID:

INT: international network.

INTB: international reserved.

NAT: national network.

NATB: national reserved.


ADD N7DPC


DSP type ： IUCS(IUCS), IUPS(IUPS), IUR(IUR), IUCS_RANAP(IUCS_RANAP),

IUCS_ALCAP(IUCS_ALCAP), AAL2SWITCH(AAL2SWITCH), STP(STP), IUPC(IUPC)

SS7 type: ITUT(International Telecommunication Union - Telecommunication Standardiza

tion Sector), ANSI(American National Standards Institute), and TTC(Telecommunication Te

chnology Committee (Japan)).



ADD ULAC:

ADD URAC:

ADD USAC:

ADD UURA:

ADD UCZ: optional

End

Start






ADD ULAC: Add location area code

ADD URAC: Add route area code

ADD USAC: Add service area code

ADD UURA: Add UTRAN Registration Area

PLMN: Public Land Mobile Network


LAC1

RAC1RAC2

SAC1SAC2

LAC2

PLMN


UE States

CELL_DCH CELL_FACH

CELL_PCHURA_PCH

IDLE

DEAD - Scanning networks (PLMN)- ”Camp on” cell

- Monitor paging channel- cell re-selection

- Dedicated Channel- Radio bearers Transmission Services

- upper layer Signalingtrigger (CN)

- Reduce action ， DRX ， and save power

RRC connection



Parameter of ADD ULAC command


LAI (location area identity)=MCC+MNC+LAC

When the system information is being broadcast in a cell, the value of the tag included in the system information block 1 (SIB1) message is within the range defined by PlmnValTagMin and PlmnValTagMax.


Parameter of ADD URAC command


RAI (Route area identity) =MCC+MNC+LAC+RAC


Parameter of ADD USAC command


SAI (Source area identity) =MCC+MNC+LAC+SAC


Parameter of UTRAN Registration Area command


Use this command to add a UTRAN registration area

URA is used by UTRAN ， CN does not know URA 。 URA is

formed by multiple cells. When UE goes to URA_PCH state, UE’s

area information is identified by URA.


Configure M3UA Local and Destination Entities

End

Start



Configuring the area information

Adding M3UA local and destination entities ADD M3LE: IP network mandatoryADD M3DE ： IP network mandatory

This command only use for IU interface IP network.

The prerequisite is OPC and N7DPC configured.


Equipment Data Configuration

Equipment data configuration is used to

identify the subracks, boards and clock

information of RNC.

This is the second configuration step of

RNC initial configuration.

During the RNC initial configuration,

equipment data include several necessary

steps as shown in the right procedure flow.

Adding the IP Address of the EMS Server

End

Start

Configuring a Cabinet

Configuring a Subrack

Configuring a Board

Adding an EMU

Configuring RNC Clock Data

Setting RNC Time

Configuring the System Information


Equipment Data Configuration

SET SYS: optional


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time


The RNC system information is stored only in the BAM database and is not sent to the host,



ADD CAB: add an Extended Processing

Rack (EPR).


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time


The Main Processing Rack (MPR) is configured by default. It need not be added through the MML command.



ADD SUBRACK: add more EPSs

SET SCUPORT ： enable the

corresponding port on the SCU board in

the main subrack


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time


The Main Processing Subrack (MPS) is configured by default. It need not be added through the MML command.


Configuring a Board

ADD BRD: This command can be used

by all types of boards except the SCUa,

GCUa, and GCGa.

SET MSP ： Use this command to set

Multiplex Section Protection (MSP)

attributes for the

AOUa/AOUc/POUa/POUc/UOIc/UOIa (ATM

or IP) board.


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time



Configuring an EMU

ADD EMU: The EMU gathers Boolean

values, analog values, and alarm threshold

information and reports them to the LMT.

One cabinet can be configured with only

one EMU.


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time




ADD CLKSRC: 增加系统时钟源

SET CLK：设置接口板时钟源

SET CLKMODE：设置系统时钟源工作模式


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time


Clock source priority ranges from 1 to 4. The clock source of priority 0 is configured by default. Priority 0 is the lowest priority, and priority 4 is the highest priority.


Setting RNC Time

SET TZ:

ADD SNTPSRVINFO ： information about the

SNTP synchronization server.

SET SNTPCLTPARA ： set the synchronization

period of the SNTP client


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time



SNTP serverSNTP server

SNTP client

SNTP clientSNTP server

RNC NodeBM2000

Setting RNC Time

RNC external network view: M2000 is the SNTP server of RNC

RNC is the SNTP client of M2000.

RNC internal network view: RNC is the SNTP server of NodeB

NodeB is the SNTP Client of RNC.


Setting RNC Time

SNTP: Simple network time protocol.

SNTP server IP is the IP address of M2000. Port number is 123.

The number of the SNTP Servers cannot exceed 16.

If multiple SNTP servers are configured, SNTP Client chooses the best

SNTP server as the clock source according to the algorithm defined in

the NTP protocol.

Parameter of SET SNTPCLTPARA command



ADD EMSIP:


End

Start



Configuring a Board

Adding an EMU


Setting RNC Time


Thank youwww.huawei.com

bsc6900v900r012 uo global and equipment data configuration-20101218-b-v1.0

Documents