UMTS Radio Access Network Configuration Example

Chapter 1 Introduction to Data Configuration ..............................................
1-1
1.1 Overview ................................................................................................

1.2 Data Configuration Tasks and Procedure ..............................................
1.3 Data Configuration References ..............................................................
1.4 Data Configuration Tools........................................................................
1-1
1-1
1-2
1-2
Chapter 2 RNC Basic Data Configuration .....................................................
2-1
2.1 Overview ................................................................................................

2.1.1 Configuration Purpose ...................................................................
2.1.2 Configuration Precondition .............................................................
2.1.3 Configuration Procedure ................................................................
2.2 RNC Basic Data Configuration ...............................................................
2.2.1 Planning RNC Basic Data ..............................................................
2.2.2 Configuring RNC Basic Data .........................................................
2.2.3 Commissioning RNC Basic Data ...................................................
2-1
2-1
2-1
2-1
2-1
2-1
2-6
2-8
Chapter 3 RNC-MSC Interconnection Data Configuration ...........................
3-1
3.1 Overview ................................................................................................

3.2 RNC-MSC (R99) Interconnection Data Configuration ............................
3.2.1 Planning RNC-MSC (R99) Interconnection Data ...........................
3.2.2 Configuring RNC-MSC (R99) Interconnection Data ......................
3.2.3 Checking RNC-MSC (R99) Interconnection Data ..........................
3.3 RNC-MSC (R4) Interconnection Data Configuration ..............................
3.3.1 Planning RNC-MSC (R4) Interconnection Data .............................
3.3.2 Configuring RNC-MSC (R4) Interconnection Data ........................
3.3.3 Checking RNC-MSC (R4) Interconnection Data ............................
3-1
3-1
3-1
3-1
3-2
3-2
3-3
3-6
3-7
3-7
3-9
3-12
Chapter 4 RNC-SGSN Interconnection Data Configuration .........................
4-1
4.1 Overview ................................................................................................

4.2 RNC-SGSN Interconnection Data Configuration....................................
4.2.1 Planning RNC-SGSN Interconnection Data ...................................
4.2.2 Configuring RNC-SGSN Interconnection Data ..............................
4.2.3 Checking RNC-SGSN Interconnection Data ..................................
4-1
4-1
4-1
4-1
4-1
4-1
4-3
4-6
Chapter 5 RNC-CBC Interconnection Data Configuration ...........................
5-1
5.1 Overview ................................................................................................
5-1

5.2 RNC-CBC Interconnection Data Configuration ......................................
5.2.1 Planning RNC-CBC Interconnection Data .....................................
5.2.2 Configuring RNC-CBC Interconnection Data .................................
5.2.3 Checking RNC-CBC Interconnection Data ....................................
5-1
5-1
5-1
5-1
5-1
5-3
5-4
Chapter 6 RNC-RNC Interconnection Data Configuration ...........................
6-1
6.1 Overview ................................................................................................

6.2 RNC-RNC Interconnection Data Configuration ......................................
6.2.1 Planning RNC-RNC Interconnection Data .....................................
6.2.2 Configuring RNC-RNC Interconnection Data.................................
6.2.3 Checking RNC-RNC Interconnection Data ....................................
6-1
6-1
6-1
6-1
6-1
6-1
6-4
6-8
Chapter 7 RNC-NodeB Interconnection Data Configuration .......................
7-1
7.1 Overview ................................................................................................

7.2 RNC-NodeB Network Topology .............................................................
7.2.1 Typical Network Topology ..............................................................
7.2.2 Data Planning Example .................................................................
7.3 RNC-NodeB1 Interconnection Data Configuration .................................
7.3.1 Planning RNC-NodeB1 Interconnection Data ................................
7.3.2 Configuring RNC-NodeB1 Interconnection Data on RNC ..............
7.3.3 Configuring RNC-NodeB1 Interconnection Data on NodeB1 ........
7.3.4 Checking RNC-NodeB1 Interconnection Data ...............................
7-1
7-1
7-1
7-1
7-2
7-2
7-3
7-4
7-4
7-6
7-9
7-17
7-17
7-17
7-20
7-22
7-31
7-31
7-31
7-33
7-35
7-42

7-46
7-46
7-46
7-48
7-50
7-58
7-58
7-58
7-60
7-62
7-70
7-76
7-76
7-78
7-80
7-87
Chapter 8 Cell and Neighboring Cell Data Configuration ............................
8-1
8.1 Overview ................................................................................................

8.1.3 Configuration Tasks .......................................................................
8.2 Cell Data Configuration ..........................................................................
8.2.1 Planning Cell Data .........................................................................
8.2.2 Configuring Logical Cell Data on RNC ...........................................
8.2.3 Configuring Local Cell Data on NodeB1 ........................................
8.2.4 Commissioning Cell Data...............................................................
8.3 Intra-Frequency Neighboring Cell Data Configuration ...........................
8.3.1 Planning Intra-Frequency Neighboring Cell Data ..........................
8.3.2 Configuring Intra-Frequency Neighboring Cell Data on RNC ........
8.3.3 Checking Intra-Frequency Neighboring Cell Data .........................
8.4 Inter-Frequency Neighboring Cell Data Configuration ...........................
8.4.1 Planning Inter-Frequency Neighboring Cell Data ..........................
8.4.2 Configuring Inter-Frequency Neighboring Cell Data on RNC ........
8.4.3 Checking Inter-Frequency Neighboring Cell Data .........................
8.5 Concentric Inter-Frequency Neighboring Cell Data Configuration .........
8.5.1 Planning Concentric Inter-Frequency Neighboring Cell Data ........
8.5.2 Configuring Concentric Inter-Frequency Neighboring Cell Data
on RNC ...................................................................................................
8.5.3 Checking Concentric Inter-Frequency Neighboring Cell Data .......
8.6 Inter-RAT Neighboring Cell Data Configuration .....................................
8-1
8-1
8-1
8-1
8-1
8-1
8-5
8-8
8-9
8-10
8-10
8-10
8-11
8-12
8-12
8-12
8-13
8-14
8-14
8-14
8-14
8-14
8.6.1 Planning Inter-RAT Neighboring Cell Data ....................................

8.6.2 Configuring Inter-RAT Neighboring Cell Data on RNC ..................
8.6.3 Checking Inter-RAT Neighboring Cell Data ...................................
8-14
8-15
8-16
Chapter 9 NodeB O&M Channel Configuration ............................................
9-1
9.1 Overview ................................................................................................

9.2 Local O&M Channel Configuration .........................................................
9.2.1 Planning Local O&M Channel Data ...............................................
9.2.2 Configuring Local O&M Channel Data ...........................................
9.2.3 Checking Local O&M Channel Data ..............................................
9.3 Remote O&M Channel Configuration .....................................................
9.3.1 Planning Remote O&M Channel Data ...........................................
9.3.2 Configuring Remote O&M Channel Data on M2000 Server ..........
9.3.3 Configuring Remote O&M Channel Data on RNC .........................
9.3.4 Configuring Remote O&M Channel Data on NodeB ......................
9.3.5 Checking Remote O&M Channel Data ..........................................
9-1
9-1
9-2
9-2
9-2
9-2
9-3
9-6
9-6
9-6
9-11
9-11
9-13
9-14
Appendix Acronyms and Abbreviations .......................................................
F-1
Index .................................................................................................................
HUAWEI
HUAWEI UMTS Radio Access Network

Configuration Example

Manual Version
T2-031695-20041001-C-1.22
Product Version
BSC6800V100R002 NodeB V100R003
BOM
31161495
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office, customer care center or company
headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com
Copyright 2004 Huawei Technologies Co., Ltd.
All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks
, HUAWEI, C&C08, EAST8000, HONET,
, ViewPoint, INtess, ETS, DMC,
TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

M900/M1800,
TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN,
HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, SoftX, iSite, U-SYS, iMUSE,
OpenEye, Lansway, SmartAX are trademarks of Huawei Technologies Co., Ltd.
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
Summary of Updates
This section provides the update history of this manual and introduces the contents of
subsequent updates.
Update History
This manual is updated for a major product version to maintain consistency with system
hardware or software versions and to incorporate customer suggestions.
Manual Version
T2-031695-20041001-C-1.22
Updates of Contents
None
Notes
Initial commercial release
About This Manual

Version
This manual applies to BSC6800 V100R002 and NodeB V100R003.
Organization of the Manual

The manual introduces data configuration instances of HUAWEI UMTS Radio Access
Network. It comprises nine chapters and one appendix. The contents of each part are
as follows:
Chapter 1 Introduction to Data Configuration gives a brief introduction to data
configuration and introduces how to log in to configuration consoles.
Chapter 2 RNC Basic Data Configuration introduces how to configure the basic data
that must be configured on the RNC before configuring any other interconnection data.
Chapter 3 RNC-MSC Interconnection Data Configuration introduces how to
configure the interconnection data between RNC and MSC in both R99 and R4.
Chapter 4 RNC-SGSN Interconnection Data Configuration introduces how to
configure RNC-SGSN interconnection data.
Chapter 5 RNC-CBC Interconnection Data Configuration introduces how to
configure RNC-CBC interconnection data.
Chapter 6 RNC-RNC Interconnection Data Configuration introduces how to
configure RNC-RNC interconnection data.
Chapter 7 RNC-NodeB Interconnection Data Configuration introduces how to
configure RNC-NodeB interconnection data in various network topologies.
Chapter 8 Cell and Neighboring Cell Data Configuration introduces how to
configure local cell, logical cell and neighboring cell data.
Chapter 9 NodeB O&M Channel Configuration introduces how to configure NodeB
local and remote O&M channels.
Appendix Acronyms and Abbreviations
Target Readers
The manual is intended for the following readers:

z
Technical support and engineers
Telecommunication administration staff
Conventions
This document uses the following conventions:
I. General conventions
Convention
Description
Arial
Normal paragraphs are in Arial.
Arial Narrow
Warnings, cautions, notes, table text and tips are in Arial Narrow.
II. GUI conventions

Convention
Description
<>
Button names are inside angle brackets <>.
[]
Menu items are inside square brackets [ ].
Multi-level menus are separated by forward slashes /. For example,

[File/Create/Folder].
III. Mouse operation

Action
Description
Click
Press the left button quickly.
Right-click
Press the right button quickly.
Double-click
Press the left button twice continuously and quickly.
IV. Symbols
Eye-catching symbols are also used in this document to highlight the points worthy of
special attention during the operation. They are defined as follows:
Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.
Table of Content
Table of Content
Chapter 1 Introduction to Data Configuration............................................................................ 1-1
1.1 Overview ............................................................................................................................ 1-1
1.2 Data Configuration Tasks and Procedure ......................................................................... 1-1
1.3 Data Configuration References ......................................................................................... 1-2
1.4 Data Configuration Tools ................................................................................................... 1-2
Chapter 2 RNC Basic Data Configuration ................................................................................... 2-1
2.1 Overview ............................................................................................................................ 2-1
2.1.1 Configuration Purpose ............................................................................................ 2-1
2.1.2 Configuration Precondition...................................................................................... 2-1
2.1.3 Configuration Procedure ......................................................................................... 2-1
2.2 RNC Basic Data Configuration .......................................................................................... 2-1
2.2.1 Planning RNC Basic Data ....................................................................................... 2-1
2.2.2 Configuring RNC Basic Data................................................................................... 2-6
2.2.3 Commissioning RNC Basic Data ............................................................................ 2-8
Chapter 3 RNC-MSC Interconnection Data Configuration ........................................................ 3-1
3.1 Overview ............................................................................................................................ 3-1
3.2 RNC-MSC (R99) Interconnection Data Configuration ....................................................... 3-2
3.2.1 Planning RNC-MSC (R99) Interconnection Data.................................................... 3-2
3.2.2 Configuring RNC-MSC (R99) Interconnection Data ............................................... 3-3
3.2.3 Checking RNC-MSC (R99) Interconnection Data................................................... 3-6
3.3 RNC-MSC (R4) Interconnection Data Configuration ......................................................... 3-7
3.3.1 Planning RNC-MSC (R4) Interconnection Data...................................................... 3-7
3.3.2 Configuring RNC-MSC (R4) Interconnection Data ................................................. 3-9
3.3.3 Checking RNC-MSC (R4) Interconnection Data................................................... 3-12
Chapter 4 RNC-SGSN Interconnection Data Configuration ...................................................... 4-1
4.1 Overview ............................................................................................................................ 4-1
4.2 RNC-SGSN Interconnection Data Configuration............................................................... 4-1
4.2.1 Planning RNC-SGSN Interconnection Data............................................................ 4-1
4.2.2 Configuring RNC-SGSN Interconnection Data ....................................................... 4-3
4.2.3 Checking RNC-SGSN Interconnection Data........................................................... 4-6
Table of Content
Chapter 5 RNC-CBC Interconnection Data Configuration ........................................................ 5-1

5.1 Overview ............................................................................................................................ 5-1
5.2 RNC-CBC Interconnection Data Configuration ................................................................. 5-1
5.2.1 Planning RNC-CBC Interconnection Data .............................................................. 5-1
5.2.2 Configuring RNC-CBC Interconnection Data.......................................................... 5-3
5.2.3 Checking RNC-CBC Interconnection Data ............................................................. 5-4
Chapter 6 RNC-RNC Interconnection Data Configuration ........................................................ 6-1
6.1 Overview ............................................................................................................................ 6-1
6.2 RNC-RNC Interconnection Data Configuration ................................................................. 6-1
6.2.1 Planning RNC-RNC Interconnection Data .............................................................. 6-1
6.2.2 Configuring RNC-RNC Interconnection Data.......................................................... 6-4
6.2.3 Checking RNC-RNC Interconnection Data ............................................................. 6-8
Chapter 7 RNC-NodeB Interconnection Data Configuration..................................................... 7-1
7.1 Overview ............................................................................................................................ 7-1
7.2 RNC-NodeB Network Topology......................................................................................... 7-2
7.2.1 Typical Network Topology....................................................................................... 7-2
7.2.2 Data Planning Example........................................................................................... 7-3
7.3 RNC-NodeB1 Interconnection Data Configuration ............................................................ 7-4
7.3.1 Planning RNC-NodeB1 Interconnection Data......................................................... 7-4
7.3.2 Configuring RNC-NodeB1 Interconnection Data on RNC ...................................... 7-6
7.3.3 Configuring RNC-NodeB1 Interconnection Data on NodeB1 ................................. 7-9
7.3.4 Checking RNC-NodeB1 Interconnection Data...................................................... 7-17
7.4 RNC-NodeB2 Interconnection Data Configuration .......................................................... 7-17
7.4.1 Planning RNC-NodeB2 Interconnection Data....................................................... 7-17
7.4.2 Configuring RNC-NodeB2 Interconnection Data on RNC .................................... 7-20
7.4.3 Configuring RNC-NodeB2 Interconnection Data on NodeB2 ............................... 7-22
ii
Table of Content

Chapter 8 Cell and Neighboring Cell Data Configuration ......................................................... 8-1
8.1 Overview ............................................................................................................................ 8-1
8.1.3 Configuration Tasks ................................................................................................ 8-1
8.2 Cell Data Configuration...................................................................................................... 8-1
8.2.1 Planning Cell Data .................................................................................................. 8-1
8.2.2 Configuring Logical Cell Data on RNC.................................................................... 8-5
8.2.3 Configuring Local Cell Data on NodeB1 ................................................................. 8-8
8.2.4 Commissioning Cell Data........................................................................................ 8-9
8.3 Intra-Frequency Neighboring Cell Data Configuration..................................................... 8-10
8.3.1 Planning Intra-Frequency Neighboring Cell Data ................................................. 8-10
8.3.2 Configuring Intra-Frequency Neighboring Cell Data on RNC ............................... 8-10
8.3.3 Checking Intra-Frequency Neighboring Cell Data ................................................ 8-11
8.4 Inter-Frequency Neighboring Cell Data Configuration..................................................... 8-12
8.4.1 Planning Inter-Frequency Neighboring Cell Data ................................................. 8-12
8.4.2 Configuring Inter-Frequency Neighboring Cell Data on RNC ............................... 8-12
8.4.3 Checking Inter-Frequency Neighboring Cell Data ................................................ 8-13
8.5 Concentric Inter-Frequency Neighboring Cell Data Configuration .................................. 8-14
8.5.1 Planning Concentric Inter-Frequency Neighboring Cell Data ............................... 8-14
8.5.2 Configuring Concentric Inter-Frequency Neighboring Cell Data on RNC............. 8-14
8.5.3 Checking Concentric Inter-Frequency Neighboring Cell Data .............................. 8-14
8.6 Inter-RAT Neighboring Cell Data Configuration .............................................................. 8-14
8.6.1 Planning Inter-RAT Neighboring Cell Data ........................................................... 8-14
8.6.2 Configuring Inter-RAT Neighboring Cell Data on RNC ......................................... 8-15
8.6.3 Checking Inter-RAT Neighboring Cell Data .......................................................... 8-16
iii
Table of Content
Chapter 9 NodeB O&M Channel Configuration.......................................................................... 9-1

9.1 Overview ............................................................................................................................ 9-1
9.2 Local O&M Channel Configuration .................................................................................... 9-2
9.2.1 Planning Local O&M Channel Data ........................................................................ 9-2
9.2.2 Configuring Local O&M Channel Data .................................................................... 9-3
9.2.3 Checking Local O&M Channel Data ....................................................................... 9-6
9.3 Remote O&M Channel Configuration ................................................................................ 9-6
9.3.1 Planning Remote O&M Channel Data .................................................................... 9-6
9.3.2 Configuring Remote O&M Channel Data on M2000 Server ................................. 9-11
9.3.3 Configuring Remote O&M Channel Data on RNC ................................................ 9-11
9.3.4 Configuring Remote O&M Channel Data on NodeB............................................. 9-13
9.3.5 Checking Remote O&M Channel Data ................................................................. 9-14
Appendix Acronyms and Abbreviations ........................................................................................ 1
Index ................................................................................................................................................
iv
Chapter 1
Introduction to Data Configuration
Chapter 1 Introduction to Data Configuration

1.1 Overview
This chapter introduces the following contents:
z
Data Configuration Tasks and Procedure
Data Configuration References
Data Configuration Tools
1.2 Data Configuration Tasks and Procedure

By some common data configuration tasks, this manual gives guidelines for the data
configurations of Huawei Universal Mobile Telecommunications System (UMTS) Radio
Access Network (RAN). In this mode the manual avoids the complexity of data
configuration due to large numbers of parameters and close relationships among them
in Huawei UMTS RAN.
The configuration tasks mentioned in this manual based on Radio Network Controller
(RNC). Before configuring interconnection data, you need configure the basic data of
the RNC first. Figure 1-1 shows the data configuration tasks and procedure.
Start
Configure basic
data of RNC
Configure
RNC-MSC
interconnection
data
Configure
RNC-SGSN
interconnection
data
Configure
RNC-RNC
interconnection
data
Configure
RNC-CBC
interconnection
data
Configure
RNC-NodeB
interconnection
data
Configure cell and

neighboring cell data
End
Figure 1-1 Configuration tasks and procedure
1-1
Configure NodeB
O&M channel
Chapter 1
Introduction to Data Configuration
For each configuration task, this manual introduces the data planning, data
configuration, and data check. Where, the parameter planning emphasizes the data
negotiated between network elements (NEs).
1.3 Data Configuration References

This manual only introduces data configurations for some common tasks in Huawei
UMTS RAN. For data configurations in other cases, refer to the following manuals:
z
HUAWEI BSC6800 WCDMA Radio Network Controller Operation Manual Data

Configuration
BTS3812&BTS3806&BTS3806A WCDMA NodeB Data Configuration
1.4 Data Configuration Tools

The following tools will be used when implementing the task described in this manual.
z
RNC MML client (Integrated in the BSC6800 Operation and Maintenance System)
NodeB Configuration Management (Integrated in NodeB Operation and

Maintenance System)
Refer to the RNC and NodeB LMT online help for the information of how to log in and
use the tools.
1-2
Chapter 2
RNC Basic Data Configuration
Chapter 2 RNC Basic Data Configuration

2.1 Overview
2.1.1 Configuration Purpose
Before configuring any other interconnection data, you must configure the basic data of
RNC first. For the convenience of introduction, data configurations presented in other
chapters adopt the basic data configured in this chapter.
2.1.2 Configuration Precondition

Before data configuration, ensure the following:
z
The RNC hardware is installed.
The RNC Back Administration Module (BAM) software and Local Maintenance
Terminal (LMT) software are installed.
The RNC BAM and Front Administration Module (FAM) can communicate with
each other normally.
2.1.3 Configuration Procedure

The configuration procedure is as follows:
1)
Configuring Local Office Data
2)
Configuring Hardware Data
3)
Configuring Clock Source Data
4)
Configuring OSP Data
2.2 RNC Basic Data Configuration

2.2.1 Planning RNC Basic Data
I. Overview
Planning RNC basic data includes the following:
1)
Planning Local Office Data
2)
Planning Subrack Data
3)
Planning WLPU Optical Port
4)
Planning Clock Source Data
5)
Planning OSP Data
2-1
Chapter 2
II. Planning Local Office Data

Local office data includes RNC identification information, RNC location information,
and RNC System Information Block 1 (SIB1) information. The following introduces
them respectively.
z
RNC identification information
Table 2-1 lists the RNC identification information.

Table 2-1 RNC identification information
Item
Data planning
RNC ID
Mobile Network Code (MNC)
460
Mobile Country Code (MCC)
000
RNC location information
Figure 2-1 shows the location areas (LAs) and routing areas (RAs) of the RNC.
LA0
RA0
RA1
RNC
RA3
RA2
LA1
Figure 2-1 RNC LA and RA planning

Table 2-2 lists the RNC LA and RA information.
Table 2-2 RNC LA and RA information
Item
Location Area Code (LAC)
Data planning
LA0 LAC = 100; Public Land Mobile Network (PLMN) value tag
= 14
LA1 LAC = 200; PLMN value tag = 58
2-2
Chapter 2
Item
Service Area Code (SAC)
Data planning
LA0 SAC = 100
LA1 SAC = 200
RA0 RAC = 0 (belonging to LA1; PLMN value tag = 912
Routing Area Code (RAC)
RA1 RAC = 1 (belonging to LA1); PLMN value tag = 1316

URA0 URA ID = 0
UTRAN Registration Area (URA) ID
URA1 URA ID = 1
URA2 URA ID = 2
URA3 URA ID = 3
RNC SIB1 information
Table 2-3 lists the RNC SIB1 information.

Table 2-3 RNC SIB1 information
Item
Circuit Switched (CS) domain /
Packet Switched (PS) domain
information
Data planning
Both CS and PS domains are configured
Periodical location update timer [T3212] = 1
CS Non-Access Stratum (NAS)

information
Attach/detach indicator [ATT] = ALLOWED

Discontinuous
Reception
[DRXCYCLELENCOEF] = 8
(DRX)
cycle
coefficient
Network Mode of Operation [NMO] = MODE1

PS NAS information
Discontinuous
Reception
[DRXCYCLELENCOEF] = 8
(DRX)
cycle
coefficient
III. Planning Subrack Data

The following are the subracks configured:
z
One WCDMA RNC Switch Subrack (WRSS)
Two WCDMA RNC Business Subracks (WRBSs): WRBS1 and WRBS3
Table 2-4 lists the configurations of the above three subracks:
2-3
Chapter 2
Table 2-4 Subrack configuration

Subrack name
Board name
WRSS
WRBS1
WRBS3
Number of boards
Slot number
WMPU
Two
0, 1
WLPU
Two
2, 4
WNET
Two
7, 8
WHPU
Three
10, 11, 12
WBIE
Two
0, 15
WFMR
Two
1, 2
WMUX
Two
7, 8
WSPU
Two
10, 11
WOSE
Two
0, 15
WFMR
Two
1, 2
WMUX
Two
7, 8
WSPU
Two
10, 11
Figure number
Figure 2-2
Figure 2-3
Figure 2-4
Where, the WOSEs in slots 0 and 15 adopt 1:1 Multiplex Section Protection (MSP)
mode.
Note:
Insert the two WFMRs of WRBS1/WRBS3 in the slots whose slot numbers are respectively even and odd.
Figure 2-2, Figure 2-3, and Figure 2-4 show the boards configured in the WRSS,
WRBS1, and WRBS3.
W
M
P
U
W
M
P
U
W
L
P
U
W
L
P
U
3
W
N
E
T
W
N
E
T
Figure 2-2 WRSS configuration
2-4
W
H
P
U
W
H
P
U
W
H
P
U
10
11
12
13
14
W
B
I
E
W
F
M
R
W
F
M
R
Chapter 2
W
M
U
X
W
M
U
X
W
M
U
X
W
M
U
X
W
S
P
U
W
S
P
U
10
11
W
S
P
U
W
S
P
U
10
11
W
B
I
E
12
13
14
15
Figure 2-3 WRBS1 configuration
W
O
S
E
W
F
M
R
W
F
M
R
W
O
S
E
12
13
14
15
Figure 2-4 WRBS3 configuration
IV. Planning WLPU Optical Port

The WLPUs configured as above adopt the optical sub-boards of STM-1 type. All the
physical links on the WLPU in slot 2 but the one over optical port 7 are backed up on
slot 4.
Table 2-5 lists the usages of the optical ports on the WLPU in slot 2.
Table 2-5 WLPU optical port planning
WLPU optical port number
Usage
Connected to WRBS1
Connected to WRBS3
Reserved
Reserved
Reserved
Reserved
Reserved
Connected to NodeB
Connected to an neighboring RNC
Reserved
10
Reserved
11
Connected to Cell Broadcast Center (CBC)
12
Connected to Mobile Service Switching Center (MSC) or

Media Gateway
13
Reserved
2-5
Chapter 2
WLPU optical port number
Usage
14
Connected to SGSN
15
Reserved
V. Planning Clock Source Data

The RNC extracts the clock source from the Iu interfaces of WLPUs in slots 2 and 4 and
adopts the preemptive auto switchover strategy.
VI. Planning OSP Data

Table 2-6 lists the original signalling point (OSP) information of the RNC.
Table 2-6 OSP information
Item
Data planning
Network Identification (NID)
National network code
OSP code
H0008, 14-bit code
ATM address
H45000086100101008F0000000000000000000000
2.2.2 Configuring RNC Basic Data

I. Overview
To configure the RNC basic data, operate as follows:
1)
Setting the BAM to Offline Mode
2)
Configuring Local Office Data
3)
Configuring Hardware Data
4)
Configuring Clock Source Data
5)
Configuring OSP Data
6)
Setting the BAM to Online Mode
II. Setting the BAM to Offline Mode

//Set the BAM to offline mode.
SET OFFLINE:
III. Configuring Local Office Data

//Configure the RNC identification information.
ADD RNCBASIC: RNCID=0, MCC="460", MNC="000";
2-6
Chapter 2
Note:
The ADD RNCBASIC command can only be executed in offline mode.
//Activate the license file to make the system support the licensed functions.
ACT LICENSE;
//Add LA0 and LA1.

ADD LAC: LAC=100, PLMNVALTAGMIN=1, PLMNVALTAGMAX=4;
ADD LAC: LAC=200, PLMNVALTAGMIN=5, PLMNVALTAGMAX=8;
//Add RA0 and RA1that belong to LA0.

ADD RAC: LAC=100, RAC=0, PLMNVALTAGMIN=9, PLMNVALTAGMAX=12;
//Add RA2 and RA3 that belong to LA1

//Add URA0, UTRA1, UTRA2, and UTRA3.

ADD URA: URAID=0;
ADD URA: URAID=1;
ADD URA: URAID=2;
ADD URA: URAID=3;
//Configure SIB1 information (CS domain information).

ADD
CNDOMAIN:
CNDOMAINID=CS_DOMAIN,
T3212=1,
ATT=ALLOWED,
DRXCYCLELENCOEF=8;
//Configure SIB1 information (PS domain information)

ADD CNDOMAIN: CNDOMAINID=PS_DOMAIN, NMO=MODE1, DRXCYCLELENCOEF=8;
IV. Configuring Hardware Data

//Set two ports on the WLPU as active and standby ports for the WRBS1.
ADD REDPORT: LSN=2, LPN=0, HSN=4, HPN=0, REDT=INTERNAL;
//Add a WRBS named WRBS1.

ADD SUBRACK: SRN=1, SRNAME="WRBS1", WLPUSN=2, WLPUPN=0, WXIET=WBIE;
//Set two ports on the WLPU as active and standby port for the WRBS3.
ADD REDPORT: LSN=2, LPN=1, HSN=4, HPN=1, REDT=INTERNAL;
//Add a WRBS named WRBS3 and set the WOSEs to 1:1 MSP mode.
ADD SUBRACK: SRN=3, SRNAME="WRBS3", WLPUSN=2, WLPUPN=1, WXIET=WOSE,
REDT=ONE_TO_ONE;
2-7
Chapter 2
//Set the WRBS1 as the RFN source subrack.

SET RFNSRC: SRN=1;
//Set the number of active WHPUs to 2.

SET WHPUAS: WHPUAS=2;
V. Configuring Clock Source Data

//Add a clock source with stratum 2 that is extracted from optical port 12 of the WLPU in
slot 2.
ADD CLKSRC: SRCGRD=4, SRCT=SDH, WLPUSN=2, WLPUPN=12;
//Add a clock source with stratum 3 that is extracted from optical port 14 of the WLPU in
slot 4.
ADD CLKSRC: SRCGRD=3, SRCT=SDH, WLPUSN=4, WLPUPN=14;
//Set the system clock switchover strategy to the preemptive auto switchover strategy.
SET CLKMODE: CLKWMODE=PREEMPTIVE_AUTO_HANDOVER_STRATEGY;
VI. Configuring OSP Data

//Add an OSP.
ADD
OPC:
NI=NAT,
SPCBITS=BIT14,
SPC=H'0008,
NSAP=
H45000086100101008F0000000000000000000000;
VII. Setting the BAM to Online Mode

//Set the BAM to online mode.
SET ONLINE;
2.2.3 Commissioning RNC Basic Data

I. Overview
To commission the configured data, operate as follows:
1)
Formatting the RNC Basic Data
2)
Loading the Files into Flash Memory
3)
Setting the Loading Control Parameters
4)
Resetting the Whole System
5)
Querying the Running Status of Each Board
6)
Checking the Consistency of BAM and FAM in Board Versions
7)
Querying the States of the OSP
II. Formatting the RNC Basic Data

Format the RNC basic data using the FMT DATA command to generate the files that
can be loaded.
2-8
Chapter 2
III. Loading the Files into Flash Memory

Load the files into the hard disk of WMPU using the LOD BRD command.
Load the files into the Flash Memory of each board in WRBSs using the LOD BRD
command.
IV. Setting the Loading Control Parameters

Set the loading control parameters of WRSS and WRBSs as Load from FLASH. If load
from BAM, not write FLASH using the SET LODPARA command.
V. Resetting the Whole System

Reset the whole system using the RST SYS command. The FAM will automatically load
the software and configuration data.
VI. Querying the Running Status of Each Board

Check the running status of each board from the panel at the O&M console.
z
Green: Indicates that the board works normally and is in active mode.
Blue: Indicates that the board works normally and is in standby mode.
Red: Indicates that the board is faulty.
VII. Checking the Consistency of BAM and FAM in Board Versions

Perform Cyclic Redundancy Checks (CRC) on the BAM and FAM using the ACT CRC
command.
Check the consistency of the BAM and FAM in board versions using the CMP BRDVER
command.
VIII. Querying the States of the OSP

Query the states of the OSP using the DSP OPC command. The correct states are as
follows:
z
SCCP OPC status should be enabled.
SCCP status should be enabled for service.
MTP3-B status should be available.
2-9
Chapter 3
RNC-MSC Interconnection Data Configuration
Chapter 3 RNC-MSC Interconnection Data

Configuration
3.1 Overview
Configuring RNC-MSC interconnection data is to configure the data that must be
configured on the RNC during the interconnection of the RNC and Mobile Service
Switching Center (MSC).

Before configuring RNC-MSC interconnection data, configure the RNC basic data,
including local office data, hardware data, clock source data, and OSP data. For the
configuration of the RNC basic data, refer to Chapter 2.

The Huawei RNC supports the MSCs of R99 and R4. As the configuration of RNC-MSC
(R99) interconnection data is different from that of RNC-MSC (R4) interconnection data,
this chapter will give configuration examples respectively.
1)
Configuring Physical Layer
2)
Configuring ATM Layer
3)
Configuring SAAL Link
4)
Configuring DSP
5)
Configuring Signalling Linkset
6)
Configuring Signalling Route
7)
Configuring Signalling Link
8)
Configuring ALCAP Adjacent Node
9)
Configuring AAL2 PATH
10) Configuring AAL2 Route
3-1
Chapter 3
3.2 RNC-MSC (R99) Interconnection Data Configuration

3.2.1 Planning RNC-MSC (R99) Interconnection Data
I. Typical Network Topology
As shown in Figure 3-1, the RNC and MSC are connected to the Synchronous Digital
Hierarchy (SDH) transmission network by Add/Drop Multiplexers (ADMs).
STM-1 ADM
ADM
SDH
STM-1
RNC
MSC
Figure 3-1 RNC-MSC (R99) network topology
Note:
If the RNC is near the MSC, as both in the same equipment room, you can use optical fiber to connect
them directly.
II. Data Planning Example

Table 3-1 lists the planning example of RNC-MSC (R99) interconnection data.
Table 3-1 RNC-MSC (R99) interconnection data planning
Item
Data planning
MSC Destination Signalling Point (DSP)

code
H0001
MSC ATM address
H45000086100101001F0000000000000000000000
Iu physical port outgoing from RNC
Optical port 12 of the WLPU in slot 2
RNC-MSC signalling links in control plane
Refer to Table 3-2
RNC-MSC AAL2 paths in user plane
Refer to Table 3-3
Table 3-2 lists the data negotiation and planning for RNC-MSC (R99) signalling links in
the control plane. Where, the dash area shows the data planning inside the RNC and
the non-dash area shows the data negotiated between the RNC and MSC. Inside the
RNC, each WSPU subsystem is configured with an SAAL link to the MSC.
3-2
Chapter 3
Table 3-2 Data negotiation and planning for RNC-MSC (R99) signalling links in control plane
VPI
VCI
WRBS
No.
WSPU
subsystem No.
SAAL
link
No.
1000
10
32
NOCLPNOSCR
1000
11
32
CBR
NOCLPNOSCR
1000
12
32
CBR
NOCLPNOSCR
1000
13
32
SLC
Service
type
Traffic
description
CBR
NOCLPNOSCR
CBR
2
3
PCR
(cell/s)
Table 3-3 lists the data negotiation and planning for RNC-MSC (R99) AAL2 PATHs in
the user plane. Where, the dash area shows the data planning inside the RNC and the
non-dash area shows the data negotiated between the RNC and MSC.
Table 3-3 Data negotiation and planning for RNC-MSC (R99) AAL2 PATHs in user plane
AAL2
Service
PATH
type
ID
WSPU
PCR
SCR
WRBS
VPI VCI From
subsystem
(cell/s) (cell/s)
No.
No.
Traffic description
RTVBR NOCLPNOSCRCDVT
7434
6424
60
32
RNC
7434
6424
60
33
RNC
7434
6424
61
32
RNC
7434
6424
61
33
RNC
7434
6424
62
32
RNC
7434
6424
62
33
RNC
7434
6424
63
32
RNC
7434
6424
63
33
RNC
3.2.2 Configuring RNC-MSC (R99) Interconnection Data

I. Configuring Physical Layer
//Set the type of WLPU optical port.
SET OPT: OPT=SDH;
//Set the type of optical port 12 on each of the WLPUs in slots 2 and 4 to STM-1.
SET WLPUSUBT: SN=2, SUBN=3, SUBT=STM-1;
//Add active and standby ports for physical transmission on the Iu-CS interface. That is
to set optical port 12 in slot 2 and optical port 12 in slot 4 to be the active and standby
ports.
3-3
Chapter 3
ADD REDPORT: LSN=2, LPN=12, HSN=4, HPN=12, REDT=EXTERNAL;
II. Configuring ATM Layer

//Add an ATM traffic record for an SAAL NNI link over the Iu-CS interface. The traffic
record index is 100. If this index is already configured over another interface, it need not
be configured here.
ADD
ATMTRF:
TRFX=100,
ST=CBR,
REMARK="Iu-SAAL",
TRFD=NOCLPNOSCR,
UT=CELL/S, PCR=1000;
//Add an ATM traffic record for an AAL2 PATH over the Iu-CS interface. The traffic
record index is 101. If this index is already configured, it need not be configured here.
ADD
ATMTRF:
TRFX=101,
REMARK="IuCS-AAL2Path",
ST=RTVBR,
MBS=1000,
TRFD=NOCLPSCRCDVT,
CDVT=102400,
UT=CELL/S,
PCR=7434,
SCR=6424;
III. Configuring SAAL Link

//Add two SAAL NNI links over the Iu-CS interface that are terminated respectively at
WSPU subsystems 0 and 1 of WRBS1.
ADD
SAALLNK:
TXTRFX=100,
SRN=1,
SSN=0,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=10,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=1,
SSN=1,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=11,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=3,
SSN=0,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=12,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=3,
SSN=1,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=13,
CARRYVCI=32;
IV. Configuring DSP

//Add an MSC DSP with index of 0 and signalling route mask of B0000.
ADD N7DPC: DPX=0, SPC=H'0001, SLSMASK=B0000, NEIGHBOR=YES, NAME="MSC",
DPCT=IUCS, STP=ON;
V. Configuring Signalling Linkset

//Add a signalling linkset to the MSC with linkset index of 0 and signalling link mask of
B1111. In addition, set the signalling linkset emergency verification switch to OFF.
3-4
Chapter 3
ADD MTP3BLKS: SIGLKSX=0, DPX=0, LNKSLSMASK=B1111, EMERGENCY=OFF;
VI. Configuring Signalling Route

//Add a signalling route to the MSC.
ADD MTP3BRT: DPX=0, SIGLKSX=0, PRIORITY=0;
VII. Configuring Signalling Link

//Add MTP3B links into the signalling linkset with index of 0.
ADD MTP3BLNK: SIGLKSX=0, SIGSLC=0, SRN=1, SSN=0, SAALLNKN=0, PRIORITY=0,
TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;
VIII. Configuring ALCAP Adjacent Node

//Add an ALCAP adjacent node, MSC, with ID of 0, interface type of Iu-CS, and DSP
index of 0.
ADD AAL2ADJNODE: ANI=0, ANT=IU, DPX=0, NAME="MSC";
IX. Configuring AAL2 PATH

//Add AAL2 PATHs to the ALCAP adjacent node, MSC.
//Add two AAL2 PATHs controlled by WSPU subsystem 0 of WRBS1.
ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=1,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,
CARRYSN=2, CARRYVPI=60, CARRYVCI=32;

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=2,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=3,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=4,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
ANI=0,
PATHID=5,
3-5
ENDSRN=3,
ENDSN=7,
CARRYSR=WRSS,
CARRYPN=12,
Chapter 3
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=6,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=7,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=8,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,
X. Configuring AAL2 Route

//Add an AAL2 route.
ADD AAL2RT: NSAP= H45000086100101001F0000000000000000000000, ANI=0,
RTX=0, OWNERSHIP=YES;
3.2.3 Checking RNC-MSC (R99) Interconnection Data

I. Checking Control Plane Data
To check the control plane data, operate as follows:
1)
Carry out the DSP SAALLNK command to check the availability of the SAAL links.
2)
Carry out the DSP MTP3BLNK command to check the availability of the MTP3B
links.
3)
Carry out the DSP SSN command to check the availability of the Signalling
Connection Control Part (SCCP) subsystems.
4)
Carry out the DSP AAL2ADJNODE command to check the availability of the
adjacent node of the Iu-CS interface, namely, MSC.
II. Checking User Plane Data

To check the user plane data, operate as follows:
1)
Carry out the DSP AAL2PATH command to check the AAL2 PATHs to the adjacent
node.
2)
Carry out the ACT VCLCC command to activate the Continuous Check (CC) of
Virtual Connect Links (VCLs) bearing the AAL2 PATHs.
3)
Carry out the DSP VCLCC command to query the CC results of VCLs bearing the
AAL2 PATHs to check whether there are Alarm Indication Signal (AIS) and RDI
alarms.
4)
Carry out the DEA VCLCC command to deactivate the CC of VCLs bearing the
AAL2 PATHs.
3-6
Chapter 3
3.3 RNC-MSC (R4) Interconnection Data Configuration

3.3.1 Planning RNC-MSC (R4) Interconnection Data
As shown in Figure 3-2, the RNC and Media Gateway (MGW) are connected to the
SDH transmission network by the Add/Drop Multiplexers (ADMs). The MGW and MSC
server are connected by network cable.
STM-1
ADM
ADM
SDH
STM-1
RNC
MGW
MSC Server
Figure 3-2 RNC-MSC(R4) network topology
Note:
If the RNC is near the MGW, as both in the same equipment room, you can use optical fiber to connect
them directly.

Table 3-4 lists the planning example of RNC-MSC (R99) interconnection data.
Table 3-4 RNC-MSC (R4) interconnection data planning
Item
Data planning
MGW Destination Signalling Point (DSP)

code
H0002
MGW ATM address
H45000086100101002F0000000000000000000000
MSC server DSP code
H0001
Iu physical port outgoing from RNC
RNC-MGW links in the control plane
Refer to Table 3-5
RNC-MGW links in the user plane
Refer to Table 3-6
Table 3-5 lists the data negotiation and planning for RNC-MSC (R4) signalling links in
the control plane. Where, the dash area shows the data planning inside the RNC and
3-7
Chapter 3
the non-dash area shows the data negotiated between the RNC and MGW. Inside the
RNC, each WSPU subsystem is configured with an SAAL link to the MGW.
Table 3-5 Data negotiation and planning for RNC-MSC (R4) signalling links in control plane
VPI
VCI
WRBS
No.
WSPU
subsystem No.
SAAL
link
No.
1000
10
32
NOCLPNOSCR
1000
11
32
CBR
NOCLPNOSCR
1000
12
32
CBR
NOCLPNOSCR
1000
13
32
PCR
SLC
Service
type
Traffic
description
(cell/s)
CBR
NOCLPNOSCR
CBR
2
3
Table 3-6 lists the data negotiation and planning for RNC-MSC (R4) AAL2 PATHs in the
user plane. Where, the dash area shows the data planning inside the RNC and the
non-dash area shows the data negotiated between the RNC and MGW.
Table 3-6 Data negotiation and planning for RNC-MSC (R4) AAL2 PATHs in user plane
AAL2
PATH
ID
Service
type
Traffic
description
PCR
(cell/s)
SCR
(cell/s)
VPI
VCI
RTVBR
NOCLPNOS
CRCDVT
7434
6424
60
RTVBR
NOCLPNOS
CRCDVT
7434
6424
RTVBR
NOCLPNOS
CRCDVT
7434
RTVBR
NOCLPNOS
CRCDVT
RTVBR
From
WRBS
No.
WSPU
subsystem No.
32
RNC
60
33
RNC
6424
61
32
RNC
7434
6424
61
33
RNC
NOCLPNOS
CRCDVT
7434
6424
62
32
RNC
RTVBR
NOCLPNOS
CRCDVT
7434
6424
62
33
RNC
RTVBR
NOCLPNOS
CRCDVT
7434
6424
63
32
RNC
RTVBR
NOCLPNOS
CRCDVT
7434
6424
63
33
RNC
3-8
Chapter 3
3.3.2 Configuring RNC-MSC (R4) Interconnection Data

SET OPT: OPT=SDH;
//Add active and standby ports for physical transmission on the Iu-CS interface. That is
ports.

//Add an ATM traffic record for an SAAL NNI link over the Iu-CS interface. The traffic
be configured here.
ADD
ATMTRF:
TRFX=100,
ST=CBR,
REMARK="Iu-SAAL",
TRFD=NOCLPNOSCR,
//Add an ATM traffic record for an AAL2 PATH over the Iu-CS interface. The traffic
record index is 101. If this index is already configured, it need not be configured here.
ADD
ATMTRF:
TRFX=101,
REMARK="IuCS-AAL2Path",
ST=RTVBR,
MBS=1000,
TRFD=NOCLPSCRCDVT,
CDVT=102400,
UT=CELL/S,
PCR=7434,
SCR=6424;

ADD
SAALLNK:
TXTRFX=100,
SRN=1,
SSN=0,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=10,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=1,
SSN=1,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=11,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=3,
SSN=0,
RXTRFX=100,
CARRYVCI=32;
3-9
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=12,
ADD
SAALLNK:
TXTRFX=100,
Chapter 3
SRN=3,
SSN=1,
RXTRFX=100,
SAALLNKN=0,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=12,
CARRYVPI=13,
CARRYVCI=32;
IV. Configuring DSP

//Add an MGW DSP with index of 0 and signalling route mask of B0000.
ADD N7DPC: DPX=0, SPC=H'0002, SLSMASK=B0000, NEIGHBOR=YES, NAME="MGW",
DPCT=IUCS_ALCAP, STP=ON;
//Add an MSC server DSP with index of 4 and signalling route mask of B0000.
ADD N7DPC: DPX=4, SPC=H'0001, SLSMASK=B0000, NEIGHBOR=NO, NAME="MSC
Server", DPCT=IUCS_RANAP, STP=ON;

//Add a signalling linkset to the MGW with linkset index of 0 and signalling link mask of

//Add a signalling route to the MGW.
//Add a signalling route to the MSC server.


TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;

//Add an ALCAP adjacent node, MGW, with ID of 0, interface type of Iu-CS, and DSP
index of 0.
ADD AAL2ADJNODE: ANI=0, ANT=IU, DPX=0, NAME="IuCS-ALCAP";
3-10
Chapter 3

//Add AAL2 PATHs to the Q.AAL2 adjacent node, MGW.
ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=1,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=2,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=3,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=4,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=5,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=6,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=7,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=12,
ANI=0,
TXTRFX=101,
PATHID=8,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD AAL2RT: NSAP=H'45000086100101002F0000000000000000000000, ANI=0,
3-11
Chapter 3
3.3.3 Checking RNC-MSC (R4) Interconnection Data

1)
Carry out the DSP SAALLNK command to check the availability of the SAAL links.
2)
Carry out the DSP MTP3BLNK command to check the availability of the MTP3B
links.
3)
Carry out the DSP SSN command to check the availability of the Signalling
Connection Control Part (SCCP) subsystems.
4)
Carry out the DSP AAL2ADJNODE command to check the availability of the
adjacent node of the Iu-CS interface, namely, MGW.

1)
Carry out the DSP AAL2PATH command to check the AAL2 PATHs to the adjacent
node.
2)
Virtual Connect Links (VCLs) bearing the AAL2 PATHs.
3)
AAL2 PATHs to check whether there are AIS and RDI alarms.
4)
Carry out the DEA VCLCC command to deactivate the CC of VCLs bearing the
AAL2 PATHs.
3-12
Chapter 4
RNC-SGSN Interconnection Data Configuration
Chapter 4 RNC-SGSN Interconnection Data

Configuration
4.1 Overview
Configuring RNC-SGSN interconnection data is to configure the data that must be
configured on the RNC during the interconnection of the RNC and Serving GPRS
Support Node (SGSN).

Before configuring RNC-SGSN interconnection data, configure the RNC basic data,

1)
2)
3)
4)
Configuring DSP
5)
6)
7)
8)
Configuring IPoA Channel
4.2 RNC-SGSN Interconnection Data Configuration

4.2.1 Planning RNC-SGSN Interconnection Data
As shown in Figure 4-1, the RNC and SGSN are connected to the SDH transmission
network by ADMs.
4-1
STM-1
Chapter 4
ADM
SDH
ADM
STM-1
SGSN
RNC
Figure 4-1 RNC-SGSN network topology
Note:
If the RNC is near the SGSN, as both in the same equipment room, you can use optical fiber to connect
them directly.

Table 4-1 lists the planning example of RNC-SGSN interconnection data.
Table 4-1 RNC-SGSN interconnection data planning
Item
Data planning
SGSN DSP code
H0007
Outgoing Iu interface of the RNC
RNC-SGSN signalling links in control plane
Refer to Table 4-2
RNC-SGSN channels in user plane
Refer to Table 4-3 and Figure 4-2
Table 4-2 lists the data negotiation and planning for RNC-SGSN signalling links in the
control plane. Where, the dash area shows the data planning inside the RNC and the
non-dash area shows the data negotiated between the RNC and SGSN. Inside the
RNC, each WSPU subsystem is configured with an SAAL link to the SGSN.
Table 4-2 Data negotiation and planning for RNC-SGSN signalling links in control plane
SLC
Service
type
Traffic
description
PCR
VPI
(cell/s)
WRBS
No.
VCI
WSPU
subsystem
No.
SAAL
link No.
CBR
NOCLPNOSCR
1000
10
32
10
CBR
NOCLPNOSCR
1000
11
32
10
CBR
NOCLPNOSCR
1000
12
32
10
CBR
NOCLPNOSCR
1000
13
32
10
4-2
Chapter 4
Table 4-3 lists the data negotiation and planning for RNC-SGSN channels in the user
plane. Where, the dash area shows the data planning inside the RNC and the non-dash
area shows the data negotiated between the RNC and SGSN, as shown in Figure 4-2.
Table 4-3 Data negotiation and planning for RNC-SGSN channels in user plane
VC
I
Logic
al No.
of
WHP
U
Subsys
tem No.
80
32
35141
5
81
32
NOCLPNOSCRC
DVT
35141
5
82
32
NOCLPNOSCRC
DVT
35141
5
83
32
Traffic
description
PCR
(cell/s
)
VP
I
UBR
NOCLPNOSCRC
DVT
35141
5
10.10.21.2/
24
UBR
NOCLPNOSCRC
DVT
10.10.21.4/
24
10.10.21.2/
24
UBR
10.10.21.4/
24
10.10.21.2/
24
UBR
IP address
of SGSN
IP address
of SGSN
gateway
IP address
of RNC
Servic
e type
10.10.121.2/
24
10.10.21.4/
24
10.10.21.2/
24
10.10.21.4/
24
Subsystem 1 10.10.21.2/24
of WHPU 1
10.10.21.4/24
To SGSN
gateway 1
Subsystem 2 10.10.22.2/24
of WHPU 1
10.10.22.4/24
To SGSN
gateway 2
10.10.121.2/24
SGSN
Subsystem 1 10.10.23.2/24
of WHPU 2
10.10.23.4/24
To SGSN
gateway 3
Subsystem 2 10.10.24.2/24
of WHPU 2
10.10.24.4/24
To SGSN
gateway 4
Figure 4-2 IPoA channels between RNC and SGSN
4.2.2 Configuring RNC-SGSN Interconnection Data

SET OPT: OPT=SDH;
4-3
Chapter 4
//Add active and standby ports for physical transmission on the Iu-PS interface. That is
ports.

//Add an ATM traffic record for an SAAL NNI link over the Iu-PS interface. The traffic
be configured here.
ADD
ATMTRF:
TRFX=100,
ST=CBR,
REMARK="Iu-SAAL",
TRFD=NOCLPNOSCR,
//Add an ATM traffic record for an IPoA channel over the Iu-PS interface. The traffic
be configured here.
ADD ATMTRF: TRFX=105, ST=UBR, UT=CELL/S, PCR=351415, CDVT=1024000,
TRFD=NOCLPNOSCRCDVT;

//Add two SAAL NNI links over the Iu-PS interface that are terminated respectively at
ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=10, CARRYSR=WRSS, CARRYPN=14,
TXTRFX=100,
RXTRFX=100,
SAALLNKT=NNI,
CARRYSN=2,
CARRYVPI=10,
CARRYVCI=32;
TXTRFX=100,
RXTRFX=100,
SAALLNKT=NNI,
CARRYSN=2,
CARRYVPI=11,
CARRYVCI=32;
//Add two SAAL NNI links over the Iu-PS interface that are terminated respectively at
TXTRFX=100,
RXTRFX=100,
SAALLNKT=NNI,
CARRYSN=2,
CARRYVPI=12,
CARRYVCI=32;
TXTRFX=100,
RXTRFX=100,
SAALLNKT=NNI,
CARRYSN=2,
CARRYVPI=13,
CARRYVCI=32;
IV. Configuring DSP

//Add an SGSN DSP with index of 5 and signalling route mask of B0000.
ADD N7DPC: DPX=5, SPC=H'0007, SLSMASK=B0000, NEIGHBOR=YES, NAME="SGSN",
DPCT=IUPS, STP=OFF;
4-4
Chapter 4

//Add a signalling linkset to the SGSN with linkset index of 5 and signalling link mask of

//Add a signalling route to the SGSN.

TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;
VIII. Configuring IPoA Channel

//Add IPoA clients to WHPU subsystems.
//Add two IPoA clients to the WHPU with logical slot No. of 1. The IP addresses are
10.10.21.2 and 10.10.22.2 respectively and the subnet masks are 255.255.255.0.
ADD
IPOACLIENT:
SRN=2,
lSN=1,
SSN=1,
IPADDR="10.10.21.2",
lSN=1,
SSN=2,
IPADDR="10.10.22.2",
MASK="255.255.255.0";
ADD
IPOACLIENT:
SRN=2,
MASK="255.255.255.0";
//Add two IPoA clients to the WHPU with logical slot No. of 2. The IP addresses are
10.10.23.2 and 10.10.24.2 respectively and the subnet masks are 255.255.255.0.
ADD
IPOACLIENT:
SRN=2,
lSN=2,
SSN=1,
IPADDR="10.10.23.2",
lSN=2,
SSN=2,
IPADDR="10.10.24.2",
MASK="255.255.255.0";
ADD
IPOACLIENT:
SRN=2,
MASK="255.255.255.0";
//Add a PVC for each IPoA client.

ADD IPOAPVC: IPADDR="10.10.21.2", PEERIPADDR="10.10.21.4", PEERT=OTHER,
CARRYSRT=WRSS,
CARRYPN=14,
TXTRFX=105,
RXTRFX=105,
CARRYSN=2,
CARRYVPI=80, CARRYVCI=32;
CARRYSRT=WRSS,
CARRYPN=14,
4-5
TXTRFX=105,
RXTRFX=105,
CARRYSN=2,
Chapter 4
CARRYSRT=WRSS,
CARRYPN=14,
TXTRFX=105,
RXTRFX=105,
CARRYSN=2,
CARRYSRT=WRSS,
CARRYPN=14,
TXTRFX=105,
RXTRFX=105,
CARRYSN=2,
CARRYVPI=83 CARRYVCI=32;
//Add a route to the SGSH for each IPoA client.

ADD
IPRT:
SRN=2,
LSN=1,
SSN=1,
RTDEST="10.10.121.2",
RTDESTMASK="255.255.255.0", NEXTHOP="10.10.21.4";
ADD
IPRT:
SRN=2,
LSN=1,
SSN=2,
RTDEST="10.10.121.2",
ADD
IPRT:
SRN=2,
LSN=1,
SSN=1,
RTDEST="10.10.121.2",
ADD
IPRT:
SRN=2,
LSN=1,
SSN=1,
RTDEST="10.10.121.2",
4.2.3 Checking RNC-SGSN Interconnection Data

1)
Carry out the DSP SAALLNK command to check whether the SAAL links are
available.
2)
Carry out the DSP MTP3BLNK command to check whether the MTP3B links are
available.
3)
Carry out the DSP SSN command to check whether the SCCP subsystem is
available.

Carry out the PNG IPADDR command to check whether all of the WHPU subsystems
are connected to the SGSN destination network.
4-6
Chapter 5
RNC-CBC Interconnection Data Configuration
Chapter 5 RNC-CBC Interconnection Data

Configuration
5.1 Overview
Configuring RNC-CBC interconnection data is to configure the data that must be
configured on the RNC during the interconnection of the RNC and Cell Broadcast
Center (CBC).

Before configuring RNC-CBC interconnection data, configure the RNC basic data,

1)
2)
3)
4)

Configuring IPoA Channel
Configuring the IP address for the CBC
Note:
For the configuration of CBC upper layer services, refer to HUAWEI BSC6800 WCDMA Radio Network
Controller Operation Manual Data Configuration.
5.2 RNC-CBC Interconnection Data Configuration

5.2.1 Planning RNC-CBC Interconnection Data
As shown in Figure 5-1, the RNC and CBC are connected to the SDH transmission
network by ADMs.
5-1
STM-1
Chapter 5
SDH
ADM
ADM
STM-1
CBC
RNC
Figure 5-1 RNC-CBC network topology
Note:
If the RNC is near the CBC, as both in the same equipment room, you can use optical fiber to connect
them directly.

Table 5-1 lists the planning example of RNC-CBC interconnection data.
Table 5-1 RNC-CBC interconnection data planning
Item
Data planning
Outgoing Iu interface of the RNC
RNC-CBC channel
Refer to Table 5-2 and Figure 5-2
Table 5-2 lists the RNC-CBC channel negotiation and planning. Where, the dash area
shows the data planning inside the RNC and the non-dash area shows the data
negotiated between the RNC and CBC, as shown in Figure 5-2.
Table 5-2 Data negotiation and planning for RNC-CBC channel
IP
address
of CBC
IP address
of CBC
gateway
IP
address
of RNC
Service
type
10.10.14
1.4/24
10.10.131.4/
24
10.10.13
1.2/24
UBR
Traffic
description
PCR
(cell/s)
V
PI
V
CI
WRBS
No.
WSPU
subsystem
No.
NOCLPNOS
CRCDVT
20000
90
32
WSPU
10.10.131.4/24
subsystem 0
of WRBS1 10.10.131.2/24
Figure 5-2 IPoA channel between RNC and CBC
5-2
To CBC
gateway
10.10.141.4/24
CBC
Chapter 5
5.2.2 Configuring RNC-CBC Interconnection Data

SET OPT: OPT=SDH;
//Set the type of optical port 11 to STM-1 on each of the WLPUs in slots 2 and 4.
//Add active and standby ports for physical transmission on the Iu-BC interface. That is
ports.

//Add an ATM traffic record for an IPoA channel over the Iu-BC interface. The traffic
be configured here.
ADD ATMTRF: TRFX=106, ST=UBR, UT=CELL/S, PCR=20000, CDVT=1024000,
TRFD=NOCLPNOSCRCDVT;
III. Configuring IPoA Channel

//Add an IPoA client to WSPU subsystem 0 of WRBS1. The IP address is 10.10.131.2
and the subnet mask is 255.255.255.0.
ADD
IPOACLIENT:
SRN=1,
LSN=10,
SSN=0,
IPADDR="10.10.131.2",
MASK="255.255.255.0";
//Add a PVC to the IPoA client.

ADD
IPOAPVC:
IPADDR="10.10.131.2",
CARRYSRT=WRSS,
CARRYPN=11,
TXTRFX=106,
PEERIPADDR="10.10.131.4",
RXTRFX=106,
CARRYSN=2,
//Add a route to the CBC.

ADD
IPRT:
SRN=1,
LSN=10,
SSN=0,
RTDEST="10.10.141.2",
IV. Configuring the IP address for the CBC

//Set WSPU subsystem 0 of WRBS1 as the Service Area Broadcast Protocol (SABP)
processing subsystem. The IP address of the CBC is 10.10.141.2 and the mask is
255.255.255.0.
ADD
CBSADDR:
SRN=1,
MASK="255.255.255.0";
5-3
SSN=0,
PEERIPADDR="10.10.141.4",
Chapter 5
5.2.3 Checking RNC-CBC Interconnection Data

Carry out the PNG IPADDR command to check whether the IPoA client on WSPU
subsystem 0 of WRBS1 is connected to the CBC destination network.
5-4
Chapter 6
RNC-RNC Interconnection Data Configuration
Chapter 6 RNC-RNC Interconnection Data

Configuration
6.1 Overview
Configuring RNC-RNC interconnection data is to configure the data that must be
configured on the local RNC during the interconnection of the local RNC and another
RNC.

Before configuring RNC-RNC interconnection data, configure the RNC basic data,

1)
2)
3)
4)
Configuring DSP
5)
6)
7)
8)
9)
10) Configuring AAL2 Route

11) Configuring Basic Information of the Other RNC
12) Configuring IP Route to the Other RNC
6.2 RNC-RNC Interconnection Data Configuration

6.2.1 Planning RNC-RNC Interconnection Data
As shown in Figure 6-1, two RNCs are connected to the SDH transmission network by
ADMs.
6-1
STM-1
Chapter 6
ADM
SDH
ADM
STM-1
Another
RNC
RNC
Figure 6-1 RNC-RNC network topology
Note:
If the local RNC is near the other RNC, as both in the same equipment room, you can use optical fiber to
connect them directly.

Table 6-1 lists the planning example of RNC-RNC interconnection data
Table 6-1 RNC-RNC interconnection data planning
Item
Data planning
DSP code of the other RNC
H0009
ATM address of the other RNC
H45000086100102009F0000000000000000000000
ID of the other RNC
MCC of the other RNC
000
MNC of the other RNC
460
Whether the other RNC supports both CS

and PS services
Yes
Outgoing Iu interface of the local RNC
RNC-RNC signalling links in control plane
Refer to Table 6-2
RNC-RNC AAL2 PATHs in user plane
Refer to Table 6-3
IP addresses for the two RNCs
Refer to Figure 6-2
Table 6-2 lists the data negotiation and planning for RNC-RNC signalling links in the
control plane. Where, the dash area shows the data planning inside the local RNC.
Inside the local RNC, each WSPU subsystem is configured with an SAAL link to the
other RNC.
6-2
Chapter 6
Table 6-2 Data negotiation and planning for RNC-RNC signalling links in control plane
SLC
Service
type
Traffic
description
PCR
(cell/s)
VPI
WRBS
No.
VCI
WSPU
subsystem
No.
SAAL
link
No.
CBR
NOCLPNOSCR
1000
10
32
12
CBR
NOCLPNOSCR
1000
11
32
12
CBR
NOCLPNOSCR
1000
12
32
12
CBR
NOCLPNOSCR
1000
13
32
12
Table 6-3 lists the data negotiation and planning for RNC-RNC AAL2 PATHs in the user
plane. Where, the dash area shows the data planning inside the local RNC.
Table 6-3 Data negotiation and planning for RNC-RNC AAL2 PATHs in user plane
PCR
(cell/s)
SCR
(cell/s)
VPI
VCI
From .
..
WRBS
No.
WSPU
subsystem
No.
NOCLPNOSCRCDVT
7434
6424
60
32
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
60
33
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
61
32
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
61
33
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
62
32
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
62
33
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
63
32
RNC
RTVBR
NOCLPNOSCRCDVT
7434
6424
63
33
RNC
AAL2
PATH
ID
Service
type
RTVBR
Traffic description
Figure 6-2 shows the IP address planning for the local RNC and the other RNC. To
support the relocations between the two RNCs, configure each WHPU subsystem of
the local RNC with IP routes to the other RNC.
6-3
Chapter 6
Subsystem 1 10.10.21.2/24
of WHPU 1
10.10.21.4/24
To SGSN
gateway 1
Subsystem 2 10.10.22.2/24
of WHPU 1
10.10.22.4/24
To SGSN
gateway 2
10.10.121.2/24
SGSN
Subsystem 1 10.10.23.2/24
of WHPU 2
10.10.23.4/24 To SGSN
gateway 3
Subsystem 2 10.10.24.2/24
of WHPU 2
10.10.24.4/24 To SGSN
gateway 4
Local RNC
Destination 10.10.141.2/24
IP address 1
Destination 10.10.142.2/24
IP address 2
Another RNC
Figure 6-2 IP address planning for the two RNCs
6.2.2 Configuring RNC-RNC Interconnection Data

SET OPT: OPT=SDH;
//Add active and standby ports for physical transmission on the Iur interface. That is to
set optical port 8 in slot 2 and optical port 8 in slot 4 to be the active and standby ports.
6-4
Chapter 6

//Add an ATM traffic record for an SAAL NNI link over the Iur interface. The traffic record
index is 100. If this index is already configured over another interface, it need not be
configured here.
ADD ATMTRF: TRFX=100, ST=CBR, REMARK="Iur", TRFD=NOCLPNOSCR, UT=CELL/S,
PCR=1000;
//Add an ATM traffic record for an AAL2 PATH over the Iur interface. The traffic record
configured here.
ADD
ATMTRF:
TRFX=101,
REMARK="Iur-AAL2Path",
ST=RTVBR,
TRFD=NOCLPSCRCDVT,
MBS=1000,
CDVT=102400,
UT=CELL/S,
PCR=7434,
SCR=6424;

//Add two SAAL NNI links over the Iur interface that are terminated respectively at
ADD
SAALLNK:
TXTRFX=100,
SRN=1,
SSN=0,
RXTRFX=100,
SAALLNKN=12,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=8,
CARRYVPI=10,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=1,
SSN=1,
RXTRFX=100,
SAALLNKN=12,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=8,
CARRYVPI=11,
CARRYVCI=32;
//Add two SAAL NNI links over the Iur interface that are terminated respectively at
ADD
SAALLNK:
TXTRFX=100,
SRN=3,
SSN=0,
RXTRFX=100,
SAALLNKN=12,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=8,
CARRYVPI=12,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=100,
SRN=3,
SSN=1,
RXTRFX=100,
SAALLNKN=12,
SAALLNKT=NNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=8,
CARRYVPI=13,
CARRYVCI=32;
IV. Configuring DSP

//Add a DSP with type of another RNC. The DSP index is 6 and signalling route mask is
B0000.
ADD
N7DPC:
DPX=6,
SPC=H'0009,
SLSMASK=B0000,
NEIGHBOR=YES,
NAME="Neighboring RNC1", DPCT=IUR, RNCID=1, STP=OFF;

//Add a signalling linkset to the other RNC. The linkset index is 6, signalling link mask is
B1111, and the signalling linkset emergency verification switch is OFF.
6-5
Chapter 6

//Add a signalling route to the other RNC.

//Add MTP3B signalling links into the signalling linkset with index of 6.
TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;
TCLEN=10, TC=170;

//Add an ALCAP adjacent node, that is, the other RNC. The adjacent node ID is 6,
interface type is Iur, and DSP index is 6.
ADD AAL2ADJNODE: ANI=6, ANT=IUR, DPX=6, NAME="Neighboring RNC1";

//Add AAL2 PATHs to the ALCAP adjacent node, that is, the other RNC.
ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=1,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=2,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=3,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=4,
ENDSRN=1,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
ANI=6,
PATHID=5,
6-6
ENDSRN=3,
ENDSN=7,
CARRYSR=WRSS,
CARRYPN=8,
Chapter 6
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=6,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=7,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=8,
ANI=6,
TXTRFX=101,
PATHID=8,
ENDSRN=3,
RXTRFX=101,
ENDSN=7,
CONTROLSSN=1,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD AAL2RT: NSAP= H45000086100102009F0000000000000000000000, ANI=6,
XI. Configuring Basic Information of the Other RNC

//Configure the basic information of the other RNC
ADD
NRNC:
RNCID=1,
MCC="000",
MNC="460",
SHOHHOTRIG=ON,
UPSRNSRSTARTTHD=60, UPSRNSRSTOPTHD=50, SERVICEIND=SUPPORT_CS_AND_PS;
XII. Configuring IP Route to the Other RNC

//Configure subsystem 1 of WHPU 1 with the routes to the other RNC.
ADD
IPRT:
SRN=2,
LSN=1,
SSN=1,
RTDEST="10.10.141.2",
ADD
IPRT:
SRN=2,
LSN=1,
SSN=1,
RTDEST="10.10.142.2",

ADD
IPRT:
SRN=2,
LSN=1,
SSN=2,
RTDEST="10.10.141.2",
ADD
IPRT:
SRN=2,
LSN=1,
SSN=2,
RTDEST="10.10.142.2",

ADD
IPRT:
SRN=2,
LSN=2,
SSN=1,
RTDEST="10.10.141.2",
ADD
IPRT:
SRN=2,
LSN=2,
SSN=1,
RTDEST="10.10.142.2",

6-7
ADD
IPRT:
Chapter 6
SRN=2,
LSN=2,
SSN=2,
RTDEST="10.10.141.2",
ADD
IPRT:
SRN=2,
LSN=2,
SSN=2,
RTDEST="10.10.142.2",
6.2.3 Checking RNC-RNC Interconnection Data

1)
Carry out the DSP SAALLNK command to check whether the SAAL links are
available.
2)
Carry out the DSP MTP3BLNK command to check whether the MTP3B links are
available.
3)
Carry out the DSP SSN command to check whether the SCCP subsystems are
available.
4)
Carry out the DSP AAL2ADJNODE to check whether the other RNC is available.

1)
Carry out the DSP AAL2PATH command to check whether the AAL2 PATHs are
functional.
2)
VCLs bearing the AAL2 PATHs.
3)
AAL2 PATHs to check whether there are AIS and RDI alarms.
4)
Carry out the DEA VCLCC command to deactivate the Continuous Check (CC) of
VCLs bearing the AAL2 PATHs.
5)
Carry out the PNG IPADDR command to check the connectivity between the local
and peer ends.
6-8
Chapter 7
RNC-NodeB Interconnection Data Configuration
Chapter 7 RNC-NodeB Interconnection Data

Configuration
7.1 Overview
Configuring RNC-NodeB interconnection data is to configure the data that must be
configured on the RNC and NodeB during the interconnection of the RNC and NodeB.

Before configuring RNC-NodeB interconnection data, configure the RNC basic data,

Huawei RNC and NodeBs can adopt different networking modes. Different networking
modes require different configuration data. This chapter introduces how to configure
RNC-NodeB interconnection data in several typical networking modes.
The procedure for configuring the interconnection data on the RNC is as follows:
1)
2)
3)
4)
Configuring NodeB1 Port
5)
6)
7)
Configuring AAL2 Route
The procedure of configuring the interconnection data on the NodeB as follows:

1)
Configuring Transmission Object
2)
Modifying ALCAP Properties
3)
Modifying AAL2 PATH Properties
4)
Modifying NCP Properties
5)
Modifying CCP Properties
In addition, if a NodeB is connected to the RNC through another NodeB, you need to
configure the related networking PVC on the latter.
7-1
Chapter 7
Note:
To configure a NodeB cell, refer to Chapter 8.
7.2 RNC-NodeB Network Topology

7.2.1 Typical Network Topology
This chapter takes the following RNC-NodeB network topology as an example.
E1/T1
NodeB5
NodeB2
E1/T1
NodeB3
SDH
E1/T1
E1/T1 over SDH

E1/T1
SDH
NodeB4
PDH/SDH
RNC
E1/T1
NodeB1
E1/T1
NodeB6
E1/T1
PDH
2G BTS
2G BSC
Figure 7-1 RNC-NodeB network topology

As shown in Figure 7-1, the RNC and NodeBs adopt the following connection modes:
z
The RNC and NodeB1 adopt Plesiochronous Digital Hierarchy (PDH) or

Synchronous Digital Hierarchy (SDH) for transmission.
The RNC and NodeB2 adopt the E1/T1 over SDH mode for transmission.
The RNC and NodeB3 adopt Permanent Virtual Channels (PVCs) provided by
NodeB2 to form a link network.
The RNC and NodeB4 adopt the ATM over SDH mode for transmission.
7-2
Chapter 7
The RNC and NodeB5 adopt PVCs provided by NodeB4 to form a link network.
The RNC and NodeB6 adopt a PDH transmission network provided by the 2G
Base Station Subsystem (BSS).
7.2.2 Data Planning Example

Table 7-1 lists the NodeB interface boards, RNC interface boards, and the WSPU
subsystems in the RNC for handling NodeBs.
Table 7-1 Interface boards and WSPU subsystems
NodeB
NodeB interface board
RNC interface board
WRBS
NodeB1
NDTI
WBIE
WRBS1
NodeB2
NDTI
WOSE
WRBS3
NodeB3
NDTI
WOSE
WRBS3
NodeB4
NAOI
WLPU
WRBS1
NodeB5
NDTI
WLPU
WRBS1
NodeB6
NDTI
WBIE
WRBS1
WSPU
subsystem
If the RNC and a NodeB, such as NodeB3 and NodeB5, adopts PVCs provided by
another NodeB to form a network, they employ a Virtual Path (VP) for switching. The
NodeB that provides networking PVCs need provide different VPIs for different NodeBs
that require these PVCs to connect with the RNC. Figure 7-2 shows a VPI planning
example. Where, an incoming VPI and the corresponding outgoing VPI are the same.
VPI=9
NodeB
VPI=9
VPI=8
VPI=8
VPI=8
VPI=7
VPI=7
VPI=6
NodeB
NodeB
NodeB
Figure 7-2 VPI planning for NodeBs

Table 7-2 lists the ATM address of each NodeB.
7-3
RNC
Chapter 7
Table 7-2 ATM addresses of NodeBs

ATM node name
ATM address
ID in RNC
NodeB1
0x45000086100101010F0000000000000000000000
11
NodeB2
0x45000086100101011F0000000000000000000000
12
NodeB3
0x45000086100101012F0000000000000000000000
13
NodeB4
0x45000086100101013F0000000000000000000000
14
NodeB5
0x45000086100101014F0000000000000000000000
15
NodeB6
0x45000086100101015F0000000000000000000000
16
Note:
z
For the convenience of introduction, this chapter takes one type of the NodeB model, BTS3812, as an
example.
This chapter only introduces how to configure the data in the control plane and signalling plane of Iub
interface. For the IPoA configuration in the management plane of Iub interface, refer to Chapter 8.
7.3 RNC-NodeB1 Interconnection Data Configuration

7.3.1 Planning RNC-NodeB1 Interconnection Data
As shown in Figure 7-3, the RNC and NodeB1 are connected to the PDH or SDH
transmission network by Add/Drop Multiplexers (ADMs).
The RNC and NodeB1 adopt the E1/T1 mode for networking. The RNC adopts the
WBIE interface board while the NodeB1 adopts the NDTI interface board.
E1/T1
ADM
PDH/SDH
NodeB1
ADM
E1/T1
RNC
Figure 7-3 RNC-NodeB1 network topology
Note:
If the RNC is near the NodeB1, as both in the same equipment room, you can use E1/T1 trunk cable to
connect them directly.
7-4
Chapter 7

The following table gives a planning example of RNC-NodeB1 interconnection data:
Table 7-3 RNC-NodeB1 interconnection data planning
Item
Data planning
Cell
2-anttena, 3 sectors x 2 frequencies
ATM address of NodeB1
0x45000086100101010F0000000000000000000000
Cable
The Iub interface adopts 3 E1/T1 trunk cables

belonging to an IMA group
Iub physical port outgoing from RNC
Links 0, 1, and 2 on WBIE 0 in WRBS1
Iub physical port outgoing from NodeB1
Links 2, 3 and 4 on NDTI 22
RNC-NodeB1 signalling links in control

plane
Refer to Table 7-4
RNC-NodeB1 channels in user plane
Refer to Table 7-5
Table 7-4 lists the data negotiation and planning for RNC-NodeB1 SAAL links in the
control plane. The NodeB Control Port (NCP) and Access Link Control Application Part
(ALCAP) respectively occupy one SAAL link. The Common Communication Ports
(CCPs) occupy six SAAL links. Where, the dash area shows the data planning inside
the RNC and the non-dash area shows the data negotiated between the RNC and
NodeB1. The Automatic Protection Switching (APS) function is disabled.
Table 7-4 Data negotiation and planning for RNC-NodeB1 signalling links in control plane
Terminating
SAAL
WSPU
link
subsystem
No.
No.
SAAL
PCR SCR
Terminating
Service
Traffic description
VPI VCI
link
WRBS No.
type
(kbps)
(kbps)
usage
NCP
RTVBR NOCLPNOSCRCDVT 84
80
32 1
30
CCP 0 RTVBR NOCLPNOSCRCDVT 84
80
33 1
31
80
34 1
32
80
35 1
33
80
36 1
34
80
37 1
35
80
38 1
36
ALCAP RTVBR NOCLPNOSCRCDVT 84
80
39 1
37
7-5
Chapter 7
Table 7-5 lists the data negotiation and planning for RNC-NodeB1 channels in the user
area shows the data negotiated between the RNC and NodeB1.
Table 7-5 Data negotiation and planning for RNC-NodeB1 channels in user plane
From
WRB
S No.
WSPU
subsyste
m No.
40
RNC
41
RNC
750
42
RNC
780
750
43
RNC
NOCLPNOSCRCDVT
780
750
44
RNC
NOCLPNOSCRCDVT
780
750
45
RNC
AAL2
PATH
ID
Service
type
Traffic description
RTVBR
PCR
(kbps)
SCR
(kbps)
NOCLPNOSCRCDVT
780
750
RTVBR
NOCLPNOSCRCDVT
780
750
RTVBR
NOCLPNOSCRCDVT
780
RTVBR
NOCLPNOSCRCDVT
RTVBR
RTVBR
VPI
VCI
7.3.2 Configuring RNC-NodeB1 Interconnection Data on RNC

//Set the attributes of E1/T1 links on the WBIE.
SET E1T1: SRN=1, SN=0, PT=WBIE_EPORT, LS=ALL, LNKT=E1_CRC4_MULTI_FRAME,
LNKCODE=HDB3;
//Set the scrambling switches of E1/T1 links on the WBIE.

SET SCRAMBLE: SRN=1, SN=0, PT=ALL, SCRAMBLESW=ON;
//Add an IMA group. The IMA ID is 0, IMA group No. is 0, and the other parameters
adopt the default values.
ADD
IMAGRP:
SRN=1,
SN=0,
IMAGRPN=0,
IMAID=0,
MINLNKNUM=1,
TXFRAMELEN=D128, IMAVER=VER1.1;
//Add three IMA links into IMA group 0. The link numbers are 0, 1, and 2.
ADD IMALNK: SRN=1, SN=0, IMAGRPN=0, IMALNKN=0;

//Add an ATM traffic record for an SAAL link over the Iub interface. The traffic record
configured here.
ADD ATMTRF: TRFX=110, ST=RTVBR, TRFD=CLPNOTAGGINGSCRCDVT, UT=KBIT/S,
PCR=84, SCR=80, MBS=1000, CDVT=102400;
7-6
Chapter 7
//Add an ATM traffic record for an AAL2 PATH over the Iub interface. The traffic record
configured here.
PCR=780, SCR=750, MBS=1000, CDVT=102400;

//Add SAAL links. These links are terminated at WSPU subsystem 0 of WRBS1.
ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=30, CARRYSR=LOCAL, ENBAPSF=OFF,
CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
IV. Configuring NodeB1 Port

//Add the NodeB1.
ADD NODEB: NODEBNAME="NodeB1", SRN=1, SSN=0;
//Add an NCP link.

ADD NCP: NODEBNAME="NodeB1", SAALLNKN=30;
//Add CCP links with port numbers of 0 to 5.

ADD CCP: NODEBNAME="NodeB1", PN=0, SAALLNKN=31;
7-7
SAALLNKT=UNI,
Chapter 7

V. Configuring ALCAP Adjacent Node

//Add an ALCAP adjacent node, that is, the NodeB1. The adjacent node ID is 11 and
the interface type is Iub.
ADD AAL2ADJNODE: ANI=11, ANT=IUB, NODEBNAME="NodeB1", SAALLNKN=37,
NAME="NodeB1";
VI. Configuring AAL2 PATH

//Add AAL2 PATHs to the ALCAP adjacent node, that is, the NodeB1. The PATH IDs
are 16.
ADD AAL2PATH: ANI=11, PATHID=1, ENDSRN=1, ENDSN=0, CARRYSR=LOCAL,
CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL, CARRYSN=0, CARRYVPI=6, CARRYVCI=40;

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
VII. Configuring AAL2 Route

//Add an AAL2 route to the NodeB1.
ADD AAL2RT: NSAP= H 45000086100101010F0000000000000000000000, ANI=11,
7-8
Chapter 7
7.3.3 Configuring RNC-NodeB1 Interconnection Data on NodeB1

I. Selecting a Configuration Template
1)
In the Configuration Management System of the NodeB1, select [File/New By

Template].
2)
Select the template 2-antenna_3_2_Transmitter Non-diversity_no backup.xml.
3)
Click <OK>.
II. Configuring an IMA Group and IMA Links

1)
Right-click [Transmission Object Tree / IMA Group Set] in [MIT Navigation Tree]
and then click [Add IMA Group] on the shortcut menu. The [Add IMA Group] dialog
box is displayed, as shown in Figure 7-4.
2)
Set [IMA Group No.] to IMA Group 0.
3)
Click <OK> to complete the addition of this IMA group.
Figure 7-4 Adding an IMA group

4)
Right-click [Transmission Object Tree / IMA Group Set / Master Cabinet Baseband
Subrack No.22 NDTI Board IMA Group 0] and then click [Add IMA Link] on the
shortcut menu. The [Add IMA Link] dialog box is displayed, as shown in Figure
7-5.
5)
Set [IMA Link No.] to IMA Link 2.
6)
Click <OK> to complete the addition of an IMA link.
7-9
Chapter 7
Figure 7-5 Adding an IMA link

7)
Repeat steps 4)6) twice to add IMA links 3 and 4.
III. Modifying ALCAP Properties

1)
Right-click [Transmission Object Tree / ALCAP Set / Master Cabinet ALCAP] and
then click [Modify ALCAP] on the shortcut menu. The [Modify Master Cabinet
ALCAP Properties] dialog box is displayed, as shown in Figure 7-6.
2)
Select the [Basic Properties] tab.
3)
Enter the data planned in section 7.3.1 .
7-10
Chapter 7
Figure 7-6 Modifying basic properties of master cabinet ALCAP

4)
Select the [Virtual Port] tab.
5)
Enter the data planned in section 7.3.1 , as shown in Figure 7-7.
7-11
Chapter 7
Figure 7-7 Modifying virtual port properties of master cabinet ALCAP

6)
Click <OK> to complete the modification of ALCAP properties.
IV. Modifying AAL2 PATH Properties

1)
Right-click [Transmission Object Tree / ALCAP Set / Master Cabinet ALCAP /

No.1 AAL2 Path] and then click [Modify AAL2 Path] on the shortcut menu. The
[Modify Master Cabinet ALCAP No.1 AAL2 Path Properties] dialog box is
displayed, as shown in Figure 7-8.
2)
3)
7-12
Chapter 7
Figure 7-8 Modifying basic properties of master cabinet ALCAP No.1 AAL2 PATH
4)
5)
Figure 7-9 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH
7-13
Chapter 7
6)
Click <OK> to complete the modification of No.1 AAL2 PATH properties.
7)
Repeat steps 1)6) to modify the properties of AAL2 PATHs 26.
V. Modifying NCP Properties

1)
Right-click [Transmission Object Tree / NCP Set / NCP] and then click [Modify
NCP] on the shortcut menu. The [Modify NCP Properties] dialog box is displayed,
as shown in Figure 7-10.
2)
3)
Figure 7-10 Modifying basic properties of NCP

4)
5)
Enter the data planned in section 7.3.1 as shown in Figure 7-11.
7-14
Chapter 7
Figure 7-11 Modifying virtual port properties of NCP

6)
Click <OK> to complete the modification of NCP properties.
VI. Modifying CCP Properties

1)
Right-click [Transmission Object Tree / CCP Set / No.0 CCP] and then click
[Modify CCP] on the shortcut menu. The [Modify No.0 CCP Properties] dialog box
is displayed, as shown in Figure 7-12.
2)
3)
7-15
Chapter 7
Figure 7-12 Modifying basic properties of CCP

4)
5)
7-16
Chapter 7
Figure 7-13 Modifying virtual port properties of CCP

6)
Click <OK> to complete the modification of No.0 CCP properties.
7)
Repeat steps 1)6) to modify the properties of CCPs 1-5.
VII. Saving the Configuration File

1)
Select [File/Save]. The [Save] dialog box is displayed.
2)
Enter the configuration file name and select .mdb as the file type.
3)
Click <Save> to save the NodeB1 configuration file.
7.3.4 Checking RNC-NodeB1 Interconnection Data

It is recommended to check the configuration data after configuring cell data.

As shown in Figure 7-14, the RNC and NodeB2 are connected to the SDH transmission
network by ADMs. They adopt 1:1 Multiplex Section Protection (MSP) mode.
7-17
Chapter 7
The RNC and NodeB2 adopt the E1/T1 over SDH mode for networking. The RNC uses
the WOSE interface boards in slots 0 and 15 while the NodeB2 uses the NDTI interface
boards.
E1 over
SDH(1:1 MSP)
E1/T1
ADM
SDH
ADM
NodeB2
RNC
Note:
z
If the RNC is near the NodeB2, as both in the same equipment room, you can use an ADM to connect
them directly.
The 1:1 MSP mode adopted between the RNC and ADM belongs to physical transmission backup.
You can configure it by just specifying the backup mode when adding a WRBS during the configuration
of RNC basic data.

The following table gives a planning example of RNC-NodeB2 interconnection data.
Item
Data planning
Cell
4-antenna, 3 sectors x 1 frequency
0x45000086100101011F0000000000000000000000
Cable
The Iub interface adopts 2 E1/T1 trunk cables

belonging to an IMA group
Links 0 and 1 on WOSE 0 in WRBS3
Links 3 and 4 on NDTI 22

plane
Refer to Table 7-7
Refer to Table 7-8
control plane. The NCP and ALCAP respectively occupy one SAAL link. The CCPs
occupy three SAAL links. Where, the dash area shows the data planning inside the
7-18
Chapter 7
RNC and the non-dash area shows the data negotiated between the RNC and NodeB2.
The APS function is disabled.
(kbps)
V
P VCI
I
Terminating
WRBS No.
Terminating
WSPU
subsystem
No.
SAAL
link No.
84
80
6 32
30
NOCLPNOSCRCDVT
84
80
6 33
31
RTVBR
NOCLPNOSCRCDVT
84
80
6 34
32
CCP 2
RTVBR
NOCLPNOSCRCDVT
84
80
6 35
33
ALCAP
RTVBR
NOCLPNOSCRCDVT
84
80
6 36
34
SAAL
link
usage
Service
type
Traffic description
NCP
RTVBR
CCP 0
PCR
SCR
(kbps)
NOCLPNOSCRCDVT
RTVBR
CCP 1
area shows the data negotiated between the RNC and NodeB2.
AAL2
PATH
ID
Service
type
Traffic description
RTVBR
2
3
From
WRBS
No.
WSPU
subsystem
No.
40
RNC
41
RNC
42
RNC
PCR
(kbps)
SCR
(kbps)
NOCLPNOSCRCDVT
780
750
RTVBR
NOCLPNOSCRCDVT
780
750
RTVBR
NOCLPNOSCRCDVT
780
750
VPI
VCI
Note:
For an E1/T1 link, the link numbers might be different in transmission equipment and
Huawei RNC/NodeB. Therefore, pay attention to the link numbering during
configuration. For the relationships of link numbers between the RNC WOSE and
transmission equipment, refer to HUAWEI BSC6800 WCDMA Radio Network
Controller Operation Manual Data Configuration.
Figure 7-15 illustrates the relationships of link numbering in this example.
7-19
Chapter 7
SDH
E1/T1
E1/T1 over SDH
4
SDH
E1/T1
E1/T1 over SDH
ADM
NDTI
WOSE
ADM
Figure 7-15 E1/T1 link numbering relationship

//Set the attributes of E1/T1 links on the WOSE.
SET E1T1: SRN=3, SN=0, PT=WOSE_OPORT, LNKT=E1_CRC4_MULTI_FRAME;
//Set the scramble switches of E1/T1 links on the WOSE.

//Add an IMA group. The IMA ID is 0, IMA group No. is 0, and the other parameters
adopt the default values.
ADD
IMAGRP:
SRN=3,
SN=0,
IMAGRPN=0,
IMAID=0,
MINLNKNUM=1,
TXFRAMELEN=D128, IMAVER=VER1.1;
//Add two IMA links into IMA group 0. The link IDs are 0 and 1.

configured here.
PCR=84, SCR=80, MBS=1000, CDVT=102400;
configured here.
PCR=780, SCR=750, MBS=1000, CDVT=102400;
7-20
Chapter 7

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

//Add the NodeB2.
//Add an NCP link.



NAME="NodeB2";

//Add AAL2 PATHs to the ALCAP adjacent node, that is, the NodeB2. The AAL2 PATH
IDs are 1 to 3.
CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
7-21
CONTROLSSN=0,
Chapter 7

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

ADD AAL2RT: NSAP= H 45000086100101011F0000000000000000000000, ANI=12,

1)

Template].
2)
3)
Click <OK>.
II. Configuring an IMA Group and IMA Links

1)
2)
Set [IMA Group No.] to IMA Group 0.
3)
Click <OK> to complete the addition of this IMA group.
7-22
Chapter 7

4)
7-17.
5)
Set [IMA Link No.] to IMA Link 3.
6)
Click <OK> to complete the addition of an IMA link.
7-23
Chapter 7

7)
Repeat steps 4)6) to add IMA link 4.

1)
2)
3)
7-24
Chapter 7

4)
5)
Enter the data planned in section7.4.1 , as shown in Figure 7-19.

7-25
6)
Chapter 7

1)

2)
3)
4)
5)
7-26
Chapter 7
6)
7)
Repeat steps 1)6) twice to modify the properties of AAL2 PATHs 2 and 3.

1)
2)
3)
7-27
Chapter 7

4)
5)
7-28
Chapter 7

6)

1)
2)
3)
7-29
Chapter 7

4)
5)
Enter the data planned in section 7.4.1 as shown in Figure 7-25.
7-30
Chapter 7

6)
7)
Repeat steps 1)6) twice to modify the properties of CCPs 1 and 2.

1)
2)
3)


As shown in Figure 7-26, the RNC and NodeB2 are connected to the SDH transmission
network by ADMs. The RNC and NodeB2 adopt the E1/T1 over SDH mode for
connection. The NodeB3 and NodeB2 are connected with each other through E1/T1
trunk cable.
7-31
Chapter 7
The RNC and NodeB3 communicate with each other through the networking PVC
provided by the NodeB2. The RNC adopts the WOSE interface board; the NodeB3 and
NodeB2 adopt the NDTI interface board.
Therefore, besides configuring the interconnection data on the NodeB3, you need to
configure the networking PVC on the NodeB2.
E1/T1
E1/T1
NodeB3
E1 over
SDH(1:1 MSP)
ADM
SDH
ADM
NodeB2
RNC

Item
Data planning
Cell
2 antenna, 1 sector x 1 frequency
H45000086100101012F0000000000000000000000
Cable
One E1/T1 trunk cable is adopted between the NodeB2

and NodeB3 and configured as a UNI link. Two E1/T1
links are used between the RNC and NodeB2 and
configured in an IMA group. That is, the RNC and
NodeB2 employ the same IMA group for bearing.
Links 0 and 1 on WOSE 0 of WRBS3
Link 7 on NDTI 22
Physical port between NodeB2 and RNC
Physical port between NodeB2 and NodeB3
Link 7 on NDTI 22

plane
Refer to Table 7-10
Refer to Table 7-11

The bandwidth configured for the NodeB3 on the
NodeB2 at least is calculated as follows:
Number of SAAL links x SAAL link bandwidth + Number
of AAL2 PATHs x AAL2 PATH bandwidth = 3 84 + 1
780 = 1032 kbps
Bandwidth for NodeB3
Therefore, configure the NodeB3 with the bandwidth of

1300 kbps
7-32
Chapter 7
Note:
The sum of the bandwidth configured for the lower level NodeB and the bandwidth configured for other
links on the NodeB2 cannot exceed the total bandwidth of the physical links between the NodeB2 and
RNC.
control plane. The NCP, ALCAP, and CCP respectively occupy one SAAL link. Where,
the dash area shows the data planning inside the RNC and the non-dash area shows
the data negotiated between the RNC and NodeB. The APS function is disabled.
SAAL
link
usage
Service
type
Traffic description
PCR
SCR
(kbps)
(kbps)
V
P
VCI
Terminating
WSPU
subsystem
Terminating
WRBS No.
No.
SAAL
link
No.
NCP
RTVBR
NOCLPNOSCRCDVT
84
80
32
35
CCP 0
RTVBR
NOCLPNOSCRCDVT
84
80
33
36
ALCAP
RTVBR
NOCLPNOSCRCDVT
84
80
34
37
area shows the data negotiated between the RNC and NodeB.
AAL2
PATH
ID
Service
type
Traffic description
RTVBR
NOCLPNOSCRCDVT
PCR
(kbps)
780
SCR
(kbps)
750
V
P
VCI
From
40
RNC
I
7
WRBS
No.
3
WSPU
subsystem
No.
0

//There is no need to configure the physical layer. The RNC and NodeB2 employ the
same IMA group.
7-33
Chapter 7

configured here.
PCR=84, SCR=80, MBS=1000, CDVT=102400;
configured here.
PCR=780, SCR=750, MBS=1000, CDVT=102400;

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=110,
RXTRFX=110,
SAALLNKT=UNI,

//Add the NodeB3.
//Add an NCP link.

//Add a CCP link with port number of 0.


NAME="NodeB3";
7-34
Chapter 7

//Add an AAL2 PATH to the ALCAP adjacent node, that is, the NodeB3. The AAL2
PATH ID is 1.
CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,

ADD AAL2RT: NSAP=H45000086100101012F0000000000000000000000, ANI=13,

1)

Template].
2)
3)
Click <OK>.
II. Modifying ALCAP Properties

1)
2)
3)
7-35
Chapter 7

4)
5)
7-36
Chapter 7

6)
III. Modifying AAL2 PATH Properties

1)

2)
3)
7-37
Chapter 7
4)
5)
7-38
6)
Chapter 7
IV. Modifying NCP Properties

1)
2)
3)

4)
5)
7-39
Chapter 7

6)
V. Modifying CCP Properties

1)
2)
3)
7-40
Chapter 7

4)
5)
7-41
Chapter 7

6)
VI. Saving the Configuration File

1)
2)
3)

I. Modifying the VPI Range
1)
Log in to the Configuration Management System of the NodeB2.
2)
Open the NodeB2 configuration file.
3)
Right-click [Physical Object Tree / Master Cabinet / Baseband Subrack / No.22

NDTI Board] and then click [Modify NDTI Board] on the shortcut menu. The
[Modify Master Cabinet Baseband Subrack No.22 NDTI Board Properties] is
4)
Select the [VPI Range] tab.
5)
Modify the max VPI to 6.
7-42
Chapter 7
Figure 7-35 Modifying the VPI range of master cabinet baseband subrack No.22 NDTI board
6)
Click <OK> to complete the modification of the VPI range.
II. Configuring the Networking PVC

1)
Right-click [Transmission Object Tree / Treelink PVC Set] in [MIT Navigation Tree]
and then click [Add Treelink PVC] on the shortcut menu. The [Add Treelink PVC]
dialog box is displayed, as shown in Figure 7-36.
2)
3)
7-43
Chapter 7
Figure 7-36 Adding basic properties of the networking PVC

4)
Select the [Source Port] tab.
5)
Enter the data planned in sectio7.5.1 , as shown in Figure 7-37.
7-44
Chapter 7
Figure 7-37 Adding the source port of the networking PVC

6)
Select the [Destination Port] tab.
7)
7-45
Chapter 7
Figure 7-38 Adding the destination port of the networking PVC

8)
Click <OK> to complete the addition of the networking PVC.
III. Saving the Configuration File

Select [File/Save] to save the configuration file.


As shown in Figure 7-39, the RNC and NodeB4 are connected with each other through
the SDH transmission network.
The RNC and NodeB4 adopt the ATM over SDH mode for networking. The RNC adopts
the WLPU interface board while the NodeB4 adopts the NAOI interface board.
7-46
Chapter 7
SDH
SDH
SDH
NodeB4
RNC
Note:
If the RNC is near the NodeB4, as both in the same equipment room, you can use optical fiber to connect
them directly.

Item
Data planning
Cell
4 antenna, 3 sectors x 1 frequency
H45000086100101013F0000000000000000000000
Optical port 7 on WLPU 2 of the WRSS
Optical port 0 on NAOI 23

plane
Refer to Table 7-13
Refer to Table 7-14
RNC and the non-dash area shows the data negotiated between the RNC and NodeB.
SAAL
link
usage
Service
type
Traffic description
NCP
RTVBR
NOCLPNOSCRCDVT
PCR
SCR
(kbps)
(kbps)
84
80
7-47
V
P
VCI
Terminating
WRBS No.
Terminating
WSPU
subsystem.
SAAL
link
No.
32
37
I
6
SAAL
link
usage
Service
type
Traffic description
CCP 0
RTVBR
CCP 1
Chapter 7
V
VCI
Terminating
WRBS No.
Terminating
WSPU
subsystem.
SAAL
link
No.
33
38
80
34
39
84
80
35
40
84
80
36
41
PCR
SCR
(kbps)
(kbps)
NOCLPNOSCRCDVT
84
80
RTVBR
NOCLPNOSCRCDVT
84
CCP 2
RTVBR
NOCLPNOSCRCDVT
ALCA
P
RTVBR
NOCLPNOSCRCDVT
P
I
Table 7-14 lists the data negotiation and planning for RNC-NodeB4 channels in the
non-dash area shows the data negotiated between the RNC and NodeB.
AAL2
PATH
ID
WSPU
subsystem
No.
PCR
SCR
(kbps)
(kbps)
NOCLPNOSCRCDVT
780
750
40
RNC
RTVBR
NOCLPNOSCRCDVT
780
750
41
RNC
RTVBR
NOCLPNOSCRCDVT
780
750
42
RNC
Service
type
Traffic description
RTVBR
2
3
VCI
From .
WRBS
No.

SET OPT: OPT=SDH;
//Set the type of optical port 7 on the WLPU in slot 2 to STM-1.


configured here.
PCR=84, SCR=80, MBS=1000, CDVT=102400;
7-48
Chapter 7
configured here.
PCR=780, SCR=750, MBS=1000, CDVT=102400;

ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=37,
SAALLNKT=UNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=6,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=38,
SAALLNKT=UNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=6,
CARRYVCI=33;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=39,
SAALLNKT=UNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=6,
CARRYVCI=34;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=40,
SAALLNKT=UNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=6,
CARRYVCI=35;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=41,
SAALLNKT=UNI,
CARRYSR=WRSS,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=6,
CARRYVCI=36;

//Add the NodeB4.
//Add an NCP link.



NAME="NodeB4";
7-49
Chapter 7

//Add AAL2 PATHs to the ALCAP adjacent node, that is, the NodeB4. The PATH IDs
are 13.
ADD
AAL2PATH:
CARRYPN=7,
ANI=14,
TXTRFX=111,
PATHID=1,
ENDSRN=1,
RXTRFX=111,
ENDSN=0,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=7,
ANI=14,
TXTRFX=111,
PATHID=2,
ENDSRN=1,
RXTRFX=111,
ENDSN=0,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=7,
ANI=14,
TXTRFX=111,
PATHID=3,
ENDSRN=1,
RXTRFX=111,
ENDSN=0,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,


1)

Template].
2)
3)
Click <OK>.
II. Configuring the NAOI

1)
Right-click [Physical Object Tree / Master Cabinet / Baseband Subrack] and then
click [Add NAOI Board] on the shortcut menu. The [Add NAOI Board] dialog box is
2)
3)
Set [Slot No.] to No.22.
7-50
Chapter 7
Figure 7-40 Adding the NAOI board

4)
Click <OK> to complete the addition of the NAOI.

1)
2)
3)
Enter the ALCAP data planned in section 7.6.1 .
7-51
Chapter 7

4)
5)
Enter the ALCAP data planned in section 7.6.1 , as shown in Figure 7-42.
7-52
Chapter 7

6)

1)

2)
3)
Enter the ALL2 PATH data planned in section 7.6.1 .
7-53
Chapter 7
4)
5)
Enter the AAL2 PATH data planned in section 7.6.1 , as shown in Figure 7-44.
6)

7-54
7)
Chapter 7

1)
2)
3)

4)
5)
7-55
Chapter 7

6)

1)
[Modify CCP] on the shortcut menu. The [Modify NCP Properties] dialog box is
2)
3)
7-56
Chapter 7

4)
5)

7-57
Chapter 7
6)
7)

1)
2)
3)


the SDH transmission network. The RNC and NodeB4 adopt the ATM over SDH mode
for networking. The NodeB5 and NodeB4 are connected with each other through E1/T1
trunk cable.
The RNC and NodeB5 communicate with each other through the networking PVC
provided by the NodeB4. The RNC adopts the WLPU; the NodeB5 adopts the NDTI;
and the NodeB4 adopts the NAOI and NDTI interface boards.
Therefore, besides configuring the interconnection data on the NodeB5, you need to
configure the networking PVC on the NodeB4.
E1/T1
NodeB5
SDH
SDH
SDH
NodeB4
RNC

Item
Data planning
Cell
2 antenna, 3 sectors x 1 frequency
H45000086100101014F0000000000000000000000
7-58
Chapter 7
Item
Data planning
Cable
Two E1/T1 trunk cables are adopted between the

NodeB5 and NodeB4 and configured in an IMA group.
The RNC and NodeB4 adopt the ATM over SDH mode
Optical port 7 on WLPU 2 of the WRSS
Physical port outgoing from NodeB4 to

connect to RNC
Optical port 0 on NAOI 23
Physical port outgoing from NodeB4 to

connect to NodeB5

plane
Refer to Table 7-16
Refer to Table 7-17

The bandwidth configured for the NodeB5 on the
NodeB4 at least is calculated as follows:
Number of SAAL links x SAAL link bandwidth + Number
of AAL2 PATHs x AAL2 PATH bandwidth = 5 84 + 3
780 = 2760 kbps.
Bandwidth for NodeB5
Therefore, configure the NodeB5 with the bandwidth of

2800 kbps
Note:
The sum of the bandwidth configured for the lower level NodeB and the bandwidth configured for other
links on the NodeB4 cannot exceed the total bandwidth of the physical links between the NodeB4 and
RNC.
RNC and the non-dash area shows the data negotiated between the RNC and NodeB.
(kbps)
V
P VCI
I
Terminating
WRBS No.
Terminating
WSPU
subsystem
No.
SAAL
link No.
84
80
7 32
42
NOCLPNOSCRCDVT
84
80
7 33
43
NOCLPNOSCRCDVT
84
80
7 34
44
SAAL
link
usage
Service
type
Traffic description
NCP
RTVBR
CCP 0
CCP 1
PCR
SCR
(kbps)
NOCLPNOSCRCDVT
RTVBR
RTVBR
7-59
SAAL
link
usage
Service
type
Traffic description
CCP 2
RTVBR
ALCAP
RTVBR
Chapter 7
(kbps)
V
P VCI
I
Terminating
WRBS No.
Terminating
WSPU
subsystem
No.
SAAL
link No.
84
80
7 35
45
84
80
7 36
46
PCR
SCR
(kbps)
NOCLPNOSCRCDVT
NOCLPNOSCRCDVT
non-dash area shows the data negotiated between the RNC and NodeB.
WSPU
subsystem
No.
PCR
SCR
(kbps)
(kbps)
V
P VCI
I
NOCLPNOSCRCDVT
780
750
7 40
RNC
RTVBR
NOCLPNOSCRCDVT
780
750
7 41
RNC
RTVBR
NOCLPNOSCRCDVT
780
750
7 42
RNC
AAL2
PATH
ID
Service
type
Traffic description
RTVBR
2
3
FROM
WSPU
No.

//Set the type of optical port 7 on the WLPU in slot 2 to STM-1.

configured here.
PCR=84, SCR=80, MBS=1000, CDVT=102400;
configured here.
PCR=780, SCR=750, MBS=1000, CDVT=102400;

7-60
ADD
SAALLNK:
TXTRFX=110,
Chapter 7
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=42,
CARRYSR=WRSS,
SAALLNKT=UNI,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=7,
CARRYVCI=32;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=43,
CARRYSR=WRSS,
SAALLNKT=UNI,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=7,
CARRYVCI=33;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=44,
CARRYSR=WRSS,
SAALLNKT=UNI,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=7,
CARRYVCI=34;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=45,
CARRYSR=WRSS,
SAALLNKT=UNI,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=7,
CARRYVCI=35;
ADD
SAALLNK:
TXTRFX=110,
SRN=1,
SSN=0,
RXTRFX=110,
SAALLNKN=46,
CARRYSR=WRSS,
SAALLNKT=UNI,
CARRYSN=2,
CARRYPN=7,
CARRYVPI=7,
CARRYVCI=36;

//Add the NodeB5.
//Add an NCP link.



NAME="NodeB5";

PATH IDs are 1 to 3.
ADD
AAL2PATH:
CARRYPN=7,
ANI=15,
TXTRFX=111,
PATHID=1,
ENDSRN=1,
RXTRFX=111,
ENDSN=0,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,

ADD
AAL2PATH:
CARRYPN=7,
ANI=15,
TXTRFX=111,
PATHID=2,
ENDSRN=1,
RXTRFX=111,
7-61
ENDSN=0,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,
ADD
AAL2PATH:
CARRYPN=7,
Chapter 7
ANI=15,
TXTRFX=111,
PATHID=3,
ENDSRN=1,
RXTRFX=111,
ENDSN=0,
CONTROLSSN=0,
CARRYSR=WRSS,
OWNERSHIP=LOCAL,


1)

Template].
2)
3)
Click <OK>.
II. Adding an IMA group

1)
2)
Set [NDTI Board No.] to Master Cabinet Baseband Subrack No.22 NDTI Board.
7-62
3)
Chapter 7
7-51.
4)
Set [IMA Link No.] to "IMA Link 6".

5)
Repeat steps 3)4) to add IMA link 4.

1)
2)
3)
7-63
Chapter 7

4)
5)
7-64
Chapter 7

6)

1)

2)
3)
7-65
Chapter 7
4)
5)
6)
7)
7-66
Chapter 7

1)
2)
3)

4)
5)
7-67
Chapter 7

6)

1)
2)
3)
7-68
Chapter 7

4)
5)
7-69
Chapter 7
1
6)
7)

1)
2)
3)

I. Adding an IMA Group
1)
2)
3)
Right-click [Transmission Object Tree / UNI Link Set / Master Cabinet Baseband
Subrack No.22 NDTI Board UNI Link 6] and then click [Delete UNI Link] on the
shortcut menu. A prompt box is displayed.
4)
Click <OK> to delete UNI link 6.
5)
Repeat steps 1)4) to delete UNI link 7.
7-70
6)
Chapter 7
7)
Set [NDTI Board No.] to Master Cabinet Baseband Subrack No.22 NDTI Board.

8)
7-61.
9)
Set [IMA Link No.] to "IMA Link 6".
7-71
Chapter 7

10) Repeat steps 7)9) to add IMA link 7.
II. Modifying the VPI Range

1)

NDTI Board] and then click [Modify NDTI Board] on the shortcut menu. The
[Modify Master Cabinet Baseband Subrack No.22 NDTI Board Properties] is
2)
3)
7-72
Chapter 7
Figure 7-62 Modifying the VPI range of master cabinet baseband subrack No.22 NDTI board
4)
5)

NAOI Board] and then click [Modify NAOI Board] on the shortcut menu. The
[Modify Master Cabinet Baseband Subrack No.23 NAOI Board Properties] is
6)
7)
7-73
Chapter 7
Figure 7-63 Modifying the VPI range of master cabinet baseband subrack No.23 NAOI board
8)
III. Configuring the Networking PVC

1)
Right-click [Transmission Object Tree / Treelink PVC Set] in [MIT Navigation Tree]
and then click [Add Treelink PVC] on the shortcut menu. The [Add Treelink PVC]
dialog box is displayed, as shown in Figure 7-64.
2)
3)
7-74
Chapter 7
.
Figure 7-64 Adding basic properties of the networking PVC
4)
Select the [Source Port] tab.
5)
Figure 7-65 Adding the source port of the networking PVC

7-75
Chapter 7
6)
Select the [Destination Port] tab.
7)
Figure 7-66 Adding the destination port of the networking PVC

8)
Click <OK> to complete the addition of the networking PVC.
IV. Saving the Configuration File

Select [File/Save] to save the NodeB5 configuration file.

the BSS transmission network of 2G GSM. The RNC and 2G BSC adopt E1/T1 trunk
cable for connection and the NodeB6 and 2G BTS adopt E1/T1 trunk cable for
connection.
The 2G BTS and BSC use E1 cable for transmission, occupying a certain number of
timeslots among 32 E1 timeslots. The rest are provided for the NodeB6 and RNC.
The RNC adopts the WBIE interface board while the NodeB6 adopts the NDTI interface
board.
7-76
Chapter 7
RNC
NodeB6
E1/T1
E1/T1
E1/T1
E1/T1
PDH
BTS
BSC

Item
Data planning
Cell
2 antenna, 1 sector x 1 frequency
0x45000086100101015F0000000000000000000000
The BTS and BSC employ one E1 cable for connection,
occupying 11 timeslots, from 6 to 16.
Cable and timeslot
The Iub interface between the NodeB6 and RNC

occupies 20 timeslots, from 1 to 5 and 17 to 31
Link 4 on WBIE 0 of WRBS1
Bearing Port No. 0 on NDTI 22 (Fractional ATM link

No.0)

plane
Refer to Table 7-19
Refer to Table 7-20
Note:
z
If the timeslot numbers used by the NodeB6 are different from those used by the RNC, a timeslot cross
device is required to convert them. The NDTI of NodeB and WBIE of RNC themselves can provide the
timeslot cross function. In this example, the timeslot numbers used by the NodeB and RNC uses are
the same.
For the configurations of 2G BSC and BTS, refer to related documents.
7-77
Chapter 7
control plane. The NCP, ALCAP, and CCP respectively occupy one SAAL link. Where,
the dash area shows the data planning inside the RNC and the non-dash area shows
the data negotiated between the RNC and NodeB. The APS function is disabled.
(kbps)
V
P VCI
I
Terminating
WRBS No.
Terminating
WSPU
subsystem
No.
SAAL
link No.
55
51
6 32
47
NOCLPNOSCRCDVT
55
51
6 33
48
NOCLPNOSCRCDVT
55
51
6 34
49
SAAL
link
usage
Service
type
Traffic description
NCP
RTVBR
CCP 0
ALCAP
PCR
SCR
(kbps)
NOCLPNOSCRCDVT
RTVBR
RTVBR
non-dash area shows the data negotiated between the RNC and NodeB6.
AAL2
PATH
ID
Service
type
Traffic description
RTVBR
NOCLPNOSCRCDVT
PCR
SCR
(kbps)
(kbps)
V
P VCI
I
1115
1100
6 40
From .
RNC
WSPU
No.
1
WSPU
subsystem
No.
0

//Set the attributes of E1/T1 links on the WBIE.
SET E1T1: SRN=1, SN=0, PT=WBIE_EPORT, LS=ALL, LNKT=E1_CRC4_MULTI_FRAME,
LNKCODE=HDB3;
//Set the scrambling switches of E1/T1 links on the WBIE.

//Add a Fractional ATM link. This link occupies link 4 on the WBIE.
ADD
FRALNK:
SRN=1,
SN=0,
BT=WBIE,
E1T1LNKN=4,
TSBITMAP=TS1&TS2&TS3&TS4&TS5&TS17&TS18&TS19&TS20&TS21&TS22&TS23&TS24
&TS25&TS26&TS27&TS28&TS29&TS30&TS31, FRALNKT=FRAATM, FRALNKN=0;
7-78
Chapter 7

//Add an ATM traffic record for an SAAL UNI link over the Iub interface. The traffic
be configured here.
PCR=55, SCR=51, MBS=1000, CDVT=102400;
configured here.
PCR=1115, SCR=1100, MBS=1000, CDVT=102400;

CARRYT=FRAATM, CARRYFRAATMLNKN=0, TXTRFX=112, RXTRFX=112, SAALLNKT=UNI,

//Add the NodeB6.
//Add an NCP link.



NAME="NodeB6";
7-79
Chapter 7

PATH ID is 1.
CARRYT=FRAATM, CARRYFRAATMLNKN=0, TXTRFX=113, RXTRFX=113, CONTROLSSN=0,


1)

Template].
2)
3)
Click <OK>.
II. Add a Fractional ATM link

1)
Right-click [Transmission Object Tree / Fractional ATM Set] in [MIT Navigation

Tree] and then click [Add Fractional ATM] on the shortcut menu. The [Add
Fractional ATM] dialog box is displayed, as shown in Figure 7-68.
2)
Enter the data planned in section 7.8.1 .In the [Basic Properties] tab.
7-80
Chapter 7
Figure 7-68 Adding a Fractional ATM link

3)
Click <OK> to complete the addition of a Fractional ATM link.

1)
2)
3)
Enter the ALCAP data planned in section 7.8.1 .
7-81
Chapter 7

4)
5)
Enter the ALCAP data planned in section 7.8.1 , as shown in Figure 7-70.
7-82
6)
Chapter 7

1)

2)
3)
Enter the ALL2 PATH data planned in section 7.8.1 .
4)
5)
Enter the AAL2 PATH data planned in section 7.8.1 , as shown in Figure 7-72.
7-83
Chapter 7
6)

1)
2)
3)
Enter the NCP data planned in section 7.8.1 .
7-84
Chapter 7

4)
5)
Enter the NCP data planned in section 7.8.1 , as shown in Figure 7-74.

6)

7-85
Chapter 7

1)
2)
3)

4)
5)
Enter the CCP data planned in section 7.8.1 , as shown in Figure 7-76.
7-86
Chapter 7

6)
Click <OK> to complete the modification of CCP properties.

1)
2)
3)

7-87
Chapter 8
Cell and Neighboring Cell Data Configuration
Chapter 8 Cell and Neighboring Cell Data

Configuration
8.1 Overview
Configuring cell data is to configure the data of both logical cell and local cell on the
RNC and NodeB.
Configuring neighboring cell data is to configure the neighboring cells of a cell on the
NodeB.
These
neighboring
cells
include
intra-frequency
neighboring
cell,
inter-frequency neighboring cell, concentric inter-frequency neighboring cell, and

inter-RAT neighboring cell.

As the cell data need be configured on both the RNC and NodeB, before data
configuration the RNC and NodeB must satisfy the following conditions:
z
RNC basic data must be configured. For the configuration, refer to Chapter 2.
RNC-NodeB interconnection data must be configured. This chapter uses the

interconnection data configured in Chapter 7.
For the convenience of introduction, this chapter takes one type of NodeB model,
BTS3812, as an example.
8.1.3 Configuration Tasks

This chapter introduces the following configuration tasks:
z
Cell Data Configuration
Intra-Frequency Neighboring Cell Data Configuration
Inter-Frequency Neighboring Cell Data Configuration
Concentric Inter-Frequency Neighboring Cell Data Configuration
Inter-RAT Neighboring Cell Data Configuration
8.2 Cell Data Configuration

8.2.1 Planning Cell Data
This section introduces the data planning for all the cells of the NodeB1 whose
inter-connection data with RNC has been configured in chapter 7.
8-1
Chapter 8
Sector 2
Sector 1
Sector 0
Frequency 2
Frequency 1
Figure 8-1 NodeB1 cell planning (3x2)

z
Logical cell IDs
According to radio network planning, the cell of NodeB1 is configured as 3 sectors x 2

frequencies as shown in Figure 8-1.
Table 8-1 lists the planned logical cell IDs
Table 8-1 Logical cell IDs
Sector 0
Sector 1
Sector 2
Frequency 1
Frequency 2
Physical resources
The following gives the physical resources used by the sectors, which are determined
by NodeB antenna directions.
- Resources used by section 0: NDDL0 (slot 0), NTRX0 (slot 2), NTRX1 (slot 3), NLPA0
(slot 0), and NLPA1 (slot 1).
- Resources used by section 1: NDDL2 (slot 7), NTRX4 (slot 8), NTRX5 (slot 9), NLPA2
(slot 2), and NLPA3 (slot 3).
- Resources used by section 2: NDDL4 (slot 13), NTRX8 (slot 14), NTRX9 (slot 15),
NLPA4 (slot 4), and NLPA5 (slot 5).
Figure 8-2 shows the physical resources used by these sectors:
8-2
Chapter 8
Sector 0
Sector 1
Sector 0
N
T
R
X
0
N
T
R
X
1
3 4 5
Sector2
Sector 1
N
D
D
L
0
N
L
P
A
0
Sector 2
N
T
R
X
4
N
D
D
L
2
6
N
T
R
X
5
N
D
D
L
4
8 9 10 11
12
N
T
R
X
8
N
T
R
X
9
13 14 15 16 17
N
L
P
A
1
N
L
P
A
2
N
L
P
A
3
N
L
P
A
4
N
L
P
A
5
18
19
Figure 8-2 Physical resource planning

Cell basic properties
Table 8-2 lists the basic properties planned for the cells.
Table 8-2 Basic properties of logical cells
Logical
Cell ID
Local
Cell
ID
BTS3812
Half
subrack
resource
pool
Left half
subrack
RD/TD*
mode
DL
frequency
(2-way)
(MHz)
Receiver
diversity;
transmit
8-3
2120
UL
frequency
(MHz)
DL
primary
scramble
Time
offset
(chip)
1930
256
Logical
Cell ID
Local
Cell
ID
4
5
Chapter 8
BTS3812
Half
subrack
resource
pool
RD/TD*
mode
DL
frequency
(2-way)
(MHz)
UL
frequency
(MHz)
DL
primary
scramble
non-diver
sity
Time
offset
(chip)
512
256
512
2115
1925
RD/TD*: Receive Diversity and Transmit Diversity
Radius of each cell: 1000 m
Handover radius of each cell: 150 m
Channel specifications of logical cells 03
Table 8-3 lists the channel specifications of logical cells 03. These specifications are
the default ones for quick cell setup, and the power values of logical cells 02 also
adopt default ones.
Table 8-3 Channel specifications of logical cells 03
Common
physical
channel ID
Command
physical
channel name
Common
transport
channel ID
Common
transport
channel name
Common
physical
channel ID
Command
physical
channel
name
PRACH
RACH
AICH
SCCPCH#1
FACH (signalling)
--
--
FACH (traffic)
--
--
PCH
10
PICH
Common
physical
channel ID
Command
physical
channel
name
Channel specifications of logical cell 4
Table 8-4 lists the channel specifications of logical cell 4.

Table 8-4 Channel specifications of logical cell 4
Common
physical
channel
ID
Command
physical channel
name
Common
transport
channel ID
PRACH
RACH
AICH
SCCPCH#1
FACH
(signalling)
--
--
FACH (service)
--
--
8-4
Common
transport
channel name
Common
physical
channel
ID
Chapter 8
Command
physical channel
name
Common
transport
channel ID
SCCPCH#2
Common
transport
channel name
Common
physical
channel ID
Command
physical
channel
name
PCH
10
PICH
FACH
(signalling)
--
--
FACH (service)
--
--
Channel specifications of logical cell 5
Table 8-5 lists the channel specifications of logical cell 5.

Table 8-5 Channel specifications of logical cell 5
Common
physical
channel ID
Command
physical
channel name
Common
transport
channel ID
Common
transport
channel name
Common
physical
channel ID
Command
physical
channel
name
PRACH
RACH
AICH
PRACH
RACH
AICH
SCCPCH#1
FACH (signalling)
--
--
FACH (traffic)
--
--
PCH
10
PICH
Power planning for logical cell 3
Maximum transmit power: 46 dBm

PCIPCH transmit power: 36 dBm
8.2.2 Configuring Logical Cell Data on RNC

I. Configuring Logical Cell 0
//Set up logical cell 0 quickly.
ADD
QUICKCELLSETUP:
UARFCNDOWNLINK=10600,
CELLID=0,
CELLNAME="Cell0",
PSCRAMBCODE=0,
UARFCNUPLINK=9650,
TCELL=CHIP0,
LAC=H'0001,
SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, URANUM=D2, URA1=0, URA2=1,

NODEBNAME="NodeB1",
LOCELL=0,
PCPICHPOWER=330;
II. Configuring Logical Cell 1

8-5
SUPBMC=FALSE,
MAXTXPOWER=430,
ADD
QUICKCELLSETUP:
Chapter 8
CELLID=1,
CELLNAME="Cell1",
PSCRAMBCODE=1,
UARFCNUPLINK=9650,
TCELL=CHIP256,
LAC=H'0001,

NODEBNAME="NodeB1",
LOCELL=1,
SUPBMC=FALSE,
MAXTXPOWER=430,
CELLNAME="Cell2",
UARFCNUPLINK=9650,
PCPICHPOWER=330;
III. Configuring Logical Cell 2

ADD
QUICKCELLSETUP:
CELLID=2,
PSCRAMBCODE=2,
TCELL=CHIP512,
LAC=H'0001,

NODEBNAME="NodeB1",
LOCELL=2,
SUPBMC=FALSE,
MAXTXPOWER=430,
CELLNAME="Cell3",
UARFCNUPLINK=9625,
PCPICHPOWER=330;
IV. Configuring Logical Cell 3

ADD
QUICKCELLSETUP:
CELLID=3,
PSCRAMBCODE=3,
TCELL=CHIP0,
LAC=H'0001,

NODEBNAME="NodeB1",
LOCELL=3,
SUPBMC=FALSE,
MAXTXPOWER=430,
PCPICHPOWER=330;
MOD CELL: CELLID=3; MAXTXPOWER=460, PCPICHPOWER=360;
V. Configuring Logical Cell 4

ADD
QUICKCELLSETUP:
CELLID=4,
CELLNAME="Cell4",
PSCRAMBCODE=4,
UARFCNUPLINK=9625,
TCELL=CHIP256,
LAC=H'0001,

NODEBNAME="NodeB1",
LOCELL=4,
SUPBMC=FALSE,
MAXTXPOWER=430,
PCPICHPOWER=330;
//Add basic information for SCCPCH 9 (that is, SCCPCH#2).

ADD SCCPCHBASIC: CELLID=4, PHYCHID=9, SCCPCHOFFSET=50, SCRAMBCODE=0,
STTDIND=FALSE,
PO1=8,
PILOTSYMBOLEXIST=NOT_EXISTS,
PO3=12,
CTFCSIZE=BIT4,
SLOTFORMAT=D8,
TFCIPRESENCE=EXISTS,
MULTIPLEXPOS=FLEXIBLE;
//Add Calculated Transport Format Combination (CTFC) information. The transport

formats of FACH 6 are 0x168, 1x168, and 2x168. The transport formats of FACH 7 are
0 x 360, and 1x 360. The CTFCs are 0, 1, 2, 3, 4, and 5.
ADD SCCPCHTFC: CELLID=4, PHYCHID=9, CTFC=0;
8-6
Chapter 8

//Add FACH 6.
ADD FACH: CELLID=4, PHYCHID=9, TRCHID=6, TTI=T10, RATEMATCHINGATTR=220,
CRCSIZE=D16,
TOAWS=20,
TOAWE=10,
MAXFACHPOWER=-10,
CMCHPI=D14,
CHCODINGTYPE=CONVOLUTIONAL, CODINGRATE=D1/2;
ADD
FACHDYNTFS:
CELLID=4,
TRCHID=6,
RLCSIZE=168,
TFSNUMBER=D3,
LOCHLISTCHOICE=ALL, TBNUMBER1=0, TBNUMBER2=1, TBNUMBER3=2;

ADD FACHLOCH: CELLID=4, TRCHID=6, SDUDISCARDTIMER=T10, MAXPDUSIZE=20;
//Add FACH 7.
ADD FACH: CELLID=4, PHYCHID=9, TRCHID=7, TTI=T10, RATEMATCHINGATTR=160,
CRCSIZE=D16,
TOAWS=30,
TOAWE=10,
MAXFACHPOWER=-10,
CMCHPI=D0,
CHCODINGTYPE=TURBO;
ADD
FACHDYNTFS:
CELLID=4,
TRCHID=7,
RLCSIZE=360,
TFSNUMBER=D2,
LOCHLISTCHOICE=ALL, TBNUMBER1=0, TBNUMBER2=1;
//Activate SCCPCH 9.
ACT SCCPCH: CELLID=4, PHYCHID=9;
VI. Configuring Logical Cell 5

ADD
QUICKCELLSETUP:
CELLID=5,
CELLNAME="Cell5",
PSCRAMBCODE=5,
UARFCNUPLINK=9625,
TCELL=CHIP512,
LAC=H'0001,

NODEBNAME="NodeB1",
LOCELL=5,
SUPBMC=FALSE,
MAXTXPOWER=430,
PCPICHPOWER=330;
//Add the basic information for PRACH 5 (that is, PRACH#2).

ADD
PRACHBASIC:
CELLID=5,
PHYCHID=5,
SCRAMBCODENO=0,
PREAMBLESIGNATURES=SIGNATURE0&SIGNATURE1&SIGNATURE2&SIGNATURE3&SIGNA
TURE4&SIGNATURE5&SIGNATURE6&SIGNATURE7,
RACHSUBCHNO=SUBCHANEL0&SUBCHANEL1&SUBCHANEL2&SUBCHANEL3&SUBCHANEL4&S
UBCHANEL5&SUBCHANEL6&SUBCHANEL7&SUBCHANEL8&SUBCHANEL9&SUBCHANEL10&SU
BCHANEL11, PUNCTURELIMIT=100%, PREAMBLETHRESHOLD=40, CONSTANTVALUE=-20,
PREAMBLERETRANSMAX=8, POWERRAMPSTEP=2, CTFCSIZE=BIT2;
//Add the Transport Format Combination Set (TFCS) information for PRACH 5.
ADD
PRACHTFC:
CELLID=5,
PHYCHID=5,
CTFC=0,
POWEROFFSETPPM=0,
CTFC=1,
POWEROFFSETPPM=0,
GAINFACTORBETAC=11, GAINFACTORBETAD=15;
ADD
PRACHTFC:
CELLID=5,
8-7
PHYCHID=5,
Chapter 8
GAINFACTORBETAC=10, GAINFACTORBETAD=15;
//Add the timeslot format information for PRACH 5.

ADD
PRACHSLOTFORMAT:
CELLID=5,
PHYCHID=5,
SLOTFORMATNUM=D4,
SLOTFORMAT1=0, SLOTFORMAT2=1, SLOTFORMAT3=2, SLOTFORMAT4=3;
//Add the Access Service Class (ASC) information for PRACH 5, that is, ASC0 and
ASC1.
ADD
PRACHASC:
CELLID=5,
PHYCHID=5,
AVAILABLESIGNATURESTARTINDEX=0,
ACCESSSERVICECLASS=ASC0,
AVAILABLESIGNATUREENDINDEX=7,
AVAILABLESUBCHANNELNUMBER=15;
ADD
PRACHASC:
CELLID=5,
PHYCHID=5,
AVAILABLESIGNATURESTARTINDEX=0,
ACCESSSERVICECLASS=ASC1,
AVAILABLESIGNATUREENDINDEX=7,
AVAILABLESUBCHANNELNUMBER=15;
//Add the access class to access service class (AC-ASC) mapping information for
PRACH 5.
ADD PRACHACTOASCMAP: CELLID=5, PHYCHID=5, AC09TOASC=1, AC10TOASC=0,
AC11TOASC=0, AC12TOASC=0, AC13TOASC=0, AC14TOASC=0, AC15TOASC=0;
//Add an RACH over PRACH 5.

ADD RACH: CELLID=5, PHYCHID=5, TRCHID=1, TTI=T20, RATEMATCHINGATTR=1,
CRCSIZE=D16, NB01MIN=3, NB01MAX=10, MMAX=2;
//Add the dynamic information of the Transport Format Set (TFS) for PRACH 5.
ADD
RACHDYNTFS:
CELLID=5,
TRCHID=2,
RLCSIZE=168,
TFSNUMBER=D1,
TBNUMBER1=1;
//Add an AICH corresponding to PRACH 5.

ADD
AICH:
CELLID=5,
PRACHPHYCHID=5,
PHYCHID=7,
AICHTXTIMING=1,
STTDIND=FALSE;
//Activate PRACH 5.
ACT PRACH: CELLID=5, PHYCHID=5;
8.2.3 Configuring Local Cell Data on NodeB1

To configure local cell data on the NodeB1, operate as follows:
1)
2)
3)
Right-click [Local Cell Object Tree / Sector 0 / No.0 Local Cell] in [MIT Navigation
Tree] and click [Modify Local Cell] on the shortcut menu. The [Modify Sector 0
No.0 Local Cell Properties] dialog box is displayed, as shown in Figure 8-3.
4)
5)
8-8
Chapter 8
Figure 8-3 Modifying local cell properties

6)
Click <OK> to complete the modification of local cell 0.
7)
Repeat steps 3) to 6) to modify local cells 15.
8)
Select [File/Save] to save the configuration file.
8.2.4 Commissioning Cell Data

Commissioning the cell data on the NodeB1 first and then on the RNC.
I. Commissioning Cell Data on NodeB1

1)
2)
3)
Select [File/Save]. The [Save as] dialog box is displayed.
4)
Enter the configuration file name and select .xml as the file type.
5)
Click <Save>. The system starts data check and download the data to the host of
the NodeB1.
6)
Restart the NodeB1.
II. Commissioning Cell Data on RNC

1)
Activate each cell using the ACT CELL command.
2)
View the setup procedure of each cell by tracing the Iub interface.
3)
Query the availability status of each cell using the DSP CELL command. Normally,
the status is Zero.
8-9
Chapter 8
8.3 Intra-Frequency Neighboring Cell Data Configuration

8.3.1 Planning Intra-Frequency Neighboring Cell Data
Take cell 0 presented in Figure 8-1 as an example. This cell is an edge cell of RNC 0.
Figure 8-4 shows the planned intra-frequency neighboring cells of cell 0.
Cell X
Cell 1
Cell M
Cell 0
Cell 2
Cell N
Cell Y
Figure 8-4 Intra-frequency neighboring cells of cell 0

The intra-frequency neighboring cells of cell 0 are planned as follows:
z
Cells 0, 1 and 2 belong to the NodeB1.
Cells X and Y belong to the same RNC (RNC 0) as cell 0. However, they belong to
different NodeBs: cell X belongs to the NodeB2 while cell Y belongs to the NodeB3.
Suppose X = 10 and Y = 20.
Cell M, cell N and cell 0 belong to different RNCs: cells M and N belong to RNC 1;
cell 0 belongs to RNC 0. Suppose M= 1 and N = 2.
Note:
Before configuring the intra-frequency neighboring cells of cell 0, ensure that the data of cells 1, 2, X, Y, M,
and N are already configured.
8.3.2 Configuring Intra-Frequency Neighboring Cell Data on RNC

I. Configuring Intra-Frequency Neighboring Cells 1, 2, X, and Y
//Configure cells 1 and 2 that belong to RNC 0 as the intra-frequency neighboring cells
of cell 0.
8-10
Chapter 8
ADD INTRAFREQCELL: CELLID=0, RNCID=0, NCELLID=1, READSFNIND=NOT_READ,

CELLINDIVIDALOFFSET=0,
CELLSFORBIDDEN1A=AFFECT,
CELLSFORBIDDEN1B=AFFECT, QOFFSET1SN=0, QOFFSET2SN=0;

II. Configuring Intra-Frequency Neighboring Cells M and N

//Configure the basic information of cell M that belongs to RNC 1.
ADD NRNCCELL: RNCID=1, CELLID=1, CELLNAME="Cell 1", PSCRAMBCODE=1,
UARFCNUPLINK=9650,
TXDIVERSITYIND=FALSE,
LAC=H'0001,
RAC=H'01,
SAC=H'0001,
SUPSSDT=FALSE,
CFGRACIND=REQUIRE,
LOWRATERLACTTIMEDEFOFFVAL=180,
HIGHRATERLACTTIMEDEFOFFVAL=80, ACTTIMEDEFOFFVALHHO=100;
//Configure cell M as an intra-frequency neighboring cell of cell 0.

//Configure the basic information of cell N that belongs to RNC 1.

UARFCNUPLINK=9650,
TXDIVERSITYIND=FALSE,
LAC=H'0001,
RAC=H'01,
SAC=H'0001,
SUPSSDT=FALSE,
CFGRACIND=REQUIRE,
LOWRATERLACTTIMEDEFOFFVAL=180,
HIGHRATERLACTTIMEDEFOFFVAL=80,
ACTTIMEDEFOFFVALHHO=100;
//Configure cell N as an intra-frequency neighboring cell of cell 0.

8.3.3 Checking Intra-Frequency Neighboring Cell Data

To check the intra-frequency neighboring cell data, operate as follows:
1)
Query the status of each intra-frequency neighboring cell of cell 0 using the DSP
CELL command.
2)
If all the cells are normal, enable the UE to move between different cells to trigger
handover and check whether the handovers are successful.
8-11
Chapter 8
8.4 Inter-Frequency Neighboring Cell Data Configuration

8.4.1 Planning Inter-Frequency Neighboring Cell Data
Figure 8-5 shows the planned inter-frequency neighboring cells of cell 0.
Cell x
Cell 5
Cell m
Cell 0
Cell 4
Cell n
Cell y
Figure 8-5 Inter-frequency neighboring cells of cell 0

The inter-frequency neighboring cells of cell 0 are planned as follows:
z
Cells 0, 4 and 5 belong to the NodeB1.
Cells x and y belong to the same RNC (RNC 0) as Cell 0. However, they belong to
different NodeBs: cell x belongs to the NodeB2 while cell y belongs to the NodeB3.
Suppose x = 11 and y = 21.
Cell m, cell n and cell 0 belong to different RNCs: cells m and n belong to RNC 1;
cell 0 belongs to RNC 0. Suppose m = 4 and n = 5.
Note:
Before configuring the inter-frequency neighboring cells of cell 0, ensure that the data cells 4, 5, x, y, m,
and n are already configured.
8.4.2 Configuring Inter-Frequency Neighboring Cell Data on RNC

I. Configuring Inter-Frequency Neighboring Cells 4, 5, x, and y
//Configure cells 4, 5, x and y that belong to RNC 0 as the inter-frequency neighboring
cells of cell 0.
8-12
Chapter 8
ADD INTERFREQCELL: CELLID=0, RNCID=0, NCELLID=4, READSFNIND=NOT_READ,

CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QOFFSET2SN=0;
II. Configuring Inter-Frequency Neighboring Cells m and n

//Configure the basic information of cell m that belongs to RNC 1.
UARFCNDOWNLINK=10560, SUPSSDT=FALSE, TXDIVERSITYIND=FALSE, LAC=H'0001,
SAC=H'0001, CFGRACIND=REQUIRE, RAC=H'01, LOWRATERLACTTIMEDEFOFFVAL=180,
//Configure cell m as an inter-frequency neighboring cell of cell 0.

//Configure the basic information of cell n that belongs to RNC 1.

UARFCNDOWNLINK=10560, SUPSSDT=FALSE, TXDIVERSITYIND=FALSE, LAC=H'0001,
SAC=H'0001, CFGRACIND=REQUIRE, RAC=H'01, LOWRATERLACTTIMEDEFOFFVAL=180,
//Configure cell n as an inter-frequency neighboring cell of cell 0.

8.4.3 Checking Inter-Frequency Neighboring Cell Data

To check inter-frequency neighboring cell data, operate as follows:
1)
Query the status of each inter-frequency neighboring cell of cell 0 using the DSP
CELL command.
2)
8-13
Chapter 8
8.5 Concentric Inter-Frequency Neighboring Cell Data

Configuration
8.5.1 Planning Concentric Inter-Frequency Neighboring Cell Data
Figure 8-6 shows the planned concentric inter-frequency neighboring cells of cell 0.
Cells 0 and 3 belong to the same sector of the NodeB1.
Cell 3
Cell 0
Figure 8-6 Concentric inter-frequency neighboring cell of cell 0
Note:
Before configuring the concentric inter-frequency neighboring cell of cell 0, ensure cell 3 is already
configured.
8.5.2 Configuring Concentric Inter-Frequency Neighboring Cell Data on RNC

//Configure cell 3 as a concentric inter-frequency neighboring cell of cell 0.
ADD CONINTERFREQCELL: CELLID=0, NCELLID=3;
8.5.3 Checking Concentric Inter-Frequency Neighboring Cell Data

None.
8.6 Inter-RAT Neighboring Cell Data Configuration

8.6.1 Planning Inter-RAT Neighboring Cell Data
Take cell 0 presented in Figure 8-1 as an example. Figure 8-7 shows the planned
inter-RAT neighboring cells of cell 0.
8-14
Chapter 8
G_Cell 2
G_Cell 1
G_Cell 3
Cell 0
G_Cell 0
G_Cell 4
G_Cell 5
Figure 8-7 Inter-RAT neighboring cells of cell 0

The inter-RAT neighboring cells of cell 0 are planned as listed in Table 8-6.
Table 8-6 Properties of inter-RAT neighboring cells of cell 0
Cell
Local area
code
Network
color code
Base station
color code
BCCH frequency
number
Cell type
G_Cell 0
H0001
GSM_AND_GPRS
G_Cell 1
H0001
10
GSM_AND_GPRS
G_Cell 2
H0001
20
GSM_AND_GPRS
G_Cell 3
H0002
30
GSM_AND_GPRS
G_Cell 4
H0002
40
GSM_AND_GPRS
G_Cell 5
H0002
50
GSM_AND_GPRS
8.6.2 Configuring Inter-RAT Neighboring Cell Data on RNC

//Configure G_cell 0 as an inter-RAT neighboring cell of cell 0.
ADD GSMCELL: MCC="460", MNC="00", LAC=H'0001, CID=0, NCC=0, BCC=0,
BCCHARFCN=0, RATCELLTYPE=GSM_AND_GPRS;
ADD INTERRATNCELL: CELLID=0, MCC="460", MNC="00", LAC=H'0001, CID=0,
CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QRXLEVMIN=-58, BLINDHOFLAG=FALSE;

8-15
Chapter 8




8.6.3 Checking Inter-RAT Neighboring Cell Data

To check the inter-RAT neighboring cell data, operate as follows:
1)
Query the status of each inter-RAT neighboring cell of cell 0 using the DSP CELL
command.
2)
8-16
Chapter 9
NodeB O&M Channel Configuration
Chapter 9 NodeB O&M Channel Configuration

9.1 Overview
NodeB O&M channel mentioned in this chapter refers to the channel between an O&M
console of NodeB (that is, LMT or M2000) and the host of NodeB, as shown in Figure
9-1.
M2000
RNC
LMT
NodeB
NodeB
LMT
Forward channel
Reverse channel
Local channel
Figure 9-1 NodeB O&M channels

The NodeB O&M channels are classified as the following:
z
Local O&M channel: the O&M channel between an LMT and the host of NodeB,
which is connected directly by Ethernet cables.
Remote O&M channel: the O&M channel between an O&M console and the host
of NodeB, which is connected through transparent channels provided by the RNC.
Where, the remote O&M channels are classified as the following:

z
Forward O&M channel: You can use this type of channel to operate and maintain a
NodeB in centralized mode on the M2000 side.
Reverse O&M channel: You can use this type of channel to operate the M2000
and RNC on the NodeB side.
9-1
Chapter 9

Before configuring a local O&M channel, ensure the NodeB LMT is connected with the
NodeB NMPT by Ethernet cable.
Before configuring a remote O&M channel, ensure the NodeB, RNC and M2000 are
properly connected.
Note:
For the convenience of introduction, this chapter takes one type of the NodeB model, BTS3812, as
example.

This chapter introduces the following contents:
1)
Local O&M Channel Configuration
2)
Remote O&M Channel Configuration
9.2 Local O&M Channel Configuration

9.2.1 Planning Local O&M Channel Data
The following takes the NodeB1 presented in Chapter 7 as an example to introduce
how to configure a local O&M channel.
For a local O&M channel, the data to be planned include the IP addresses of the NodeB
LMT and NMPT, which are dependant on the planning of remote O&M channel.
However, to enable the LMT to log in to the NMPT for configuration, first configure an IP
address for the LMT according to the default IP address of the NMPT.
The default IP address of the NMPT is 17.21.2.15 and the default subnet mask is
255.255.0.0. Correspondingly, the IP address of the LMT for login is 17.21.2.20 and the
subnet mask is 255.255.0.0.
The IP address of the NMPT planned in this example is 10.1.40.16 and the subnet
mask is 255.255.255.248. Correspondingly, the IP address of the LMT is 10.1.40.20
and the subnet mask is 255.255.255.248.
9-2
Chapter 9
9.2.2 Configuring Local O&M Channel Data

I. Configuring the IP Address of the LMT before Logging in to the NodeB
Note:
The following configuration procedure is applicable to Windows XP Professional. For other operating
systems, the procedures might be different.
1)
Select [Start / Settings / Control Panel] on the LMT.
2)
Double-click the Network and Dial-up Connections icon.
3)
Right-click [Local Area Connection] and then click [Properties] on the shortcut
menu. The [Local Area Connection Properties] dialog box is displayed.
4)
In the [General] tab, double-click Internet Protocol (TCP/IP). The [Internet

Protocol (TCP/IP) Properties] dialog log box is displayed.
5)
Select Use the following IP address.
6)
Enter the IP address of the LMT, as shown in Figure 9-2.
Figure 9-2 Modifying IP address of LMT
9-3
Chapter 9
II. Logging in to the NodeB Host from the LMT

1)
Select [Start / Programs / Huawei Local Maintenance Terminal NodeB / NodeB

V100R003 / NodeB Operation & Maintenance System]. The [Login] dialog box is
Figure 9-3 Login

2)
Click <Office >. The [Office Management] is displayed, as shown in Figure 9-4.
Figure 9-4 Office management

3)
Click <Add>. The [Office Information] dialog box is displayed, as shown in Figure
9-5.
9-4
Chapter 9
Figure 9-5 Office information

4)
Enter the default IP address of NMPT mentioned in 9.2.1 .
5)
Click <OK>. The [Office Management] dialog box is displayed again.
6)
Click <OK>. The [Login] dialog box is displayed again.
7)
Type admin in the [User name] box, NodeB in the [Password] box, and select
the office you just configured.
8)
Click <OK> to log in to the NMPT.
III. Modifying the IP Address of the NMPT

1)
Select [Service / Configuration Management System]. The [Select Version] dialog

box is displayed.
2)
Select a version.
3)
Click <OK> to start the corresponding configuration management system.
4)
Select [File/Open ].
5)
6)
Right-click the root node BTS3812 in [MIT Navigation Tree] and then click
[Modify NodeB] on the shortcut menu. The [Modify NodeB Properties] dialog box
7)
Enter the data planned in 9.2.1 , that is, the planned IP address of NMPT.
9-5
Chapter 9
Figure 9-6 Modifying BTS3812 properties

8)
Click <OK> to complete the modification of the IP address of NMPT.
IV. Reconfiguring the IP Address of the LMT

Modify the IP address of the LMT to 10.1.40.20 and the subnet mask to
255.255.255.248. Refer to section 9.2.2 I.
V. Re-logging in to the NodeB

Modify the IP address of the office to the modified IP address of the NMPT and then
re-log in to the NodeB. Refer to section 9.2.2 II.
9.2.3 Checking Local O&M Channel Data

Check whether the modified IP address of the NMPT can be reached by the Ping
command in the NodeB LMT.
9.3 Remote O&M Channel Configuration

9.3.1 Planning Remote O&M Channel Data
In this example the remote O&M channel between the M2000 and NodeB passes the
network as shown in Figure 9-7.
9-6
NodeB LMT
Chapter 9
RNC LMT
M2000 Client
M2000 Server
Subnet A
Fire Wall
Subnet B
DDN
Gate Way
Subnet C
RNC
BAM
Subnet D
WMPU
Subnet E
WMUX
WMUX
WMUX
Subnet F
NodeB1
NodeB2
Subnet N1
LMT
NodeB40
Subnet 40
Subnet N2
LMT
LMT
Figure 9-7 Network including remote O&M channel

The Huawei NodeB supports the dynamic IPoA setup function. When the NodeB
configuration file is unavailable or the IPoA channel fails, an IPoA channel can be set up
automatically between the NodeB and RNC. This scheme demands the following:
z
The PVC for setting up the IPoA should be fixed, that is, VPI/VCI=1/33.
The PVC used to carry the IPoA channel must be configured in the UNI link with
the minimum link number or the IMA group which includes the link with the
minimum link number.
If the NodeB is connected with the RNC by the networking PVC provided by another
NodeB, It is still can be regarded that this NodeB belongs to subnet F on the layer of IP
as shown in Figure 9-7. In this case the VC from this NodeB to the RNC is composed of
two segments: one is between this NodeB and the other NodeB that provides the
networking PVC; the other is between the NodeB that provides the networking PVC
and the RNC. You need to configure the PVC of the NodeB that provides this PVC.
9-7
Chapter 9
Note:
According to the requirement of the dynamic IPoA setup function, it is recommend to configure the
networking PVC as VC switch. This is different from the setting of other Iub links.
II. Planning IP Subnet

In this example the RNC is not located in the same area as the M2000 and connected
to the M2000 by a WAN DDN passing through a firewall.
Table 9-1 shows the network planning for the O&M channel from the M2000 to NodeB.
Where, as an example the WMUX in the WRBS1 handles 40 NodeBs.
Table 9-1 IP subnet planning
Subnet name
Subnet
Subnet mask
Remarks
Subnet A
10.1.1.0
255.255.255.0
Planned IP subnet
Subnet B
10.1.2.0
255.255.255.0
Planned IP subnet
Subnet C
10.1.3.0
255.255.255.0
Planned IP subnet
Subnet D
10.1.4.0
255.255.255.0
Planned IP subnet
Subnet E
192.1.1.0
255.255.255.0
Automatically
generated by
system
Subnet F
10.1.10.1
255.255.255.0
Planned IP subnet
Subnet N1
10.1.40.16
255.255.255.248
Planned IP subnet
Subnet N2
10.1.40.32
255.255.255.248
Planned IP subnet
Subnet 40
10.1.42.128
255.255.255.248
Planned IP subnet
the
III. Planning IP Address

Table 9-2 lists the planned IP addresses of the IP equipment on the O&M channel.
Table 9-2 IP address planning
Equipment
M2000 Server
Fire Wall
Gate Way
Port
IP address
Subnet mask
Port of subnet A
10.1.1.1
255.255.255.0
Port of subnet A
10.1.1.2
255.255.255.0
Port of subnet B
10.1.2.1
255.255.255.0
Port of subnet B
10.1.2.2
255.255.255.0
9-8
Chapter 9
Equipment
BAM
WMPU
WMUX (WRBS1)
NodeB1
NodeB2
Node40
Port
IP address
Subnet mask
Port of subnet C
10.1.3.1
255.255.255.0
Port of subnet C (in the

external network)
10.1.3.2
255.255.255.0
Port of subnet D (in the

internal network)
10.1.4.1
255.255.255.0
Port of subnet D
10.1.4.2
255.255.255.0
Port of subnet E
192.1.1.254
255.255.255.0
Port of subnet E
192.1.1.1
255.255.255.0
Port of subnet F
10.1.10.1
255.255.255.0
Port of subnet F
10.1.10.10
255.255.255.0
Port of subnet N1
10.1.40.16
255.255.255.248
Port of subnet F
10.1.10.11
255.255.255.0
Port of subnet N2
10.1.40.32
255.255.255.248
Port of subnet F
10.1.10.50
255.255.255.0
Port of subnet 80
10.1.42.128
255.255.255.248
The following describes some IP addresses listed in the above table:

z
The IP addresses of the BAM in the internal and external networks are configured
during BAM installation.
The IP address of the WMPU in subnet E is 192.1.1.254/24 fixedly.
The IP address of the WMUX in subnet E is 192.1.1.WRBS No. fixedly in this

example. Here, the WRBS No. is 1.
IV. Planning IP Route

The following only introduces the data planning for the IP routes to the NodeB1. For the
routes to other NodeBs, the data planning is similar.
To enable M2000 data to be sent to subnet F where the NodeB1 is in, configure the
routes to subnet F at all nodes on the O&M channel, as listed in Table 9-3.
Table 9-3 Forward IP route planning
Node
Route planning
M2000 Server
Route to subnet F with the next hop of the IP address of Fire Wall
Fire Wall
Route to subnet F with the next hop of the IP address of Gate Way
Gate Way
Route to subnet F with the next hop of the IP address of BAM
9-9
Chapter 9
Node
Route planning
BAM
Route to subnet F with the next hop of the IP address of WMPU
WMPU
Route to subnet F with the next hop of the IP address of WMUX
To enable NodeB1 data to be sent to subnet A where the M200 is in, configure the
routes to subnet A at all nodes on the O&M channel, as listed in Table 9-4.
Table 9-4 Reverse IP route planning
Node
Route planning
NodeB1 LMT
Route to subnet A with the next hop of the IP

address of the NMPT of he NodeB1
NodeB1

address of the WMUX
WMUX

address of the WMPU
WMPU
Route to subnet A with the next hop of the

internal IP address of the BAM
BAM

address of the Gate Way
Gate Way

address of the IP address of the Fire Wall
The following describes some routes presented in the above table:

z
Configure the route to subnet A from the NodeB LMT only when you configure the
reverse O&M channel.
Actually, you need not configure the route from NodeB1 LMT to subnet A, for the
system can directly route the IP packets to the WMUX according to the default
route.
V. Planning IPoA PVC

The following only introduces the data planning for the IPoA PVC of the NodeB1. For
the IPoA PVCs of other NodeBs, the data planning is similar.
Table 9-5 lists the data planning for the IPoA PVC between the NodeB1 and RNC.
Table 9-5 IPoA PVC planning
NodeB
NodeB1
Service
type
NRTVBR
Traffic description
CLPNOTAGGINGSCR
9-10
PCR
SCR
(kbps)
(kbps)
84
64
VPI
1
VCI
33
Chapter 9
9.3.2 Configuring Remote O&M Channel Data on M2000 Server

Note:
z
The following only introduces how to configure the O&M channel from the M2000 to NodeB. For other
NodeBs, the configuration procedure is similar.
After completing the following configuration, you need to configure related routes on the Fire Wall and
Gate Way according to Table 9-3 and Table 9-4, which is not introduced here.
T o configure the remote O&M channel on the M2000 server, operate as follows:
1)
Log in to the Solaris system of the M2000 server as a root user.
2)
Execute the following command to add a route to NodeB1.
# router add 10.1.10.10/25 10.1.1.2

3)
Execute the following command to create a file S97route under /etc/rc2.d.
# vi /etc/rc2.d/S97route
4)
Add a record in the created file ( add an permanent route).
route add 10.1.10.10/25 10.1.1.2

5)
Save the file and exit vi.
9.3.3 Configuring Remote O&M Channel Data on RNC

//Use the IMA group existing in the RNC and NodeB1 directly. No physical layer needs
to be configured here.

//Add an ATM traffic record for an IPoA channel over the Iub interface. The traffic record
configured here.
ADD
ATMTRF:
TRFX=130,
ST=NRTVBR,
TRFD=CLPNOTAGGINGSCR,
UT=KBIT/S,
PCR=84, SCR=64, MBS=1000;
III. Configuring IPoA Client

//Add the IPoA client to the WMUX in WRBS1.
ADD
IPOACLIENT:
SRN=1,
MASK="255.255.255.0";
IV. Configuring IPoA PVC

//Configuring an IPoA PVC.
9-11
lSN=7,
SSN=0,
IPADDR="10.1.10.1",
Chapter 9
ADD IPOAPVC: IPADDR="10.1.10.1", PEERIPADDR="10.1.10.10", PEERT=NODEB,

PEERNAME="NodeB1", CARRYSRT=WRBS, CARRYSRN=1, ENBAPSF=OFF, CARRYT=IMA,
CARRYIMAGRPN=0,
TXTRFX=130,
RXTRFX=130,
CARRYSN=0,
CARRYVPI=1,
CARRYVCI=33;
V. Configuring Route
Note:
If there are two BAM servers working in active/standby mode, the following route configuration need be
performed on both the active and standby BAM servers.
//Open the Routing and Remote Access service on the BAM server.
1)
Select [Start / Settings / Control Panel].
2)
Double-click [Administrative Tools].
3)
Double-click [Services]. The [Services] dialog box is displayed.
4)
Double-click [Routing and Remote Access].
5)
Select the [General] tab.
6)
Modify [Startup type] to Automatic.
7)
Click <OK>.
//Configure the route to the NodeB on the BAM server.

1)
Select [File/Run ].
2)
Type cmd. The [cmd.exe] dialog box is displayed.
3)
Type >route add 10.1.10.0 mask 255.255.255.0 10.1.4.2 -p.
//Configure the route to the M2000 on the BAM server.

1)
Select [File/Run ].
2)
Type cmd. The [cmd.exe] dialog box is displayed.
3)
Type >route add 10.1.1.0 mask 255.255.255.0 10.1.3.1 -p.
//Configure the route to the NodeB on the WMPU.

ADD
IPRT:
SRN=2,
LSN=0,
SSN=0,
RTDEST="10.1.10.0",
//Configure the route to the M2000 on the WMPU.

ADD
IPRT:
SRN=2,
LSN=0,
SSN=0,
RTDEST="10.1.1.0",
//Configure the route to the M2000 on the WMUX.

ADD
IPRT:
SRN=1,
LSN=7,
SSN=0,
9-12
RTDEST="10.1.1.0",
Chapter 9
9.3.4 Configuring Remote O&M Channel Data on NodeB

To configure the remote O&M channel on the NodeB, operate as follows:
1)
2)
3)
Right-click [Transmission Object Tree / IPoA Device Set / IPoA Device] and then
click [Modify IPoA Device] on the shortcut menu. The [Modify IPoA Device
Properties] dialog box is displayed, as shown in Figure 9-8.
4)
5)
Figure 9-8 Modifying basic properties of IPoA device

6)
7)
9-13
Chapter 9
Figure 9-9 Modifying virtual port properties of IPoA device

8)
Click <OK> to complete the modification of IPoA device properties.
Note:
There is no need to configure the route to the M2000 on the LMT and host of the NodeB1.
9.3.5 Checking Remote O&M Channel Data

To check the remote O&M channel data, operate as follows:
1)
Check whether the IPoA address of the NodeB can be reached by the Ping
command on the M2000.
2)
Check whether the address of the M2000 can be reached by the Ping command
on the NodeB1 LMT.
9-14

A
AAL2
ATM Adaptation Layer type 2
ADM
add/drop multiplexer
AICH
Acquisition Indicator Channel
AIS
Alarm Indication Signal
ALCAP
Access Link Control Application Part
APS
Automatic Protection Switch(ing)
ATM
Asynchronous Transfer Mode
B
BAM
Back Administration Module
BCCH
Broadcast Control CHannel
BSC
Base Station Controller
BSC6800
Huawei RNC Model
BSS
Base Station Subsystem
BTS2812
Huawei NodeB Model
C
CBC
Cell Broadcast Center
CBR
Constant Bit Rate
CCP
Common Communication Port
CS
Circuit-Switched
D
DDN
Digital Data Network
G
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communications
I
IMA
Inverse Multiplexing on ATM
IP
Internet Protocol
IPoA
Internet Protocols over ATM
F-1
LAC
Location Area Code
LMT
Local Maintenance Terminal
M
MCC
Mobile Country Code
MGW
Media
MML
Man Machine Language
MNC
Mobile Network Code
MSC
Mobile Service Switching Center
MSP
Multiplex Section Protection
MTP3B
Message transfer part (broadband)
GateWay
N
NAOI
NodeB ATM Optical Interface unit
NCC
Network Color Code
NCP
NodeB Control Port
NDTI
NodeB Digital Trunk Interface unit
NMPT
NodeB Main Processor & Timing unit
P
PCH
Paging Channel
PCIPCH
Primary Common Pilot CHannel
PCR
Peak Cell Rate
PDH
Plesiochronous Digital Hierarchy
PICH
Paging indicator channel
PLMN
Public Land Mobile Network
PRACH
Packet Random Access Channel
PS
Packet Switched
PVC
Permanent Virtual Channel
R
RAC
Routing Area Code
RACH
Random Access CHannel
RAN
Radio Access Network
RANAP
Radio Access Network Application Part
RFN
RNC Frame Number counter
RNC
Radio Network Controller
F-2
SAAL
Signaling ATM Adaptation Layer
SABP
Service Area Broadcast Protocol
SCCP
Signaling Connection and Control Part
SCCPCH
Secondary Common Control Physical Channel
SDH
Synchronous Digital Hierarchy
SGSN
Serving GPRS Support Node
STM-1
Synchronous Transport Mode-1
STP
Signaling Transfer Point
T
TFC
Transport Format Combination
TS
Time Slot
U
UBR
Unspecified Bit Rate
UE
User Equipment
UMTS
Universal mobile telecommunication services/Universal

Mobile Telecommunications System
URA
UTRAN Registration Area
V
VC
Virtual Circuit
W
WBIE
WCDMA RNC BaseStation Interface Board
WCDMA
Wideband CDMA
WFMR
WCDMA RNC Radio Frame processing board
WHPU
WCDMA RNC High speed Packet processing board
WLPU
WCDMA RNC Line Process Unit
WMPU
WCDMA RNC Main Process Unit
WMUX
WCDMA RNC system MUltipleXer unit
WNET
WCDMA RNC NETwork switch board
WOSE
WCDMA RNC Single mode Optical interface board of E1/T1
WRBS
WCDMA RNC Business Subrack
WRSS
WCDMA RNC Switch Subrack
WSPU
WCDMA Signaling Process Unit
F-3
Index
Index
configuration procedure
configuration example, 1-1
cell and neighboring cell data, 8-1
NodeB O&M channel, 9-2
cell data configuration, 8-1
RNC basic data configuration, 2-1
checking
RNC-CBC interconnection, 5-1
concentric inter-frequency neighboring cell data,
RNC-MSC interconnection, 3-1
8-14
RNC-NodeB interconnection, 7-1
inter-frequency neighboring cell data, 8-13
RNC-RNC connection, 6-1
inter-RAT neighboring cell data, 8-16
RNC-SGSN interconnection, 4-1
intra-frequency neighboring cell data, 8-11
configuration purpose
local O&M channel data, 9-6
cell and neighboring cell, 8-1
remote O&M channel data, 9-14
RNC-CBC interconnection data, 5-4
RNC-MSC (R4) interconnection data, 3-12
RNC-NodeB1 interconnection data, 7-17
configuring
concentric inter-frequency neighboring cell on
RNC-RNC interconnection data, 6-8
RNC, 8-14
RNC-SGSN interconnection data, 4-6
inter-frequency neighboring cell on RNC, 8-12
commissioning
inter-RAT neighboring cell on RNC, 8-15
cell data, 8-9
intra-frequency neighboring cell on RNC, 8-10
on NodeB1, 8-9
local cell data on NodeB1, 8-8
on RNC, 8-9
RNC basic data, 2-8
logical cell data on RNC, 8-5
remote O&M channel data on M2000, 9-11
8-14
remote O&M channel data on NodeB, 9-13
configuration precondition
remote O&M channel data on RNC, 9-11
cell and neighboring cell, 8-1
RNC basic data, 2-6
RNC basic data configuraiton, 2-1
RNC-NodeB1 interconnection data on NodeB1,
7-9
RNC-NodeB1 interconnection data on RNC, 7-6
i-1
Index
7-22

7-42
local O&M channel configuration, 9-2
7-35
NodeB O&M channel configuration, 9-1
7-50
planning
cell data, 8-1
7-70
8-14
7-62
7-80
NodeB O&M channel
IP address, 9-8
IP route, 9-9
IP subnet, 9-8
IPoA PVC, 9-10
data configuration references, 1-2
remote O&M channel data, 9-6
data configuration tools, 1-2
RNC basic bata
data planning example
subrack data, 2-3
RNC basic data, 2-1
clock source data, 2-6
local office data, 2-2
RNC-NodeB1 interconnection, 7-5
OSP data, 2-6
WLPU optical port, 2-5
RNC-RNC interconnection, 6-2
data planning Example

Planning
i-2
Index
RNC-NodeB4 interconnection data configuration,
RNC-MSC (R99) Interconnection Data, 3-2
7-46
remote O&M channel configuration, 9-6
7-58
RNC identification information, 2-2
7-76
RNC location information, 2-2
RNC-RNC interconnection data configuration, 6-1
RNC SIB1 information, 2-3
RNC-SGSN interconnection data configuration, 4-1
RNC-CBC interconnection data configuration, 5-1

RNC-MSC (R4) interconnection data configuration,
3-7
typical network topology
RNC-MSC (R99) interconnection data configuration,
3-2
RNC-MSC interconnection data configuration, 3-1
RNC-MSC interconnection, 3-2, 3-7
RNC-NodeB interconnection data configuration, 7-1
RNC-NodeB network topology, 7-2
7-4
7-17
7-31
RNC-RNC interconnection, 6-1

i.
i-3

UMTS Radio Access Network Configuration Example

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UMTS Radio Access Network Configuration Example

Uploaded by

Copyright:

Available Formats

Chapter 1 Introduction to Data Configuration ..............................................

1.1 Overview ................................................................................................

Chapter 2 RNC Basic Data Configuration .....................................................

2.1 Overview ................................................................................................

Chapter 3 RNC-MSC Interconnection Data Configuration ...........................

3.1 Overview ................................................................................................

Chapter 4 RNC-SGSN Interconnection Data Configuration .........................

4.1 Overview ................................................................................................

Chapter 5 RNC-CBC Interconnection Data Configuration ...........................

5.1 Overview ................................................................................................

5.1.1 Configuration Purpose ...................................................................

Chapter 6 RNC-RNC Interconnection Data Configuration ...........................

6.1 Overview ................................................................................................

Chapter 7 RNC-NodeB Interconnection Data Configuration .......................

7.1 Overview ................................................................................................

7.5.5 Checking RNC-NodeB3 Interconnection Data ...............................

Chapter 8 Cell and Neighboring Cell Data Configuration ............................

8.1 Overview ................................................................................................

8.6.1 Planning Inter-RAT Neighboring Cell Data ....................................

Chapter 9 NodeB O&M Channel Configuration ............................................

9.1 Overview ................................................................................................

Appendix Acronyms and Abbreviations .......................................................

HUAWEI UMTS Radio Access Network

HUAWEI UMTS Radio Access Network

BSC6800V100R002 NodeB V100R003

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium,

About This Manual

Organization of the Manual

The manual is intended for the following readers:

Technical support and engineers

Telecommunication administration staff

Normal paragraphs are in Arial.

II. GUI conventions

Button names are inside angle brackets <>.

Menu items are inside square brackets [ ].

Multi-level menus are separated by forward slashes /. For example,

III. Mouse operation

Press the left button quickly.

Press the right button quickly.

Press the left button twice continuously and quickly.

Caution: Means reader be extremely careful during the operation.

Chapter 5 RNC-CBC Interconnection Data Configuration ........................................................ 5-1

7.6 RNC-NodeB4 Interconnection Data Configuration .......................................................... 7-46

Chapter 9 NodeB O&M Channel Configuration.......................................................................... 9-1

Chapter 1 Introduction to Data Configuration

Data Configuration Tasks and Procedure

Data Configuration References

Data Configuration Tools

1.2 Data Configuration Tasks and Procedure

Configure cell and

Figure 1-1 Configuration tasks and procedure

1.3 Data Configuration References

HUAWEI BSC6800 WCDMA Radio Network Controller Operation Manual Data

BTS3812&BTS3806&BTS3806A WCDMA NodeB Data Configuration

1.4 Data Configuration Tools

NodeB Configuration Management (Integrated in NodeB Operation and

Chapter 2 RNC Basic Data Configuration

2.1.2 Configuration Precondition

The RNC hardware is installed.