UMTS Radio Access Network Configuration Example

Chapter 1 Introduction to Data Configuration .............................................. 1.1 Overview ................................................................................................ 1.2 Data Configuration Tasks and Procedure ..............................................
1.3 Data Configuration References .............................................................. 1.4 Data Configuration Tools........................................................................ Chapter 2 RNC Basic Data Configuration ..................................................... 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 ................................................... Chapter 3 RNC-MSC Interconnection Data Configuration ........................... 3.1 Overview ................................................................................................ 3.1.1 Configuration Purpose ................................................................... 3.1.2 Configuration Precondition ............................................................. 3.1.3 Configuration Procedure ................................................................ 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 ............................ Chapter 4 RNC-SGSN Interconnection Data Configuration ......................... 4.1 Overview ................................................................................................ 4.1.1 Configuration Purpose ................................................................... 4.1.2 Configuration Precondition ............................................................. 4.1.3 Configuration Procedure ................................................................ 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 .................................. Chapter 5 RNC-CBC Interconnection Data Configuration ........................... 5.1 Overview ................................................................................................
1-1 1-1 1-1 1-2 1-2 2-1 2-1 2-1 2-1 2-1 2-1 2-1 2-6 2-8 3-1 3-1 3-1 3-1 3-1 3-2 3-2 3-3 3-6 3-7 3-7 3-9 3-12 4-1 4-1 4-1 4-1 4-1 4-1 4-1 4-3 4-6 5-1 5-1
5.1.1 Configuration Purpose ................................................................... 5.1.2 Configuration Precondition ............................................................. 5.1.3 Configuration Procedure ................................................................ 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 .................................... Chapter 6 RNC-RNC Interconnection Data Configuration ........................... 6.1 Overview ................................................................................................ 6.1.1 Configuration Purpose ................................................................... 6.1.2 Configuration Precondition ............................................................. 6.1.3 Configuration Procedure ................................................................ 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 .................................... Chapter 7 RNC-NodeB Interconnection Data Configuration ....................... 7.1 Overview ................................................................................................ 7.1.1 Configuration Purpose ................................................................... 7.1.2 Configuration Precondition ............................................................. 7.1.3 Configuration Procedure ................................................................ 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.4 RNC-NodeB2 Interconnection Data Configuration ................................. 7.4.1 Planning RNC-NodeB2 Interconnection Data ................................ 7.4.2 Configuring RNC-NodeB2 Interconnection Data on RNC .............. 7.4.3 Configuring RNC-NodeB2 Interconnection Data on NodeB2 ........ 7.4.4 Checking RNC-NodeB2 Interconnection Data ............................... 7.5 RNC-NodeB3 Interconnection Data Configuration ................................. 7.5.1 Planning RNC-NodeB3 Interconnection Data ................................ 7.5.2 Configuring RNC-NodeB3 Interconnection Data on RNC .............. 7.5.3 Configuring RNC-NodeB3 Interconnection Data on NodeB3 ........ 7.5.4 Configuring RNC-NodeB3 Interconnection Data on NodeB2 ........
5-1 5-1 5-1 5-1 5-1 5-3 5-4 6-1 6-1 6-1 6-1 6-1 6-1 6-1 6-4 6-8 7-1 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.5.5 Checking RNC-NodeB3 Interconnection Data ............................... 7.6 RNC-NodeB4 Interconnection Data Configuration ................................. 7.6.1 Planning RNC-NodeB4 Interconnection Data ................................ 7.6.2 Configuring RNC-NodeB4 Interconnection Data on RNC .............. 7.6.3 Configuring RNC-NodeB4 Interconnection Data on NodeB4 ........ 7.6.4 Checking RNC-NodeB4 Interconnection Data ............................... 7.7 RNC-NodeB5 Interconnection Data Configuration ................................. 7.7.1 Planning RNC-NodeB5 Interconnection Data ................................ 7.7.2 Configuring RNC-NodeB5 Interconnection Data on RNC .............. 7.7.3 Configuring RNC-NodeB5 Interconnection Data on NodeB5 ........ 7.7.4 Configuring RNC-NodeB5 Interconnection Data on NodeB4 ........ 7.8 RNC-NodeB6 Interconnection Data Configuration ................................. 7.8.1 Planning RNC-NodeB6 Interconnection Data ................................ 7.8.2 Configuring RNC-NodeB6 Interconnection Data on RNC .............. 7.8.3 Configuring RNC-NodeB6 Interconnection Data on NodeB6 ........ 7.8.4 Checking RNC-NodeB6 Interconnection Data ............................... Chapter 8 Cell and Neighboring Cell Data Configuration ............................ 8.1 Overview ................................................................................................ 8.1.1 Configuration Purpose ................................................................... 8.1.2 Configuration Precondition ............................................................. 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 .....................................
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 8-1 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 ................................... Chapter 9 NodeB O&M Channel Configuration ............................................ 9.1 Overview ................................................................................................ 9.1.1 Configuration Purpose ................................................................... 9.1.2 Configuration Precondition ............................................................. 9.1.3 Configuration Procedure ................................................................ 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 .......................................... Appendix Acronyms and Abbreviations ....................................................... Index .................................................................................................................
8-14 8-15 8-16 9-1 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 F-1
HUAWEI
HUAWEI UMTS Radio Access Network Configuration Example
HUAWEI UMTS Radio Access Network Configuration Example

Manual Version Product Version BOM T2-031695-20041001-C-1.22 BSC6800V100R002 NodeB V100R003 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 Notes Initial commercial release
Updates of Contents
None
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 z
Technical support and engineers Telecommunication administration staff
Conventions
This document uses the following conventions:
I. General conventions
Convention Arial Arial Narrow Description Normal paragraphs are in Arial. 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 Click Right-click Double-click Press the left button quickly. Press the right button quickly. Press the left button twice continuously and quickly. Description
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.
Configuration Example HUAWEI UMTS Radio Access Network
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.1.1 Configuration Purpose ............................................................................................ 3-1 3.1.2 Configuration Precondition...................................................................................... 3-1 3.1.3 Configuration Procedure ......................................................................................... 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.1.1 Configuration Purpose ............................................................................................ 4-1 4.1.2 Configuration Precondition...................................................................................... 4-1 4.1.3 Configuration Procedure ......................................................................................... 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.1.1 Configuration Purpose ............................................................................................ 5-1 5.1.2 Configuration Precondition...................................................................................... 5-1 5.1.3 Configuration Procedure ......................................................................................... 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.1.1 Configuration Purpose ............................................................................................ 6-1 6.1.2 Configuration Precondition...................................................................................... 6-1 6.1.3 Configuration Procedure ......................................................................................... 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.1.1 Configuration Purpose ............................................................................................ 7-1 7.1.2 Configuration Precondition...................................................................................... 7-1 7.1.3 Configuration Procedure ......................................................................................... 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 7.4.4 Checking RNC-NodeB2 Interconnection Data...................................................... 7-31 7.5 RNC-NodeB3 Interconnection Data Configuration .......................................................... 7-31 7.5.1 Planning RNC-NodeB3 Interconnection Data....................................................... 7-31 7.5.2 Configuring RNC-NodeB3 Interconnection Data on RNC .................................... 7-33 7.5.3 Configuring RNC-NodeB3 Interconnection Data on NodeB3 ............................... 7-35 7.5.4 Configuring RNC-NodeB3 Interconnection Data on NodeB2 ............................... 7-42 7.5.5 Checking RNC-NodeB3 Interconnection Data...................................................... 7-46
ii
Table of Content
7.6 RNC-NodeB4 Interconnection Data Configuration .......................................................... 7-46 7.6.1 Planning RNC-NodeB4 Interconnection Data....................................................... 7-46 7.6.2 Configuring RNC-NodeB4 Interconnection Data on RNC .................................... 7-48 7.6.3 Configuring RNC-NodeB4 Interconnection Data on NodeB4 ............................... 7-50 7.6.4 Checking RNC-NodeB4 Interconnection Data...................................................... 7-58 7.7 RNC-NodeB5 Interconnection Data Configuration .......................................................... 7-58 7.7.1 Planning RNC-NodeB5 Interconnection Data....................................................... 7-58 7.7.2 Configuring RNC-NodeB5 Interconnection Data on RNC .................................... 7-60 7.7.3 Configuring RNC-NodeB5 Interconnection Data on NodeB5 ............................... 7-62 7.7.4 Configuring RNC-NodeB5 Interconnection Data on NodeB4 ............................... 7-70 7.8 RNC-NodeB6 Interconnection Data Configuration .......................................................... 7-76 7.8.1 Planning RNC-NodeB6 Interconnection Data....................................................... 7-76 7.8.2 Configuring RNC-NodeB6 Interconnection Data on RNC .................................... 7-78 7.8.3 Configuring RNC-NodeB6 Interconnection Data on NodeB6 ............................... 7-80 7.8.4 Checking RNC-NodeB6 Interconnection Data...................................................... 7-87 Chapter 8 Cell and Neighboring Cell Data Configuration ......................................................... 8-1 8.1 Overview ............................................................................................................................ 8-1 8.1.1 Configuration Purpose ............................................................................................ 8-1 8.1.2 Configuration Precondition...................................................................................... 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.1.1 Configuration Purpose ............................................................................................ 9-1 9.1.2 Configuration Precondition...................................................................................... 9-2 9.1.3 Configuration Procedure ......................................................................................... 9-2 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

1.1 Overview
This chapter introduces the following contents:
z z 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
Configure NodeB O&M channel
End
Figure 1-1 Configuration tasks and procedure
1-1
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 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

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 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) 2) 3) 4) Configuring Local Office Data Configuring Hardware Data Configuring Clock Source Data 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) 2) 3) Planning Local Office Data Planning Subrack Data Planning WLPU Optical Port
4) 5)
Planning Clock Source Data Planning OSP Data
2-1
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 RNC ID Mobile Network Code (MNC) Mobile Country Code (MCC) 0 460 000 Data planning
RNC location information
Figure 2-1 shows the location areas (LAs) and routing areas (RAs) of the RNC.
LA0
RA0
RA1
RNC
RA2
RA3
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
Item Service Area Code (SAC) LA0 SAC = 100 LA1 SAC = 200
Data planning
RA0 RAC = 0 (belonging to LA1; PLMN value tag = 912 Routing Area Code (RAC) RA1 RAC = 1 (belonging to LA1); PLMN value tag = 1316 RA2 RAC = 2 (belonging to LA2); PLMN value tag = 1720 RA3 RAC = 3 (belonging to LA2); PLMN value tag = 2124 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 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
Table 2-4 Subrack configuration Subrack name Board name WMPU WRSS WLPU WNET WHPU WBIE WRBS1 WFMR WMUX WSPU WOSE WRBS3 WFMR WMUX WSPU Number of boards Two Two Two Three Two Two Two Two Two Two Two Two Slot number 0, 1 2, 4 7, 8 10, 11, 12 0, 15 1, 2 7, 8 10, 11 0, 15 1, 2 7, 8 10, 11 Figure 2-4 Figure 2-3 Figure 2-2 Figure number
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 0 W M P U 1 W L P U 2 3 W L P U 4 5 6 W N E T 7 W N E T 8 9 W H P U 10 W H P U 11 W H P U 12 13 14
Figure 2-2 WRSS configuration
2-4

W B I E 0 W F M R 1 W F M R 2 3 4 5 6 W M U X 7 W M U X 8 9 W S P U 10 W S P U 11 12

W B I E 13 14 15
Figure 2-3 WRBS1 configuration
W O S E 0
W F M R 1
W F M R 2 3 4 5 6
W M U X 7
W M U X 8 9
W S P U 10
W S P U 11 12 13 14
W O S E 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 0 1 2 3 4 5 6 7 8 9 10 11 12 13 Connected to WRBS1 Connected to WRBS3 Reserved Reserved Reserved Reserved Reserved Connected to NodeB Connected to an neighboring RNC Reserved Reserved Connected to Cell Broadcast Center (CBC) Connected to Mobile Service Switching Center (MSC) or Media Gateway Reserved Usage
2-5
WLPU optical port number 14 15 Connected to SGSN Reserved
Usage
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 Network Identification (NID) OSP code ATM address National network code H0008, 14-bit code H45000086100101008F0000000000000000000000 Data planning
2.2.2 Configuring RNC Basic Data

I. Overview
To configure the RNC basic data, operate as follows: 1) 2) 3) 4) 5) 6) Setting the BAM to Offline Mode Configuring Local Office Data Configuring Hardware Data Configuring Clock Source Data Configuring OSP Data 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
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 RAC: LAC=100, RAC=1, PLMNVALTAGMIN=13, PLMNVALTAGMAX=16;
//Add RA2 and RA3 that belong to LA1

ADD RAC: LAC=200, RAC=2, PLMNVALTAGMIN=17, PLMNVALTAGMAX=20; ADD RAC: LAC=200, RAC=3, PLMNVALTAGMIN=21, PLMNVALTAGMAX=24;
//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
//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) 2) 3) 4) 5) 6) 7) Formatting the RNC Basic Data Loading the Files into Flash Memory Setting the Loading Control Parameters Resetting the Whole System Querying the Running Status of Each Board Checking the Consistency of BAM and FAM in Board Versions 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
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 z 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 z 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

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. The configuration procedure is as follows: 1) 2) 3) 4) 5) 6) 7) 8) 9) Configuring Physical Layer Configuring ATM Layer Configuring SAAL Link Configuring DSP Configuring Signalling Linkset Configuring Signalling Route Configuring Signalling Link Configuring ALCAP Adjacent Node Configuring AAL2 PATH
10) Configuring AAL2 Route
3-1
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
SDH
ADM
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 MSC Destination Signalling Point (DSP) code MSC ATM address Iu physical port outgoing from RNC RNC-MSC signalling links in control plane RNC-MSC AAL2 paths in user plane H0001 H45000086100101001F0000000000000000000000 Optical port 12 of the WLPU in slot 2 Refer to Table 3-2 Refer to Table 3-3 Data planning
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
Table 3-2 Data negotiation and planning for RNC-MSC (R99) signalling links in control plane SLC 0 1 2 3 Service type CBR CBR CBR CBR Traffic description NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR PCR (cell/s) 1000 1000 1000 1000 VPI 10 11 12 13 VCI 32 32 32 32 WRBS No. 1 1 3 3 WSPU subsystem No. 0 1 0 1 SAAL link No. 0 0 0 0
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 1 2 3 4 5 6 7 8 Traffic description WSPU PCR SCR WRBS VPI VCI From subsystem (cell/s) (cell/s) No. No. 7434 7434 7434 7434 7434 7434 7434 7434 6424 6424 6424 6424 6424 6424 6424 6424 60 60 61 61 62 62 63 63 32 33 32 33 32 33 32 33 RNC RNC RNC RNC RNC RNC RNC RNC 1 1 1 1 3 3 3 3 0 0 1 1 0 0 1 1
RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT RTVBR NOCLPNOSCRCDVT
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; SET WLPUSUBT: SN=4, 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
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, ST=RTVBR, MBS=1000, CDVT=102400, PCR=7434,
REMARK="IuCS-AAL2Path", SCR=6424;
TRFD=NOCLPSCRCDVT,
UT=CELL/S,
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: SRN=1, SSN=0, SAALLNKN=0, CARRYSR=WRSS, CARRYSN=2, CARRYPN=12, CARRYVPI=10,
TXTRFX=100, CARRYVCI=32; ADD SAALLNK:
RXTRFX=100,
SAALLNKT=NNI,
SRN=1,
SSN=1,
SAALLNKN=0,
CARRYSR=WRSS, CARRYSN=2,
CARRYPN=12, CARRYVPI=11,
TXTRFX=100, CARRYVCI=32;
RXTRFX=100,
SAALLNKT=NNI,
RXTRFX=100,
SAALLNKT=NNI,
SRN=3,
SSN=1,
SAALLNKN=0,
RXTRFX=100,
SAALLNKT=NNI,
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
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; ADD MTP3BLNK: SIGLKSX=0, SIGSLC=1, SRN=1, SSN=1, SAALLNKN=0, PRIORITY=0, TCLEN=10, TC=170; ADD MTP3BLNK: SIGLKSX=0, SIGSLC=2, SRN=3, SSN=0, SAALLNKN=0, PRIORITY=0, TCLEN=10, TC=170; ADD MTP3BLNK: SIGLKSX=0, SIGSLC=3, SRN=3, SSN=1, SAALLNKN=0, PRIORITY=0, 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: ANI=0, PATHID=1, ENDSRN=1, ENDSN=7, CARRYSR=WRSS,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYSN=2, CARRYVPI=60, CARRYVCI=32; ADD AAL2PATH: ANI=0, PATHID=2, ENDSRN=1, ENDSN=7, CARRYSR=WRSS,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYSN=2, CARRYVPI=60, CARRYVCI=33;
//Add two AAL2 PATHs controlled by WSPU subsystem 1 of WRBS1.

CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,

3-5

CARRYPN=12, TXTRFX=101,

RXTRFX=101, CONTROLSSN=0, OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
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) 2) 3) 4) Carry out the DSP SAALLNK command to check the availability of the SAAL links. Carry out the DSP MTP3BLNK command to check the availability of the MTP3B links. Carry out the DSP SSN command to check the availability of the Signalling Connection Control Part (SCCP) subsystems. 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) 2) 3) Carry out the DSP AAL2PATH command to check the AAL2 PATHs to the adjacent node. Carry out the ACT VCLCC command to activate the Continuous Check (CC) of Virtual Connect Links (VCLs) bearing the AAL2 PATHs. 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
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
SDH
ADM
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 MGW Destination Signalling Point (DSP) code MGW ATM address MSC server DSP code Iu physical port outgoing from RNC RNC-MGW links in the control plane RNC-MGW links in the user plane H0002 H45000086100101002F0000000000000000000000 H0001 Optical port 12 of the WLPU in slot 2 Refer to Table 3-5 Refer to Table 3-6 Data planning
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
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 SLC 0 1 2 3 Service type CBR CBR CBR CBR Traffic description NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR PCR (cell/s) 1000 1000 1000 1000 VPI 10 11 12 13 VCI 32 32 32 32 WRBS No. 1 1 3 3 WSPU subsystem No. 0 1 0 1 SAAL link No. 0 0 0 0
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 1 2 3 4 5 6 7 8 Service type RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR Traffic description NOCLPNOS CRCDVT NOCLPNOS CRCDVT NOCLPNOS CRCDVT NOCLPNOS CRCDVT NOCLPNOS CRCDVT NOCLPNOS CRCDVT NOCLPNOS CRCDVT NOCLPNOS CRCDVT PCR (cell/s) 7434 7434 7434 7434 7434 7434 7434 7434 SCR (cell/s) 6424 6424 6424 6424 6424 6424 6424 6424 VPI VCI From RNC RNC RNC RNC RNC RNC RNC RNC WRBS No. 1 1 1 1 3 3 3 3 WSPU subsystem No. 0 0 1 1 0 0 1 1
60 60 61 61 62 62 63 63
32 33 32 33 32 33 32 33
3-8
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 to set optical port 12 in slot 2 and optical port 12 in slot 4 to be the active and standby ports.

//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 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, ST=RTVBR, MBS=1000, CDVT=102400, PCR=7434,
REMARK="IuCS-AAL2Path", SCR=6424;
TRFD=NOCLPSCRCDVT,
UT=CELL/S,

RXTRFX=100,
SAALLNKT=NNI,
SRN=1,
SSN=1,
SAALLNKN=0,
RXTRFX=100,
SAALLNKT=NNI,
RXTRFX=100,
SAALLNKT=NNI,
3-9

ADD SAALLNK: SRN=3, SSN=1,

SAALLNKN=0, CARRYSR=WRSS, CARRYSN=2, CARRYPN=12, CARRYVPI=13,
RXTRFX=100,
SAALLNKT=NNI,
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 B1111. In addition, set the signalling linkset emergency verification switch to OFF.

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



//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

//Add AAL2 PATHs to the Q.AAL2 adjacent node, MGW. //Add two AAL2 PATHs controlled by WSPU subsystem 0 of WRBS1.
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,

CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,
CARRYPN=12,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,

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

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

To check the user plane data, operate as follows: 1) 2) 3) 4) Carry out the DSP AAL2PATH command to check the AAL2 PATHs to the adjacent node. Carry out the ACT VCLCC command to activate the Continuous Check (CC) of Virtual Connect Links (VCLs) bearing the AAL2 PATHs. Carry out the DSP VCLCC command to query the CC results of VCLs bearing the AAL2 PATHs to check whether there are AIS and RDI alarms. 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

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, 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 configuration procedure is as follows: 1) 2) 3) 4) 5) 6) 7) 8) Configuring Physical Layer Configuring ATM Layer Configuring SAAL Link Configuring DSP Configuring Signalling Linkset Configuring Signalling Route Configuring Signalling Link 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
ADM
SDH
ADM
STM-1
RNC
SGSN
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 SGSN DSP code Outgoing Iu interface of the RNC RNC-SGSN signalling links in control plane RNC-SGSN channels in user plane H0007 Optical port 14 of the WLPU in slot 2 Refer to Table 4-2 Refer to Table 4-3 and Figure 4-2 Data planning
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 0 1 2 3 Service type CBR CBR CBR CBR Traffic description NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR PCR (cell/s) 1000 1000 1000 1000 10 11 12 13 VPI 32 32 32 32 VCI 1 1 3 3 WRBS No. WSPU subsystem No. 0 1 0 1 SAAL link No. 10 10 10 10
4-2
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 IP address of SGSN gateway 10.10.21.4/ 24 10.10.21.4/ 24 10.10.21.4/ 24 10.10.21.4/ 24 PCR (cell/s ) 35141 5 35141 5 35141 5 35141 5 Logic al No. of WHP U 1 1 2 2
IP address of SGSN
IP address of RNC
Servic e type
Traffic description
VP I
VC I
Subsys tem No.
10.10.121.2/ 24
10.10.21.2/ 24 10.10.21.2/ 24 10.10.21.2/ 24 10.10.21.2/ 24
UBR UBR UBR UBR
NOCLPNOSCRC DVT NOCLPNOSCRC DVT NOCLPNOSCRC DVT NOCLPNOSCRC DVT
80 81 82 83
32 32 32 32
1 2 1 2
Subsystem 1 10.10.21.2/24 of WHPU 1
10.10.21.4/24
To SGSN gateway 1
10.10.22.4/24
To SGSN gateway 2
10.10.121.2/24 SGSN
10.10.23.4/24
To SGSN gateway 3
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;
SET WLPUSUBT: SN=2, SUBN=3, SUBT=STM-1;
4-3
//Add active and standby ports for physical transmission on the Iu-PS interface. That is to set optical port 14 in slot 2 and optical port 14 in slot 4 to be the active and standby ports.

//Add an ATM traffic record for an SAAL NNI link over the Iu-PS interface. The traffic record index is 100. If this index is already configured over another interface, it need not be configured here.
//Add an ATM traffic record for an IPoA channel over the Iu-PS interface. The traffic record index is 105. If this index is already configured over another interface, it need not 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 WSPU subsystems 0 and 1 of WRBS1.
ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=10, CARRYSR=WRSS, CARRYPN=14, TXTRFX=100, CARRYVCI=32; ADD SAALLNK: SRN=1, SSN=1, SAALLNKN=10, CARRYSR=WRSS, CARRYPN=14, TXTRFX=100, CARRYVCI=32; RXTRFX=100, SAALLNKT=NNI, CARRYSN=2, CARRYVPI=11, RXTRFX=100, SAALLNKT=NNI, CARRYSN=2, CARRYVPI=10,
//Add two SAAL NNI links over the Iu-PS interface that are terminated respectively at WSPU subsystems 0 and 1 of WRBS3.
ADD SAALLNK: SRN=3, SSN=0, SAALLNKN=10, CARRYSR=WRSS, CARRYPN=14, TXTRFX=100, CARRYVCI=32; ADD SAALLNK: SRN=3, SSN=1, SAALLNKN=10, CARRYSR=WRSS, CARRYPN=14, TXTRFX=100, CARRYVCI=32; RXTRFX=100, SAALLNKT=NNI, CARRYSN=2, CARRYVPI=13, RXTRFX=100, SAALLNKT=NNI, CARRYSN=2, CARRYVPI=12,
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

//Add a signalling linkset to the SGSN with linkset index of 5 and signalling link mask of B1111. In addition, set the signalling linkset emergency verification switch to OFF.

//Add a signalling route to the SGSN.

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",
MASK="255.255.255.0"; ADD IPOACLIENT: SRN=2, lSN=1, SSN=2, IPADDR="10.10.22.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.
MASK="255.255.255.0"; ADD IPOACLIENT: SRN=2, lSN=2, SSN=2, IPADDR="10.10.24.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; ADD IPOAPVC: IPADDR="10.10.22.2", PEERIPADDR="10.10.22.4", PEERT=OTHER, CARRYSRT=WRSS, CARRYPN=14, TXTRFX=105, RXTRFX=105, CARRYSN=2,
4-5

CARRYVPI=81, CARRYVCI=32;
ADD IPOAPVC: IPADDR="10.10.23.2", PEERIPADDR="10.10.23.4", PEERT=OTHER, CARRYSRT=WRSS, CARRYPN=14, TXTRFX=105, RXTRFX=105, CARRYSN=2,
CARRYVPI=82, CARRYVCI=32; ADD IPOAPVC: IPADDR="10.10.24.2", PEERIPADDR="10.10.24.4", PEERT=OTHER, 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",
RTDESTMASK="255.255.255.0", NEXTHOP="10.10.24.4";
4.2.3 Checking RNC-SGSN Interconnection Data

To check the control plane data, operate as follows: 1) 2) 3) Carry out the DSP SAALLNK command to check whether the SAAL links are available. Carry out the DSP MTP3BLNK command to check whether the MTP3B links are available. 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

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, 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 configuration procedure is as follows: 1) 2) 3) 4)
Configuring Physical Layer Configuring ATM Layer 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
ADM
SDH
ADM
STM-1
RNC
CBC
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 Outgoing Iu interface of the RNC RNC-CBC channel Data planning Optical port 11 of the WLPU in slot 2 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 10.10.14 1.4/24 IP address of CBC gateway 10.10.131.4/ 24 IP address of RNC 10.10.13 1.2/24 Service type UBR Traffic description NOCLPNOS CRCDVT PCR (cell/s) 20000 V PI 90 V CI 32 WRBS No. 1 WSPU subsystem No. 0
WSPU 10.10.131.4/24 subsystem 0 of WRBS1 10.10.131.2/24
To CBC gateway
10.10.141.4/24
CBC
Figure 5-2 IPoA channel between RNC and CBC
5-2
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 to set optical port 11 in slot 2 and optical port 11 in slot 4 to be the active and standby ports.

//Add an ATM traffic record for an IPoA channel over the Iu-BC interface. The traffic record index is 106. If this index is already configured over another interface, it need not 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", CARRYPN=11, TXTRFX=106, PEERIPADDR="10.10.131.4", RXTRFX=106, CARRYSN=2,
CARRYSRT=WRSS,
CARRYVPI=90, CARRYVCI=32;
//Add a route to the CBC.

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, SSN=0, PEERIPADDR="10.10.141.4",
MASK="255.255.255.0";
5-3
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

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, 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 configuration procedure is as follows: 1) 2) 3) 4) 5) 6) 7) 8) 9) Configuring Physical Layer Configuring ATM Layer Configuring SAAL Link Configuring DSP Configuring Signalling Linkset Configuring Signalling Route Configuring Signalling Link Configuring ALCAP Adjacent Node Configuring AAL2 PATH
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
ADM
SDH
ADM
STM-1
RNC
Figure 6-1 RNC-RNC network topology
Another RNC
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 DSP code of the other RNC ATM address of the other RNC ID of the other RNC MCC of the other RNC MNC of the other RNC Whether the other RNC supports both CS and PS services Outgoing Iu interface of the local RNC RNC-RNC signalling links in control plane RNC-RNC AAL2 PATHs in user plane IP addresses for the two RNCs H0009 H45000086100102009F0000000000000000000000 1 000 460 Yes Optical port 8 of the WLPU in slot 2 Refer to Table 6-2 Refer to Table 6-3 Refer to Figure 6-2 Data planning
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
Table 6-2 Data negotiation and planning for RNC-RNC signalling links in control plane SLC 0 1 2 3 Service type CBR CBR CBR CBR Traffic description NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR NOCLPNOSCR PCR (cell/s) 1000 1000 1000 1000 10 11 12 13 VPI 32 32 32 32 VCI 1 1 3 3 WRBS No. WSPU subsystem No. 0 1 0 1 SAAL link No. 12 12 12 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 AAL2 PATH ID 1 2 3 4 5 6 7 8 Service type RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR Traffic description NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT PCR (cell/s) 7434 7434 7434 7434 7434 7434 7434 7434 SCR (cell/s) 6424 6424 6424 6424 6424 6424 6424 6424 VPI 60 60 61 61 62 62 63 63 VCI 32 33 32 33 32 33 32 33 From . .. RNC RNC RNC RNC RNC RNC RNC RNC WRBS No. 1 1 1 1 3 3 3 3 WSPU subsystem No. 0 0 1 1 0 0 1 0
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
10.10.21.4/24
To SGSN gateway 1
10.10.22.4/24
To SGSN gateway 2
10.10.121.2/24 SGSN
10.10.23.4/24 To SGSN gateway 3
Subsystem 2 10.10.24.2/24 of WHPU 2 Local RNC
10.10.24.4/24 To SGSN gateway 4
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

//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 index is 101. If this index is already configured over another interface, it need not be configured here.
ADD ATMTRF: TRFX=101, ST=RTVBR, MBS=1000, UT=CELL/S, CDVT=102400, PCR=7434,
REMARK="Iur-AAL2Path", SCR=6424;
TRFD=NOCLPSCRCDVT,

//Add two SAAL NNI links over the Iur interface that are terminated respectively at WSPU subsystems 0 and 1 of WRBS1.
ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=12, CARRYSR=WRSS, CARRYSN=2, CARRYPN=8,
RXTRFX=100,
SAALLNKT=NNI,
CARRYVPI=10,
SRN=1,
SSN=1,
SAALLNKN=12,
CARRYPN=8,
RXTRFX=100,
SAALLNKT=NNI,
CARRYVPI=11,
//Add two SAAL NNI links over the Iur interface that are terminated respectively at WSPU subsystems 0 and 1 of WRBS3.
ADD SAALLNK: SRN=3, SSN=0, SAALLNKN=12, CARRYSR=WRSS, CARRYSN=2, CARRYPN=8,
RXTRFX=100,
SAALLNKT=NNI,
CARRYVPI=12,
SRN=3,
SSN=1,
SAALLNKN=12,
CARRYPN=8,
RXTRFX=100,
SAALLNKT=NNI,
CARRYVPI=13,
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

//Add a signalling route to the other RNC.

//Add MTP3B signalling links into the signalling linkset with index of 6.

//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 two AAL2 PATHs controlled by WSPU subsystem 0 of WRBS1.
CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,
CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,

6-6

CARRYPN=8, TXTRFX=101,

RXTRFX=101, CONTROLSSN=0, OWNERSHIP=LOCAL,
CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=0,
OWNERSHIP=LOCAL,

CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,
CARRYPN=8,
TXTRFX=101,
RXTRFX=101,
CONTROLSSN=1,
OWNERSHIP=LOCAL,

ADD AAL2RT: NSAP= H45000086100102009F0000000000000000000000, ANI=6, RTX=0, OWNERSHIP=YES;
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.



6-7

ADD IPRT: SRN=2,

LSN=2, SSN=2, RTDEST="10.10.141.2",
6.2.3 Checking RNC-RNC Interconnection Data

To check the control plane data, operate as follows: 1) 2) 3) 4) Carry out the DSP SAALLNK command to check whether the SAAL links are available. Carry out the DSP MTP3BLNK command to check whether the MTP3B links are available. Carry out the DSP SSN command to check whether the SCCP subsystems are available. Carry out the DSP AAL2ADJNODE to check whether the other RNC is available.

To check the user plane data, operate as follows: 1) 2) 3) 4) 5) Carry out the DSP AAL2PATH command to check whether the AAL2 PATHs are functional. Carry out the ACT VCLCC command to activate the Continuous Check (CC) of VCLs bearing the AAL2 PATHs. Carry out the DSP VCLCC command to query the CC results of VCLs bearing the AAL2 PATHs to check whether there are AIS and RDI alarms. Carry out the DEA VCLCC command to deactivate the Continuous Check (CC) of VCLs bearing the AAL2 PATHs. 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

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, including local office data, hardware data, clock source data, and OSP data. For the configuration of the RNC basic data, refer to Chapter 2.

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) 5) 6) 7) Configuring Physical Layer Configuring ATM Layer Configuring SAAL Link Configuring NodeB1 Port Configuring ALCAP Adjacent Node Configuring AAL2 PATH Configuring AAL2 Route
The procedure of configuring the interconnection data on the NodeB as follows: 1) 2) 3) 4) 5) Configuring Transmission Object Modifying ALCAP Properties Modifying AAL2 PATH Properties Modifying NCP Properties 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
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

SDH
NodeB3
E1/T1
E1/T1 over SDH

SDH
E1/T1
PDH/SDH
E1/T1 NodeB1
NodeB4
RNC
NodeB6 E1/T1
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
z z

z z
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 NodeB1 NodeB2 NodeB3 NodeB4 NodeB5 NodeB6 NodeB interface board NDTI NDTI NDTI NAOI NDTI NDTI RNC interface board WBIE WOSE WOSE WLPU WLPU WBIE WRBS WRBS1 WRBS3 WRBS3 WRBS1 WRBS1 WRBS1 WSPU subsystem 0 0 0 0 0 0
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=7 VPI=8 VPI=7 VPI=6 NodeB NodeB NodeB RNC
Figure 7-2 VPI planning for NodeBs Table 7-2 lists the ATM address of each NodeB.
7-3
Table 7-2 ATM addresses of NodeBs ATM node name NodeB1 NodeB2 NodeB3 NodeB4 NodeB5 NodeB6 ATM address 0x45000086100101010F0000000000000000000000 0x45000086100101011F0000000000000000000000 0x45000086100101012F0000000000000000000000 0x45000086100101013F0000000000000000000000 0x45000086100101014F0000000000000000000000 0x45000086100101015F0000000000000000000000 ID in RNC 11 12 13 14 15 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
ADM
E1/T1
NodeB1
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

The following table gives a planning example of RNC-NodeB1 interconnection data: Table 7-3 RNC-NodeB1 interconnection data planning Item Cell ATM address of NodeB1 Cable Iub physical port outgoing from RNC Iub physical port outgoing from NodeB1 RNC-NodeB1 signalling links in control plane RNC-NodeB1 channels in user plane Data planning 2-anttena, 3 sectors x 2 frequencies 0x45000086100101010F0000000000000000000000 The Iub interface adopts 3 E1/T1 trunk cables belonging to an IMA group Links 0, 1, and 2 on WBIE 0 in WRBS1 Links 2, 3 and 4 on NDTI 22 Refer to Table 7-4 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 SAAL PCR SCR Terminating Service Traffic description VPI VCI link WRBS No. type (kbps) (kbps) usage NCP RTVBR NOCLPNOSCRCDVT 84 80 80 80 80 80 80 80 80 6 6 6 6 6 6 6 6 32 1 33 1 34 1 35 1 36 1 37 1 38 1 39 1 0 0 0 0 0 0 0 0 Terminating SAAL WSPU link subsystem No. No. 30 31 32 33 34 35 36 37
CCP 0 RTVBR NOCLPNOSCRCDVT 84 CCP 1 RTVBR NOCLPNOSCRCDVT 84 CCP 2 RTVBR NOCLPNOSCRCDVT 84 CCP 3 RTVBR NOCLPNOSCRCDVT 84 CCP 4 RTVBR NOCLPNOSCRCDVT 84 CCP 5 RTVBR NOCLPNOSCRCDVT 84 ALCAP RTVBR NOCLPNOSCRCDVT 84
7-5
Table 7-5 lists the data negotiation and planning for RNC-NodeB1 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 NodeB1. Table 7-5 Data negotiation and planning for RNC-NodeB1 channels in user plane AAL2 PATH ID 1 2 3 4 5 6 Service type RTVBR RTVBR RTVBR RTVBR RTVBR RTVBR Traffic description NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT PCR (kbps) 780 780 780 780 780 780 SCR (kbps) 750 750 750 750 750 750 6 6 6 6 6 6 VPI VCI 40 41 42 43 44 45 From RNC RNC RNC RNC RNC RNC WRB S No. 1 1 1 1 1 1 WSPU subsyste m No. 0 0 0 0 0 0
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 IMALNK: SRN=1, SN=0, IMAGRPN=0, IMALNKN=1; ADD IMALNK: SRN=1, SN=0, IMAGRPN=0, IMALNKN=2;

//Add an ATM traffic record for an SAAL link over the Iub interface. The traffic record index is 110. If this index is already configured over another interface, it need not be configured here.
ADD ATMTRF: TRFX=110, ST=RTVBR, TRFD=CLPNOTAGGINGSCRCDVT, UT=KBIT/S, PCR=84, SCR=80, MBS=1000, CDVT=102400;
7-6
//Add an ATM traffic record for an AAL2 PATH over the Iub interface. The traffic record index is 111. If this index is already configured over another interface, it need not be configured here.

//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,
CARRYSN=0, CARRYVPI=6, CARRYVCI=32; ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=31, CARRYSR=LOCAL, ENBAPSF=OFF, CARRYT=IMA, CARRYIMAGRPN=0, TXTRFX=110, RXTRFX=110, SAALLNKT=UNI,
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; ADD CCP: NODEBNAME="NodeB1", PN=1, SAALLNKN=32;
7-7
ADD CCP: NODEBNAME="NodeB1", PN=2, SAALLNKN=33; ADD CCP: NODEBNAME="NodeB1", PN=3, SAALLNKN=34; ADD CCP: NODEBNAME="NodeB1", PN=4, SAALLNKN=35; ADD CCP: NODEBNAME="NodeB1", PN=5, SAALLNKN=36;
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; ADD AAL2PATH: ANI=11, PATHID=2, ENDSRN=1, ENDSN=0, CARRYSR=LOCAL, CARRYT=IMA, CARRYIMAGRPN=0, TXTRFX=111, RXTRFX=111, CONTROLSSN=0,
OWNERSHIP=LOCAL, CARRYSN=0, CARRYVPI=6, CARRYVCI=45;
VII. Configuring AAL2 Route

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

I. Selecting a Configuration Template
1) 2) 3) In the Configuration Management System of the NodeB1, select [File/New By Template]. Select the template 2-antenna_3_2_Transmitter Non-diversity_no backup.xml. 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) 3) Set [IMA Group No.] to IMA Group 0. 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) 6) Set [IMA Link No.] to IMA Link 2. Click <OK> to complete the addition of an IMA link.
7-9
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) 3) Select the [Basic Properties] tab. Enter the data planned in section 7.3.1 .
7-10
Figure 7-6 Modifying basic properties of master cabinet ALCAP 4) 5) Select the [Virtual Port] tab. Enter the data planned in section 7.3.1 , as shown in Figure 7-7.
7-11
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) Select the [Basic Properties] tab. Enter the data planned in section 7.3.1 .
7-12
Figure 7-8 Modifying basic properties of master cabinet ALCAP No.1 AAL2 PATH 4) 5) Select the [Virtual Port] tab. Enter the data planned in section 7.3.1 , as shown in Figure 7-9.
Figure 7-9 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH
7-13
6) 7)
Click <OK> to complete the modification of No.1 AAL2 PATH properties. 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) Select the [Basic Properties] tab. Enter the data planned in section 7.3.1 .
Figure 7-10 Modifying basic properties of NCP 4) 5) Select the [Virtual Port] tab. Enter the data planned in section 7.3.1 as shown in Figure 7-11.
7-14
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) Select the [Basic Properties] tab. Enter the data planned in section 7.3.1 .
7-15
Figure 7-12 Modifying basic properties of CCP 4) 5) Select the [Virtual Port] tab. Enter the data planned in section 7.3.1 , as shown in Figure 7-13.
7-16
Figure 7-13 Modifying virtual port properties of CCP 6) 7) Click <OK> to complete the modification of No.0 CCP properties. Repeat steps 1)6) to modify the properties of CCPs 1-5.
VII. Saving the Configuration File

1) 2) 3) Select [File/Save]. The [Save] dialog box is displayed. Enter the configuration file name and select .mdb as the file type. 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
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) ADM SDH ADM RNC
E1/T1
NodeB2
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. Table 7-6 RNC-NodeB2 interconnection data planning Item Cell ATM address of NodeB2 Cable Iub physical port outgoing from RNC Iub physical port outgoing from NodeB2 RNC-NodeB2 signalling links in control plane RNC-NodeB2 channels in user plane Data planning 4-antenna, 3 sectors x 1 frequency 0x45000086100101011F0000000000000000000000 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 Refer to Table 7-7 Refer to Table 7-8
Table 7-7 lists the data negotiation and planning for RNC-NodeB2 SAAL links in the 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
RNC and the non-dash area shows the data negotiated between the RNC and NodeB2. The APS function is disabled. Table 7-7 Data negotiation and planning for RNC-NodeB2 signalling links in control plane SAAL link usage NCP CCP 0 CCP 1 CCP 2 ALCAP Service type RTVBR RTVBR RTVBR RTVBR RTVBR PCR (kbps) 84 84 84 84 84 SCR (kbps) 80 80 80 80 80 V P VCI I 6 32 6 33 6 34 6 35 6 36 Terminating WRBS No. 3 3 3 3 3 Terminating WSPU subsystem No. 0 0 0 0 0 SAAL link No. 30 31 32 33 34
Traffic description
NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT
Table 7-8 lists the data negotiation and planning for RNC-NodeB2 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 NodeB2. Table 7-8 Data negotiation and planning for RNC-NodeB2 channels in user plane AAL2 PATH ID 1 2 3 Service type RTVBR RTVBR RTVBR Traffic description NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT PCR (kbps) 780 780 780 SCR (kbps) 750 750 750 VPI 6 6 6 VCI 40 41 42 From RNC RNC RNC WRBS No. 3 3 3 WSPU subsystem No. 0 0 0
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
SDH
3 4
E1/T1 E1/T1 SDH
E1/T1 over SDH E1/T1 over SDH
1 0
NDTI
ADM
ADM
WOSE
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.
ADD IMALNK: SRN=3, SN=0, IMAGRPN=0, IMALNKN=0; ADD IMALNK: SRN=3, SN=0, IMAGRPN=0, IMALNKN=1;

7-20


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


ADD CCP: NODEBNAME="NodeB2", PN=0, SAALLNKN=31; ADD CCP: NODEBNAME="NodeB2", PN=1, SAALLNKN=32; ADD CCP: NODEBNAME="NodeB2", PN=2, SAALLNKN=33;


//Add AAL2 PATHs to the ALCAP adjacent node, that is, the NodeB2. The AAL2 PATH IDs are 1 to 3.
7-21

ADD AAL2RT: NSAP= H 45000086100101011F0000000000000000000000, ANI=12, RTX=0, OWNERSHIP=YES;

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-16. 2) 3) Set [IMA Group No.] to IMA Group 0. Click <OK> to complete the addition of this IMA group.
7-22
Figure 7-16 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-17. 5) 6) Set [IMA Link No.] to IMA Link 3. Click <OK> to complete the addition of an IMA link.
7-23
Figure 7-17 Adding an IMA link 7) Repeat steps 4)6) to add IMA link 4.

7-24
Figure 7-18 Modifying basic properties of master cabinet ALCAP 4) 5) Select the [Virtual Port] tab. Enter the data planned in section7.4.1 , as shown in Figure 7-19.
Figure 7-19 Modifying virtual port properties of master cabinet ALCAP

7-25
6)
Click <OK> to complete the modification of ALCAP properties.

7-26
Figure 7-21 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH 6) 7) Click <OK> to complete the modification of No.1 AAL2 PATH properties. Repeat steps 1)6) twice to modify the properties of AAL2 PATHs 2 and 3.

7-27
Figure 7-22 Modifying basic properties of NCP 4) 5) Select the [Virtual Port] tab. Enter the data planned in section 7.4.1 , as shown in Figure 7-23.
7-28

7-29
Figure 7-24 Modifying basic properties of CCP 4) 5) Select the [Virtual Port] tab. Enter the data planned in section 7.4.1 as shown in Figure 7-25.
7-30
Figure 7-25 Modifying virtual port properties of CCP 6) 7) Click <OK> to complete the modification of No.0 CCP properties. Repeat steps 1)6) twice to modify the properties of CCPs 1 and 2.



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
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 over SDH(1:1 MSP) ADM SDH ADM RNC
E1/T1
E1/T1
NodeB3
NodeB2

The following table gives a planning example of RNC-NodeB3 interconnection data. Table 7-9 RNC-NodeB3 interconnection data planning Item Cell ATM address of NodeB3 Data planning 2 antenna, 1 sector x 1 frequency H45000086100101012F0000000000000000000000 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 Links 3 and 4 on NDTI 22 Link 7 on NDTI 22 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: Bandwidth for NodeB3 Number of SAAL links x SAAL link bandwidth + Number of AAL2 PATHs x AAL2 PATH bandwidth = 3 84 + 1 780 = 1032 kbps Therefore, configure the NodeB3 with the bandwidth of 1300 kbps
Cable
Iub physical port outgoing from RNC Iub physical port outgoing from NodeB3 Physical port between NodeB2 and RNC Physical port between NodeB2 and NodeB3 RNC-NodeB3 signalling links in control plane RNC-NodeB3 channels in user plane
7-32
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.
Table 7-10 lists the data negotiation and planning for RNC-NodeB3 SAAL links in the 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. Table 7-10 Data negotiation and planning for RNC-NodeB3 signalling links in control plane SAAL link usage NCP CCP 0 ALCAP Service type RTVBR RTVBR RTVBR PCR (kbps) 84 84 84 SCR (kbps) 80 80 80 V P I 7 7 7 32 33 34 VCI Terminating WRBS No. 3 3 3 Terminating WSPU subsystem No. 0 0 0 SAAL link No. 35 36 37
Traffic description
NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT
Table 7-11 lists the data negotiation and planning for RNC-NodeB3 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 NodeB. Table 7-11 Data negotiation and planning for RNC-NodeB3 channels in user plane AAL2 PATH ID 1 Service type RTVBR PCR (kbps) 780 SCR (kbps) 750 V P I 7 40 VCI From RNC 3 WRBS No. WSPU subsystem No. 0
Traffic description NOCLPNOSCRCDVT

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



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

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

ADD CCP: NODEBNAME="NodeB3", PN=0, SAALLNKN=36;

7-34

//Add an AAL2 PATH to the ALCAP adjacent node, that is, the NodeB3. The AAL2 PATH ID is 1.

ADD AAL2RT: NSAP=H45000086100101012F0000000000000000000000, ANI=13, RTX=0, OWNERSHIP=YES;

II. Modifying ALCAP Properties

7-35
7-36
III. Modifying AAL2 PATH Properties

7-37
Figure 7-29 Modifying basic properties of master cabinet ALCAP No.1 AAL2 PATH 4) 5) Select the [Virtual Port] tab. Enter the data planned in section7.5.1 , as shown in Figure 7-30.
Figure 7-30 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH
7-38
6)
Click <OK> to complete the modification of No.1 AAL2 PATH properties.
IV. Modifying NCP Properties

7-39
V. Modifying CCP Properties

7-40
7-41
Figure 7-34 Modifying virtual port properties of CCP 6) Click <OK> to complete the modification of No.0 CCP properties.
VI. Saving the Configuration File


I. Modifying the VPI Range
1) 2) 3) Log in to the Configuration Management System of the NodeB2. Open the NodeB2 configuration file. 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 displayed, as shown in Figure 7-35. 4) 5) Select the [VPI Range] tab. Modify the max VPI to 6.
7-42
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) Select the [Basic Properties] tab. Enter the data planned in section 7.5.1 .
7-43
Figure 7-36 Adding basic properties of the networking PVC 4) 5) Select the [Source Port] tab. Enter the data planned in sectio7.5.1 , as shown in Figure 7-37.
7-44
Figure 7-37 Adding the source port of the networking PVC 6) 7) Select the [Destination Port] tab. Enter the data planned in section7.5.1 , as shown in Figure 7-38.
7-45
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
SDH SDH NodeB4
SDH
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.

The following table gives a planning example of RNC-NodeB4 interconnection data. Table 7-12 RNC-NodeB4 interconnection data planning Item Cell ATM address of NodeB4 Iub physical port outgoing from RNC Iub physical port outgoing from NodeB4 RNC-NodeB4 signalling links in control plane RNC-NodeB4 channels in user plane Data planning 4 antenna, 3 sectors x 1 frequency H45000086100101013F0000000000000000000000 Optical port 7 on WLPU 2 of the WRSS Optical port 0 on NAOI 23 Refer to Table 7-13 Refer to Table 7-14
Table 7-13 lists the data negotiation and planning for RNC-NodeB4 SAAL links in the 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 RNC and the non-dash area shows the data negotiated between the RNC and NodeB. The APS function is disabled. Table 7-13 Data negotiation and planning for RNC-NodeB4 signalling links in control plane SAAL link usage NCP Service type RTVBR PCR (kbps) 84 SCR (kbps) 80 V P I 6 32 VCI Terminating WRBS No. 1 Terminating WSPU subsystem. 0 SAAL link No. 37
Traffic description NOCLPNOSCRCDVT
7-47
SAAL link usage CCP 0 CCP 1 CCP 2 ALCA P
Service type RTVBR RTVBR RTVBR RTVBR
Traffic description NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT
PCR (kbps) 84 84 84 84
SCR (kbps) 80 80 80 80
V P I 6 6 6 6 33 34 35 36 VCI
Terminating WRBS No. 1 1 1 1
Terminating WSPU subsystem. 0 0 0 0
SAAL link No. 38 39 40 41
Table 7-14 lists the data negotiation and planning for RNC-NodeB4 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 NodeB. Table 7-14 Data negotiation and planning for RNC-NodeB4 channels in user plane AAL2 PATH ID 1 2 3 Service type RTVBR RTVBR RTVBR PCR (kbps) 780 780 780 SCR (kbps) 750 750 750 V P I 6 6 7 40 41 42 RNC RNC RNC VCI From . WRBS No. 1 1 1 0 0 0 WSPU subsystem No.
Traffic description NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT

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


7-48

RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=38,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=39,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=40,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=41,
RXTRFX=110,
SAALLNKT=UNI,

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



7-49

//Add AAL2 PATHs to the ALCAP adjacent node, that is, the NodeB4. The PATH IDs are 13.
CARRYPN=7,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYPN=7,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYPN=7,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL,


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 displayed, as shown in Figure 7-40. 2) 3) Select the [Basic Properties] tab. Set [Slot No.] to No.22.
7-50
Figure 7-40 Adding the NAOI board 4) Click <OK> to complete the addition of the NAOI.

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-41. 2) 3) Select the [Basic Properties] tab. Enter the ALCAP data planned in section 7.6.1 .
7-51
Figure 7-41 Modifying basic properties of master cabinet ALCAP 4) 5) Select the [Virtual Port] tab. Enter the ALCAP data planned in section 7.6.1 , as shown in Figure 7-42.
7-52

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-43. 2) 3) Select the [Basic Properties] tab. Enter the ALL2 PATH data planned in section 7.6.1 .
7-53
Figure 7-43 Modifying basic properties of master cabinet ALCAP No.1 AAL2 PATH 4) 5) Select the [Virtual Port] tab. Enter the AAL2 PATH data planned in section 7.6.1 , as shown in Figure 7-44.
Figure 7-44 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH 6) Click <OK> to complete the modification of No.0 AAL2 PATH properties.
7-54
7)
Repeat steps 1)6) twice to modify the properties of AAL2 PATHs 2 and 3.

7-55

1) Right-click [Transmission Object Tree / CCP Set / No.0 CCP] and then click [Modify CCP] on the shortcut menu. The [Modify NCP Properties] dialog box is displayed, as shown in Figure 7-47. 2) 3) Select the [Basic Properties] tab. Enter the data planned in section 7.6.1 .
7-56
Figure 7-48 Modifying virtual port properties of CCP

7-57
6) 7)
Click <OK> to complete the modification of No.0 CCP properties. Repeat steps 1)6) twice to modify the properties of CCPs 1 and 2.



As shown in Figure 7-49, 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 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 NodeB4
SDH
SDH
RNC

The following table gives a planning example of RNC-NodeB5 interconnection data. Table 7-15 RNC-NodeB5 interconnection data planning Item Cell ATM address of NodeB5 Data planning 2 antenna, 3 sectors x 1 frequency H45000086100101014F0000000000000000000000
7-58
Item Cable Iub physical port outgoing from RNC Iub physical port outgoing from NodeB5 Physical port outgoing from NodeB4 to connect to RNC Physical port outgoing from NodeB4 to connect to NodeB5 RNC-NodeB5 signalling links in control plane RNC-NodeB5 channels in user plane
Data planning 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 Links 3 and 4 on NDTI 22 Optical port 0 on NAOI 23 Links 6 and 7 on NDTI 22 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:
Bandwidth for NodeB5
Number of SAAL links x SAAL link bandwidth + Number of AAL2 PATHs x AAL2 PATH bandwidth = 5 84 + 3 780 = 2760 kbps. 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.
Table 7-16 lists the data negotiation and planning for RNC-NodeB5 SAAL links in the 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 RNC and the non-dash area shows the data negotiated between the RNC and NodeB. The APS function is disabled. Table 7-16 Data negotiation and planning for RNC-NodeB5 signalling links in control plane SAAL link usage NCP CCP 0 CCP 1 Service type RTVBR RTVBR RTVBR PCR (kbps) 84 84 84 SCR (kbps) 80 80 80 V P VCI I 7 32 7 33 7 34 Terminating WRBS No. 1 1 1 Terminating WSPU subsystem No. 0 0 0 SAAL link No. 42 43 44
Traffic description
7-59
SAAL link usage CCP 2 ALCAP
Service type RTVBR RTVBR
Traffic description
PCR (kbps) 84 84
SCR (kbps) 80 80
V P VCI I 7 35 7 36
Terminating WRBS No. 1 1
Terminating WSPU subsystem No. 0 0
SAAL link No. 45 46
NOCLPNOSCRCDVT NOCLPNOSCRCDVT
Table 7-17 lists the data negotiation and planning for RNC-NodeB5 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 NodeB. Table 7-17 Data negotiation and planning for RNC-NodeB5 channels in user plane AAL2 PATH ID 1 2 3 Service type RTVBR RTVBR RTVBR Traffic description NOCLPNOSCRCDVT NOCLPNOSCRCDVT NOCLPNOSCRCDVT PCR (kbps) 780 780 780 SCR (kbps) 750 750 750 V P VCI I 7 40 7 41 7 42 FROM RNC RNC RNC WSPU No. 1 1 1 0 0 0 WSPU subsystem No.

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


7-60

ADD SAALLNK: SRN=1, SSN=0,

SAALLNKN=42, CARRYSR=WRSS, CARRYSN=2, CARRYPN=7, CARRYVPI=7,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=43,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=44,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=45,
RXTRFX=110,
SAALLNKT=UNI,
SRN=1,
SSN=0,
SAALLNKN=46,
RXTRFX=110,
SAALLNKT=UNI,

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




//Add an AAL2 PATH to the ALCAP adjacent node, that is, the NodeB5. The AAL2 PATH IDs are 1 to 3.
CARRYPN=7,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
CARRYPN=7,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL,
7-61

ADD AAL2PATH: ANI=15,

PATHID=3, ENDSRN=1, ENDSN=0, CARRYSR=WRSS,
CARRYPN=7,
TXTRFX=111,
RXTRFX=111,
CONTROLSSN=0,
OWNERSHIP=LOCAL,


II. Adding an IMA group

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-50. 2) Set [NDTI Board No.] to Master Cabinet Baseband Subrack No.22 NDTI Board.
Figure 7-50 Adding an IMA group
7-62
3)
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-51.
4)
Set [IMA Link No.] to "IMA Link 6".

7-63
7-64

7-65
Figure 7-55 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH 6) 7) Click <OK> to complete the modification of No.1 AAL2 PATH properties. Repeat steps 1)6) twice to modify the properties of AAL2 PATHs 2 and 3.
7-66

7-67

7-68
7-69
1 Figure 7-59 Modifying virtual port properties of CCP 6) 7) Click <OK> to complete the modification of No.0 CCP properties. Repeat steps 1)6) twice to modify the properties of CCPs 1 and 2.


I. Adding an IMA Group
1) 2) 3) Log in to the Configuration Management System of the NodeB4. Open the NodeB4 configuration file. 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) 5) Click <OK> to delete UNI link 6. Repeat steps 1)4) to delete UNI link 7.
7-70
6)
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-60.
7)
Set [NDTI Board No.] to Master Cabinet Baseband Subrack No.22 NDTI Board.
Figure 7-60 Adding an IMA group 8) 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-61. 9) Set [IMA Link No.] to "IMA Link 6".
7-71
II. Modifying the VPI Range

1) 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 displayed, as shown in Figure 7-62. 2) 3) Select the [VPI Range] tab. Modify the max VPI to 6.
7-72
Figure 7-62 Modifying the VPI range of master cabinet baseband subrack No.22 NDTI board 4) 5) Click <OK> to complete the modification of the VPI range. Right-click [Physical Object Tree / Master Cabinet / Baseband Subrack / No.23 NAOI Board] and then click [Modify NAOI Board] on the shortcut menu. The [Modify Master Cabinet Baseband Subrack No.23 NAOI Board Properties] is displayed, as shown in Figure 7-63. 6) 7) Select the [VPI Range] tab. Modify the max VPI to 6.
7-73
Figure 7-63 Modifying the VPI range of master cabinet baseband subrack No.23 NAOI board 8) Click <OK> to complete the modification of the VPI range.
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) Select the [Basic Properties] tab. Enter the data planned in section 7.7.1 .
7-74
. Figure 7-64 Adding basic properties of the networking PVC 4) 5) Select the [Source Port] tab. Enter the data planned in section 7.7.1 , as shown in Figure 7-65.
Figure 7-65 Adding the source port of the networking PVC

7-75
6) 7)
Select the [Destination Port] tab. Enter the data planned in section 7.7.1 , as shown in Figure 7-66.
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.

As shown in Figure 7-67, the RNC and NodeB6 are connected with each other through 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
NodeB6 E1/T1 E1/T1
RNC
E1/T1
PDH
E1/T1
BTS
BSC

The following table gives a planning example of RNC-NodeB6 interconnection data. Table 7-18 RNC-NodeB6 interconnection data planning Item Cell ATM address of NodeB6 Data planning 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. 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) Refer to Table 7-19 Refer to Table 7-20
Cable and timeslot
Iub physical port outgoing from RNC Iub physical port outgoing from NodeB6 RNC-NodeB6 signalling links in control plane RNC-NodeB6 channels in user plane
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
Table 7-19 lists the data negotiation and planning for RNC-NodeB6 SAAL links in the 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. Table 7-19 Data negotiation and planning for RNC-NodeB6 signalling links in control plane SAAL link usage NCP CCP 0 ALCAP Service type RTVBR RTVBR RTVBR PCR (kbps) 55 55 55 SCR (kbps) 51 51 51 V P VCI I 6 32 6 33 6 34 Terminating WRBS No. 1 1 1 Terminating WSPU subsystem No. 0 0 0 SAAL link No. 47 48 49
Traffic description
Table 7-20 lists the data negotiation and planning for RNC-NodeB6 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 NodeB6. Table 7-20 Data negotiation and planning for RNC-NodeB6 channels in user plane AAL2 PATH ID 1 Service type RTVBR Traffic description NOCLPNOSCRCDVT PCR (kbps) 1115 SCR (kbps) 1100 V P VCI I 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

//Add an ATM traffic record for an SAAL UNI link over the Iub interface. The traffic record index is 112. If this index is already configured over another interface, it need not be configured here.

ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=47, CARRYSR=LOCAL, ENBAPSF=OFF, CARRYT=FRAATM, CARRYFRAATMLNKN=0, TXTRFX=112, RXTRFX=112, SAALLNKT=UNI, CARRYSN=0, CARRYVPI=6, CARRYVCI=32; ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=48, CARRYSR=LOCAL, ENBAPSF=OFF, CARRYT=FRAATM, CARRYFRAATMLNKN=0, TXTRFX=112, RXTRFX=112, SAALLNKT=UNI, CARRYSN=0, CARRYVPI=6, CARRYVCI=33; ADD SAALLNK: SRN=1, SSN=0, SAALLNKN=49, CARRYSR=LOCAL, ENBAPSF=OFF, CARRYT=FRAATM, CARRYFRAATMLNKN=0, TXTRFX=112, RXTRFX=112, SAALLNKT=UNI, CARRYSN=0, CARRYVPI=6, CARRYVCI=34;

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


ADD CCP: NODEBNAME="NodeB6", PN=0, SAALLNKN=48;

7-79

//Add an AAL2 PATH to the ALCAP adjacent node, that is, the NodeB6. The AAL2 PATH ID is 1.
ADD AAL2PATH: ANI=16, PATHID=1, ENDSRN=1, ENDSN=0, CARRYSR=LOCAL, CARRYT=FRAATM, CARRYFRAATMLNKN=0, TXTRFX=113, RXTRFX=113, CONTROLSSN=0, OWNERSHIP=LOCAL, CARRYSN=0, CARRYVPI=6, CARRYVCI=40;


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
Figure 7-68 Adding a Fractional ATM link 3) Click <OK> to complete the addition of a Fractional ATM link.

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-69. 2) 3) Select the [Basic Properties] tab. Enter the ALCAP data planned in section 7.8.1 .
7-81
Figure 7-69 Modifying basic properties of master cabinet ALCAP 4) 5) Select the [Virtual Port] tab. Enter the ALCAP data planned in section 7.8.1 , as shown in Figure 7-70.
Figure 7-70 Modifying virtual port properties of master cabinet ALCAP
7-82
6)
Click <OK> to complete the modification of ALCAP 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-71. 2) 3) Select the [Basic Properties] tab. Enter the ALL2 PATH data planned in section 7.8.1 .
Figure 7-71 Modifying basic properties of master cabinet ALCAP No.1 AAL2 PATH 4) 5) Select the [Virtual Port] tab. Enter the AAL2 PATH data planned in section 7.8.1 , as shown in Figure 7-72.
7-83
Figure 7-72 Modifying virtual port properties of master cabinet ALCAP No.1 AAL2 PATH 6) Click <OK> to complete the modification of No.1 AAL2 PATH 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-73. 2) 3) Select the [Basic Properties] tab. Enter the NCP data planned in section 7.8.1 .
7-84
Figure 7-73 Modifying basic properties of NCP 4) 5) Select the [Virtual Port] tab. Enter the NCP data planned in section 7.8.1 , as shown in Figure 7-74.
7-85

Figure 7-75 Modifying basic properties of CCP 4) 5) Select the [Virtual Port] tab. Enter the CCP data planned in section 7.8.1 , as shown in Figure 7-76.
7-86
Figure 7-76 Modifying virtual port properties of CCP 6) Click <OK> to complete the modification of CCP properties.


7-87
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 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 z z z 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

Sector 2 Sector 0
Sector 1
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 Frequency 1 Frequency 2 0 3 1 4 Sector 1 2 5 Sector 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
Sector 0
Sector 1
Sector 2
Sector 0
Sector 1
Sector2
N D D L 0
0 1
N T R X 0
N T R X 1
N D D L 2
6 7
N T R X 4
N T R X 5
N D D L 4
12
N T R X 8
N T R X 9
3 4 5
8 9 10 11
13 14 15 16 17
18
19
N L P A 0
0
N L P A 1
1
N L P A 2
2
N L P A 3
3
N L P A 4
4
N L P A 5
5
Figure 8-2 Physical resource planning

z
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 (2-way) DL frequency (MHz) UL frequency (MHz) DL primary scramble Time offset (chip)
0 1
0 1
Receiver diversity; transmit
2120
1930
0 1
0 256
8-3
Logical Cell ID
Local Cell ID
BTS3812 Half subrack resource pool
RD/TD* mode (2-way) non-diver sity
DL frequency (MHz)
UL frequency (MHz)
DL primary scramble
Time offset (chip)
2 3 4 5
2 3 4 5
2 2115 1925 4 5 6
512 0 256 512
RD/TD*: Receive Diversity and Transmit Diversity
z z z
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 4 8 Command physical channel name PRACH SCCPCH#1 1 4 5 3 Common transport channel ID Common transport channel name RACH FACH (signalling) FACH (traffic) PCH Common physical channel ID 6 --10 Command physical channel name AICH --PICH
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 4 8 Command physical channel name PRACH SCCPCH#1 1 4 5 Common transport channel ID Common transport channel name RACH FACH (signalling) FACH (service) Common physical channel ID 6 --Command physical channel name AICH ---
8-4
Common physical channel ID
Command physical channel name 3
Common transport channel ID
Common transport channel name PCH FACH (signalling) FACH (service)
Common physical channel ID 10 ---
Command physical channel name PICH ---
SCCPCH#2
6 7
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 4 5 8 Command physical channel name PRACH PRACH SCCPCH#1 Common transport channel ID 1 2 4 5 3 Common transport channel name RACH RACH FACH (signalling) FACH (traffic) PCH 6 7 --10 Common physical channel ID Command physical channel name AICH AICH --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: CELLID=0, CELLNAME="Cell0", UARFCNUPLINK=9650, LAC=H'0001,
UARFCNDOWNLINK=10600,
PSCRAMBCODE=0,
TCELL=CHIP0,
SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, URANUM=D2, URA1=0, URA2=1, NODEBNAME="NodeB1", PCPICHPOWER=330; LOCELL=0, SUPBMC=FALSE, MAXTXPOWER=430,
II. Configuring Logical Cell 1

8-5

ADD QUICKCELLSETUP: CELLID=1,

CELLNAME="Cell1", UARFCNUPLINK=9650, LAC=H'0001,
PSCRAMBCODE=1,
TCELL=CHIP256,
III. Configuring Logical Cell 2

PSCRAMBCODE=2,
TCELL=CHIP512,
IV. Configuring Logical Cell 3

PSCRAMBCODE=3,
TCELL=CHIP0,
SAC=H'0000, CFGRACIND=REQUIRE, RAC=H'00, URANUM=D2, URA1=0, URA2=1, NODEBNAME="NodeB1", PCPICHPOWER=330; MOD CELL: CELLID=3; MAXTXPOWER=460, PCPICHPOWER=360; LOCELL=3, SUPBMC=FALSE, MAXTXPOWER=430,
V. Configuring Logical Cell 4

PSCRAMBCODE=4,
TCELL=CHIP256,
//Add basic information for SCCPCH 9 (that is, SCCPCH#2).

ADD SCCPCHBASIC: CELLID=4, PHYCHID=9, SCCPCHOFFSET=50, SCRAMBCODE=0, STTDIND=FALSE, PO1=8, PO3=12, SLOTFORMAT=D8, CTFCSIZE=BIT4, TFCIPRESENCE=EXISTS,
PILOTSYMBOLEXIST=NOT_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; ADD SCCPCHTFC: CELLID=4, PHYCHID=9, CTFC=1;
8-6
ADD SCCPCHTFC: CELLID=4, PHYCHID=9, CTFC=2; ADD SCCPCHTFC: CELLID=4, PHYCHID=9, CTFC=3; ADD SCCPCHTFC: CELLID=4, PHYCHID=9, CTFC=4; ADD SCCPCHTFC: CELLID=4, PHYCHID=9, CTFC=5;
//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

PSCRAMBCODE=5,
TCELL=CHIP512,
//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,
GAINFACTORBETAC=11, GAINFACTORBETAD=15; ADD PRACHTFC: CELLID=5, PHYCHID=5, CTFC=1, POWEROFFSETPPM=0,
8-7
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, ACCESSSERVICECLASS=ASC0,
AVAILABLESIGNATURESTARTINDEX=0, AVAILABLESUBCHANNELNUMBER=15; ADD PRACHASC: CELLID=5,
AVAILABLESIGNATUREENDINDEX=7,
PHYCHID=5,
ACCESSSERVICECLASS=ASC1,
AVAILABLESIGNATURESTARTINDEX=0, AVAILABLESUBCHANNELNUMBER=15;
AVAILABLESIGNATUREENDINDEX=7,
//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) Log in to the Configuration Management System of the NodeB1. Open the NodeB1 configuration file. 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) Select the [Basic Properties] tab. Enter the data planned in section 8.2.1 .
8-8
Figure 8-3 Modifying local cell properties 6) 7) 8) Click <OK> to complete the modification of local cell 0. Repeat steps 3) to 6) to modify local cells 15. 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) 4) 5) 6) Log in to the Configuration Management System of the NodeB1. Open the NodeB1 configuration file. Select [File/Save]. The [Save as] dialog box is displayed. Enter the configuration file name and select .xml as the file type. Click <Save>. The system starts data check and download the data to the host of the NodeB1. Restart the NodeB1.
II. Commissioning Cell Data on RNC

1) 2) 3) Activate each cell using the ACT CELL command. View the setup procedure of each cell by tracing the Iub interface. Query the availability status of each cell using the DSP CELL command. Normally, the status is Zero.
8-9
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 0 Cell 2 Cell Y
Cell M
Cell N
Figure 8-4 Intra-frequency neighboring cells of cell 0 The intra-frequency neighboring cells of cell 0 are planned as follows:
z 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
ADD INTRAFREQCELL: CELLID=0, RNCID=0, NCELLID=1, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, CELLSFORBIDDEN1A=AFFECT,
CELLSFORBIDDEN1B=AFFECT, QOFFSET1SN=0, QOFFSET2SN=0; ADD INTRAFREQCELL: CELLID=0, RNCID=0, NCELLID=2, 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, RAC=H'01, UARFCNDOWNLINK=10600, LAC=H'0001, 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.

ADD NRNCCELL: RNCID=1, CELLID=2, CELLNAME="Cell 2", PSCRAMBCODE=2, UARFCNUPLINK=9650, TXDIVERSITYIND=FALSE, RAC=H'01, HIGHRATERLACTTIMEDEFOFFVAL=80, UARFCNDOWNLINK=10600, LAC=H'0001, SAC=H'0001, SUPSSDT=FALSE, CFGRACIND=REQUIRE,
LOWRATERLACTTIMEDEFOFFVAL=180, 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) 2) Query the status of each intra-frequency neighboring cell of cell 0 using the DSP CELL command. 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
8.4 Inter-Frequency Neighboring Cell Data Configuration

8.4.1 Planning Inter-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-5 shows the planned inter-frequency neighboring cells of cell 0.
Cell x Cell 5 Cell 0 Cell 4 Cell y
Cell m
Cell n
Figure 8-5 Inter-frequency neighboring cells of cell 0 The inter-frequency neighboring cells of cell 0 are planned as follows:
z 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
ADD INTERFREQCELL: CELLID=0, RNCID=0, NCELLID=4, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QOFFSET2SN=0; ADD INTERFREQCELL: CELLID=0, RNCID=0, NCELLID=5, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QOFFSET2SN=0; ADD INTERFREQCELL: CELLID=0, RNCID=0, NCELLID=11, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QOFFSET2SN=0; ADD INTERFREQCELL: CELLID=0, RNCID=0, NCELLID=21, 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.
ADD NRNCCELL: RNCID=1, CELLID=4, CELLNAME="Cell 4", PSCRAMBCODE=4, UARFCNDOWNLINK=10560, SUPSSDT=FALSE, TXDIVERSITYIND=FALSE, LAC=H'0001, SAC=H'0001, CFGRACIND=REQUIRE, RAC=H'01, LOWRATERLACTTIMEDEFOFFVAL=180, HIGHRATERLACTTIMEDEFOFFVAL=80, ACTTIMEDEFOFFVALHHO=100;
//Configure cell m as an inter-frequency neighboring cell of cell 0.

ADD INTERFREQCELL: CELLID=0, RNCID=1, NCELLID=4, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QOFFSET2SN=0;
//Configure the basic information of cell n that belongs to RNC 1.

ADD NRNCCELL: RNCID=1, CELLID=5, CELLNAME="Cell 5", PSCRAMBCODE=5, UARFCNDOWNLINK=10560, SUPSSDT=FALSE, TXDIVERSITYIND=FALSE, LAC=H'0001, SAC=H'0001, CFGRACIND=REQUIRE, RAC=H'01, LOWRATERLACTTIMEDEFOFFVAL=180, HIGHRATERLACTTIMEDEFOFFVAL=80, ACTTIMEDEFOFFVALHHO=100;
//Configure cell n as an inter-frequency neighboring cell of cell 0.

ADD INTERFREQCELL: CELLID=0, RNCID=1, NCELLID=5, READSFNIND=NOT_READ, CELLINDIVIDALOFFSET=0, QOFFSET1SN=0, QOFFSET2SN=0;
8.4.3 Checking Inter-Frequency Neighboring Cell Data

To check inter-frequency neighboring cell data, operate as follows: 1) 2) Query the status of each inter-frequency neighboring cell of cell 0 using the DSP CELL command. 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-13
8.5 Concentric Inter-Frequency Neighboring Cell Data Configuration

8.5.1 Planning Concentric Inter-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-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
G_Cell 2 G_Cell 1 Cell 0 G_Cell 0 G_Cell 5
G_Cell 3
G_Cell 4
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 G_Cell 0 G_Cell 1 G_Cell 2 G_Cell 3 G_Cell 4 G_Cell 5 Local area code H0001 H0001 H0001 H0002 H0002 H0002 Network color code 0 0 0 1 1 1 Base station color code 0 0 0 1 1 1 BCCH frequency number 0 10 20 30 40 50 Cell type GSM_AND_GPRS GSM_AND_GPRS GSM_AND_GPRS GSM_AND_GPRS GSM_AND_GPRS 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




8.6.3 Checking Inter-RAT Neighboring Cell Data

To check the inter-RAT neighboring cell data, operate as follows: 1) 2) Query the status of each inter-RAT neighboring cell of cell 0 using the DSP CELL command. 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-16
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

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) 2) Local O&M Channel Configuration 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
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) 2) 3) 4) 5) 6)
Select [Start / Settings / Control Panel] on the LMT. Double-click the Network and Dial-up Connections icon. Right-click [Local Area Connection] and then click [Properties] on the shortcut menu. The [Local Area Connection Properties] dialog box is displayed. In the [General] tab, double-click Internet Protocol (TCP/IP). The [Internet Protocol (TCP/IP) Properties] dialog log box is displayed. Select Use the following IP address. Enter the IP address of the LMT, as shown in Figure 9-2.
Figure 9-2 Modifying IP address of LMT
9-3
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 displayed, as shown in Figure 9-3.
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
Figure 9-5 Office information 4) 5) 6) 7) 8) Enter the default IP address of NMPT mentioned in 9.2.1 . Click <OK>. The [Office Management] dialog box is displayed again. Click <OK>. The [Login] dialog box is displayed again. Type admin in the [User name] box, NodeB in the [Password] box, and select the office you just configured. Click <OK> to log in to the NMPT.
III. Modifying the IP Address of the NMPT

1) 2) 3) 4) 5) 6) Select [Service / Configuration Management System]. The [Select Version] dialog box is displayed. Select a version. Click <OK> to start the corresponding configuration management system. Select [File/Open ]. Open the NodeB1 configuration file. 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 is displayed, as shown in Figure 9-6. 7) Enter the data planned in 9.2.1 , that is, the planned IP address of NMPT.
9-5
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 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 Subnet F
WMUX
NodeB1
NodeB2 Subnet N2 LMT
NodeB40 Subnet 40 LMT
Subnet N1 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 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
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 A Subnet B Subnet C Subnet D Subnet E Subnet F Subnet N1 Subnet N2 Subnet 40 Subnet 10.1.1.0 10.1.2.0 10.1.3.0 10.1.4.0 192.1.1.0 10.1.10.1 10.1.40.16 10.1.40.32 10.1.42.128 Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.248 255.255.255.248 255.255.255.248 Remarks Planned IP subnet Planned IP subnet Planned IP subnet Planned IP subnet Automatically generated by system Planned IP subnet Planned IP subnet Planned IP subnet 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 Port of subnet A Port of subnet A Port of subnet B Port of subnet B IP address 10.1.1.1 10.1.1.2 10.1.2.1 10.1.2.2 Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0
9-8
Equipment
Port Port of subnet C Port of subnet C (in the external network) Port of subnet D (in the internal network) Port of subnet D Port of subnet E Port of subnet E Port of subnet F Port of subnet F Port of subnet N1 Port of subnet F Port of subnet N2 Port of subnet F Port of subnet 80
IP address 10.1.3.1 10.1.3.2 10.1.4.1 10.1.4.2 192.1.1.254 192.1.1.1 10.1.10.1 10.1.10.10 10.1.40.16 10.1.10.11 10.1.40.32 10.1.10.50 10.1.42.128
Subnet mask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.248 255.255.255.0 255.255.255.248 255.255.255.0 255.255.255.248
BAM
WMPU
WMUX (WRBS1)
NodeB1
NodeB2 Node40
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.
z z
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 M2000 Server Fire Wall Gate Way Route planning Route to subnet F with the next hop of the IP address of Fire Wall Route to subnet F with the next hop of the IP address of Gate Way Route to subnet F with the next hop of the IP address of BAM
9-9
Node BAM WMPU
Route planning Route to subnet F with the next hop of the IP address of 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 NodeB1 LMT NodeB1 WMUX WMPU BAM Gate Way Route planning Route to subnet A with the next hop of the IP address of the NMPT of he NodeB1 Route to subnet A with the next hop of the IP address of the WMUX Route to subnet A with the next hop of the IP address of the WMPU Route to subnet A with the next hop of the internal IP address of the BAM Route to subnet A with the next hop of the IP address of the Gate Way Route to subnet A with the next hop of the IP 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 PCR (kbps) 84 64 SCR (kbps) 1 VPI VCI 33
9-10
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) 2) Log in to the Solaris system of the M2000 server as a root user. 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 index is 130. If this index is already configured over another interface, it need not be 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.
MASK="255.255.255.0";
IV. Configuring IPoA PVC

//Configuring an IPoA PVC.
9-11
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, CARRYVCI=33; TXTRFX=130, RXTRFX=130, CARRYSN=0, CARRYVPI=1,
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) 2) 3) 4) 5) 6) 7) Select [Start / Settings / Control Panel]. Double-click [Administrative Tools]. Double-click [Services]. The [Services] dialog box is displayed. Double-click [Routing and Remote Access]. Select the [General] tab. Modify [Startup type] to Automatic. Click <OK>.
//Configure the route to the NodeB on the BAM server. 1) 2) 3) Select [File/Run ]. Type cmd. The [cmd.exe] dialog box is displayed. 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) 2) 3) Select [File/Run ]. Type cmd. The [cmd.exe] dialog box is displayed. 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.

//Configure the route to the M2000 on the WMPU.

//Configure the route to the M2000 on the WMUX.

9-12
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) Log in to the Configuration Management System of the NodeB1. Open the NodeB1 configuration file. 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) Select the [Basic Properties] tab. Enter the data planned in section 9.3.1 .
Figure 9-8 Modifying basic properties of IPoA device 6) 7) Select the [Virtual Port] tab. Enter the data planned in section 9.3.1 , as shown in Figure 9-9.
9-13
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) 2) Check whether the IPoA address of the NodeB can be reached by the Ping command on the M2000. Check whether the address of the M2000 can be reached by the Ping command on the NodeB1 LMT.
9-14
Appendix Acronyms and Abbreviations

A AAL2 ADM AICH AIS ALCAP APS ATM B BAM BCCH BSC BSC6800 BSS BTS2812 C CBC CBR CCP CS D DDN G GPRS GSM I IMA IP IPoA L Inverse Multiplexing on ATM Internet Protocol Internet Protocols over ATM General Packet Radio Service Global System for Mobile Communications Digital Data Network Cell Broadcast Center Constant Bit Rate Common Communication Port Circuit-Switched Back Administration Module Broadcast Control CHannel Base Station Controller Huawei RNC Model Base Station Subsystem Huawei NodeB Model ATM Adaptation Layer type 2 add/drop multiplexer Acquisition Indicator Channel Alarm Indication Signal Access Link Control Application Part Automatic Protection Switch(ing) Asynchronous Transfer Mode
F-1
LAC LMT M MCC MGW MML MNC MSC MSP MTP3B N NAOI NCC NCP NDTI NMPT P PCH PCIPCH PCR PDH PICH PLMN PRACH PS PVC R RAC RACH RAN RANAP RFN RNC S
Location Area Code Local Maintenance Terminal
Mobile Country Code Media GateWay
Man Machine Language Mobile Network Code Mobile Service Switching Center Multiplex Section Protection Message transfer part (broadband)
NodeB ATM Optical Interface unit Network Color Code NodeB Control Port NodeB Digital Trunk Interface unit NodeB Main Processor & Timing unit
Paging Channel Primary Common Pilot CHannel Peak Cell Rate Plesiochronous Digital Hierarchy Paging indicator channel Public Land Mobile Network Packet Random Access Channel Packet Switched Permanent Virtual Channel
Routing Area Code Random Access CHannel Radio Access Network Radio Access Network Application Part RNC Frame Number counter Radio Network Controller
F-2
SAAL SABP SCCP SCCPCH SDH SGSN STM-1 STP T TFC TS U UBR UE UMTS URA V VC W WBIE WCDMA WFMR WHPU WLPU WMPU WMUX WNET WOSE WRBS WRSS WSPU
Signaling ATM Adaptation Layer Service Area Broadcast Protocol Signaling Connection and Control Part Secondary Common Control Physical Channel Synchronous Digital Hierarchy Serving GPRS Support Node Synchronous Transport Mode-1 Signaling Transfer Point
Transport Format Combination Time Slot
Unspecified Bit Rate User Equipment Universal mobile telecommunication services/Universal Mobile Telecommunications System UTRAN Registration Area
Virtual Circuit
WCDMA RNC BaseStation Interface Board Wideband CDMA WCDMA RNC Radio Frame processing board WCDMA RNC High speed Packet processing board WCDMA RNC Line Process Unit WCDMA RNC Main Process Unit WCDMA RNC system MUltipleXer unit WCDMA RNC NETwork switch board WCDMA RNC Single mode Optical interface board of E1/T1 WCDMA RNC Business Subrack WCDMA RNC Switch Subrack WCDMA Signaling Process Unit
F-3
Index
Index
C
cell and neighboring cell data, 8-1 cell data configuration, 8-1 checking concentric inter-frequency neighboring cell data, 8-14 inter-frequency neighboring cell data, 8-13 inter-RAT neighboring cell data, 8-16 intra-frequency neighboring cell data, 8-11 local O&M channel data, 9-6 remote O&M channel data, 9-14 RNC-CBC interconnection data, 5-4 RNC-MSC (R4) interconnection data, 3-12 RNC-MSC (R99) interconnection data, 3-6 RNC-NodeB1 interconnection data, 7-17 RNC-NodeB2 interconnection data, 7-31 RNC-NodeB3 interconnection data, 7-46 RNC-NodeB4 interconnection data, 7-58 RNC-NodeB6 interconnection data, 7-87 RNC-RNC interconnection data, 6-8 RNC-SGSN interconnection data, 4-6 commissioning cell data, 8-9 on NodeB1, 8-9 on RNC, 8-9 RNC basic data, 2-8 concentric inter-frequency neighboring cell data, 8-14 configuration precondition cell and neighboring cell, 8-1 NodeB O&M channel, 9-2 RNC basic data configuraiton, 2-1 RNC-CBC interconnection, 5-1 RNC-MSC interconnection, 3-1 RNC-NodeB interconnection, 7-1 RNC-RNC connection, 6-1 RNC-SGSN interconnection, 4-1 configuration procedure configuration example, 1-1 NodeB O&M channel, 9-2 RNC basic data configuration, 2-1 RNC-CBC interconnection, 5-1 RNC-MSC interconnection, 3-1 RNC-NodeB interconnection, 7-1 RNC-RNC connection, 6-1 RNC-SGSN interconnection, 4-1 configuration purpose cell and neighboring cell, 8-1 NodeB O&M channel, 9-1 RNC basic data configuration, 2-1 RNC-CBC interconnection, 5-1 RNC-MSC interconnection, 3-1 RNC-NodeB interconnection, 7-1 RNC-RNC connection, 6-1 RNC-SGSN interconnection, 4-1 configuring concentric inter-frequency neighboring cell on RNC, 8-14 inter-frequency neighboring cell on RNC, 8-12 inter-RAT neighboring cell on RNC, 8-15 intra-frequency neighboring cell on RNC, 8-10 local cell data on NodeB1, 8-8 local O&M channel data, 9-3 logical cell data on RNC, 8-5 remote O&M channel data on M2000, 9-11 remote O&M channel data on NodeB, 9-13 remote O&M channel data on RNC, 9-11 RNC basic data, 2-6 RNC-CBC interconnection data, 5-3 RNC-MSC (R4) interconnection data, 3-9 RNC-MSC (R99) interconnection data, 3-3 RNC-NodeB1 interconnection data on NodeB1, 7-9 RNC-NodeB1 interconnection data on RNC, 7-6
i-1
Configuration Example HUAWEI UMTS Radio Access Network RNC-NodeB2 interconnection data on NodeB2, 7-22 RNC-NodeB2 interconnection data on RNC, 7-20 RNC-NodeB3 interconnection data on NodeB2, 7-42 RNC-NodeB3 interconnection data on NodeB3, 7-35 RNC-NodeB3 interconnection data on RNC, 7-33 RNC-NodeB4 interconnection data on NodeB4, 7-50 RNC-NodeB4 interconnection data on RNC, 7-48 RNC-NodeB5 interconnection data on NodeB4, 7-70 RNC-NodeB5 interconnection data on NodeB5, 7-62 RNC-NodeB5 interconnection data on RNC, 7-60 RNC-NodeB6 interconnection data on NodeB6, 7-80 RNC-NodeB6 interconnection data on RNC, 7-78 RNC-RNC interconnection data, 6-4 RNC-SGSN interconnection data, 4-3 inter-RAT neighboring cell data, 8-14 intra-frequency neighboring cell data, 8-10
Index
L
local O&M channel configuration, 9-2
N
NodeB O&M channel configuration, 9-1
P
planning cell data, 8-1 concentric inter-frequency neighboring cell data, 8-14 inter-frequency neighboring cell data, 8-12 inter-RAT neighboring cell data, 8-14 intra-frequency neighboring cell data, 8-10 local O&M channel data, 9-2 NodeB O&M channel IP address, 9-8 IP route, 9-9 IP subnet, 9-8 IPoA PVC, 9-10 remote O&M channel data, 9-6 RNC basic bata subrack data, 2-3 RNC basic data, 2-1 clock source data, 2-6 local office data, 2-2 OSP data, 2-6 WLPU optical port, 2-5 RNC-CBC interconnection data, 5-1 RNC-MSC (R4) interconnection data, 3-7 RNC-NodeB1 interconnection data, 7-4 RNC-NodeB2 interconnection data, 7-17 RNC-NodeB3 interconnection data, 7-31 RNC-NodeB4 interconnection data, 7-46 RNC-NodeB5 interconnection data, 7-58 RNC-NodeB6 interconnection data, 7-76 RNC-RNC interconnection data, 6-1 RNC-SGSN interconnection data, 4-1 Planning
D
data configuration references, 1-2 data configuration tools, 1-2 data planning example RNC-CBC interconnection, 5-2 RNC-MSC interconnection, 3-7 RNC-NodeB interconnection, 7-3 RNC-NodeB1 interconnection, 7-5 RNC-NodeB2 interconnection, 7-18 RNC-NodeB3 interconnection, 7-32 RNC-NodeB4 interconnection, 7-47 RNC-NodeB5 interconnection, 7-58 RNC-NodeB6 interconnection, 7-77 RNC-RNC interconnection, 6-2 RNC-SGSN interconnection, 4-2 data planning Example RNC-MSC interconnection, 3-2
I
inter-frequency neighboring cell data, 8-12
i-2
Configuration Example HUAWEI UMTS Radio Access Network RNC-MSC (R99) Interconnection Data, 3-2
Index RNC-NodeB4 interconnection data configuration, 7-46 RNC-NodeB5 interconnection data configuration, 7-58 RNC-NodeB6 interconnection data configuration, 7-76 RNC-RNC interconnection data configuration, 6-1 RNC-SGSN interconnection data configuration, 4-1
R
remote O&M channel configuration, 9-6 RNC basic data configuration, 2-1 RNC identification information, 2-2 RNC location information, 2-2 RNC SIB1 information, 2-3 RNC-CBC interconnection data configuration, 5-1 RNC-MSC (R4) interconnection data configuration, 3-7 RNC-MSC (R99) interconnection data configuration, 3-2 RNC-MSC interconnection data configuration, 3-1 RNC-NodeB interconnection data configuration, 7-1 RNC-NodeB network topology, 7-2 RNC-NodeB1 interconnection data configuration, 7-4 RNC-NodeB2 interconnection data configuration, 7-17 RNC-NodeB3 interconnection data configuration, 7-31
T
typical network topology NodeB O&M channel, 9-6 RNC-CBC interconnection, 5-1 RNC-MSC interconnection, 3-2, 3-7 RNC-NodeB interconnection, 7-2 RNC-NodeB1 interconnection, 7-4 RNC-NodeB2 interconnection, 7-17 RNC-NodeB3 interconnection, 7-31 RNC-NodeB4 interconnection, 7-46 RNC-NodeB5 interconnection, 7-58 RNC-NodeB6 interconnection, 7-76 RNC-RNC interconnection, 6-1 RNC-SGSN interconnection, 4-1
i.
i-3

UMTS Radio Access Network Configuration Example

Uploaded by

Document Information

Original Description:

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 ................................................................................................ 1.2 Data Configuration Tasks and Procedure ..............................................

HUAWEI UMTS Radio Access Network Configuration Example

HUAWEI UMTS Radio Access Network Configuration Example

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

About This Manual

Organization of the Manual

The manual is intended for the following readers:

Technical support and engineers Telecommunication administration staff

II. GUI conventions

III. Mouse operation

Configuration Example HUAWEI UMTS Radio Access Network

Configuration Example HUAWEI UMTS Radio Access Network

Configuration Example HUAWEI UMTS Radio Access Network

Configuration Example HUAWEI UMTS Radio Access Network

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 1 Introduction to Data Configuration

Chapter 1 Introduction to Data Configuration

1.2 Data Configuration Tasks and Procedure

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

Configure NodeB O&M channel

Figure 1-1 Configuration tasks and procedure

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 1 Introduction to Data Configuration

1.3 Data Configuration References

1.4 Data Configuration Tools

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 2 RNC Basic Data Configuration

Chapter 2 RNC Basic Data Configuration

2.1.2 Configuration Precondition

2.1.3 Configuration Procedure

2.2 RNC Basic Data Configuration

Planning Clock Source Data Planning OSP Data

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 2 RNC Basic Data Configuration

II. Planning Local Office Data

RNC identification information

RNC location information

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 2 RNC Basic Data Configuration

RNC SIB1 information

III. Planning Subrack Data

Table 2-4 lists the configurations of the above three subracks:

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 2 RNC Basic Data Configuration

Figure 2-2 WRSS configuration

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 2 RNC Basic Data Configuration

Figure 2-3 WRBS1 configuration

Figure 2-4 WRBS3 configuration

IV. Planning WLPU Optical Port

Configuration Example HUAWEI UMTS Radio Access Network

Chapter 2 RNC Basic Data Configuration

WLPU optical port number 14 15 Connected to SGSN Reserved