BTS3802C Operation Manual-Data Configuration

Chapter 1 Introduction to Configuration Management System .................. 1.1 Overview ................................................................................................ 1.2 Configuration Management System Interface ........................................
1.3 MIT Navigation Tree ............................................................................... 1.4 NodeB-Level Properties and Cabinet-Level Properties .......................... 1.5 Equipment Panel .................................................................................... Chapter 2 Overview of NodeB Data Configuration ....................................... 2.1 Overview ................................................................................................ 2.2 Tools for NodeB Data Configuration ...................................................... 2.3 Template and Configuration File ............................................................ 2.3.1 Name of Configuration File and Template ..................................... 2.3.2 Usage of Template and Configuration File .................................... 2.4 Data Conflict ........................................................................................... 2.5 Key Properties of Template .................................................................... 2.6 Configuration File Editing vs. Equivalent MML Command ..................... 2.6.1 Equivalent MML Commands .......................................................... 2.6.2 Operations with No Equivalent MML Commands .......................... 2.6.3 Dynamic Commands and Static Commands ................................. Chapter 3 NodeB Initial Configuration Process ............................................ 3.1 Overview of NodeB Initial Configuration Process ................................... 3.2 Comprehensive NodeB Initial Configuration Process ............................ 3.2.1 Networking Condition ..................................................................... 3.2.2 Process of Comprehensive NodeB Initial Configuration ................ 3.3 Simplified NodeB Initial configuration Process ....................................... 3.3.1 Simplification Requirements .......................................................... 3.3.2 Simplified NodeB Initial Configuration Sequence .......................... Chapter 4 Common Procedures-Configuration File and Applying Data .... 4.1 Starting Configuration Management System.......................................... 4.1.1 Overview ........................................................................................ 4.1.2 Points for attention ......................................................................... 4.1.3 Procedure ...................................................................................... 4.2 Creating a Configuration File Using a Template .................................... 4.2.1 Overview ........................................................................................ 4.2.2 Points for Attention ......................................................................... 4.2.3 Procedure ...................................................................................... 4.3 Creating a Configuration File without Template ..................................... 4.3.1 Overview ........................................................................................ 4.3.2 Points for Attention .........................................................................
1-1 1-1 1-1 1-2 1-3 1-4 2-1 2-1 2-1 2-2 2-2 2-2 2-3 2-3 2-4 2-4 2-4 2-5 3-1 3-1 3-1 3-1 3-2 3-5 3-5 3-6 4-1 4-1 4-1 4-1 4-1 4-2 4-2 4-2 4-2 4-3 4-3 4-3
4.3.3 Procedure ...................................................................................... 4.4 Saving a Configuration File as a Template ............................................ 4.4.1 Overview ........................................................................................ 4.4.2 Points for Attention ......................................................................... 4.4.3 Procedure ...................................................................................... 4.5 Applying Configuration File Data ............................................................ 4.5.1 Overview of Applying Configuration File Data ............................... 4.5.2 Applying Data by Downloading Configuration File ......................... 4.5.3 Applying Data by Executing Equivalent MML Command............... 4.6 Checking Consistency between Configuration File Data and Running Data ............................................................................................... 4.6.1 Overview ........................................................................................ 4.6.2 Points for Attention ......................................................................... 4.6.3 Procedure ...................................................................................... Chapter 5 Local Cell Configuration Procedures ........................................... 5.1 Selecting/Modifying NodeB Configuration Type ..................................... 5.1.1 Overview ........................................................................................ 5.1.2 Points for Attention ......................................................................... 5.1.3 Procedure ...................................................................................... 5.2 Modifying Local Cell Logical Properties ................................................. 5.2.1 Overview ........................................................................................ 5.2.2 Points for Attention ......................................................................... 5.2.3 Procedure in Case of NodeB Initial Configuration ......................... 5.2.4 Procedure in Case of In-Service Property Modification ................. 5.3 Modifying NDRU Properties ................................................................... 5.3.1 Overview ........................................................................................ 5.3.2 Points for Attention ......................................................................... 5.3.3 Procedure ...................................................................................... Chapter 6 Transport Configuration Procedures ........................................... 6.1 Configuring E1/T1 as E1 or T1 ............................................................... 6.1.1 Overview ........................................................................................ 6.1.2 Points for Attention ......................................................................... 6.1.3 Procedure ...................................................................................... 6.2 Adding a UNI Link .................................................................................. 6.2.1 Overview ........................................................................................ 6.2.2 Points for Attention ......................................................................... 6.2.3 Procedure ...................................................................................... 6.3 Adding a Fractional ATM Link ................................................................ 6.3.1 Overview ........................................................................................ 6.3.2 Points for Attention .........................................................................
4-4 4-4 4-4 4-4 4-4 4-5 4-5 4-5 4-7 4-9 4-9 4-9 4-9 5-1 5-1 5-1 5-2 5-2 5-3 5-3 5-3 5-3 5-5 5-6 5-6 5-6 5-6 6-1 6-1 6-1 6-1 6-1 6-2 6-2 6-2 6-2 6-5 6-5 6-5
6.3.3 Procedure ...................................................................................... 6.4 Adding an NCP Port ............................................................................... 6.4.1 Overview ........................................................................................ 6.4.2 Points for Attention ......................................................................... 6.4.3 Procedure ...................................................................................... 6.5 Adding a CCP Port ................................................................................. 6.5.1 Overview ........................................................................................ 6.5.2 Points for Attention ......................................................................... 6.5.3 Procedure ...................................................................................... 6.6 Adding an ALCAP Node ......................................................................... 6.6.1 Overview ........................................................................................ 6.6.2 Points for Attention ......................................................................... 6.6.3 Procedure ...................................................................................... 6.7 Adding an AAL2 PATH ........................................................................... 6.7.1 Overview ........................................................................................ 6.7.2 Points for Attention ......................................................................... 6.7.3 Procedure ...................................................................................... 6.8 Expanding Iub Transport Capacity ......................................................... 6.8.1 Overview ........................................................................................ 6.8.2 Points for Attention ......................................................................... 6.8.3 Procedure ...................................................................................... 6.9 Adding a Transparent Link ..................................................................... 6.9.1 Overview ........................................................................................ 6.9.2 Points for Attention ......................................................................... 6.9.3 Procedure ...................................................................................... 6.10 Adding an SDT CES Channel .............................................................. 6.10.1 Overview ...................................................................................... 6.10.2 Points for Attention ....................................................................... 6.10.3 Procedure .................................................................................... 6.11 Adding a Treelink PVC ......................................................................... 6.11.1 Overview ...................................................................................... 6.11.2 Points for Attention ....................................................................... 6.11.3 Procedure .................................................................................... 6.12 Modifying NCP or ALCAP .................................................................... 6.12.1 Overview ...................................................................................... 6.12.2 Points for Attention ....................................................................... 6.12.3 Procedure .................................................................................... 6.13 Modifying a CCP or AAL2PATH ........................................................... 6.13.1 Overview ...................................................................................... 6.13.2 Points for Attention ....................................................................... 6.13.3 Procedure ....................................................................................
6-5 6-7 6-7 6-8 6-8 6-9 6-9 6-9 6-9 6-10 6-10 6-10 6-11 6-12 6-12 6-12 6-12 6-14 6-14 6-14 6-14 6-15 6-15 6-15 6-15 6-16 6-16 6-16 6-16 6-19 6-19 6-19 6-19 6-20 6-20 6-20 6-21 6-21 6-21 6-21 6-21
Chapter 7 Maintenance Channel Configuration Procedures ....................... 7.1 Modifying Local Maintenance Channel .................................................. 7.1.1 Overview ........................................................................................ 7.1.2 Points for attention ......................................................................... 7.1.3 Procedure ...................................................................................... 7.2 Adding IPoA Maintenance Channel ....................................................... 7.2.1 Overview ........................................................................................ 7.2.2 Points for Attention ......................................................................... 7.2.3 Procedure ...................................................................................... 7.3 Modifying IPoA Maintenance Channel ................................................... 7.3.1 Overview ........................................................................................ 7.3.2 Points for Attention ......................................................................... 7.3.3 Procedure ...................................................................................... 7.4 Modifying SNTP Properties .................................................................... 7.4.1 Overview ........................................................................................ 7.4.2 Points for Attention ......................................................................... 7.4.3 Procedure ...................................................................................... 7.5 Modifying NASU O&M Mode mode ........................................................ 7.5.1 Overview ........................................................................................ 7.5.2 Points for attention ......................................................................... 7.5.3 Procedure ...................................................................................... Chapter 8 Supplementary Configuration Procedures .................................. 8.1 Selecting Clock Source .......................................................................... 8.1.1 Overview ........................................................................................ 8.1.2 Points for Attention ......................................................................... 8.1.3 Procedure ...................................................................................... 8.2 Configuring External Alarm Ports ........................................................... 8.2.1 Overview ........................................................................................ 8.2.2 Points for Attention ......................................................................... 8.2.3 Procedure ...................................................................................... 8.3 Configuring Power Supply Mode ............................................................ 8.3.1 Overview ........................................................................................ 8.3.2 Points for Attention ......................................................................... 8.3.3 Procedure ...................................................................................... 8.4 Configuring Module Temperature Thresholds ........................................ 8.4.1 Overview ........................................................................................ 8.4.2 Points for Attention ......................................................................... 8.4.3 Procedure ...................................................................................... 8.5 Modifying Engineering Parameters ........................................................
7-1 7-1 7-1 7-1 7-1 7-2 7-2 7-2 7-2 7-4 7-4 7-4 7-4 7-5 7-5 7-5 7-5 7-7 7-7 7-7 7-7 8-1 8-1 8-1 8-1 8-1 8-4 8-4 8-4 8-4 8-6 8-6 8-6 8-6 8-8 8-8 8-9 8-9 8-11
8.5.1 Overview ........................................................................................ 8.5.2 Points for Attention ......................................................................... 8.5.3 Procedure ...................................................................................... Chapter 9 Local Cell Properties ..................................................................... 9.1 Overview of Local Cell Properties .......................................................... 9.2 Architecture of Local Cells ...................................................................... 9.3 Properties of NodeB configuration type .................................................. 9.4 Local Cell Logical Properties .................................................................. Chapter 10 Transport Properties .................................................................... 10.1 Overview of Transport Properties......................................................... 10.2 Architecture of NodeB Transport .......................................................... 10.2.1 Transport Ports ............................................................................ 10.2.2 Transport Networking and Transport Protocol Architecture ......... 10.2.3 Transport Networking Mode Selection ......................................... 10.2.4 Peers of the Transport Protocol layers ........................................ 10.3 ATM Physical Layer Bearer Properties ................................................ 10.3.1 Overview ...................................................................................... 10.3.2 UNI Link Properties ...................................................................... 10.3.3 Fraction ATM Link Properties ...................................................... 10.4 Iub Transport Object Properties ........................................................... 10.4.1 Overview ...................................................................................... 10.4.2 Architecture of Iub Transport ....................................................... 10.4.3 Properties of NCP, CCP, ALCAP, AAL2PATH and IPoA ............ 10.4.4 Determine Iub Transport Object Properties ................................. 10.5 Transparent Link Properties ................................................................. 10.5.1 Overview ...................................................................................... 10.5.2 Architecture of Transparent Link .................................................. 10.5.3 Properties of Transparent Link ..................................................... 10.6 SDT CES Channel Properties .............................................................. 10.6.1 Overview ...................................................................................... 10.6.2 Architecture of SDT CES Channel ............................................... 10.6.3 Bandwidth Planning for CES Channel ......................................... 10.6.4 Properties of CES Channel .......................................................... 10.7 Treelink PVC Properties ....................................................................... 10.7.1 Overview of Treelink PVC Properties .......................................... 10.7.2 Architecture of Treelink PVC ........................................................ 10.7.3 VPI Planning ................................................................................ 10.7.4 Bandwidth Planning for Treelink PVC .......................................... 10.7.5 Properties of Treelink PVC ..........................................................
8-11 8-11 8-11 9-1 9-1 9-1 9-2 9-3 10-1 10-1 10-1 10-1 10-2 10-6 10-7 10-8 10-8 10-8 10-8 10-9 10-9 10-10 10-11 10-11 10-12 10-12 10-12 10-12 10-13 10-13 10-13 10-14 10-14 10-15 10-15 10-15 10-16 10-16 10-16
10.8 Transport Configuration Guideline ....................................................... 10-18 10.8.1 Configure Tree Transport Network from Upper-level-segment to Lower- level- segment ......................................................................... 10-18 10.8.2 Configure Each Segment from Bottom Layer to Top Layer ......... 10-18 Chapter 11 Maintenance Channel Properties ............................................... 11.1 Overview of Maintenance Channel Configuration ................................ 11.2 Architecture of BTS3802C Maintenance channel ................................ 11.3 IP Planning ........................................................................................... 11.3.1 IP networking ............................................................................... 11.3.2 IP addresses ................................................................................ 11.3.3 IP routes....................................................................................... 11.4 IPoA Maintenance Channel Configuration Guideline ........................... Chapter 12 Transport Bandwidth Planning ................................................... 12.1 Planning Transport Bandwidth ............................................................. 12.2 Bandwidth of ATM Physical Layer Bearer ............................................ 12.3 Calculating Traffic................................................................................. 12.4 Planning Number of AAL2PATHs ........................................................ 12.5 Calculating PVC Bandwidth Consumed by a CES Channel ................ Appendix Acronyms and Abbreviations ....................................................... Index ................................................................................................................. 11-1 11-1 11-1 11-2 11-2 11-3 11-4 11-5 12-1 12-1 12-2 12-2 12-3 12-3 F-1
HUAWEI
BTS3802C WCDMA NodeB Operation Manual-Data Configuration V100R003
BTS3802C WCDMA NodeB Operation Manual

Volume Manual Version Product Version BOM Data Configuration T2-031644-20040930-C-1.31 V100R003 31161044
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office 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, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng 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-031644-20040225-C-1.30 T2-031644-20040930-C-1.31 Initial field trial release Secondary field trial release Notes
Updates Made between Versions 1.30 and 1.31

1) Separating procedure information from parameter description and optimize procedure information. 2) Adding indexes.
About This Manual

Release Notes
This manual applies to BTS3802C WCDMA NodeB Operation Manual Data Configuration V100R003
Organization
Part Part 1: Interface Description Introduce the interfaces of the configuration management system. Chapter Chap 1 Introduction Management System to Configuration
Chap 2 Overview of NodeB Data Configuration Chap 3 NodeB Initial Configuration Processes Part 2: Processes and Procedures Provide operation processes and procedures for NodeB data configuration. By following a process or procedure, you can accomplish a NodeB configuration task. Chap 4 Common Procedures-Configuration File and Applying Data Chap 5 Local Cell Configuration Procedures Chap 6 Transport Configuration Procedures Chap 7 Maintenance Channel Configuration Procedures Chap 8 Supplementary Configuration Procedure Describe the properties for NodeB data configuration. From this part, you know what the properties mean and how to determine the property values. Describe the full names of the abbreviation and acronyms used in this document Chap 9 Local Cell Properties Chap 10 Transport Properties Chap 11 Maintenance Channel Properties Chap 12 Transport Bandwidth Planning
Part 3: Properties
Part 4: Abbreviation and Acronym
App. Acronyms and Abbreviations
Intended Audience
The manual is intended for the following readers:
z
WCDMA BTS3802C operator
z z z z
WCDMA RAN operator WCDMA RAN field engineer WCDMA RAN network planner WCDMA RAN system engineers
Conventions
The manual uses the following conventions:
I. General conventions
Convention Arial Arial Narrow Boldface Courier New Description Normal paragraphs are in Arial. Warnings, Cautions, Notes and Tips are in Arial Narrow. Headings are in Boldface. Terminal Display is in Courier New.
II. GUI conventions

Convention <> [] / Description Button names are inside angle brackets. For example, click the <OK> button. Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window. Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].
III. Mouse operation

Action Click Double Click Drag Description Press the left button or right button quickly (left button by default). Press the left button twice continuously and quickly. Press and hold the left button and drag it to a certain position.
IV. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:
Caution, Warning, Danger: Means reader be extremely careful during the operation. Note, Comment, Tip, Knowhow, Thought: Means a complementary description.
Operation Manual-Data Configuration BTS3802C WCDMA NodeB
Table of Contents
Table of Contents
Chapter 1 Introduction to Configuration Management System................................................ 1-1 1.1 Overview ............................................................................................................................ 1-1 1.2 Configuration Management System Interface ................................................................... 1-1 1.3 MIT Navigation Tree .......................................................................................................... 1-2 1.4 NodeB-Level Properties and Cabinet-Level Properties..................................................... 1-3 1.5 Equipment Panel................................................................................................................ 1-4 Chapter 2 Overview of NodeB Data Configuration .................................................................... 2-1 2.1 Overview ............................................................................................................................ 2-1 2.2 Tools for NodeB Data Configuration.................................................................................. 2-1 2.3 Template and Configuration File........................................................................................ 2-2 2.3.1 Name of Configuration File and Template .............................................................. 2-2 2.3.2 Usage of Template and Configuration File ............................................................. 2-2 2.4 Data Conflict ...................................................................................................................... 2-3 2.5 Key Properties of Template ............................................................................................... 2-3 2.6 Configuration File Editing vs. Equivalent MML Command ................................................ 2-4 2.6.1 Equivalent MML Commands ................................................................................... 2-4 2.6.2 Operations with No Equivalent MML Commands ................................................... 2-4 2.6.3 Dynamic Commands and Static Commands .......................................................... 2-5 Chapter 3 NodeB Initial Configuration Process ......................................................................... 3-1 3.1 Overview of NodeB Initial Configuration Process.............................................................. 3-1 3.2 Comprehensive NodeB Initial Configuration Process........................................................ 3-1 3.2.1 Networking Condition .............................................................................................. 3-1 3.2.2 Process of Comprehensive NodeB Initial Configuration......................................... 3-2 3.3 Simplified NodeB Initial configuration Process .................................................................. 3-5 3.3.1 Simplification Requirements.................................................................................... 3-5 3.3.2 Simplified NodeB Initial Configuration Sequence ................................................... 3-6 Chapter 4 Common Procedures-Configuration File and Applying Data ................................. 4-1 4.1 Starting Configuration Management System..................................................................... 4-1 4.1.1 Overview ................................................................................................................. 4-1 4.1.2 Points for attention .................................................................................................. 4-1 4.1.3 Procedure................................................................................................................ 4-1 4.2 Creating a Configuration File Using a Template................................................................ 4-2 4.2.1 Overview ................................................................................................................. 4-2 4.2.2 Points for Attention.................................................................................................. 4-2 4.2.3 Procedure................................................................................................................ 4-2 4.3 Creating a Configuration File without Template ................................................................ 4-3 4.3.1 Overview ................................................................................................................. 4-3
i
Table of Contents
4.3.2 Points for Attention.................................................................................................. 4-3 4.3.3 Procedure................................................................................................................ 4-4 4.4 Saving a Configuration File as a Template........................................................................ 4-4 4.4.1 Overview ................................................................................................................. 4-4 4.4.2 Points for Attention.................................................................................................. 4-4 4.4.3 Procedure................................................................................................................ 4-4 4.5 Applying Configuration File Data ....................................................................................... 4-5 4.5.1 Overview of Applying Configuration File Data ........................................................ 4-5 4.5.2 Applying Data by Downloading Configuration File.................................................. 4-5 4.5.3 Applying Data by Executing Equivalent MML Command........................................ 4-7 4.6 Checking Consistency between Configuration File Data and Running Data .................... 4-9 4.6.1 Overview ................................................................................................................. 4-9 4.6.2 Points for Attention.................................................................................................. 4-9 4.6.3 Procedure................................................................................................................ 4-9 Chapter 5 Local Cell Configuration Procedures ........................................................................ 5-1 5.1 Selecting/Modifying NodeB Configuration Type ................................................................ 5-1 5.1.1 Overview ................................................................................................................. 5-1 5.1.2 Points for Attention.................................................................................................. 5-2 5.1.3 Procedure................................................................................................................ 5-2 5.2 Modifying Local Cell Logical Properties............................................................................. 5-3 5.2.1 Overview ................................................................................................................. 5-3 5.2.2 Points for Attention.................................................................................................. 5-3 5.2.3 Procedure in Case of NodeB Initial Configuration .................................................. 5-3 5.2.4 Procedure in Case of In-Service Property Modification .......................................... 5-5 5.3 Modifying NDRU Properties............................................................................................... 5-6 5.3.1 Overview ................................................................................................................. 5-6 5.3.2 Points for Attention.................................................................................................. 5-6 5.3.3 Procedure................................................................................................................ 5-6 Chapter 6 Transport Configuration Procedures ........................................................................ 6-1 6.1 Configuring E1/T1 as E1 or T1 .......................................................................................... 6-1 6.1.1 Overview ................................................................................................................. 6-1 6.1.2 Points for Attention.................................................................................................. 6-1 6.1.3 Procedure................................................................................................................ 6-1 6.2 Adding a UNI Link .............................................................................................................. 6-2 6.2.1 Overview ................................................................................................................. 6-2 6.2.2 Points for Attention.................................................................................................. 6-2 6.2.3 Procedure................................................................................................................ 6-2 6.3 Adding a Fractional ATM Link............................................................................................ 6-5 6.3.1 Overview ................................................................................................................. 6-5 6.3.2 Points for Attention.................................................................................................. 6-5 6.3.3 Procedure................................................................................................................ 6-5 6.4 Adding an NCP Port .......................................................................................................... 6-7
ii
Table of Contents
6.4.1 Overview ................................................................................................................. 6-7 6.4.2 Points for Attention.................................................................................................. 6-8 6.4.3 Procedure................................................................................................................ 6-8 6.5 Adding a CCP Port ............................................................................................................ 6-9 6.5.1 Overview ................................................................................................................. 6-9 6.5.2 Points for Attention.................................................................................................. 6-9 6.5.3 Procedure................................................................................................................ 6-9 6.6 Adding an ALCAP Node .................................................................................................. 6-10 6.6.1 Overview ............................................................................................................... 6-10 6.6.2 Points for Attention................................................................................................ 6-10 6.6.3 Procedure.............................................................................................................. 6-11 6.7 Adding an AAL2 PATH .................................................................................................... 6-12 6.7.1 Overview ............................................................................................................... 6-12 6.7.2 Points for Attention................................................................................................ 6-12 6.7.3 Procedure.............................................................................................................. 6-12 6.8 Expanding Iub Transport Capacity .................................................................................. 6-14 6.8.1 Overview ............................................................................................................... 6-14 6.8.2 Points for Attention................................................................................................ 6-14 6.8.3 Procedure.............................................................................................................. 6-14 6.9 Adding a Transparent Link............................................................................................... 6-15 6.9.1 Overview ............................................................................................................... 6-15 6.9.2 Points for Attention................................................................................................ 6-15 6.9.3 Procedure.............................................................................................................. 6-15 6.10 Adding an SDT CES Channel........................................................................................ 6-16 6.10.1 Overview ............................................................................................................. 6-16 6.10.2 Points for Attention.............................................................................................. 6-16 6.10.3 Procedure............................................................................................................ 6-16 6.11 Adding a Treelink PVC .................................................................................................. 6-19 6.11.1 Overview ............................................................................................................. 6-19 6.11.2 Points for Attention.............................................................................................. 6-19 6.11.3 Procedure............................................................................................................ 6-19 6.12 Modifying NCP or ALCAP.............................................................................................. 6-20 6.12.1 Overview ............................................................................................................. 6-20 6.12.2 Points for Attention.............................................................................................. 6-20 6.12.3 Procedure............................................................................................................ 6-21 6.13 Modifying a CCP or AAL2PATH .................................................................................... 6-21 6.13.1 Overview ............................................................................................................. 6-21 6.13.2 Points for Attention.............................................................................................. 6-21 6.13.3 Procedure............................................................................................................ 6-21 Chapter 7 Maintenance Channel Configuration Procedures .................................................... 7-1 7.1 Modifying Local Maintenance Channel.............................................................................. 7-1 7.1.1 Overview ................................................................................................................. 7-1
iii
Table of Contents
7.1.2 Points for attention .................................................................................................. 7-1 7.1.3 Procedure................................................................................................................ 7-1 7.2 Adding IPoA Maintenance Channel................................................................................... 7-2 7.2.1 Overview ................................................................................................................. 7-2 7.2.2 Points for Attention.................................................................................................. 7-2 7.2.3 Procedure................................................................................................................ 7-2 7.3 Modifying IPoA Maintenance Channel .............................................................................. 7-4 7.3.1 Overview ................................................................................................................. 7-4 7.3.2 Points for Attention.................................................................................................. 7-4 7.3.3 Procedure................................................................................................................ 7-4 7.4 Modifying SNTP Properties ............................................................................................... 7-5 7.4.1 Overview ................................................................................................................. 7-5 7.4.2 Points for Attention.................................................................................................. 7-5 7.4.3 Procedure................................................................................................................ 7-5 7.5 Modifying NASU O&M Mode mode ................................................................................... 7-7 7.5.1 Overview ................................................................................................................. 7-7 7.5.2 Points for attention .................................................................................................. 7-7 7.5.3 Procedure................................................................................................................ 7-7 Chapter 8 Supplementary Configuration Procedures ............................................................... 8-1 8.1 Selecting Clock Source...................................................................................................... 8-1 8.1.1 Overview ................................................................................................................. 8-1 8.1.2 Points for Attention.................................................................................................. 8-1 8.1.3 Procedure................................................................................................................ 8-1 8.2 Configuring External Alarm Ports ...................................................................................... 8-4 8.2.1 Overview ................................................................................................................. 8-4 8.2.2 Points for Attention.................................................................................................. 8-4 8.2.3 Procedure................................................................................................................ 8-4 8.3 Configuring Power Supply Mode ....................................................................................... 8-6 8.3.1 Overview ................................................................................................................. 8-6 8.3.2 Points for Attention.................................................................................................. 8-6 8.3.3 Procedure................................................................................................................ 8-6 8.4 Configuring Module Temperature Thresholds ................................................................... 8-8 8.4.1 Overview ................................................................................................................. 8-8 8.4.2 Points for Attention.................................................................................................. 8-9 8.4.3 Procedure................................................................................................................ 8-9 8.5 Modifying Engineering Parameters.................................................................................. 8-11 8.5.1 Overview ............................................................................................................... 8-11 8.5.2 Points for Attention................................................................................................ 8-11 8.5.3 Procedure.............................................................................................................. 8-11 Chapter 9 Local Cell Properties ................................................................................................... 9-1 9.1 Overview of Local Cell Properties...................................................................................... 9-1 9.2 Architecture of Local Cells ................................................................................................. 9-1
iv
Table of Contents
9.3 Properties of NodeB configuration type ............................................................................. 9-2 9.4 Local Cell Logical Properties ............................................................................................. 9-3 Chapter 10 Transport Properties ............................................................................................... 10-1 10.1 Overview of Transport Properties .................................................................................. 10-1 10.2 Architecture of NodeB Transport ................................................................................... 10-1 10.2.1 Transport Ports.................................................................................................... 10-1 10.2.2 Transport Networking and Transport Protocol Architecture................................ 10-2 10.2.3 Transport Networking Mode Selection................................................................ 10-6 10.2.4 Peers of the Transport Protocol layers ............................................................... 10-7 10.3 ATM Physical Layer Bearer Properties ......................................................................... 10-8 10.3.1 Overview ............................................................................................................. 10-8 10.3.2 UNI Link Properties ............................................................................................. 10-8 10.3.3 Fraction ATM Link Properties.............................................................................. 10-8 10.4 Iub Transport Object Properties..................................................................................... 10-9 10.4.1 Overview ............................................................................................................. 10-9 10.4.2 Architecture of Iub Transport............................................................................. 10-10 10.4.3 Properties of NCP, CCP, ALCAP, AAL2PATH and IPoA ................................. 10-11 10.4.4 Determine Iub Transport Object Properties ...................................................... 10-11 10.5 Transparent Link Properties ........................................................................................ 10-12 10.5.1 Overview ........................................................................................................... 10-12 10.5.2 Architecture of Transparent Link ....................................................................... 10-12 10.5.3 Properties of Transparent Link.......................................................................... 10-12 10.6 SDT CES Channel Properties ..................................................................................... 10-13 10.6.1 Overview ........................................................................................................... 10-13 10.6.2 Architecture of SDT CES Channel .................................................................... 10-13 10.6.3 Bandwidth Planning for CES Channel .............................................................. 10-14 10.6.4 Properties of CES Channel ............................................................................... 10-14 10.7 Treelink PVC Properties .............................................................................................. 10-15 10.7.1 Overview of Treelink PVC Properties ............................................................... 10-15 10.7.2 Architecture of Treelink PVC............................................................................. 10-15 10.7.3 VPI Planning...................................................................................................... 10-16 10.7.4 Bandwidth Planning for Treelink PVC............................................................... 10-16 10.7.5 Properties of Treelink PVC................................................................................ 10-16 10.8 Transport Configuration Guideline............................................................................... 10-18 10.8.1 Configure Tree Transport Network from Upper-level-segment to Lower-level-segment .................................................................................................... 10-18 10.8.2 Configure Each Segment from Bottom Layer to Top Layer.............................. 10-18 Chapter 11 Maintenance Channel Properties........................................................................... 11-1 11.1 Overview of Maintenance Channel Configuration ......................................................... 11-1 11.2 Architecture of BTS3802C Maintenance channel.......................................................... 11-1 11.3 IP Planning..................................................................................................................... 11-2 11.3.1 IP networking....................................................................................................... 11-2
v
Table of Contents
11.3.2 IP addresses ....................................................................................................... 11-3 11.3.3 IP routes .............................................................................................................. 11-4 11.4 IPoA Maintenance Channel Configuration Guideline .................................................... 11-5 Chapter 12 Transport Bandwidth Planning .............................................................................. 12-1 12.1 Planning Transport Bandwidth....................................................................................... 12-1 12.2 Bandwidth of ATM Physical Layer Bearer ..................................................................... 12-2 12.3 Calculating Traffic .......................................................................................................... 12-2 12.4 Planning Number of AAL2PATHs.................................................................................. 12-3 12.5 Calculating PVC Bandwidth Consumed by a CES Channel ......................................... 12-3 Appendix Acronyms and Abbreviations ..................................................................................... F-1 Index ................................................................................................................................................ i-1
vi
Chapter 1 Introduction to Configuration Management System

1.1 Overview
This chapter introduces the configuration management systems of BTS3802C. This chapter covers the following aspects:
z z z z
Configuration management system interface MIT navigation tree NodeB-level properties and cabinet-level properties Equipment panel
1.2 Configuration Management System Interface

After starting the Configuration Management System, select [File/Open] on the main menu to open an existing configuration file or select [File/New by Template] to create a new one. Figure 1-1 shows the window finally displayed in the configuration management system.
(1) (2) (3) (4) (5)
(6)
(1) Main menu (3) MIT (Management Information Tree) navigation tree (5) Equipment panel
(2) Tool bar (4) MIT navigation node (6) Result output window
Figure 1-1 Configuration Management System interface
1-1
In this window, you can perform most configuration operations through the MIT navigation tree and equipment panel.
1.3 MIT Navigation Tree

Figure 1-2 shows the MIT navigation tree.
AAL2 ALCAP ATM CCP CES IPoA NCP NMCU NDRU PVC UNI
ATM Adaptation Layer type 2 Access Link Control Application Protocol Asynchronous Transfer Mode Communication Control Port Circuit Emulation Service Internet Protocol over ATM NodeB Control Port NodeB Maintenance and Control unit NodeB Digital and Transceiver Unit Permanent Virtual Channel User Network Interface
Figure 1-2 MIT navigation tree MIT navigation tree arranges the configuration properties into different layers. The root node at the highest layer is [BTS3802C]. The layers immediately under the highest are:
z z z
[Physical Object Tree] [Transmission Object Tree] [Local Cell Object Tree]
These object trees also have sub-trees.

1-2
MIT navigation tree provides access to all data configuration operations. Right-click a node in the MIT navigation tree to display a shortcut menu. Through this menu, you can:
z z z z
Add a node, Delete a node, View the properties of a node, Modify the properties of a node.
1.4 NodeB-Level Properties and Cabinet-Level Properties

In the MIT tree, the node a property resides in indicates the effect range of the property. For example, the properties at the NodeB level have their effects on the entire NodeB while the properties at the module/object level have their effects on the corresponding module or object. Right click the root node [BTS3802C], and select [Modify NodeB] in the shortcut menu. to display the dialog box [Modify BTS3802C Properties], as shown in Figure 1-3. The properties in this dialog box are of the root node. As NodeB-level properties, they have effects on the entire NodeB.
Figure 1-3 NodeB level properties
1-3
Right click the node [BTS3802C/Physical Object Tree/**** Board], and select [Modify **** Board] in the shortcut menu to display the dialog box [Modify **** Board Properties]. As module-level properties, these properties in this dialog box have effects on the corresponding module.
1.5 Equipment Panel

The Configuration Management System provides graphic board/module configuration management interface, as shown in Figure 1-4.
Figure 1-4 Equipment panel In the equipment panel, the slots with module names displayed are slots configured with modules. Right-click a slot on the equipment panel to display a shortcut menu. Through this menu, you can:
z z z z
Add a module, Delete a module, View the properties of a module, Modify the properties of a module.
1-4
Chapter 2 Overview of NodeB Data Configuration

2.1 Overview
This section provides information on the following aspects:
z z z z
Tools for NodeB data configuration Template and configuration file Key properties of a template and data conflict Configuration file editing vs. equivalent MML command
2.2 Tools for NodeB Data Configuration

It is recommended to use the configuration management system to perform data configuration, although most of the properties can be configured by executing MML commands on the Operation & Maintenance System. The advantages are as follows:
z
The configuration management system provides data consistency mechanism and guarantees data integrity. The configuration management system provides template. Template makes NodeB data configuration relatively an easy work. The configuration management system supports modifying properties, exporting the equivalent MML commands along with the specified properties and then executing the exported equivalent MML commands on the Operation & Maintenance System (O&M system).
This document focuses on NodeB data configuration in the configuration management system.
Notes: Configuring data directly with MML commands is a shortcut for experts, who are familiar with the MML commands, the properties and the property coupling relationships.
2-1
2.3 Template and Configuration File

2.3.1 Name of Configuration File and Template
When saving a new configuration file, you must name it. The format of configuration file name is "configuration file name.extension name". There are two configuration file types:
z z
formal configuration files, which have the extension name of "xml" temporary configuration files, which have the extension name of "mdb"
A template is an ".xml" configuration file. Any ".xml" configuration file can serve as template. Name a template as one that indicates the NodeB configuration type. For example, name a template as "2antenna_1sectors_1frequencies_no transmit diversity .xml". Table 2-1describes the differences between .mdb file and .xml file. Table 2-1 Differences between .mdb files and .xml files File type Check before saving .mdb If a configuration file is to be saved as an .mdb file, the configuration management system does not check the file before saving it. .xml When a configuration file is to be saved as an .xml file, the configuration management system checks the data consistency. If there are any invalid or inconsistent properties found, the configuration management system prompts you to modify them. The saving succeeds only when there are no problems. An .xml file can be loaded to a NodeB.
Download to the NodeB Equivalent MML command
An .mdb file cannot be loaded to a NodeB. To load an .mdb file to a NodeB, save the mdb file as an .xml file beforehand. After an .mdb file is opened, the configuration management system does not record the edit operations with the equivalent MML commands.
After an .xml file is opened, the configuration management system records the edit operations with equivalent MML commands.
A template is an ".xml" configuration file. Name a template as one that indicates the NodeB configuration type. For example, name a template as "2antenna_1sector(s)_1frequency(s)_notransmitdiversity.xml".
2.3.2 Usage of Template and Configuration File

Configuration files contain all the configuration properties of a NodeB. A template is a configuration file used as pattern to create other configuration files.
2-2
To facilitate NodeB configuration, the configuration management system provides a set of preset configuration files, namely templates, for typical NodeB configuration types. Each template contains a set of default properties for a NodeB configuration type. You can select the one applicable to the target NodeB configuration type, and then make a few changes on it according to the actual situation to finish the NodeB data configuration.
2.4 Data Conflict

Data configuration is to organize and allocate resources. Data conflict occurs in many cases such as:
z
To allocate a resource for an application but the resource has already been used. In this case, allocate other resource for the application. To add an application but not all of the resources for the application have been ready. In this case, prepare all the resources for the application before adding the application.
To remove a resource but the resource has already been occupied by an application. In this case, remove the application first.
During the data configuration, the configuration management system provides all the available resources for selection, such as E1/T1 ports. If there is no resource available, modify the configuration according to the prompt provided by the configuration management system.
2.5 Key Properties of Template

The template provides a set of properties. Among them, properties of RF channels are the key properties. They closely relate to "NodeB configuration type". Avoid modifying these key properties separately because these key properties are closely coupled and modifying these key properties individually may cause data conflict. It is recommended to modify these key properties by selecting another template. In this way, you can configure the RF channels without detailed knowledge of NodeB RF channels. Except the key properties, other properties can be modified individually.
2-3
2.6 Configuration File Editing vs. Equivalent MML Command

2.6.1 Equivalent MML Commands
After an ".xml" configuration file is opened or created, the configuration management system records the edit operations in terms of equivalent MML commands. The result of executing the equivalent MML commands on O&M system is the same as that of downloading the modified configuration file to the NodeB and resetting the NodeB. You can browse the recorded commands through [View/Browse MML command] on the main menu of the configuration management system.
Caution:
z z
A few operations having no equivalent MML commands. If the configuration file opened is .mdb file, the configuration management system does not record the equivalent MML commands.
2.6.2 Operations with No Equivalent MML Commands

For most configuration operations, there are equivalent MML commands serving the same property modifications. However, for some property-modifying operations, there are no equivalent MML commands. When one of these operations is performed in the configuration management system, the configuration management system prompts the following information in the "text output column" as shown in Figure 2-1.
Figure 2-1 Prompt of "no corresponding MMLs for current operation Configuration operations without equivalent MML commands include the following items:
z z
"E1/T1 Work Mode" in [BTS3802C] properties Some property modifications, for example NCP, CCP property modification operations
2-4

z
Delete IPoA Device in the [BTS3802C/Transmission Object Tree/IPoA device Set]
Results of performing operations having no equivalent MML command are as follows:

z
After the operation having no equivalent MML command is performed, you must download the configuration file to the NodeB and then reset the NodeB to bring the data into effect.
When you perform such an operation and click <OK>, the configuration management system will clear all the previously recorded equivalent MML commands. The record of the equivalent MML commands remains empty until the configuration file is closed and reopened.
Tip: If the equivalent MML commands are cleared, you can view the cleared equivalent MML commands by undoing the previous operation by clicking operation. . After viewing the commands, click to restore the
2.6.3 Dynamic Commands and Static Commands

MML commands are classified into dynamic commands and static commands. Table 2-2 describes the differences between them. Table 2-2 Differences between dynamic commands and static commands Commands Dynamic commands Executing result Executing dynamic commands modifies both the properties of the configuration file in the NodeB and the running parameters. Executing static commands only modifies the properties of the configuration file in the NodeB. The running parameters do not change yet To obtain the effect of downloading configuration file and resetting NodeB Execute dynamic equivalent MML commands
Static commands
Execute static commands and then reset the NodeB for NodeB static commands or reset the module for module static commands
Static commands are further classified into NodeB static commands and module static commands. For NodeB static commands, the new values take effect only after the NodeB is reset. For module static commands, the new values take effect only after the module is reset.
2-5
The NodeB static commands include the following commands:

z z z
MOD TXDELAY (setting transmit channel delay) MOD RXANTMODE (setting receive antenna diversity mode) MOD RXDELAY (setting receiving channel delay)
The module static command includes the following command:

z
SET NDRUWM (setting NDRU work mode)
2-6
Chapter 3 NodeB Initial Configuration Process

3.1 Overview of NodeB Initial Configuration Process
This chapter describes the process of NodeB initial configuration. You need perform NodeB initial configuration in the following cases:
z
During new NodeB deployment or network optimization, it may need to add a new NodeB. For network optimization, the NodeB configuration type may need to change, for example from 1sector*1frequency (1*1 in short) to 1sectors*2frequency (1*2). In this case, another template should be used to create a configuration file. All properties in the new configuration file should be edited by following the NodeB initial configuration process.
This chapter provides comprehensive NodeB initial configuration process and simplified NodeB configuration process.
z
Comprehensive NodeB initial configuration process provides a general scenario to accomplish the data configuration of various network situations. Simplified NodeB initial configuration process provides a reduced scenario for simple but common network situations.
3.2 Comprehensive NodeB Initial Configuration Process

3.2.1 Networking Condition
NodeB adapts to various transport networking conditions. NodeBs may cascade to form tree networking. In that case, configure the new NodeB from upper level to lower level, as shown in Figure 3-1.
3-1

Step 1 Initial configuration process
New NodeB
RNC
Step 2 Initial configuration process
Local NodeB
New NodeB
Local NodeB Step 3 Initial configuration process
NodeB
RNC
Upper level NodeB
New NodeB
NodeB
NodeB
RNC
Figure 3-1 Configuring the new NodeB from the upper level to lower level
3.2.2 Process of Comprehensive NodeB Initial Configuration

Figure 3-2 illustrates the comprehensive NodeB initial configuration process. The comprehensive NodeB initial configuration includes upper level node configuration, NodeB essential configuration, supplementary configuration, and transport configuration for 2G BTS or other equipment. Table 3-1 describes these configuration stages and their targets.
3-2

upper level node configuration NodeB Essential Configuration

Supplemen tary Configuration Transport configuration for 2G B TS or other device
Local cell configurat ion RNC: Configure Iub transport objects and logical cell properties
A1
Selec t NodeB configura tion type Modify Local Cell log ical properties
B1
Select clock source (Iub or G PS clock)

C1
Add transparent link
D1
B2
Configure external alarm collection Configure power supply mode
Add C ES channel
C2 D2
Upper level 2G BT S: If 2G BT S provides fractional E1/ T1 slots for the local Node B, configure fractional E1/T1 t imeslots on the 2G B TS
Iub transport configuration Configuring E1/T1 Work Mode as E1 Mode or T1 Mode

B3
C3
Add Treelink P VC (for lower level NodeB) Apply data by exec uting equivalent MML commands or downloading configuration file
D3
Configure module temperature threshold

C4
A2
Upper level NodeBs: If the local NodeB is cascaded after other NodeBs, add Treelink PVC on all of the upperlevel-NodeBs for all the local NodeB P VCs A3 Apply data on a ll the upper level nodes
A4
On Iub inter face: Add UNI link or Add Fractiona l ATM link
B4
Configure engineering parameters C5 Apply data by exec uting equivalent MML com mands or downloading configuration file
Add/ Modify NC P Add/ Modify CC P Add/ Modify ALCA P Add/ Modify A AL2P ATH
B5
D4
B6
B7
C6
B8
Maintenance channel configuration Modify local main tenance channel Modify IPo A maintenance channel Modify N ASU O& M mode
B9
B10
B11
Modify SNT P
B12
Apply data by downloading configuration file
B13
Figure 3-2 Comprehensive NodeB initial configuration process
Note: By applying the process shown in Figure 3-2 iteratively from the upper level node to lower level node, you can achieve the data configuration of a tree network.
3-3
Table 3-1 NodeB configuration stage and stage target Stage Upper Level Node Configuration Stage target For simple networking, complete RNC configuration. For sharing 2G transport, completer RNC and upper level 2G BTS/BSC configuration. For NodeB tree networking, complete RNC and upper level NodeB configuration. Essential Configuration Upon the completion of essential configuration, NodeB is able to provide normal services. Local cell configuration Iub Transport configuration Procedures RNC procedure 2G BTS/BSC procedure if 2G BTS provides fractional E1/T1 timeslots for the NodeB. Upper Level NodeB procedures: Add treelink PVC Select NodeB configuration type Modify Local cell logical properties Configure E1/T1 as E1 or T1 Add UNI link or Add Fractional ATM link Add/modify NCP Add/modify CCP Add/modify ALCAP Add/modify AAL2PATH Maintenance channel configuration Modify Local maintenance channel Modify IPoA maintenance channel Modify NASU O&M mode Modify SNTP Supplementary Configuration To ensure the persistence and stability of NodeB Supplementary configuration can be done at a convenient time before or after NodeB is able to provide normal services. Select Clock source Configure External Alarm collection Configure Power Supply mode Configure module temperature threshold Configure Engineering parameter Transport Configuration for 2G BTS or other device Apply data To provide transport channels for lower level equipments, such as 2G BTS and monitoring equipment. To apply configuration data Add transparent link Add CES channel Apply data Chapter 4 Chapter 6 Chapter 8 Chapter 7 Chapter 6 Location Not provided in this manual Chapter 6
Chapter 5
3-4
Notes:
z
After finishing essential configuration, apply the data to check the basic function and service of the NodeB, as shown in Figure 3-2 (B13). According to engineering schedule, it is also possible to apply the data until the supplementary configuration is finished, as shown in (C5), or the transport configuration for 2G BTS or other equipment is finished, as shown in (D3).
Refer to WCDMA NodeB installation Manual - System Commission for checking the basic function and service of the NodeB.
3.3 Simplified NodeB Initial configuration Process

3.3.1 Simplification Requirements
Simplification requirements include two aspects, namely simple networking and application of default properties. Simple Networking:
z z z
The new NodeB connects directly with the RNC. The new NodeB does not cascade with lower level NodeB. The NodeB does not share transport with 2G equipment.
Application of default Properties: Only the following properties need modification:

z z z z z z
Local cell ID NDDL attenuation value E1/T1 work mode (E1 or T1) ATM address IPoA local IP address and peer IP address SNTP IP address
Except the above properties, use the default settings defined in the selected template for all the other properties including:
z z z z z
UNI link, NCP, CCP, AAL2PATH IPoA except the IP address ALCAP except the ATM address Installation slot of NDRU Properties of synchronization clock source, module temperature threshold, power supply mode and external alarm collection.
3-5
Note:
z
Because some of the properties must be consistent between NodeB and RNC, select the property value for RNC configuration according to NodeB default value. The hardware installation must be consistent with the NodeB default properties.
3.3.2 Simplified NodeB Initial Configuration Sequence

Figure 3-3 illustrates the simplified NodeB initial configuration process. Only the highlighted blocks are necessary for simplified NodeB initial configuration. The blocks that are not highlighted can be pruned because default settings are used.
3-6

upper level node configuration NodeB Essential Configuration

Supplemen tary Configuration Transport configuration for 2G B TS or other device
Local cell configurat ion RNC: Configure Iub transport objects and logical cell properties
A1
Selec t NodeB configura tion type Modify Local Cell log ical properties
B1
Select clock source (Iub or G PS clock)

C1
Add transparent link
D1
B2
Configure external alarm collection Configure power supply mode
Add C ES channel
C2 D2
Upper level 2G BT S: If 2G BT S prov ides fractional E1/ T1 slots for the local Node B, configure fractional E1/T1 t imeslots on the 2G B TS A2
Iub transport configuration Configuring E1/T1 Work Mode as E1 Mode or T1 Mode

B3
C3
Add Treelink P VC for lower level NodeB
Configure module temperature threshold

C4
D3
On Iub inter face: Add UNI link or Add Fractiona l ATM link
B4
Upper level NodeBs: If the local NodeB is cascaded after other NodeBs, add Treelink PVC on all of the upperlevel-NodeBs for all the local NodeB P VCs
A3
Configure engineering parameters C5 Apply data by executing equivalent MML com mands or downloading configuration file
Add/ Modify NC P Add/ Modify CC P Add/ Modify ALCA P Add/ Modify A AL2P ATH
B5
Apply data by exec uting equivalent MML commands or downloading configuration file
D4
B6
B7
C6
Apply data on a ll the upper level nodes

A4
B8
Maintenance channel configuration Modify local main tenance channel Modify IPo A maintenance channel Modify N ASU O& M mode
B11
B9
B10
Modify SNT P
B12
Apply data by downloading configuration file
B13
Figure 3-3 Simplified NodeB initial configuration process Table 3-2 describes the procedures required for simplified NodeB initial configuration in detail. Table 3-2 Procedures and properties in simplified NodeB initial configuration process Step 1 Procedure procedure B1 Properties select NodeB configuration type --Note Location Chapter 5
3-7
Step 2 3 4 5 6 7
Procedure procedure B2 Procedure B3 procedure B8 procedure B12 procedure B13 procedure B14
Properties set Local cell ID Configure E1/T1 as E1 or T1 set ATM address set IPoA local IP address, IPoA peer IP address set SNTP IP address Apply the properties
Note Set the local cell IDs of all the Cells --------Install the board, jumper, transport line, and signal line according to the configuration file
Location
Chapter 6
Chapter 8 Chapter 4
3-8
Chapter 4 Common Procedures-Configuration File and Applying Data

4.1 Starting Configuration Management System
4.1.1 Overview
Target Application occasion Prerequisite To start the configuration management system for configuration file creating or editing NodeB initial configuration In-service property modification during network optimization After the installation of NodeB Local Maintenance Terminal (LMT), the item [Start/Programs/Huawei Local Maintenance Terminal/NodeB V100R003 /NodeB Operation & Maintenance System] is in the Windows Start menu.
4.1.2 Points for attention

None
4.1.3 Procedure
1) Select [Start/Programs/Huawei Local Maintenance Terminal/NodeB
V100R003/NodeB Operation & Maintenance System] to start Local Maintenance Terminal (LMT), and the [Login] dialog box is displayed. 2) To start the LMT in offline mode, click <Cancel> in the [Login] dialog box; to start the LMT in online mode, type the user name, password, and office name, and click <OK> in the dialog box. Note: Start the LMT in online mode in one of the following cases:
z z
To upload the configuration file from the NodeB for property modification To apply the new properties after the properties are modified
The configuration management system works in offline mode, even if the LMT is in online mode.
4-1
3) 4)
Select the corresponding version in the [Select Version] dialog box to start the corresponding LMT. Select [Service/Configuration Management System] on the LMT main menu, and then select the corresponding version in the pop-up [Select Version] dialog box to start the configuration management system.
4.2 Creating a Configuration File Using a Template

4.2.1 Overview
Target Application occasion Prerequisite To create a configuration file using a template NodeB initial configuration In-service property modification during network optimization There is a suitable template.
4.2.2 Points for Attention

General Verification command After selecting a template, do not modify key parameters of the configuration file. None
4.2.3 Procedure
Follow the procedure below to create a configuration file using a template: 1) 2) Start configuration management system. Refer to section 4.1 . Select [File/New By Template] on the main menu to display the dialog box [Open Template File], as shown in Figure 4-1.
4-2
Figure 4-1 Opening a template 3) 4) 5) Select the template matching the target NodeB configuration type in the [Open Template File] dialog box, and then click <Open>. Modify the property settings. Select [File/Save] on the main menu, enter the file name, and click <Save> to save this configuration file in the computer. If the file type is selected as "xml", the file will be saved after it passes the consistency check.
4.3 Creating a Configuration File without Template

4.3.1 Overview
Target Application occasion Prerequisite To create a configuration file for advanced and special NodeB configuration type No suitable template is available Be familiar with the NodeB configuration principles. Refer to Appendix A for NodeB configuration principles

General Verification command If there is a template suitable, it is recommended to create a configuration file using a template. None
4-3
4.3.3 Procedure
Follow the procedure below to create a configuration file without template: 1) 2) 3) 4) 5) 6) Start configuration management system. Refer to section 4.1 . Select [File/New]. The configuration management system displays the dialog box [Add NodeB]. In the [Add NodeB] dialog box, set the NodeB-level properties, and then click <OK>. The [Add NMCU Module] dialog box is displayed. In the [Add NMCU Module] dialog box, set the module-level properties, and then click <OK>. Modify the configuration data. Select [File/Save], enter the file name, and click <Save> to save this configuration file in the computer. If the file type is to be saved as "xml", the configuration management system saves it after the file passes the consistency check.
4.4 Saving a Configuration File as a Template

4.4.1 Overview
Target Application occasion To create a template for the consistency and standardization of multiple NodeB data configurations When you configure multiple NodeBs with similar properties, it is more convenient to save a configuration file as a template, and then use it to create other configuration files. The method ensures the consistency and standardization of the configurations. Prerequisite None

None
4.4.3 Procedure
Follow the procedure below to save a configuration file as a template: 1) 2) Select [File/Save as Template] after editing a configuration file. Enter the name of the template in the [Save as Template] dialog box, and then click <OK>. The template is created after passing the consistency check.
4-4
4.5 Applying Configuration File Data

4.5.1 Overview of Applying Configuration File Data
As shown in Figure 4-2, you can take the configuration data into effect by either downloading the configuration file (on the left of Figure 4-2) or executing MML command (on the right of Figure 4-2).
new properties Configuration management system

Save configuration file Export equivalent MML command
Configuration file LMT computer

Dow nload configuration file into the NodeB
MML command batch file LMT computer

Execute equivalent MML command
Configuration file parameters

Restart NodeB Reset NodeB to take static commands into effect Dynamic commands take effect immediately after they are executed.
Running parameters BTS3802C
Figure 4-2 Applying configuration data
4.5.2 Applying Data by Downloading Configuration File

I. Overview
Target Application occasion To apply the data after preparing the configuration file NodeB Initial configuration NodeB configuration type is changed Edit operations having no equivalent MML commands are performed NodeB static data is modified Large quantities of data are modified Prerequisite None
4-5
II. Points for attention

General Verification command Resetting NodeB interrupts the service of the NodeB. None
III. Procedure
Follow the procedure below to apply data by downloading a configuration file: 1) After editing a configuration file in the configuration management system, click main menu [File/Save] in the configuration management system to save the configuration file. 2) 3) Rename the configuration file as "NodeBCfg.xml". For NodeB in-service property modification, to avoid call drop, execute BLK CELL to block all cells in Normal or LOW mode in the NodeB O&M system. Otherwise, skip this step and go to next step. 4) 5) Download the configuration file on O&M system through MML command DLD CFGFILE. Change the hardware configuration according to the configuration file. Adjust the installation of NDRU. Adjust the RF jumpers, and transport lines.
Note: The hardware installation must be consistent with the data configuration. Select [Physical Object Tree] in the MIT navigation tree to open the equipment panel. In the equipment panel, you can obtain the information about the modules and NDRU properties configured. To view the settings of the interconnection jumpers of NDRU, which corresponds to the NodeB configuration type, right-click [NDRU] on the equipment panel, and then select [Properties] in the shortcut menu to display the [Slot n NDRU Board Properties] dialog box.
6)
Restart the NodeB through MML command RST SYS.
4-6
4.5.3 Applying Data by Executing Equivalent MML Command

I. Overview
Target Application occasion Prerequisite To apply the data while avoiding configuration file download and NodeB reset The NodeB configuration type has not been changed. All the property-modifying operations in configuration management system have equivalent MML commands.
II. Points for Attention

General When a board is added through an equivalent MML command, it will be restarted automatically, and the restarting process will last for up to three minutes. Commands of modifying properties of the board can be executed only after the board restarts successfully. If a batch file contains MML commands of adding a board and modifying the properties of the board immediately after, split the batch file into two files. Executing MML commands modifies not only the running parameters but also the properties in the NodeB configuration file. Therefore, it is necessary to back up the configuration file. Verification command None
III. Procedure
Follow the procedure below to applying data by executing equivalent MML commands: 1) 2) Modify the properties in configuration management system. Click [View/Browse MML command] on the main menu of the configuration management system. Figure 4-3 shows the dialog box [Browse MML Command]. In the dialog box, click the <Export> to save the recorded commands in a text file.
4-7
Figure 4-3 Browsing Equivalent MML command 3)

z z
For in-service property modification, to avoid call drop, execute BLK CELL to block the cells in Normal or LOW mode in any situation below. Static properties are modified Cell service is interrupted when the MML commands are executed Otherwise, skip this step and go to next step.
4) 5)
Execute the equivalent MML commands on O&M system. Change the hardware configuration according to the property modifications made.
Note: The hardware installation must be consistent with the data configuration. Select [Physical Object Tree] in the MIT navigation tree to open the equipment panel. In the equipment panel, you can get the information about the modules and NDRU properties configured.
6)
If static parameters are modified, restart the NodeB through the MML command RST SYS or the board through the MML command RST BRD. Otherwise, this procedure ends.
For static commands, refer to MML online help.
4-8
4.6 Checking Consistency between Configuration File Data and Running Data
4.6.1 Overview
Target Application occasion To make sure the configuration modification has taken effect. The following situations will cause inconsistency between configuration file data stored in NodeB and NodeB running Data: -The configuration file has been downloaded, but the NodeB has not been restarted yet. -The static configuration command has been executed, but the NodeB has not been restarted yet. Prerequisite None

General Verification command Resetting NodeB interrupts the service of the NodeB. None
4.6.3 Procedure
Follow the procedure below to check consistency between configuration file data and running data: 1) 2) Carry out MML command CHK DATA on O&M system. If there is inconsistency between configuration file data stored in NodeB and NodeB running data, reset the NodeB through the MML command RST SYS.
4-9
Chapter 5 Local Cell Configuration Procedures

5.1 Selecting/Modifying NodeB Configuration Type
5.1.1 Overview
Target Application occasion To create a new configuration file for a new NodeB configuration type by selecting a template NodeB initial configuration In-service property modification involves NodeB configuration type properties Configuration tasks, such as adding/deleting cell, adding/deleting sector, and adding/deleting frequency are instances of modifying NodeB configuration type. Prerequisite There is a suitable template for the target NodeB configuration type.
Note: NodeB configuration type properties include the following parameters:

z z z z z
Sector*Frequency Receive diversity mode Transmit diversity mode NDRU connect mode NDRU work mode
5-1

General After configuring the NodeB configuration type with a template, do not modify NodeB configuration type properties. To modify the NodeB configuration type properties, select another template to create a new configuration file. Make the same modifications to RNC. For initial configuratio n For in-service property modification Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. Modifying a NodeB configuration type entails downloading configuration file and resetting NodeB, and thus interrupts services of the NodeB. To add or remove a cell or sector, select another template. Avoid using the following methods to add or delete a cell or a sector: Right-click [BTS3802C/Cell Object Tree/Sector n/Cell m] in the navigation tree, and then select [Delete Cell] to delete the selected cell. When a cell or a sector is deleted in this way, its resources, such as RF modules, still exist. This operation may result in inconsistency between configuration data. Verification command None
5.1.3 Procedure
Follow the procedure below to select/modify NodeB configuration type: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Select [File/New By Template] in configuration management system. In the [Open Template File] dialog box, select the template applicable to the target NodeB configuration type, and then click<OK> to create a new configuration file. For example, if the target NodeB configuration type is "1 1 (sector frequency), No Transmit diversity", select the template "1_1_No Transmit diversity.xml". 5) In case of NodeB initial configuration, click main menu [File/Save] in the configuration management system to name and save the configuration file. This procedure ends. In case of in-service property modification, go to next step. 6) Click main menu [File/Close] in configuration management system to close the newly created configuration file. Click [File/Open] to open the old configuration file. Record the old properties on a paper, and then close the old configuration file.
5-2
7)
Click [File/Open] in configuration management system to open the new configuration file. Enter the properties, including those in the old configuration file that need not be modified, into the new configuration file.
8) 9)
Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.2 Applying Data by Downloading Configuration File. Otherwise, this procedure ends.
5.2 Modifying Local Cell Logical Properties

5.2.1 Overview
Target Application occasion Prerequisite To modify Local cell ID, cell radius, and cell inner handover radius NodeB initial configuration In-service property modification during network optimization None

General Local cell ID, cell radius and cell inner handover radius must comply with the radio network plan. To modify the Local Cell ID of a cell, decide sector and frequency to which the cell belongs. Be sure to select the right cell. Make the corresponding modifications to RNC For initial configuration For in-service property modification Verification command Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. Modifying Local Cell ID of a local cell interrupts the service of the local cell. Therefore, when modifying two local cell IDs, modify them one by one. That is, begin to modify another local cell ID only after the previously modified local cell has restored its service. LST LOCELL, DSP CELL
5.2.3 Procedure in Case of NodeB Initial Configuration

Follow the procedure below to modify logical properties of the local cell during NodeB initial configuration: 1) Start configuration management system. Refer to section 4.1 .
5-3
2) 3)
Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click [Local Cell Object Tree/ No. m Local Cell] in the MIT navigation tree, and then select [Modify Local Cell] on the shortcut menu to display the [Modify No. m Local Cell Properties] dialog box, as shown in Figure 5-1. In the [Basic Properties] tab, modify the values of [Local Cell ID], [Cell Radius], and [Cell Inner Handover Radius].
Figure 5-1 Setting local cell logical properties
Note: The property "NDRU No." is the key parameter and cannot be modified. The other disabled fields in Figure 5-1 are NodeB configuration type properties. To modify the NodeB configuration type properties, refer to section 5.1 Selecting/Modifying NodeB Configuration Type
4) 5)
5-4
5.2.4 Procedure in Case of In-Service Property Modification

Follow the procedure below to modify logical properties of the local cell during in-service property modification: 1) 2) 3) 4) 5) Start configuration management system. Refer to section 4.1 . Upload the data configuration file through the MML command ULD CFGFILE on O&M system. Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. If the properties to be modified include Local cell ID (Cell No.), go to step 6). Otherwise, go to step 5). Right-click [Local Cell Object Tree/No. m Local Cell] in the MIT navigation tree, and then select [Modify Local Cell] on the shortcut menu to display the [Modify No. n Local Cell Properties] dialog box, as shown in Figure 5-1. In the [Basic Properties] tab, modify the values of [Local Cell ID], [Cell Radius] and [Cell Inner Handover Radius]. After that, go to step 8). 6) 7) Right-click [BTS3802C/ No. n local Cell] in the MIT navigation tree, and then select [Delete Local Cell] in the shortcut menu. Add another cell. Right-click [BTS3802C/Local Cell Object Tree] in the MIT navigation tree, and then select [Add Local Cell] in the shortcut menu to display the [Add Local Cell] dialog box. Enter the new Local Cell ID and other original properties in this dialog box.
Note: Another method of modifying the local cell ID is to right-click [[BTS3802C/ Local Cell Object Tree/No. n Local Cell] on the MIT navigation tree, and select [Modify No. n Local Cell] to modify the local cell ID. However, this operation does not have equivalent MML command and the only way to apply the new properties is to download the configuration file and restart the NodeB. Restarting the NodeB interrupts the service of the whole NodeB.
8) 9)
Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
5-5
Note: When the configuration file is closed in the configuration management system, the equivalent MML commands recorded are cleared. In that case, the only way to apply the properties modified is to download the configuration file. To save the MML commands, refer to section 4.5.3 .
5.3 Modifying NDRU Properties

5.3.1 Overview
Target Application occasion Prerequisite To modify NDRU work mode and connect mode In-service property modification, NodeB configuration type is to be changed according to network optimization. None

General Select another template to modify these NDRU properties. Do not modify these properties in this way: Right-click NDRU in the equipment panel or MIT navigation tree, and then select [Modify NDRU Board] to modify the NDRU properties. For in-service property modification Verification command Modifying a NodeB configuration type entails downloading configuration file and resetting NodeB, and thus interrupts services of the NodeB. None
5.3.3 Procedure
To modify the NDRU work mode and connect mode is to modify the NodeB configuration type. To modify NodeB configuration type, refer to section 5.1 .
5-6
Chapter 6 Transport Configuration Procedures

6.1 Configuring E1/T1 as E1 or T1
6.1.1 Overview
Target Application occasion Prerequisite To configure E1/T1 work mode as E1 or T1 NodeB initial configuration The E1/T1 work mode must be consistent with the settings of the NMCU DIP switches.

General For initial configuration Perform the operation on the peer node (upper level NodeB, lower level NodeB or RNC) also. NMBU E1 ports 2 and 3, which connect with the NASU E1 Port, cannot be configured as T1 port. Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. The E1/T1 work mode is a NodeB-level property and has effect on the entire NodeB. The transport bandwidth, frame structure, and line code of E1 and T1 are different. The transport bandwidth, frame structure, and line code are changed along with the E1/T1 work mode. Verification command DSP E1T1WORKMODE
6.1.3 Procedure
Follow the procedure below to configure E1/T1 work mode as E1 mode or T1 mode : 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) Click main menu [File/Open] to open the configuration file to be edited.
6-1
4)
Right-click the root node [BTS3802C] in the MIT navigation tree, and then select [Modify 3802C NodeB] to display the [Modify BTS3802C Properties] dialog box. Set the E1/T1 work mode in this dialog box. The default mode is E1.
5) 6)
6.2 Adding a UNI Link

6.2.1 Overview
Target Application occasion Prerequisite To add a UNI link NodeB initial configuration In-service property modification during network optimization The E1/T1 line is ready.

General For initial configuration For in-service property modification Verification command Perform the operation on the peer node (upper level NodeB, lower level NodeB or RNC) also. Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. After a UNI is added, allocate PVCs, such as NCP, CCP, AAL2PATH, ALCAP, IPoA, Treelink PVC, and CES on the UNI link. LST UNILNK, DSP UNILNK
6.2.3 Procedure
Follow the procedure below to add a UNI link: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] to open the configuration file to be edited. Set NMBU E1/T1 Port Properties
6-2
Right-click NMCU on the equipment panel, and select [Modify NMCU Board] in the shortcut menu to open the dialog box "Modify Slot 2 NMCU Board Properties", as shown in Figure 6-1. Modify the properties of the E1/T1 used for the UNI link in this dialog box. Then click <OK>.
Figure 6-1 NMBU E1/T1 properties
Note: In the tab of the E1/T1 ports, set [Clock Work Mode] to:
z z
Master mode when the E1/T1 ports are connected to the lower level equipment Slave mode when the E1/T1 ports are connected to the upper level node (RNC or upper NodeB)
5)
Add a UNI link
Right-click [Transmission Object Tree/UNI Link Set] in MIT navigation tree and then select [Add UNI Link] in the shortcut tree to display the [Add UNI Link] dialog box shown in Figure 6-2. Modify the UNI link properties in this dialog box and then click <OK>.
6-3
Figure 6-2 UNI properties
Note: "UNI Link No." defines the E1/T1 port of the link.
6) 7)
6-4
6.3 Adding a Fractional ATM Link

6.3.1 Overview
Target Application occasion Prerequisite To add a Fractional ATM link NodeB initial configuration In-service property modification during network optimization The E1/T1 line is ready.

General For initial configuration For in-service property modification Verification command Perform the operation on the peer node (upper level NodeB, lower level NodeB or RNC) also. Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. After a Fractional ATM link is added, Add PVCs, such as NCP, CCP, AAL2PATH, ALCAP, IPoA, Treelink PVC or CES channel on the Fractional ATM link. LST FRAATM, DSP FRAATM
6.3.3 Procedure
Follow the procedure below to add a Fractional ATM link: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] to open the configuration file to be edited. Set NMBU E1/T1 Port Properties
Right-click NMCU on the equipment panel, and select [Modify NMCU Board] in the shortcut menu to display the dialog box "Modify Slot 2 NMCU Board Properties", as shown in Figure 6-3. Modify the properties of the E1/T1 used for the Fractional ATM link in this dialog box. Then click <OK>.
6-5
Figure 6-3 NMBU E1/T1 properties
Note: In the tab of the E1/T1 ports, set [Clock Work Mode] to:
z z
Master mode when the E1/T1 ports are connected to the lower level equipment Slave mode when the E1/T1 ports are connected to the upper level node (RNC or upper NodeB)
5)
Right-click [Transmission Object Tree/Fractional ATM Link Set]. Select [Add Fractional ATM Link] to display the [Add Fractional ATM Link] dialog box, as shown in Figure 6-4. Enter the Fractional ATM link properties in the dialog box, and then click <OK>.
6) 7)
6-6
Figure 6-4 Fractional ATM properties
6.4 Adding an NCP Port

6.4.1 Overview
Target Application occasion Prerequisite To add an NCP port NodeB initial configuration The ATM physical layer bearer (UNI link, or fractional ATM link) is ready
6-7

For initial configuration Only one NCP can be added for a NodeB. Perform the operation on the RNC also. Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. Verification command LST CP, DSP CP
6.4.3 Procedure
Follow the procedure below to add an NCP port: 1) 2) 3) 4) Start configuration management system. Refer to section 4.1 . Click main menu [File/Open] to open the configuration file to be edited. Right-click [Transmission Object Tree/NCP Set] and then select [Add NCP] in the shortcut menu to display the [Add NCP] dialog box, as shown in Figure 6-5. Modify NCP properties in the dialog box, and then click <OK>.
Figure 6-5 NCP properties 5) Click main menu [File/Save] in the configuration management system to save the configuration file.
6-8
6)
To apply the data now, refer to section 4.5.3
Applying Data by Executing
Equivalent MML Command. Otherwise, this procedure ends.
Note: When the configuration file is closed in the configuration management system, the equivalent MML commands recorded are cleared, and the only way to apply the properties modified is to download the configuration file. To save the MML commands, refer to section 4.5.3 .
6.5 Adding a CCP Port

6.5.1 Overview
Target Application occasion Prerequisite To add a CCP port NodeB initial configuration In-service property modification during network optimization The ATM physical layer bearer (UNI link, or fractional ATM link) is ready

General A NodeB must have at least one CCP port and can have more. Perform the operation on the RNC also. For initial configuration For in-service property modification Verification command Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. On all of the upper-level NodeBs, add Treelink PVCs for the CCP PVC of the local NodeB when this local NodeB is cascaded under other NodeBs. LST CP, DSP CP
6.5.3 Procedure
Follow the procedure below to add a CCP port: 1) Start configuration management system. Refer to section 4.1 .
6-9
2)
In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system.
3) 4) 5) 6) 7)
Click main menu [File/Open] to open the configuration file to be edited. Right-click [Transmission Object Tree/CCP Set] on the MIT navigation tree, and then select [Add CCP] to display the [Add CCP] dialog box. Modify the CCP properties and then click <OK>. Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
6.6 Adding an ALCAP Node

6.6.1 Overview
Target Application occasion Prerequisite To add an ALCAP node NodeB initial configuration The ATM physical layer bearer (UNI link, IMA group, STM-1 link, or fractional ATM link) is ready

For initial configuration A NodeB has only one ALCAP node. Perform the operation on the RNC also. Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. Verification command LST AAL2NODE, DSP AAL2NODE
6-10
6.6.3 Procedure
Follow the procedure below to add an ALCAP node: 1) 2) 3) Start configuration management system. Refer to section 4.1 . Click main menu [File/Open] to open the configuration file to be edited. Right-click [Transmission Object Tree/ALCAP Set], and then select [Add ALCAP] to display the [Add ALCAP] dialog box, as shown in Figure 6-6.
Figure 6-6 Adding an ALCAP 4) 5) 6) Modify the ALCAP properties and then click <OK>. Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends. Note: When the configuration file is closed in the configuration management system, the equivalent MML commands recorded are cleared. In that case, the only way to apply the properties modified is to download the configuration file. To save the MML commands, refer to section 4.5.3 .
6-11
6.7 Adding an AAL2 PATH

6.7.1 Overview
Target Application occasion Prerequisite To add an AAL2PATH under an ALCAP node NodeB initial configuration In-service property modification during network optimization The ATM physical layer bearer (UNI link or fractional ATM link) is ready The ALCAP exists

General A NodeB must have at least one AAL2PATH and can have more. Perform the operation on the RNC also. For initial configuration For in-service property modification Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. Before adding an AAL2PATH, add/expand the ATM physical layer bearer (add UNI link or Fractional ATM link) on the Iub interface to bear the AAL2PATH. On all of the upper-level NodeBs, add Treelink PVCs for the AAL2PATH PVC of the local NodeB when this local NodeB is cascaded under other NodeBs. Verification command LST AAL2PATH, DSP AAL2PATH
6.7.3 Procedure
Follow the procedure below to add an AAL2 PATH: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) 5) Click main menu [File/Open] to open the configuration file to be edited. Right-click [Transmission Object Tree/ALCAP Set/ALCAP], and then select [Add AAL2PATH] to display the [Add AAL2PATH] dialog box, as shown in Figure 6-7. Modify the AAL2 PATH properties in the dialog box, and then click <OK>.
6-12
Figure 6-7 Adding an AAL2PATH For details of the properties, click <Help> on the dialog box. 6) 7) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends. Note: When the configuration file is closed in the configuration management system, the equivalent MML commands recorded are cleared. In that case, the only way to apply the properties modified is to download the configuration file. To save the MML commands, refer to section 4.5.3 .
6-13
6.8 Expanding Iub Transport Capacity

6.8.1 Overview
Target Application occasion Prerequisite To expand Iub transport capacity In-service property modification during network optimization None
Note: To expand Iub Transport capacity is to broaden the transport bandwidth of the ATM physical layer bearer (UNI link, Fractional ATM link) to bear more AAL2PATHs and add more AAL2PATHs. The bandwidth of each AAL2 PATH added adopts the default value.

For in-service property modification The operation adds new ATM physical layer bearers, or increases the bandwidth of an ATM physical layer bearer. If there are multiple ATM physical layer bearers, it may be necessary to perform bandwidth planning and reallocate the PVC channels for these ATM physical layer bearers. For transport bandwidth planning, refer to section 5.4. Before expanding operation, perform the "Upper level node configuration" shown in Figure 3-2. Verification command None
6.8.3 Procedure
Follow the procedure below to expand Iub transport capacity: 1)
z z
Expand ATM physical layer bearer. To add UNI link, see 6.2 "Adding a UNI Link". To add Fractional ATM link or use more timeslots in Fractional ATM link, see "6.3 Adding a Fractional ATM Link". Add AAL2 PATH
2)
Add AAL2PATH under ALCAP node. See 6.7 "Adding an AAL2 PATH".
6-14
6.9 Adding a Transparent Link

6.9.1 Overview
Target Application occasion Prerequisite Add a Transparent Link NodeB initial configuration In-service property modification during network optimization NASU exists. E1/T1 0, which corresponds to NASU E1 port 3, or E1/T1 1, which corresponds to NASU E1 port 4 is available for connecting to the lower level equipment.

For initial configuration For in-service property modification Verification command Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. None
LST TRPLNK, DSP TRPLNK
6.9.3 Procedure
Follow the procedure below to add a transparent link: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] to open the configuration file to be edited. Right-click [Transmission Object Tree/Transparent Link Set] in the MIT navigation tree, and then select [Add Transparent Link] in the shortcut menu to display the [Add Transparent Link] dialog box. Select the E1/T1 port in this dialog box, and then click <OK>. 5) 6) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
6-15
6.10 Adding an SDT CES Channel

6.10.1 Overview
Target Application occasion Prerequisite To add an SDT CES channel NodeB initial configuration In-service property modification during network optimization The NMCU E1/T1 port 0 or 1 connects to the lower level equipment

For initial configuration For in-service property modification Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. CES channel consumes upper level PVC bandwidth heavily. Plan the bandwidth carefully. Refer to section 14.6.5. On all of the upper-level NodeBs, add Treelink PVCs for the CES PVC of the local NodeB when this local NodeB is cascaded under other NodeBs. LST UDTCES, LST SDTCES
Verification command
6.10.3 Procedure
Follow the procedure below to add an SDT CES channel: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] to open the configuration file to be edited. Set properties of NMCU E1/T1 ports connected with lower level node (2G BTS or monitoring device)
6-16
Right-click an NMCU in the MIT navigation tree or equipment panel, and then select [Modify NMCU Board] to display the [Modify Slot 2 NMCU Properties] dialog box, as shown in Figure 6-8. In this dialog box, modify the properties of the E1/T1 connected to the lower level equipment in the CES channel and then click <OK>.
Figure 6-8 NMCU E1/T1 properties 5) Add ATM physical layer bearer to the upper level node for bearing the PVC of the CES channel. Refer to section 6.2 or 6.3 to add UNI link, or fractional ATM link. If the ATM physical layer bearer to the upper level node for bearing the PVC exists, skip this step and go to next step. 6) add a CES channel Right-click [Transmission Object Tree/SDT Set] in the MIT navigation tree, and then select [Add SDT CES] in the shortcut menu to display the [Add SDT CES] dialog box, as shown in Figure 6-9. Modify the CES properties in the [Basic Properties] tab and [Virtual Port] tab. Then click <OK>.
6-17
Figure 6-9 Adding an SDT CES channel
Note: The E1/T1 ports, which can serve CES channel, are NMCU E1/T1 ports 0,and 1.
7) 8)
6-18
6.11 Adding a Treelink PVC

6.11.1 Overview
Target Application occasion Prerequisite To add a treelink PVC for lower level NodeB NodeB initial configuration In-service property modification during network optimization None

For initial configuration For in-service property modification Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. On all of the upper-level NodeBs, add Treelink PVCs for the PVCs of the local NodeB when this local NodeB is cascaded under other NodeBs. Treelink PVCs added must provide ATM switch route for all the PVCs of the local NodeB. PVCs of the local NodeB include the NCP, CCPs, ALCAP, AAL2PATHs, CES, and IPoA device. LST TREELNKPVC
6.11.3 Procedure
Follow the procedure below to add a Treelink PVC: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] in configuration management system to open the configuration file to be edited. Add ATM physical layer bearer to lower level node for bearing the PVCs defined by a Treelink PVC. Refer to section 6.2 or 6.3 to add UNI link, or fractional ATM link. If the ATM physical layer bearer to lower level node for bearing the PVCs exists, skip this step and go to next step. 5) Add ATM physical layer bearer to upper level node for bearing the PVCs defined by a Treelink PVC. Refer to section 6.2 or 6.3 to add UNI link, or fractional ATM link. If the ATM physical layer bearer to upper level node for bearing the PVCs exists, skip this step and go to next step.
6-19
6)
Right-click [Transmission Object Tree/PVC Set], and then select [Add PVC] in the shortcut menu to display the [Add PVC] dialog box. Edit the treelink PVC properties in this dialog box, and then click <OK>.
7) 8)
6.12 Modifying NCP or ALCAP

6.12.1 Overview
Target Application occasion Prerequisite To modify properties of NCP or ALCAP In-service property modification during network optimization The NCP or ALCAP exists

For in-service property modification A NodeB has only one NCP and one ALCAP. Modifying NCP or ALCAP properties interrupts the services of the entire NodeB. Make the corresponding modifications to RNC. Verification command LST CP DSP CP LST AAL2NODE DSPAAL2NODE
6-20
6.12.3 Procedure
Follow the procedure below to modify NCP or ALCAP: 1) 2) 3) 4) Start configuration management system. Refer to section 4.1 . Upload the data configuration file through the MML command ULD CFGFILE on O&M system. Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click [Transmission Object Tree/XXX Set/XXX], for example [Transmission Object Tree / NCP Set / NCP], on the MIT navigation tree, and then select [Modify XXX] to display the [Modify XXX properties] dialog box. Modify the properties in the dialog box and then click <OK>. 5) 6) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.2 Applying Data by Downloading Configuration File. Otherwise, this procedure ends.
6.13 Modifying a CCP or AAL2PATH

6.13.1 Overview
Target Application occasion Prerequisite To modify properties of CCP or AAL2PATH In-service property modification during network optimization The CCP or AAL2PATH exists

For in-service property modification Verification command A NodeB must have at least one CCP and one AAL2 PATH. If all CCPs or AAL2 PATHs are deleted, the services of the entire NodeB will be interrupted. Make the same modifications to RNC. LST CP, DSP CP LST AAL2 PATH, DSP AAL2 PATH
6.13.3 Procedure
Follow the procedure below to modify a CCP or AAL2PATH: 1) Start configuration management system. Refer to section 4.1 .
6-21
2) 3) 4)
Upload the data configuration file through the MML command ULD CFGFILE on O&M system. Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click [Transmission Object Tree/XXX Set/XXX], for example [Transmission Object Tree/CCP Set/CCP], on the MIT navigation tree, and then select [Properties] to display the [properties] dialog box. Record the properties that remain unchanged.
5)
Right-click [Transmission Object Tree/XXX Set/XXX], for example [Transmission Object Tree / CCP Set / CCP] on the MIT navigation tree, select [Delete XXX] to display the [Delete XXX] dialog box, and then click <OK>.
Tip: If there is only one CCP or AAL2 PATH, to avoid call drop, perform the following operations:
z
Add a temporary CCP or AAL2 PATH on the NodeB and RNC. The CCP No, AAL2PATH No. and (VPI, VCI) must be different from the old one and the target one. Delete the old CCP or AAL2PATH. Add a CCP or AAL2PATH with the desired properties. Delete the temporary CCP or AAL2PATH.
z z z
6)
Right-click [Transmission Object Tree/XXX Set/XXX], for example [Transmission Object Tree / CCP Set / CCP] on the MIT navigation tree, and select [Add XXX] to display the [Add XXX] dialog box. Modify the properties in the dialog box and then click <OK>.
Note: Another method to modify the CCP or AAL2PATH properties is to right-click [Transmission Object Tree/XXX Set/XXX] on the MIT navigation tree and then select [Modify XXX] to modify the properties. However, this operation does not have equivalent MML commands and the only way to apply the new properties is to download the configuration file and restart the NodeB. Note that restarting NodeB interrupts service of the NodeB.
7) 8)
6-22
6-23
Chapter 7 Maintenance Channel Configuration Procedures

7.1 Modifying Local Maintenance Channel
7.1.1 Overview
Target Application occasion Prerequisite To modify the NMBU Ethernet port IP address, which is referred as local IP address NodeB initial configuration In-service property modification For a new NodeB, the NMBU has its initial IP address. You need to obtain this IP address to log into the NodeB.

General Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. After modifying NMBU Ethernet IP, relog into the NodeB with the new IP address in case of local maintenance. Verification command LST IP
7.1.3 Procedure
Follow the procedure below to modify the local maintenance channel: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click the root node [BTS3802C] in the MIT navigation tree, and then select [Modify 3802C NodeB] in the shortcut menu to display the [Modify BTS3802C Properties] dialog box.
7-1
5) 6) 7)
Modify the local IP address and its subnet mask in this dialog box and then click <OK>. Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
7.2 Adding IPoA Maintenance Channel

7.2.1 Overview
Target Application occasion Prerequisite Add an IPoA device NodeB initial configuration The NodeB has no IPoA device.

For initial configuration Only one IPoA can be added for a NodeB. Figure 3-2 illustrates the location of this procedure in the NodeB initial configuration process. Verification command LST IPOA
7.2.3 Procedure
Follow the procedure below to add an IPoA maintenance channel: 1) 2) Start configuration management system. Refer to section 4.1 . Click main menu [File/Open] in the configuration management system to open the configuration file to be edited.
7-2
3)
Add ATM physical layer bearer to the upper level node for bearing the IPoA PVC. Refer to section 6.2 or 6.3 to add a UNI link or fractional ATM link. If the ATM physical layer bearer to the upper level node for bearing the IPoA exists, skip this step and go to next step.
4)
Right-click [Transmission Object Tree/IPoA Device Set], and select [Add IPoA Device] to display the [Add IPoA Device] dialog box, as shown in Figure 7-1.
Figure 7-1 IPoA properties 5) Modify the IPoA properties, and then click <OK>.
Note:
z z
The properties in [Virtual Port] define the properties of the PVC bearing this IPoA. The NodeB IPoA peer IP serves as the default gateway. All indirect IP packets will be sent to RNC through the IPoA device.
6) 7)
Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 "Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
7-3
7.3 Modifying IPoA Maintenance Channel

7.3.1 Overview
Target Application occasion To modify the properties of IPoA device, such as IP address and bandwidth of the IPoA NodeB initial configuration In-service property modification during network optimization Prerequisite The IPoA device exists.

For in-service property modification Modify the corresponding properties on RNC. When the IPoA local IP is modified, the far end LMT needs to log into the NodeB again using the new IPoA local IP. IPoA is borne on ATM physical layer bearer. To increase the IPoA cell rate, expand the bandwidth of the existing ATM physical layer bearer first. Verfication command LST IPOA
7.3.3 Procedure
Follow the procedure below to modify the IPoA maintenance channel: 1) 2) 3) 4) 5) 6) 7) Start configuration management system. Refer to section 4.1 . Upload the data configuration file through the MML command ULD CFGFILE on O&M system. Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click the corresponding node in the configuration navigation tree, and then select <Modify IPoA> in the shortcut menu. Modify the IPoA properties and then click <OK>. Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
7-4
7.4 Modifying SNTP Properties

7.4.1 Overview
Target Application occasion Prerequisite To modify the properties of SNTP NodeB initial configuration In-service property modification during network optimization The SNTP server exists.
Note: NodeB supports Simple Network Time Protocol (SNTP) to synchronize the time of NodeB with other equipment, like RNC or M2000 server. NodeB initiates synchronization requests to the SNTP Server periodically through the IPoA device and processes the response of the SNTP server. BTS3802C does not care the messages the SNTP Server broadcasts.

General Verfication command None LST SNTPCLTPARA
7.4.3 Procedure
Follow the procedure below to modify SNTP properties: 1) 2) Start configuration management system. Refer to section 4.1 . In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE in O&M system. In case of NodeB initial configuration, skip this step and go to next step.
7-5
3) 4)
Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Activate the SNTP Function.
Right-click the root node [BTS3802C] in the MIT navigation tree, and then select [Modify 3802C NodeB] to display the [Modify BTS3802C Properties] dialog box as shown in Figure 7-2. Set [SNTP Switch of Time Sync] as "ON" in the dialog box. After the "SNTP switch of Time Sync" is set as ON, the [SNTP Server IP address] field will appear.
Figure 7-2 Setting SNTP server 5)

z z z z
Modify the following properties in the dialog box, and then click <OK>. [SNTP Server IP address] [SNTP Sync Period (min)] The time zone the NodeB located The daytime save time (DST) flag
For details of the properties, click <Help> on the dialog box. 6) 7) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
7-6
7.5 Modifying NASU O&M Mode mode

7.5.1 Overview
Target Application occasion Prerequisite To configure the NASU O&M mode as local mode or remote mode NodeB initial configuration In-service property modification during network optimization NMCU has built-in NASU. Add IPoA device before modifying the NASU O&M mode as remote mode

General To modify the NASU O&M mode is to configure the NASU maintenance channel. Only NASU transport manager uses this maintenance channel for NASU operation and maintenance. LST DIALBACK
Verfication command
7.5.3 Procedure
Follow the procedure below to modify the NASU O&M mode: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click [Physical Object Tree/No.2 NMCU Board] in the navigation tree or right-click NMCU on the equipment panel. After that, select [Modify NMCU board Properties] to display the dialog box Modify Slot 2 NMCU Board properties, as shown in Figure 7-3.
7-7
5)
To modify the NASU O&M mode as local, set the NASU O&M mode as Local, as shown in Figure 7-3 and then click <OK>. Go to step 7).
Figure 7-3 NMCU properties
Notes: When NASU O&M mode is configured as local, you can connect the NASU transport manager to the Ethernet port A_ETH on NMCU for the maintenance of NASU and the IP address used by transport manager to log into NASU is the NASU board IP. NASU board IP is defined on the NASU. The NASU board IP can be found using the search function of the transport manager of Optix Navigator. The NASU O&M IP address in Figure 7-3 is not the NASU board IP.
6)
z z
To modify the NASU O&M mode as remote: Set the NASU O&M mode as remote. Modify the NASU O&M IP address and IP Mask.
After that, click <OK> and then go to next step.
7-8
Notes: The NASU O&M IP resides in the NMBU for direct communication with the NASU board IP when the NASU O&M mode is configured as remote. Because the NASU board IP is often set as 129.9.*.*, configure the NASU O&M IP in this subnet.
7) 8)
7-9
Chapter 8 Supplementary Configuration Procedures

8.1 Selecting Clock Source
8.1.1 Overview
Target Application occasion Prerequisite To select GPS clock or Iub clock as the clock source NodeB initial configuration In-service property modification during network optimization Before selecting "GPS Clock", install GPS clock equipment.

General Verification command None DSP IUBCLK
8.1.3 Procedure
Follow the procedure below to select the clock source: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Select a clock source. Right-click [BTS3802C] in the MIT navigation tree, and select [Modify 3802C NodeB] in the shortcut menu to display the [Modify BTS3802C Properties] dialog box, as shown in Figure 8-1. Select Clock Source in [Synchronization Clock Source].
8-1
Figure 8-1 Selecting a synchronization clock source 5) 6) If GPS clock source is selected, go to step 8). If Iub clock source is selected, go to next step. Select E1/T1 Port as Iub Clock Source Right-click NMCU on the equipment panel, and select [Modify NMCU Board] in the shortcut menu to open the dialog box "Modify NMCU Board Properties", as shown in Figure 8-2. In the [Basic Properties] tab of the dialog box, select the E1/T1 port as the Iub clock source.
Note: Only the E1/T1 ports, which connect with the RNC or the upper level NodeB and whose clock work modes are set as "Slave mode", can be selected.
8-2
Figure 8-2 Selecting NMCU Iub clock source 7) 8) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
8-3
8.2 Configuring External Alarm Ports

8.2.1 Overview
Target Application occasion Prerequisite To enable external alarm ports NodeB initial configuration NodeB in-service property modification None

General Verfication command The cable connections of the external alarm ports and external devices must be consistent with the data configuration. LST INFALMTYPE
8.2.3 Procedure
Follow the procedure below to configure external alarm ports: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Right-click [BTS3802C] on the MIT navigation tree, and then select [Modify 3802C NodeB] to display the [Modify BTS3802C Properties] dialog box, as shown in Figure 8-3. 5)
z z
Set the corresponding alarm equipment in "No.0 External Alarm", "No.1 External Alarm", "No.2 External Alarm", and "No.3 External Alarm", and then click <OK>. If a port is not connected with any alarm device, select OFF To apply the default settings, select "DEFAULT".
8-4
Figure 8-3 Alarm collection type definition 6) 7) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
8-5
8.3 Configuring Power Supply Mode

8.3.1 Overview
Target Application occasion Prerequisite To configure power supply mode NodeB initial configuration NodeB in-service property modification External Alarm interface 1 must be defined to collect Mains Failure alarms, and External Alarm interface 2 must be defined to collect Battery Undervoltage alarms. These alarms are trigger conditions for the NodeB to shut down the NDRUs
Note: Normally a NodeB is equipped with a UPS. When mains power supply fails, UPS provides power supply for the NodeB. The power supply provided by the UPS lasts a limited period.
z
If NodeB is configured as Not power save, when mains power supply fails, UPS supplies power to the entire NodeB until the mains supply is restored or UPS is exhausted. If NodeB is configured as power save, power supply mode can be further configured as "delay mode", "under voltage mode" or "mixed mode". In case of mains failure, after a defined period (delay mode) or when the UPS voltage drops under the defined value (under voltage mode), NodeB shuts down the NDRUs to ensure the power supply of the transport module (NMCU).

General Verification command None LST PWSAVE
8.3.3 Procedure
Follow the procedure below to set the power supply mode: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) Click main menu [File/Open] in the configuration management system to open the configuration file to be edited.
8-6
4)
Configure External Alarm interface 1 as default to collect power drop alarms, and External Alarm interface 2 to collect battery low voltage alarms. Refer to section 8.2 for operation procedure.
5)
Right-click [BTS3802C] in the MIT navigation tree, and then select [Modify 3802C NodeB] to display the dialog box [Modify BTS3802C properties], as shown in Figure 8-4.
6)
Set [Power supply mode]. If the selected power supply mode is "delay mode" or "mixed mode", enter the delay duration in [Power time delay (minute)], and then click <OK>.
Note: If the Power supply mode is configured as "Not Power Save", the value of [Power time delay (minute)] is invalid.
Figure 8-4 Power supply mode 7) 8) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to section 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
8-7
Note: When the configuration file is closed in the configuration management system, the equivalent MML commands recorded are cleared. In that case, the only way to apply the properties modified is to download the configuration file. To save the MML commands, refer to 4.5.3 .
8.4 Configuring Module Temperature Thresholds

8.4.1 Overview
Target Application occasion Prerequisite To configure NodeB module temperature threshold NodeB initial configuration NodeB in-service property modification None
Note: Temperature out of thresholds triggers an environment temperature alarm. They can further trigger NodeB auto protection mechanism. Figure 8-5 illustrates the meanings of temperature thresholds.
Temperature drops
T4
T5
T4: Under temperature lower Limit T5: Under temperature Upper Limit
Temperature rises T1 T2 T3 T1: Over Temperature Lower Limit T2: Over Temperature Middle Limit T3: Over Temperature Upper Limit When the temperature rises to T2, a minor alarm occurs. When the temperature rises to T3, a major alarm occurs. When temperature drops to T2, the major alarm is cleared. When the temperature drops to T1, the minor alarm is cleared.
When the temperature drops to T4, a minor alarm occurs. When the temperature rises to T5, this alarm is cleared.
Figure 8-5 Temperature thresholds
8-8

General Verification command None LST BRDTEMPTHD
8.4.3 Procedure
Follow the procedure below to configure module temperature thresholds: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD CFGFILE on O&M system. 3) 4) Click main menu [File/Open] in the configuration management system to open the configuration file to be edited. Set NMCU temperature thresholds. Right-click the NMCU Board in the navigation tree or NodeB equipment panel, and then select [Modify NMCU Board] in the shortcut menu to display the dialog box [Modify NMCU Board Properties], as shown in Figure 8-6. Enter the value of each temperature threshold in this dialog box. The default values are recommended.
Figure 8-6 Setting NMCU temperature thresholds
8-9
5)
Set temperature thresholds of NDRU and power amplifier
Right-click the NDRU Board in the navigation tree or NodeB equipment panel, and then select [Modify NDRU Board] to display the dialog box [Modify NDRU Board Properties], as shown in Figure 8-7. Enter the temperature thresholds in this dialog box. Default values are recommended.
Figure 8-7 Setting temperature thresholds of NDRU and power amplifier 6) 7) Click main menu [File/Save] in the configuration management system to save the configuration file. To apply the data now, refer to 4.5.3 Applying Data by Executing Equivalent MML Command. Otherwise, this procedure ends.
8-10
8.5 Modifying Engineering Parameters

8.5.1 Overview
Target Application occasion Prerequisite To store the engineering parameters in NodeB for quick reference during NodeB maintenance NodeB initial configuration In-service property modification during network optimization None

General Engineering parameters are not running parameters. Instead, they serve as reference for maintenance only. There is no need to restart a NodeB after an engineering parameter file is downloaded to the NodeB. None
8.5.3 Procedure
Follow the procedure below to modify engineering parameters: 1) 2) Start configuration management system. Refer to section 4.1 . In case of NodeB initial configuration, skip this step and go to next step. In case of in-service property modification, upload the data configuration file through the MML command ULD FILE on O&M system. 3) 4) Click main menu [File/Edit Engineering Parameters] in the configuration management system to open the engineering parameter file to be edited. Click <yes> in the pop-up message box to open an existing engineering file, or click <No> to create a new engineering configuration file. In the latter case, the dialog box shown in Figure 8-8 is displayed. 5) 6) Set the engineering parameters in the tabs in this dialog box. Click <Save> in the dialog box. Enter the name and path of the engineering parameter file in the [Save As] dialog box, and then click <OK>.
8-11
Figure 8-8 Engineering parameters 7) Load the engineering parameter file to the NodeB through the DLD FILE command on O&M system. This procedure ends.
8-12
Chapter 9 Local Cell Properties

9.1 Overview of Local Cell Properties
This chapter describes local cell properties including:
z z z
Architecture of local cells NodeB configuration type properties Local Cell logical properties
9.2 Architecture of Local Cells

Figure 9-1 illustrates the cells provided by a NodeB.
RNC
BTS3802C
Two antennas corresponding to one sector (in case of 2-way receive diversity) Antenna mast Two sectors
Sector A Sector B Frequency a Frequency b Cells in the same sector Cells with the same frequency
Figure 9-1 Mapping between radio network coverage and NodeB equipment Table 9-1 and Table 9-2 list the radio network properties in Figure 9-1. Network planner determines these properties.
9-1
Table 9-1 Properties of NodeB configuration type NodeB configuration type Receive diversity Number of sectors Number of frequencies Transmit diversity 2-way receive diversity 1 2 No transmit diversity Example
Table 9-2 Correspondence between sectors, frequencies and Local Cell IDs Sector A Frequency a Frequency b Local Cell ID Aa Local Cell ID Ab Local Cell ID Ba Sector B
In Table 9-2, each column stands for a co-sector cell group and each row stands for a co-frequency cell group. The physical resources for a local cell include baseband resources and RF resources. The baseband resources reside in the NMCU and the RF resources in the NDRU. NDRU consists of NTRU, power amplifier, and NDRF (NodeB Duplexer and Rx Filter). The radio network properties determine the physical resources properties. The properties configured in NodeB include the following types:
z z
NodeB configuration type properties Local cell logical properties
9.3 Properties of NodeB configuration type

Table 9-3 lists the properties related to the NodeB configuration type.
9-2
Table 9-3 NodeB configuration type properties Properties Options Source of the data Peer to be consistent with None RNC Example
Receive diversity mode Sector*carrier Transmit diversity mode
2-antenna, 4-antenna 1*1, 1*2, 2*1 Transmit diversity, No transmit diversity, half frequency (0.5_0.5) NDRU 1, NDRU 3 Two Rx and one Tx channel, One Rx and one Tx channel
network planning network planning network planning
2-antenna 1*1 No transmit diversity
slot(s) of NDRU(s) NDRU work mode
decided by: receive diversity mode, transmit diversity mode, and carrier*sector Configured as "connection" only when the configuration type is 1*2
None
Determined by the selected template
NDRU Connect mode
Connectionless, Connection
Note:
0.5_0.5 configuration type is similar to a transmit diversity mode in terms of configuration. 0.5_0.5 configuration type is only applicable to 1*1. For RNC (Logical cell), 0.5_0.5 belongs to the category of no transmit diversity.
The organization of the RF resources closely relates to the "NodeB configuration type". To simplify the configuration of the RF resources, the configuration management system provides templates of all typical NodeB configuration types. You can use these templates to configure the RF resources, and save the time spent on learning the principle of the RF resources. To maintain the data consistency, avoid partially modifying the NodeB configuration type properties after finishing the configuration of the NodeB configuration type by using template. If some of the properties related to the NodeB configuration type must be modified, select a new template, and then enter all other properties again.
9.4 Local Cell Logical Properties

Table 9-4 lists the local cell logical properties.
9-3
Table 9-4 Local cell logical properties Local cell Local cell 1 Local cell logical properties Local Cell ID1 NDRU used Source of the data Peer to be consistent with RNC None example
The data depends on network planning. All the cells of a NodeB belong to a cell group. For no transmit diversity, it is necessary to specify the NDRU that the cell uses. For transmit diversity, one local cell uses both the NDRUs.
1 NDRU0
Cell radius (Unit: m) Cell inner handover radius (Unit: m) Maximum transmit power Unit: dBm Range: 0 - 50 Step: 0.1 dB
Decided by network planning Decided by network planning Cell Inner Handover Radius should be at least 78.125m (that is 1chip) less than Cell Radius This value must be not less than the maximum transmitting power defined in the network planning. This value cannot be larger than the capacity of the power amplification module of the NodeB. For the information about the maximum of various power amplification modules, refer to the online help.
RNC RNC
1000 0
RNC
370
Local cell 2
Local Cell ID2 NDRU Cell radius Cell inner handover radius Maximum transmit power
The local cell logical properties can be modified individually. However, these properties must be consistent with the settings on RNC.
Caution: The module installation must be consistent with the above properties. After data configuration, view the equipment panel of the configuration management system to check the modules configured.
9-4
Chapter 10 Transport Properties

10.1 Overview of Transport Properties
This chapter describes the following aspects:
z z z z z z z
Architecture of NodeB Transport ATM Physical Layer Bearer properties Iub transport object properties Transparent link properties SDT CES channel properties Treelink PVC properties Transport configuration guideline.
10.2 Architecture of NodeB Transport

10.2.1 Transport Ports
Figure 10-1 illustrates the external transport ports provided by BTS3802C.
NMCU
NASU E1 1 NASU E1 2 NMBU E1 2 NMBU E1 3 A A B B NMBU E1/T1 0 NMBU E1/T1 1
NASU
NASU E1 3 NASU E1 4
NMBU
Transparent transport mode STM-1 0 STM-1 1
Transparent transport switch E1(T1) 1
Non-transparent transport mode
E1(T1) 0
NMBU: NodeB Maintenance and Baseband Unit NASU: NodeB Access Unit Non-transparent link mode: Turn the transparent link switch to B Transparent link mode: Turn the transparent link switch to A
Figure 10-1 BTS3802C transport ports
Note:
Figure 10-1 shows the correspondence between NASU ports and NMBU ports. The tributary E1s in STM-1 of NASU are configured through transport manager.
10-1
Table 10-1 lists the applications of the transport ports. Table 10-1 Applications of BTS3802C transport ports NASU status No NASU Available Port E1(T1) 0 E1(T1) 1 Built-in NASU E1(T1) 0 Transparent link mode Non-transparent link Non-transparent link Non-transparent link Transparent link Connected equipment Connecting NMBU and external equipment Connecting NMBU and external equipment Connecting NMBU and external equipment As No. 3 E1 on NASU, this port connects NASU and external equipment. Connecting NMBU and external equipment As No. 4 E1 on NASU, this port connects NASU and external equipment. Connecting NMBU and NASU Connecting NMBU and NASU Connecting NASU and external equipment Connecting NASU and external equipment Application UNI, Fractional ATM or Connecting with a cascading node in SDT CES UNI, Fractional ATM or Connecting with a cascading node in SDT CES UNI, Fractional ATM or Connecting with a cascading node in SDT CES E1 from STM-1
E1(T1) 1
Non-transparent link Transparent link
UNI, Fractional ATM or Connecting with a cascading node in SDT CES E1 From STM-1
E1 2 E1 3 STM-1 0 STM-1 1
E1 From STM-1, configured as UNI E1 From STM-1, configured as UNI STM-1 STM-1
10.2.2 Transport Networking and Transport Protocol Architecture

Figure 10-2, Figure 10-3, Figure 10-4, Figure 10-5, Figure 10-6, Figure 10-7 and Figure 10-8 illustrate typical transport networking modes.
10-2
AAL layer and the higher layer ATM layer PVC ATM physical layer link (UNI) Physical medium (No. 0, 1 E1/T1)
AA
BTS3802C
RNC
NASU
No.0 and No.1 E1/T1 Optical fiber
NASU
BTS3802C (A)
AA
BTS3802C (B)
AAL layer and the higher layer ATM layer PVC ATM physical layer link (UNI) Physical medium (No. 2, 3 E1/T1)
Figure 10-2 Direct Transport networking and the protocol architecture of the segment In Figure 10-2, there can be no, one or multiple BTS3802C (A)s between BTS3802C(B) and RNC. The existence of BTS3802C (A)s does not affect the data configuration on BTS3802C LMT, because BTS3802C(B) uses the tributary E1 of the STM-1 and the STM-1 is provided by the NASU and configured on the transport manager.
Note: Ring-networking mode can be realized by configuring SDH equipment (NASU). For BTS3802C, the ring-networking mode is the same as the mode illustrated in Figure 10-2.
10-3
AAL lay er and the higher lay er
TREELINK PVC
ATM lay er (PVC)
ATM lay er PVC
ATM phy sical lay er link UNI Phy sical medium(E1/T1)
ATM phy sical lay er link (UNI) Phy sical medium(E1/T1 )
AA RNC
No.0 or 1 E1/T1
D
No.0 or 1 E1/T1
BTS3802C (A)
BTS3802C (B)
Figure 10-3 Treelink PVC and the protocol architecture of each segment
AAL layer and higher layer ATM layer PVC ATM physical layer link (UNI) Physical Medium(E1) A
Transparent transport
D
NASU
RNC
Optical fiber
BTS3802C (A)
No.0, 1 E1
BTS3802C (B)
Figure 10-4 Transparent link networking and the protocol architecture of each segment
10-4
AAL layer and the higher layer ATM layer (PVC) ATM physical layer link (Fractional ATM) Physical medium E RNC 2G equipment cross channel F Physical medium(E1/T1 timeslot) A BTS3802C
2G BSC
2G BTS
No.0 and No.1 E1/T1 (some timeslots)
Figure 10-5 Fractional ATM networking and the protocol architecture of each segment In Figure 10-5, the configurations of the "E" and "F" segments are implemented on RNC and 2G equipment and thus are not described in this manual. This manual only focuses on the configuration of segment A. Figure 10-6, Figure 10-7 and Figure 10-8 illustrate the transport channels for cascading 2G BTS.
AAL layer and higher layer CES CHANNEL ATM layer (PVC) CES CHANNEL
ATM physical layer link Physical medium(E1/T1) A
E1/T1 line F 2G BSC
E1/T1 line C 2G BTS
RNC
No.0 or No.1 E1
BTS3802C
No.1 or 0 E1
Figure 10-6 CES channel networking for 2G BTS and transport protocol architecture of each segment In Figure 10-6, the configurations of "E" and "F" are implemented on RNC and 2G equipment. This manual will not introduce the configuration of "E" and "F".
10-5
E1 line C
NASU
2G BSC
RNC
Optical fiber
BTS3802C
Optical fiber
2G BTS
Figure 10-7 SDH network shared with 2G BTS and transport protocol architecture of each segment
Transparent transport D NASU 2G BSC RNC/ADM

Optical fiber BTS3802C(A)
E1 line
C
No.0 or 1 E1
2G BTS
Figure 10-8 Transparent link for 2G BTS and transport protocol architecture of each segment
10.2.3 Transport Networking Mode Selection

There are three networking modes for tree networking of BTS3802Cs, as listed in Table 10-2. Table 10-2 NodeB tree networking modes NodeB tree networking mode Using optical fiber (BTS3802C(A) and (B) in Figure 10-2) Using transparent links (Figure 10-4) Transport bandwidth Each node can be configured with at most two UNI links. Each node exclusively occupies its UNI link transport bandwidth. Each node can be configured with at most two UNI links. Each node exclusively occupies its UNI link transport bandwidth. Using treelink PVC (Figure 10-3) The NodeB and the neighboring lower level NodeB share the upper level link by statistic multiplex mode and thus save the transport bandwidth. Configuration method The configuration is made on NASU through transport manager. No special configuration is needed on BTS3802C (B). Apart from the configuration on NASU by transport manager, configuration of transparent channel on BTS3802C (A) in Figure 10-4 is also needed. Configure treelink PVCs for all PVCs of BTS3802C (B) on all the upper NodeBs. BTS3802C (A) is illustrated as an upper NodeB
10-6
BTS3802C provides three modes of transport channels for 2G BTS, as shown in Table 10-3. Table 10-3 Modes of transport channels provided for 2G BTS Mode SDH networking (Figure 10-7) Transparent channel (Figure 10-8) SDT CES channel (Figure 10-6) Transport bandwidth The transport bandwidth depends on the transport bandwidth of SDH STM-1. A BTS3802C provides at most two transparent link E1s. A BTS3802C provides at most two CES channels. In a CES channel, only parts of E1/T1 timeslots are available. Configuration method Configure on NASU through transport manager. No more configurations are needed on BTS3802C. Apart from the configuration on NASU through transport manager, configure transparent channel on BTS3802C. Configure CES channel on BTS3802C.
10.2.4 Peers of the Transport Protocol layers

Figure 10-2, Figure 10-3, Figure 10-4, Figure 10-5, Figure 10-6, Figure 10-7 and Figure 10-8 show that in various networking modes, peers of transport protocol layers are different:
z
For segment "AA" in Figure 10-2, the peers of the physical medium (E1/T1 line) layer, the ATM Physical Layer Bearer, and the ATM layer on BTS3802C are on the RNC. Therefore, the BTS3802C negotiates with RNC for the configuration data of the protocol layers.
For segment "A", the peers of the protocol layers for BTS3802C may be on the upper NodeB or RNC.
For example:
z
For segment "A" in Figure 10-3, the peers of the physical medium (E1/T1 line) layer, ATM Physical Layer Bearer, and ATM layer on BTS3802C are on the upper NodeB. The BTS3802C negotiates with the upper NodeB for the configuration data of these protocol layers. However, the peers of the AAL layer and the higher layer on BTS3802C are on the RNC, and the BTS3802C must negotiate with RNC for the configuration data of the AAL protocol layer and the higher protocol layers.
For segment "A" in Figure 10-4, the peer for negotiating the data of the clock mode, line coding, frame structure, ATM Physical Layer Bearer, and ATM layer PVC on BTS3802C is the RNC, while the peer for negotiating the E1 port No. is the upper NodeB.
During transport configuration, data negotiation is very important. The peers of each protocol layer for negotiation must be carefully selected based on the corresponding
10-7
transport protocol architecture shown in Figure 10-2, Figure 10-3, Figure 10-4, Figure 10-5, Figure 10-6, Figure 10-7 and Figure 10-8.
10.3 ATM Physical Layer Bearer Properties

10.3.1 Overview
This section describes the ATM physical layer bearer properties. Table 10-4 lists the ATM Physical Layer Bearers supported in BTS3802C. Table 10-4 ATM Physical Layer Bearer types on Iub interface Bearer Type UNI link Fractional ATM link Port NMBU E1/T1 0 to 3 can be configured as UNI links. Only NMBU E1/T1 0 and 1 can be configured as fractional ATM link.
10.3.2 UNI Link Properties

Table 10-5 lists the UNI link properties. Table 10-5 UNI Link properties (the data provided serves as examples only) UNI No. (E1/T1 port) UNI 2 UNI 3 E1/T1 mode E1 E1 E1/T1 properties Clock mode Slave Slave Frame structure CRC-4 CRC-4 Line code HDB3 HDB3 Link property Scramble mode Enable Enable Port on RNC/ upper NodeB Board Slot Slot n Slot n E1/T1 Port Port m Port m
Note: Line properties and link properties: The properties on both sides of an E1/T1 must be the same except for the clock mode. Clock mode: The port connecting with the upper level node must be set as "Slave mode", and the one connecting the lower level node must be set as "Master mode". When "Line code" is "AMI mode", "Scramble mode" must be set as "Enable".
10.3.3 Fraction ATM Link Properties

Figure 10-9 shows the configuration principle of Fractional ATM transport channel.
10-8
(VPI,VCI) for NCP (VPI,VCI) for CCP (VPI,VCI) for ALCAP (VPI,VCI) for IPoA (VPI,VCI) for AAL2 PATH (VPI,VCI) for T reelink PVC VPI,VCI Fractional AT M Fractional AT M link VPI,VCI Fractional AT M
Available timeslots Unavailable timeslots
. .
NMBU E1/T1 0 or 1 BTS3802C2G BTS
. .
2G BSC--RNC
Figure 10-9 Architecture of Fractional ATM link Table 10-6 lists the Fractional ATM link properties. Table 10-6 Fractional ATM link properties Fractional ATM link No. (E1/T1 No.) Fractional ATM link 0 E1/T1 mode E1 E1/T1 Line property Clock mode Slave Frame structure CRC-4 Line code HDB 3 Link property Scrambl e mode Enable Time slot 1~10 Port on RNC/ upper NodeB Board Slot Slot n E1/T1 Port Port m
Note: Line properties and link properties: The properties on both sides of E1/T1 must be the same except for the clock mode. The "Scramble mode" of a Fractional ATM link must be consistent with that of the RNC or the upper level NodeB. Clock mode: The port connecting with the upper level node must be set as "Slave mode", and the one connecting the lower level node must be set as "Master mode". When "Line code" is "AMI mode", "Scramble mode" must be set as "Enable".
10.4 Iub Transport Object Properties

10.4.1 Overview
This chapter describes the properties of segment "AA" and "A" in Figure 10-2, Figure 10-3, Figure 10-4 and Figure 10-5.
10-9
10.4.2 Architecture of Iub Transport

Figure 10-10 illustrates the objects constituting an lub transport layer. A NodeB must be configured with the following Iub transport objects:
z z z
One NCP One ALCAP At least one CCP. If there are multiple CCPs added, they work in load-sharing mode. It is advisable that the number of CCPs be the number of cells. One or more AAL2PATHs. The number of AAL2PATHs depends on the service capacity of the NodeB. See Chapter 12 Transport Bandwidth Planning. One IPoA
(VPI, VCI) for IPoA (VPI, VCI) for NCP (VPI, VCI) for CCP1
lay er
(VPI, VCI) for CCP2 (optional) (VPI, VCI) for ALCAP (VPI, VCI) for AAL2PATH1 (VPI, VCI) for AAL2PATH2 (optional)
AT M
...
RNC/upper NodeB
ATM physical layer link (UNI/Fractional ATM)
NodeB
Figure 10-10 Iub Transport Objects Table 10-7 lists the transport objects on ATM Layer and the Higher Layers. Table 10-7 Transport objects on ATM Layer and the Higher Layers Objects PVC Explanation (ATM Physical Layer Bearer, (VPI, VCI)) defines a PVC channel. A PVC channel must be unique within a NodeB, namely, (ATM Physical Layer Bearer, (VPI, VCI)) must be unique. NCP,CCP, ALCAP, AL2PATH, IPoA A NodeB must have an NCP, an ALCAP, one or two CCPs, one or two AAL2 PATHs, and an IPoA. Relationship between objects If PVCs are borne on the same ATM physical link, the total bandwidth of the PVCs should be smaller than the bandwidth of this link. An Iub interface transport object (NCP, CCP, ALCAP, or AAL2PATH) corresponds to one PVC channel.
10-10
AT M
lay er
Note:
An AAL2 PATH supports up to 248 micro channels. As each AMR voice consumes two micro channels, and the full configuration of BTS3802C supports 64 such channels, together with the demands of the common channels, one AAL2 PATHs may be enough for a fully configured BTS3802C. The peak rate of the AAL2path must satisfy the traffic demand.
10.4.3 Properties of NCP, CCP, ALCAP, AAL2PATH and IPoA

Table 10-8 lists the properties of the Iub transport objects. Table 10-8 Properties of the Iub transport objects (the data serves as examples) Iub transport objects PVC Bearing link identifier on NodeB UNI0 UNI0 UNI0 UNI0 UNI0 VPI VCI Peak rate (kbit/s) 64 64 64 64 64 ATM address AAL and the higher layer Address Other Properties
IPoA NCP CCP1 CCP2 ALCAP node
6 6 6 6 6
90 91 93 94 92
Local IP, Peer IP,
Service Type, Sustaining Cell Rate Timer_CC, Timer_POLL, Timer_No_Response , Timer_Keep_Alive, Max Connection Control Count, Max Poll Data Count, Max STAT Count. Sustaining Cell Rate, Max Burst Size, Cell Delay Variation Tolerance
AAL2 PATH 0 (path id = 1) AAL2 PATH 1 (path id = 2) Note: The CCP ID and AAL2PATH ID must be identical on the NodeB and RNC
UNI 1
60
1920
Note: For Figure 10-2, Figure 10-4 and Figure 10-5, the peer to negotiate with is RNC. For Figure 10-3, the peer is the upper NodeB. The properties should be consistent with the peer.
Note: These properties must be consistent with the RNC.
10.4.4 Determine Iub Transport Object Properties

The procedure of determining Iub transport object properties is as follows:
10-11
1) 2)
Decide the E1/T1 mode, port connection, and ATM Physical Layer Bearer type between the peers. This step decides the properties in Table 10-5. Decide the ATM physical layer bearers of NCP, CCP, ALCAP, AAL2 PATH and IPoA. This step decides the properties of "the bearing link on NodeB" in Table 10-8. The data is the ATM Physical Layer Bearer decided in the previous step. If multiple ATM Physical Layer Bearers are used, you must evenly allocate the bandwidth of the links to bear the Iub transport objects.
3)
Decide VPIs and VCIs of NCP, CCP, ALCAP, IPoA, and AAL2 PATH. (VPI, VCI) should be unique when the PVCs are on a common physical link. This step decides the "VPI" and "VCI" in Table 10-8.
4)
Decide the ATM address of the ALCAP and the IP address of IPoA device in Table 10-8.
10.5 Transparent Link Properties

10.5.1 Overview
Transparent link is for the transport networking modes illustrated in Figure 10-4 and Figure 10-8.
10.5.2 Architecture of Transparent Link

Figure 10-1 shows the architecture of transparent link. Transparent link refers to the E1 (No.0 E1 or No.1 E1) when their transparent link switch is switched to "A". In transparent link, E1 0/1, which are the tributary E1 of NASU, transport data of the cascaded equipment (for example, lower level NodeB, 2G BTS, and monitor equipment). NASU is a built-in SDH unit. NodeB E1 0 and 1 connect with NASU E1 3 and 4 respectively. To establish a transparent link, you must:
z z z
Equip BTS3802C with an NMCU that has a built-in NASU module. Configure the properties of NASU by the NASU transport manager. Set transparent link switch by the BTS3802C configuration management system.
This chapter introduces the operation of setting the transparent link switch. This document does not include the data configuration of NASU through transport manager.
10.5.3 Properties of Transparent Link

According to the transport protocol stacks illustrated in Figure 10-4 and Figure 10-8, the properties of the transparent link (D segment) include only the E1 port connection relationship between the NodeB and the cascading equipment. The E1 properties, including clock mode, link code, and frame structure, must be negotiated with the protocol peers of the E1 line shown in Figure 10-4 and Figure 10-8. They do
10-12
not involve the transparent link configuration on BTS3802C (A) because the transparent link bypasses the BTS3802C (A). Table 10-9 lists the properties of the transparent link. Table 10-9 Properties of Transparent link (the data provided serves as examples only) Transparent link Transparent link A Transparent link B E1 port on the NodeB ( E1 0 or E1 1) E1 0 E1 n E1 port on the cascading equipment
10.6 SDT CES Channel Properties

10.6.1 Overview
This section describes the CES channel properties of segments "D" and "C" in Figure 10-6. The description covers the following aspects:
z z z
Architecture of CES channel CES Channel Bandwidth Planning Properties of CES Channel
10.6.2 Architecture of SDT CES Channel

Figure 10-11 illustrates the CES channel provided by the NodeB for lower level equipment. The figure highlights the E1/T1 timeslots available for the lower level equipment in mauve.
Channel to lower level equipment
avail abl e timeslots on NMBU E1/T1 0,1
Channel to upper level node
. .
CES c hannel NCP CCP ALCAP IPoA AAL2 PATH network ing PVC VPI, VCI UNI, Frac tional ATM link E1/T1 port
CES channel NCP CCP ALCAP IPoA AAL2 PATH networking PVC VPI, VCI UNI, Fractional ATM link I u b physical port
...
...
Lower level equipment (2G BTS)
BT S3802C NMCU
Upper level node (RNC or NodeB)
Figure 10-11 SDT CES channel

10-13
Configuring the structured CES channel includes configuring the "channel to the lower level equipment" and "channel to upper level node". According to Figure 10-6, the SDT CES channel comprises the segments of "A", "C", "D", "E" and "F". Among them, the configurations of segments "A","D" and "C" are described in this document.
10.6.3 Bandwidth Planning for CES Channel

The bandwidth of PVC consumed by the CES channel may be considerably large. Without a reasonable planning, the PVC bandwidth may be larger than the UNI link bandwidth bearing this PVC, which will result in abnormal CES channel. For the calculating and planning bandwidth, refer to 12.5 .
10.6.4 Properties of CES Channel

Table 10-10 describes the CES channel properties. Decide the peer of each transport protocol layer for data negotiation according to Figure 10-6. Table 10-10 CES channel properties Channel to Lower Level Node Channel to Upper Level Node ATM Physical Layer Bearer Properties described in Table 10-11 Negotiate with the lower level equipment. Properties described in Table 10-5 Negotiate with the upper level node. ATM layer and the higher layer Properties described in Table 10-12 Negotiate with the upper level node (upper level NodeB or RNC).
Table 10-11 Properties of CES channel to lower level equipment (the data serves as examples) CES channel No. 0 E1/T1 properties on NodeB side E1/T1 No. (E1/T1 0 or 1) E1/T1 0 E1/T1 mode E1 Link code HDB 3 Frame structure CRC-4 Clock mode Master mode Timeslot available 0, 1 E1/T1 on Cascading equipment
2G BTS E1/T1 n
Note: Except for E1/T1 port No. and clock mode, all the other properties must be identical with the settings on the E1/T1 peer (cascading equipment). The clock mode must be configured as master mode. The clock mode on the peer must be configured as slave mode.
10-14
Table 10-12 Properties of CES channel to upper level equipment (ATM layer and the higher layer) CES channel No. 0 Bearing link identifier on NodeB UNI 0 6 VPI 40 VCI 47 ATM cell filling degree
Note: A BTS3802C can support at most two CES channel
Note: The configuration must be consistent with the upper node (upper NodeB or RNC). (VPI, VCI) must be unique among the PVCs on the same ATM Physical Layer Bearer.
Note: It must be consistent with the setting on RNC. The filling degree must be larger than the number of timeslots. The maximum filling degree is 47.
10.7 Treelink PVC Properties

10.7.1 Overview of Treelink PVC Properties
This section introduces the configuration of "D" in Figure 10-3.
10.7.2 Architecture of Treelink PVC

Figure 10-12 illustrates the architecture of Treelink PVC. In this figure, BTS3802C cascades with a lower level NodeB. By Treelink PVCs, BTS3802C provides switching route for the PVCs of the lower level NodeB.
Lower level NodeB PVCs Neighboring lower l evel NodeB PVCs
(VPI,VCI) for NCP (VPI,VCI) for CCP (VPI,VCI) for ALCAP VPI,VCI) for AAL2PATH (VPI,VCI) for IPoA (VPI,VCI) for CES (VPI,VCI) for Treelink PVC
Treelink PVC (ATM ro ute table)
(VPI, VCI)1 UNI/Fractional AT M E1/T1 port
(VPI, VCI)1 UNI/Fractional AT M E1/T 1 port
...
...
...
...
Cascading NodeB
Local BTS3802C
RNC or upper NodeB
Figure 10-12 Architecture of Treelink PVC Configure a treelink PVC for each PVC of the lower level NodeB, as shown in Figure 10-12.
10-15
10.7.3 VPI Planning

To simplify and standardize PVC data, use the VPI plan illustrated in Figure 10-13. In this way, the VPIs of PVCs in "D" of Figure 10-13 can be the VPIs of PVCs in "A".
AAL lay er and higher lay er
ATM lay er (PVC)
ATM lay er PVC
TREELINK PVC
ATM phy sical lay er link UNI Phy sical medium(E1/T1)
ATM phy sical lay er link (UNI) Phy sical medium(E1/T1 )
AA RNC
No.0 or 1 E1/T1
A
No.0 or 1 E1/T1
BTS3802C (A)
BTS3802C (B)
BTS3802C (C)
VPIs, except that of networking PVC, are 6
Figure 10-13 VPI planning
10.7.4 Bandwidth Planning for Treelink PVC

The transport bandwidth should be carefully planned. For the calculation and planning of transport bandwidth, refer to Chapter 12 .
10.7.5 Properties of Treelink PVC

Table 10-13 describes the Treelink PVC properties. Decide the peer of each protocol layer for data negotiation according to Figure 10-13. Table 10-13 Treelink PVC Properties ATM Physical Layer Bearer source port (to the lower level node) Refer to Table 10-5 to create such a table for the lower level NodeB destination port (to the upper level node) Record in Table 10-5 of the local NodeB Described in Table 10-14 ATM layer PVC
Negotiate the properties of the ATM Physical Layer Bearer first.
10-16
Table 10-14 Properties of Treelink PVC (ATM route table) (The data serves as examples) PVCs on the Iub interface of the lower level NodeB Source port ATM Physical Layer Bearer on the local NodeB Treelink PVC0 (for neighboring lower level NodeB NCP) Treelink PVC1 (for neighboring lower level NodeB CCP1) Treelink PVC3 (for neighboring lower level NodeB ALCAP) Treelink PVC4 (for neighboring lower level NodeB AAL2 PATH 1) Treelink PVC6 (for neighboring lower level NodeB IPoA) Treelink PVC7 (for neighboring lower level NodeB CES channel 1) Treelink PVC10 (for neighboring lower level NodeB treelink PVC1) Note "AA" in Figure 10-13 "D" in Figure 10-13 No.1 UNI (8, 90) No.0 UNI (8, 90) 64 No.1 UNI (7, 40) No.0 UNI (7, 40) 64 No.1 UNI (7, 60) No.0 UNI (7, 60) 1920 No.1 UNI (7, 92) No.0 UNI (7, 92) 64 No.1 UNI (7, 93) No.0 UNI (7, 93) 64 No.1 UNI PVC (VPI, VCI) (7, 91) Destination port ATM Physical Layer Bearer on the local NodeB No.0 UNI PVC (VPI, VCI) (7,91) Bandwidth (kbit/s) 64
No.1 UNI
(7, 90)
No.0 UNI
(7, 90) 64
the peer is the lower level NodeB, "A" in Figure 10-13
(VPI, VCI) must be unique on the same ATM Physical Layer Bearer. The bandwidth of D should equal to the bandwidth of A which is listed in the Table 10-8 of BTS3802C (B). BTS3802C supports up to 24 treelink PVCs and up to five levels of cascade.
10-17
10.8 Transport Configuration Guideline

10.8.1 Configure Tree Transport Network from Upper-level-segment to Lower-level-segment
Tree transport networks are made up of segments, such as AA, A, C, D shown in Figure 10-2, Figure 10-3, Figure 10-4, Figure 10-5, Figure 10-6, Figure 10-7 and Figure 10-8. Tree transport networks should be configured from upper-level segment to lower-level segment. Taking the networking modes in Figure 10-2, Figure 10-3, Figure 10-4, Figure 10-5, Figure 10-6, Figure 10-7 and Figure 10-8 as examples, the configuration sequence is as follows: 1) 2) Configure segment "AA" or "A" first. Configure segment "C" and then "D".
10.8.2 Configure Each Segment from Bottom Layer to Top Layer

Taking the segment AA in Figure 10-2 as an example, to configure the segment AA is to configure the NCP, CCP, ALCAP, AAL2 path, and IPoA. The segment is made up of different layers, as shown in Figure 10-14. The transport configuration should be implemented from the bottom layer upward.
CES AAL2 PATH CBR VBR-RT VBR-NRT NCP or CCP or ALCAP or IPoA
Iub data segmentation packing
AAL1
AAL2
AAL5
IMA/UNI/STM-1
VCI-101
VPI-10 VPI-10
ATM Cell
VCI-100 VCI-100
E1/T1/SDH(STM-1)
VCI-101
VPI-20 AAL Layer ATM Layer Physical Layer
Figure 10-14 Transport channels in the NodeB The data configuration sequence is as follows: 1) Configure the E1/T1 ports.
10-18
2) 3)
Configure the UNI or Fractional ATM. Configure the NCP, CCP, ALCAP, AAL2 path, IPoA, and treelink PVC.
10-19
Chapter 11 Maintenance Channel Properties

11.1 Overview of Maintenance Channel Configuration
This chapter provides information on the following subjects:
z z z
Architecture of BTS3802C maintenance channel IP Planning IPoA Maintenance Channel Configuration Guideline
11.2 Architecture of BTS3802C Maintenance channel

Figure 11-1 illustrates the architecture of BTS3802C maintenance channel.
NMCU
NMCU panel
NASU O&M s witch: A: IPoA maintenance B: Local maintenanc e
NMBU Ethernet port IP (IP0

M_ETH
NASU
NMBU
NMBU local maintenanc e channel
RST
B A
NASU board IP (IP1)
A_ETH
NASU local maintenanc e channel NASU Ethernet port
NASU O&M IP (IP2)
IPoA local IP (IP1) (IPoA peer IP is IP3)
IPoA devic e
NASU IPoA maintenanc e channel
NMBU IPoA mai ntenance c hannel
Figure 11-1 Architecture of NASU maintenance channel
11-1
Caution: As shown in Figure 11-1, between NASU local maintenance channel and NASU IPoA maintenance channel, only one can be selected. The selection depends on the status of the "NASU O&M switch".
z
If NASU local maintenance mode is selected, the IP address of the NASU Ethernet port is NASU board IP defined on the NASU, not the NASU O&M IP address defined in the NMBU properties. If NASU IPoA maintenance mode is selected, the NASU Ethernet port cannot be used.
Table 11-1 describes the types of BTS3802C maintenance channels. Table 11-1 Maintenance channels in BTS3802C Type NodeB maintenance channels Maintenance channel NMBU local maintenance channel NMBU IPoA maintenance channel NASU local maintenance channel NASU IPoA maintenance channel: SDH internal maintenance channel Description Log into BTS3802C through the NMBU Ethernet port on BTS3802C NMCU Log into BTS3802C through the IPoA between BTS3802C and RNC Log into NASU through NASU Ethernet port on NMCU by using NASU board IP (not NASU O&M IP) Log into NASU through the IPoA between BTS3802C and RNC The channel is the SDH inband Data Communication Channel (DCC). This maintenance channel is introduced in the manual of NASU transport manager. This manual does not provide the related information
NASU maintenance channels
11.3 IP Planning
11.3.1 IP networking
Figure 11-2 illustrates the BTS3802C IP networking.
11-2

NASU board IP NASU O&M IP IPoA local IP
SNT P server subnet5
IPoA peer IP RNC BAM IP NASU subnet1 NMBU NMCU BTS3802C subnet2 subnet3 RNC subnet4
subnet6
M2000 centralized network manager
T ransport manager LMT 1 (Optix Navigator)
T ransport manager Optix NES iManage
LMT 2
Figure 11-2 BTS3802C IP network
11.3.2 IP addresses
Table 11-2 lists the IP address for BTS3802C maintenance. Table 11-2 BTS3802C IP addresses (the data in selected value serves as an example only) Subnet 1 IP name NASU board IP Optix Navigator transport manager IP NASU O&M IP 2 NMBU Ethernet port IP LMT1 IP 3 IPoA local IP IPoA peer IP 4 LMT2 IP Optix iManager transport manager IP RNC BAM IP 5 6 SNTP server IP M2000 IP Location NASU Transport manager NMBU NMBU LMT1 NMBU RNC LMT2 Transport manager RNC BAM Server M2000 Application When NASU is configured as local maintenance, NASU board IP is the NASU Ethernet port IP on NMCU. In this case, the NASU Ethernet port connects with NASU transport manager using crossover network cable. Ethernet port IP of NMBU for the interconnection with NASU. NMBU Ethernet port connects with LMT using crossover Ethernet cable for NodeB local maintenance. Interconnection with RNC for maintenance of BTS3802C and its NASU from Far RNC through Iub interface. IPoA maintenance through LMT2 to BTS3802C IPoA maintenance through Optix iManage to NASU Selected value 129.9.1.1/16 129.9.1.2/16
129.9.8.1/16 17. 21.2.15/16 17. 21.148.14/16 12.13.11.1/16 12.13.1.4/16 192.13.13.2/16 192.13.13.3/16
IP Gateway for far end equipment (LMT, M2000 or SNTP server) to access BTS3802C For time synchronization of BTS3802C with the SNTP server For centralized network management of
11-3
192.13.13.4/24 10.150.22.33/16 10.160.22.13/16
Subnet
IP name
Location BTS3802C
Application
Selected value
Caution: Different devices cannot have the same IP address. Subnet 1, Subnet 2, Subnet 3 and Subnet 4 cannot be the same. One subnet cannot enclose another.
Note:
The default IP subnet of NASU board IP address is 129.9.*.*. The IP address of Optix Navigator should be in this subnet so that Optix Navigator can find NASU during local maintenance. Optix Navigator configures the NASU board IP address. LMT can only query the NASU bard IP address by using the command LST NASUIP. Before using the command to query the NASU board IP address, the following requirements must be satisfied:
z z
Set NASU maintenance mode as remote. Set NASU O&M IP address. The NASU O&M IP address must be in the same subnet of the NASU board IP address, which is 129.9.*.*.
11.3.3 IP routes
Inter-subnet IP communication entails the configuration of IP routes. Table 11-3 lists the IP routes for BTS3802C maintenance. Table 11-3 IP Routes for BTS3802C maintenance Maintenance channel NMBU IPoA maintenance channel NASU IPoA maintenance channel From LMT2 NMBU Optix NES iManage NASU To NMBU IPoA local IP LMT2 NASU Optix NES iManager IP Gateway RNC BAM IP address in Figure 11-2 IPoA peer IP address in Figure 11-2 RNC BAM IP address in Figure 11-2 Gateway for the 1st hop: NASU O&M IP address. Configure the gateway on NASU. Gateway of the 2nd hop: BTS3802C IPoA peer IP address. Configure the gateway on NMBU. NMBU IPoA maintenance channel M2000 NMBU NMBU IPoA local IP M2000 IP address of the router Port to which M2000 is connected IPoA peer IP address
11-4
Maintenance channel NMBU IPoA maintenance channel
From NMBU SNTP SNTP
To IPoA peer IP address
IP Gateway
NMBU IPoA local IP
IP address of the router Port to which SNTP is connected
11.4 IPoA Maintenance Channel Configuration Guideline

Figure 11-3 shows the configuration of the IPoA maintenance channel.
The route to LMT (IP4), SNTP Ser ver, (A) Configure IPoA gateway: IP2 local IP: IP1
IPoA peer IP: IP2
(D) Configure the (C) Configure LMT route to BTS3802C Ether net IP: IP4 (IP1), gateway:IP3
NMBU ETH IP
IP0
IP1
IP2 IP4 LMT
Lower level Node B IP6
IP3 Local BTS3802C IP5 RNC
The route to LMT(IP4), gateway:IP5
Configure IPoA local IP: IP6
(B) Configure networ king PVC
IPoA peer IP:IP5
Configure the route to lower NodeB (IP6), gateway:I P3
Figure 11-3 IPoA maintenance configuration Table 11-4describes the operation for IPoA maintenance channel illustrated in Figure 11-3. Table 11-4 IPoA maintenance channel configuration Task Configure Local BTS3802C IPoA maintenance channel Position Configuration on NodeB Configuration on LMT Configuration on RNC Configure Lower Level NodeB IPoA maintenance channel Configuration on lower level NodeB Configuration on Local BTS3802C Operation Configure IPoA device (A in Figure 11-3). The corresponding IPoA should also be configured on RNC (1) IP address of the Ethernet port on LMT: Refer to (C) in Figure 11-3, (2) IP route from LMT to NodeB: Refer to (D) in Figure 11-3. (1) Configure IPoA device for the local BTS3802C. (2)Configure the routes on RNC for IP communication between NodeB and far end LMT. Configure IPoA device. The corresponding IPoA should also be configured on RNC Configure a treelink PVC for the lower node IPoA, namely (B) in Figure 11-3.
11-5
Task
Position Configuration on LMT Configuration on RNC
Operation (1) Configure IP address of the Ethernet port on LMT (2) Configure IP route from LMT to the lower level NodeB. (1) Configure IPoA device for the lower level NodeB (2) Configure the IP routes for communication between NodeB and far end LMT.
11-6
Chapter 12 Transport Bandwidth Planning

12.1 Planning Transport Bandwidth
Serv ice traff ic PVC bandwi dth ATM phy sical lay er link bandwidth
VPI-10
VPI-10
RNC or upper NodeB
NodeB
Figure 12-1 Traffic and the bearing transport objects Figure 12-1 shows the Traffic and the bearing PVCs and the bearing ATM Physical Layer Bearers. The purposes of transport bandwidth planning are as follows:
z
Guarantee that the bandwidth of the PVCs bearing NCP, CCP, ALCAP and AAL2PATH satisfies the demands of the service transport. For the bandwidth of NCP, CCP, ALCAP and AAL2PATH, the default values are advisable.
If there are multiple ATM Physical Layer Bearers, the PVCs of the Iub interface transport objects (NCP, CCP, ALCAP and AAL2PATH) should be distributed onto different ATM physical layer bearers evenly.
If multiple PVCs are borne on the same physical bearers, make sure that the sum of the bandwidths is smaller than the bandwidth of the ATM Physical Layer Bearer.
The rule for planning the transport bandwidth is as follows: Total bandwidth of the ATM physical layer bearers between the local NodeB and the upper node (RNC or upper level NodeB) service traffic of the local NodeB (SCR for VBR) + bandwidth occupied by CES + service traffic of all the lower level NodeB In the formula above,
z
If no lower NodeB is configured, then "service traffic of all the lower level NodeB" is zero. If there is no CES channel in the local NodeB then the bandwidth occupied by the CES is zero.
12-1
12.2 Bandwidth of ATM Physical Layer Bearer

Table 12-1 shows the bandwidth and overhead of E1/T1. Table 12-1 Bandwidth and overhead of E1/T1 E1/T1 mode E1 1.92 Mbit/s; E1 overhead: (1 1.920 Mbit/s / 2.048 Mbit/s) x 100% = 6.25% T1 1.536 Mbit/s 0.064 Mbit/s x timeslot occupied Bandwidth of UNI link Bandwidth of Fractional ATM link 0.064 Mbit/s x timeslot occupied
12.3 Calculating Traffic

Formula for calculating traffic is as follows: Traffic = voice traffic VAD + data traffic + signaling traffic Taking UNI link as an example, the formula is detailed in Table 12-2. Table 12-2 Formulas for calculating traffic Formula Voice traffic = voice service traffic + voice channel associated signaling traffic + Voice signaling part control frame traffic. Sub-formula Voice service traffic = 12.2 kbit/s x N (number of voice subscribers) / (1 - FP overhead) / (1 - ATM overhead) / (1 - AAL2 overhead) / (1 - E1 overhead (UNI)) = 12.2 kbit/s x N (number of voice subscribers) / 0.51. Voice channel associated signaling traffic = 3.4 kbit/s x N (number of voice subscribers) / (1 - FP overhead) / (1 - ATM overhead) / (1 - AAL2 overhead) / (1 E1 overhead (UNI)) = 3.4 kbit/s x N (number of voice subscribers) / 0.53. Voice signaling part control frame traffic = 1.09 kbit/s N (number of voice subscribers) / (1 - FP overhead) / (1 - ATM overhead) / (1 - AAL2 overhead) / (1 E1 overhead (UNI)) = 1.09 kbit/s N (number of voice subscribers) / 0.69. Data traffic = data service traffic + data channel associated signaling traffic + Data signaling control frame traffic. Data service traffic = 64.4 kbit/s M (number of data subscribers) / (1 - FP overhead) / (1 - ATM overhead) / (1 - AAL2 overhead) / (1 - E1 overhead (UNI)) = 64.4 kbit/s M (number of data subscribers) / 0.75 Data channel associated signaling traffic = 3.4 kbit/s N (number of voice subscribers) / (1 - FP overhead) / (1 - ATM overhead) / (1 - AAL2 overhead) / (1 E1 overhead (UNI)) = 3.4 kbit/s N (number of voice subscribers) / 0.53 Data signaling control frame traffic = 1.09 kbit/s N (number of voice subscribers) / (1 - FP overhead) / (1 - ATM overhead) / (1 - AAL2 overhead) / (1 - E1 overhead (UNI)) = 1.09 kbit/s N (number of voice subscribers) / 0.69 Signaling part traffic = 0.32kbit/s N VAD Voice Activity Detection factor N=Number of voice subscribers + data subscribers
12-2
Taking UNI link as an example, the simplified model of service traffic is as follows: Service traffic = voice traffic VAD + data traffic + signaling part traffic = 31.9kbit/s N (number of voice subscribers) VAD + 93.9bit/s M (number of data subscribers) + 0.32 (M + N) In the model above:
z z z
VAD can be 0.5, N is 12.2kbit/s AMR voice, M is 64.4kbit/s data service.
In full configuration, BTS3802C supports 128 12.2kbit/s AMR voice subscribers. According to the formula above,
z
service traffic= 31.9kbit/s*128*0.51=2084.4kbit/s
If UNI links are to bear the service traffic, the number of UNI links needed is:
z
Number of UNI links =service traffic/2Mbit/s =1.042
To bear the service traffic plus the bandwidth consumed by IPoA, two UNI links must be equipped for a fully configured BTS3802C.
12.4 Planning Number of AAL2PATHs

One AAL2 PATH supports up to 248 micro channels. Each AMR voice occupies two micro channels. The full configuration of BTS3802C supports 128 AMR voice channels, and together with the common channels of the two cells, at least two AAL2 PATHs are needed. For non-full configuration, the number can be reduced proportionally. For the bandwidth of the AAL2PATH PVCs, the default value is advisable.
12.5 Calculating PVC Bandwidth Consumed by a CES Channel

The bandwidth of the PVC channel in the CES channel may be large. Without a reasonable planning, it is likely that the PVC bandwidth is larger than the UNI link bandwidth bearing this PVC, which will result in CES channel abnormal. The bandwidth in the upper level PVC allocated for CES link is as follows: PVC channel bandwidth = number of timeslots occupied*64kb/s*cell size (byte)/fill-in bytes In the formula above, cell size is 53 bytes for ATM cell. According to this formula, the bandwidth of a structured CES channel ranges from 0.07Mb/s to 25.44Mb/s. Its maximum value is much larger than the bandwidth of a UNI link (1.920Mb/s).
12-3
The following configurations are advisable to meet the CES channel bandwidth demand:
z
Allocate more transport bandwidth of the ATM Physical Layer Bearer to bear this PVC. For example, switch other PVCs on this UNI link to other UNI link. Increase the fill-in byte. The default value 47 is advisable. Note that larger fill-in degree means more transport delay, so the specific value of fill-in byte should depend on the requirement of delay. In addition, the fill-in byte should be larger than the number of timeslots available in the CES.
12-4
Appendix
Acronyms and Abbreviations
Appendix Acronyms and Abbreviations

A AAL AAL1 AAL2 AAL3 AAL5 ALCAP AMR ATM B BSC C CBR CCP CES CID F FACH FLASH FP FPGA I IP IPoA L Internet Protocol Internet Protocols over ATM Forward Access Channel FLASH memory Frame protocol Field Programmable Gate Array Constant Bit Rate Communication Control Port Circuit Emulation Service Channel Identifier Base Station Controller ATM Adaptation Layer ATM Adaptation Layer Type 1 ATM Adaptation Layer type 2 ATM Adaptation Layer type 3 ATM Adaptation Layer type 5 Access Link Control Application Protocol Adaptive MultiRate Asynchronous Transfer Mode
F-1
Appendix
LMT M MIT MML N NBAP NCP NASU NMBU NMCU NPSU NTRU NDRU NDRF NHPA NEPA NAPA NDUP O O&M P PDH PM PVC R RNC RT RX
Local Maintenance Terminal
Management Information Tree Man Machine Language
NodeB Application Part NodeB Control Port NodeB Access SDH Unit NodeB Maintenance and Baseband unit NodeB Maintenance and Control unit NodeB Power Supply Unit NodeB Transceiver Unit NodeB Digital and Radio Unit NodeB Duplexer and Rx Filter NodeB High Power Amplifier NodeB Enhanced Power Amplifier NodeB Advanced Power Amplifier NodeB Duplexer Unit
Operation Administration and Maintenance
Plesiochronous Digital Hierarchy Physical Medium sub-layer Permanent Virtual Channel
Radio link controller Real time Receiver
F-2
Appendix
S SAAL SAR SDH SDT SDU STM STM-1 T TC TRX TS TX U UDT UNI V VBR VBR-RT VC VCI VP VPI W WCDMA Wide(band) Code Division Multiple Access Variable Bit Rate Real Time Variable Bit Rate Virtual Channel Virtual Channel Identifier Virtual Path Virtual Path Identifier Unstructured Data Transfer User Network Interface Transmission Convergence Sub-layer Transceiver Time Slot Transmit Signaling ATM Adaptation Layer Segmentation And Reassembly Synchronous Digital Hierarchy Structured Data Transfer Service Data Unit Synchronous Transfer Mode Synchronous Transfer Mode 1
F-3
Index
Index
A
AAL2PATH adding, 6-12 modifying, 6-21 planning, 12-3 property, 10-12 adding AAL2PATH, 6-12 ALCAP, 6-10 CCP, 6-9 fractional ATM link, 6-5 IPoA, 7-2 NCP, 6-7 SDT CES channel, 6-16 transparent link, 6-15 treelink PVC, 6-19 UNI link, 6-2 ALCAP adding, 6-10 modifying, 6-20 property, 10-12 applying configuration data, 4-5 by downloading file, 4-5 by MML command, 4-7 architecture fractional ATM link, 10-9 Iub transport, 10-10 local cell, 9-1 maintenance channel, 11-1 SDT CES channel, 10-14 transport, 10-1 Treelink PVC, 10-16 ATM physical layer bearer bandwidth, 12-2 property, 10-8
B
bandwidth ATM physical layer bearer, 12-2
C
cabinet-level property, 1-3 calculating traffic, 12-2 capacity transport. see bandwidth CCP adding, 6-9 modifying, 6-21 property, 10-12 CES channel. see SDT CES channel property, 10-15 checking data consistency, 4-9 clock selecting source, 8-1 configuration data applying by downloading file, 4-5 applying by MML command, 4-7 configuration file, 2-2 creating using template, 4-2 creating without template, 4-3 saving as template, 4-4 configuration management system equipment panel, 1-4 interface, 1-1 MIT navigation tree, 1-2 starting, 4-1 configuring E1/T1 work mode, 6-1 engineering parameter, 8-11 external alarm port, 8-4
i-1
Operation Manual-Data Configuration BTS3802C WCDMA NodeB local cell, 5-1 module temperature threshold, 8-8 NDRU temperature threshold, 8-8 NMCU temperature threshold, 8-8 NodeB configuration type, 5-1 power amplifier temperature threshold, 8-8 power save mode, 8-6 creating configuration file using a template, 4-2 configuration file without template, 4-3 template, 4-4 architecture, 10-9 networking, 10-5 property, 10-8 fractional ATM networking protocol, 10-5
Index
G
guideline IPoA maintenance channel, 11-5 transport configuration, 10-19
D
data conflict, 2-3 data consistency check, 4-9 determining Iub transport layer property, 10-12 direct transport networking protocol, 10-3 dynamic command, 2-5
I
initial configuration NodeB, 3-1 NodeB (comprehensive), 3-1 NodeB (simplified), 3-5 IP address, 11-3 IP network IP address, 11-3 IP route, 11-4 planning, 11-2 IP route, 11-4 IPoA adding, 7-2 maintenance channel guideline, 11-5 modifying, 7-4 property, 10-12 Iub transport architecture, 10-10 determining property, 10-12 expanding capacity, 6-14 object property, 10-9 configuring, 6-1
E
E1/T1 work mode engineering parameter configuring, 8-11 equipment panel, 1-4 equivalent MML command, 2-4 operations with no equivalent MML commands, 2-4 expanding Iub transport capacity, 6-14 external alarm port configuring, 8-4
K
key properties of template, 2-3
F
far end maintenance channel. see IPoA maintenance channel file data and running data checking consistency, 4-9 fractional ATM link adding, 6-5
L
local cell architecture, 9-1 configuring, 5-1 local cell logical property modifying, 5-3
i-2
Operation Manual-Data Configuration BTS3802C WCDMA NodeB property, 9-3 local cell property, 9-1 local cell logical property, 9-3 NodeB configuration type, 9-2 local maintenance channel modifying, 7-1 NodeB configuration type configuring, 5-1 property, 9-2 NodeB initial configuration, 3-1 comprehensive, 3-1 simplified, 3-5 NodeB-level property, 1-3
Index
M
maintenance channel architecture, 11-1 MIT navigation tree, 1-2 MML command equivalent MML command, 2-4 modifying AAL2PATH, 6-21 ALCAP, 6-20 CCP, 6-21 IPoA, 7-4 local cell logical property, 5-3 local maintenance channel, 7-1 NASU O&M mode, 7-7 NCP, 6-20 NDRU property, 5-6 NodeB configuration type, 5-1 SNTP, 7-5
O
operations with no equivalent MML commands, 2-4
P
peers of transport protocol, 10-7 planning AAL2PATH, 12-3 IP network, 11-2 SDT CES channel, 12-3 transport bandwidth, 12-1 VPI, 10-17 power amplifier modifying temperature threshold, 8-8 power save mode configuring, 8-6 property AAL2PATH, 10-12 ALCAP, 10-12 ATM physical layer bearer, 10-8 CCP, 10-12 CES channel, 10-15 fractional ATM link, 10-8 IPoA, 10-12 Iub transport object, 10-9 local cell, 9-1 local cell logical property, 9-3 NCP, 10-12 NodeB configuration type, 9-2 SDT CES channel, 10-14 transparent link, 10-13 transport, 10-1 Treelink PVC, 10-17 UNI link, 10-8 property in configuration file
N
NASU O&M mode modifying, 7-7 NCP adding, 6-7 modifying, 6-20 property, 10-12 NDRU modifying property, 5-6 modifying temperature threshold, 8-8 near end maintenance channel. see local maintenance channel network IP, 11-2 NMCU modifying temperature threshold, 8-8
i-3
Operation Manual-Data Configuration BTS3802C WCDMA NodeB equivalent MML command, 2-4 adding, 6-15 networking, 10-4 property, 10-13 protocol, 10-4 transport architecture, 10-1 bandwidth, 12-1 capacity. see bandwidth configuration guideline, 10-19 networking, 10-2 planning bandwidth, 12-1 port, 10-1 protocol architecture, 10-2 protocol peers, 10-7 transport networking selection, 10-6 transport property, 10-1 treelink PVC adding, 6-19 networking, 10-4 protocol, 10-4 Treelink PVC architecture, 10-16 property, 10-17
Index
R
running data checking consistency, 4-9
S
SDT CES channel adding, 6-16 architecture, 10-14 networking, 10-5 networking protocol, 10-5 planning, 12-3 property, 10-14 selecting clock source, 8-1 SNTP modifying, 7-5 starting configuration management system, 4-1 static command, 2-5
T
temperature threshold configuring, 8-8 template, 2-2 creating, 4-4 key property, 2-3 name, 2-2 to create a configuration file, 4-2 usage, 2-2 tools for NodeB data configuration, 2-1 traffic calculating, 12-2 transparent link
U
UNI link adding, 6-2 property, 10-8
V
VPI planning, 10-17
i.
i-4

BTS3802C Operation Manual-Data Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BTS3802C Operation Manual-Data Configuration

Uploaded by

Copyright:

Available Formats

Chapter 1 Introduction to Configuration Management System .................. 1.1 Overview ................................................................................................ 1.2 Configuration Management System Interface ........................................

BTS3802C WCDMA NodeB Operation Manual-Data Configuration V100R003

BTS3802C WCDMA NodeB Operation Manual

Huawei Technologies Co., Ltd.

Copyright 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

, HUAWEI, C&C08, EAST8000, HONET,

, ViewPoint, INtess, ETS, DMC,

Updates Made between Versions 1.30 and 1.31

About This Manual

Part 4: Abbreviation and Acronym

App. Acronyms and Abbreviations

WCDMA BTS3802C operator

II. GUI conventions

III. Mouse operation

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 1 Introduction to Configuration Management System

Chapter 1 Introduction to Configuration Management System

1.2 Configuration Management System Interface

Figure 1-1 Configuration Management System interface

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 1 Introduction to Configuration Management System

1.3 MIT Navigation Tree

These object trees also have sub-trees.

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 1 Introduction to Configuration Management System

1.4 NodeB-Level Properties and Cabinet-Level Properties

Figure 1-3 NodeB level properties

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 1 Introduction to Configuration Management System

1.5 Equipment Panel

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 2 Overview of NodeB Data Configuration

Chapter 2 Overview of NodeB Data Configuration

2.2 Tools for NodeB Data Configuration

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 2 Overview of NodeB Data Configuration

2.3 Template and Configuration File

Download to the NodeB Equivalent MML command

2.3.2 Usage of Template and Configuration File

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 2 Overview of NodeB Data Configuration

2.4 Data Conflict

2.5 Key Properties of Template

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 2 Overview of NodeB Data Configuration

2.6 Configuration File Editing vs. Equivalent MML Command

2.6.2 Operations with No Equivalent MML Commands

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 2 Overview of NodeB Data Configuration

Delete IPoA Device in the [BTS3802C/Transmission Object Tree/IPoA device Set]

Results of performing operations having no equivalent MML command are as follows:

2.6.3 Dynamic Commands and Static Commands

Operation Manual-Data Configuration BTS3802C WCDMA NodeB

Chapter 2 Overview of NodeB Data Configuration

The NodeB static commands include the following commands:

The module static command includes the following command:

SET NDRUWM (setting NDRU work mode)