bts3802c operation manual-data configuration.pdf

8/14/2019 BTS3802C Operation Manual-Data Configuration.pdf

http://slidepdf.com/reader/full/bts3802c-operation-manual-data-configurationpdf 1/136

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........................................................................................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.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 andRunning Data 4-9...............................................................................................

4.6.1 Overview 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.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.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.3 Procedure 6-1......................................................................................

6.2 Adding a UNI Link 6-2..................................................................................

6.2.1 Overview 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.3 Procedure 6-5......................................................................................

6.4 Adding an NCP Port 6-7...............................................................................

6.4.1 Overview 6-7........................................................................................


6.4.3 Procedure 6-8......................................................................................

6.5 Adding a CCP Port 6-9.................................................................................

6.5.1 Overview 6-9........................................................................................


6.5.3 Procedure 6-9......................................................................................

6.6 Adding an ALCAP Node 6-10.........................................................................

6.6.1 Overview 6-10........................................................................................


6.6.3 Procedure 6-11......................................................................................

6.7 Adding an AAL2 PATH 6-12...........................................................................

6.7.1 Overview 6-12........................................................................................


6.7.3 Procedure 6-12......................................................................................

6.8 Expanding Iub Transport Capacity 6-14.........................................................

6.8.1 Overview 6-14........................................................................................


6.8.3 Procedure 6-14......................................................................................

6.9 Adding a Transparent Link 6-15.....................................................................6.9.1 Overview 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.3 Procedure 6-19....................................................................................

6.12 Modifying NCP or ALCAP 6-20....................................................................

6.12.1 Overview 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.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........................................................................................

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.3 Procedure 7-2......................................................................................

7.3 Modifying IPoA Maintenance Channel 7-4...................................................

7.3.1 Overview 7-4........................................................................................


7.3.3 Procedure 7-4......................................................................................

7.4 Modifying SNTP Properties 7-5....................................................................

7.4.1 Overview 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.3 Procedure 8-1......................................................................................

8.2 Configuring External Alarm Ports 8-4...........................................................

8.2.1 Overview 8-4........................................................................................


8.2.3 Procedure 8-4......................................................................................

8.3 Configuring Power Supply Mode 8-6............................................................

8.3.1 Overview 8-6........................................................................................


8.3.3 Procedure 8-6......................................................................................

8.4 Configuring Module Temperature Thresholds 8-8........................................

8.4.1 Overview 8-8........................................................................................


8.4.3 Procedure 8-9......................................................................................

8.5 Modifying Engineering Parameters 8-11........................................................



8.5.1 Overview 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......................................................................

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



HUAWEI

BTS3802C WCDMA NodeB

Operation Manual-Data Configuration

V100R003



BTS3802C WCDMA NodeB

Operation Manual

Volume Data Configuration

Manual Version T2-031644-20040930-C-1.31

Product Version V100R003

BOM 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: [email protected]



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 Notes

T2-031644-20040225-C-1.30 Initial field trial release

T2-031644-20040930-C-1.31 Secondary field trial release

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

Intended Audience

The manual is intended for the following readers:

WCDMA BTS3802C operator

Part Description Chapter

Part 1: Interface

Introduce the interfaces of theconfiguration managementsystem.

Chap 1 Introduction to ConfigurationManagement System

Chap 2 Overview of NodeB Data Configuration

Chap 3 NodeB Initial Configuration Processes

Chap 4 Common Procedures-Configuration Fileand Applying Data

Chap 5 Local Cell Configuration Procedures

Chap 6 Transport Configuration Procedures

Chap 7 Maintenance Channel ConfigurationProcedures

Part 2: Processesand

Procedures

Provide operation processes andprocedures for NodeB dataconfiguration.

By following a process orprocedure, you can accomplish aNodeB configuration task.

Chap 8 Supplementary Configuration Procedure

Chap 9 Local Cell Properties

Chap 10 Transport Properties

Chap 11 Maintenance Channel Properties

Part 3: Properties

Describe the properties for NodeBdata configuration.

From this part, you know what theproperties mean and how todetermine the property values. Chap 12 Transport Bandwidth Planning

Part 4: Abbreviationand Acronym

Describe the full names of theabbreviation and acronyms usedin this document

App. Acronyms and Abbreviations



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 Description

Arial Normal paragraphs are in Arial.

Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.

Boldface Headings are in Boldface.

Courier New 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 squarebrackets. 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 Description

Click Press the left button or right button quickly (left button by default).

Double Click Press the left button twice continuously and quickly.

Drag 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 ConfigurationBTS3802C WCDMA NodeB Table of Contents

i

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




ii

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




iii


6.5 Adding a CCP Port ............................................................................................................ 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




iv

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




v

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




vi

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



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB

Chapter 1Introduction to Configuration Management System

1-1

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:

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 (2) Tool bar(3) MIT (Management Information Tree) navigation tree (4) MIT navigation node(5) Equipment panel (6) Result output window

Figure 1-1 Configuration Management System interface





1-2

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 ATM Adaptation Layer type 2 ALCAP Access Link Control Application Protocol ATM Asynchronous Transfer ModeCCP Communication Control PortCES Circuit Emulation ServiceIPoA Internet Protocol over ATMNCP NodeB Control PortNMCU NodeB Maintenance and Control unit

NDRU NodeB Digital and Transceiver UnitPVC Permanent Virtual ChannelUNI 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:

[Physical Object Tree]

[Transmission Object Tree]

[Local Cell Object Tree]

These object trees also have sub-trees.





1-3

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:

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 correspondingmodule 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-4

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:

Add a module,

Delete a module,

View the properties of a module,

Modify the properties of a module.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 2 Overview of NodeB Data Configuration

2-1

Chapter 2 Overview of NodeB Data Configuration

2.1 Overview

This section provides information on the following aspects:

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:

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

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:

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 .mdb .xml

Checkbeforesaving

If a configuration file is to be saved asan .mdb file, the configuration managementsystem does not check the file before saving

it.

When a configuration file is to be saved as an .xml file, theconfiguration management system checks the dataconsistency. If there are any invalid or inconsistent

properties found, the configuration management systemprompts you to modify them. The saving succeeds onlywhen there are no problems.

Downloadto theNodeB

An .mdb file cannot be loaded to a NodeB.

To load an .mdb f ile to a NodeB, save themdb file as an .xml file beforehand.

An .xml file can be loaded to a NodeB.

EquivalentMMLcommand

After an .mdb file is opened, theconfiguration management system does notrecord the edit operations with theequivalent MML commands.

After an .xml file is opened, the configuration managementsystem records the edit operations with equivalent MMLcommands.

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

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 afew 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:

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 thisway, you can configure the RF channels without detailed knowledge of NodeB RF

channels.

Except the key properties, other properties can be modified individually.




2-4

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:

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:

"E1/T1 Work Mode" in [BTS3802C] properties

Some property modifications, for example NCP, CCP property modification

operations




2-5

“Delete IPoA Device” in the [BTS3802C/Transmission Object Tree/IPoA device

Set]

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

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 . After viewing the commands, click to restore the

operation.

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 Executing result To obtain the effect of downloadingconfiguration file and resetting NodeB

Dynamiccommands

Executing dynamic commandsmodifies both the properties of theconfiguration file in the NodeB and therunning parameters.

Execute dynamic equivalent MMLcommands

Staticcommands

Executing static commands onlymodifies the properties of theconfiguration file in the NodeB. Therunning parameters do not change yet

Execute static commands and then resetthe NodeB for NodeB static commands orreset the module for module staticcommands

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

The NodeB static commands include the following commands:

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:

SET NDRUWM (setting NDRU work mode)



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 3 NodeB Initial Configuration Process

3-1

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:

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.

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

RNCNew NodeB NodeB

Upper level NodeBLocal NodeB

RNCNodeB NodeBNew NodeB

RNCNew NodeB

Local NodeB

Step 1

Initial configuration process

Step 2


Step 3


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

Table 3-1 NodeB configuration stage and stage target

Stage Stage target Procedures Location

RNC procedure

2G BTS/BSC procedure if 2G BTSprovides fractional E1/T1 timeslots forthe NodeB.

Not

providedin thismanual

Upper Level

NodeConfiguration

For simple networking, complete RNC

configuration.

For sharing 2G transport, completer RNCand upper level 2G BTS/BSCconfiguration.

For NodeB tree networking, completeRNC and upper level NodeB configuration.

Upper Level NodeB procedures: Addtreelink PVC

Chapter 6

Select NodeB configuration typeLocal cellconfiguration

Modify Local cell logical properties

Chapter 5

Configure E1/T1 as E1 or T1

Add UNI link or Add Fractional ATM link

Add/modify NCP

Add/modify CCP

Add/modify ALCAP

Iub Transport

configuration

Add/modify AAL2PATH

Chapter 6

Modify Local maintenance channel

Modify IPoA maintenance channel

Modify NASU O&M mode

EssentialConfiguration

Upon the completion ofessential configuration,NodeB is able to providenormal services.

Maintenancechannelconfiguration

Modify SNTP

Chapter 7

Select Clock source

Configure External Alarm collection

Configure Power Supply mode

Configure module temperature threshold

SupplementaryConfiguration

To ensure the persistence and stability ofNodeB

Supplementary configuration can be doneat a convenient time before or after NodeBis able to provide normal services.

Configure Engineering parameter

Chapter 8

Add transparent linkTransport

Configurationfor 2G BTS orother device

To provide transport channels for lower

level equipments, such as 2G BTS andmonitoring equipment. Add CES channel

Chapter 6

Apply data To apply configuration data Apply data Chapter 4




3-5

Notes:

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:

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:

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 templatefor all the other properties including:

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

Note:

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

Step Procedure Properties Note Location

2 procedure B2 set Local cell ID Set the local cell IDs of all the Cells

3 Procedure B3 Configure E1/T1 as E1 or T1 - - -

4 procedure B8 set ATM address - - -

5 procedure B12 set IPoA local IP address,IPoA peer IP address

- - -

Chapter 6

6 procedure B13 set SNTP IP address - - - Chapter 8

7 procedure B14 Apply the properties Install the board, jumper, transport line,and signal line according to theconfiguration file

Chapter 4




Chapter 4Common Procedures-Configuration File and Applying Data

4-1

Chapter 4 Common Procedures-Configuration File

and Applying Data

4.1 Starting Configuration Management System

4.1.1 Overview

Target To start the configuration management system for configuration file creating or

editing

NodeB initial configurationApplicationoccasion

In-service property modification during network optimization

Prerequisite After the installation of NodeB Local Maintenance Terminal (LMT), the item[Start/Programs/Huawei Local Maintenance Terminal/NodeB V100R003 /NodeBOperation & 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:

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

3) Select the corresponding version in the [Select Version] dialog box to start the

corresponding LMT.

4) Select [Service/Configuration Management System] on the LMT main menu, and

then select the corresponding version in the pop-up [Select Version] dialog box tostart the configuration management system.

4.2 Creating a Configuration File Using a Template

4.2.1 Overview

Target To create a configuration file using a template



Prerequisite There is a suitable template.

4.2.2 Points for Attention

General After selecting a template, do not modify key parameters of the configurationfile.

Verification

command

None

4.2.3 Procedure

Follow the procedure below to create a configuration file using a template:

1) Start configuration management system. Refer to section 4.1 .

2) Select [File/New By Template] on the main menu to display the dialog box [Open

Template File], as shown in Figure 4-1.





4-3

Figure 4-1 Opening a template

3) Select the template matching the target NodeB configuration type in the [Open

Template File] dialog box, and then click <Open>.

4) Modify the property settings.

5) 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 To create a configuration file for advanced and special NodeB configurationtype

Applicationoccasion

No suitable template is available

Prerequisite Be familiar with the NodeB configuration principles. Refer to Appendix A for

NodeB configuration principles


General If there is a template suitable, it is recommended to create a configuration fileusing a template.

Verificationcommand

None





4-4

4.3.3 Procedure

Follow the procedure below to create a configuration file without template:

1) Start configuration management system. Refer to section 4.1 .2) Select [File/New]. The configuration management system displays the dialog box

[Add NodeB].

3) In the [Add NodeB] dialog box, set the NodeB-level properties, and then click

<OK>. The [Add NMCU Module] dialog box is displayed.

4) In the [Add NMCU Module] dialog box, set the module-level properties, and then

click <OK>.

5) Modify the configuration data.

6) 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 To create a template for the consistency and standardization of multiple NodeBdata configurations

Application

occasion

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 createother 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) Select [File/Save as Template] after editing a configuration file.

2) 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-5

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).

Configuration file

parameters

Running parameters

BTS3802C

Dow nload configuration

file into the NodeBExecute equivalent MML command

Restart NodeBReset NodeB to take static commands

into effect

Dynamic commands take effect

immediately after they are executed.

Configuration file MML command batch file

Export equivalent MML commandSave configuration file

Configuration management system

LMT computer

new properties

LMT computer

Figure 4-2 Applying configuration data

4.5.2 Applying Data by Downloading Configuration File

I. Overview

Target 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

Applicationoccasion

Large quantities of data are modified

Prerequisite None





4-6

II. Points for attention

General Resetting NodeB interrupts the service of the NodeB.

Verificationcommand

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) Rename the configuration file as "NodeBCfg.xml".

3) 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) Download the configuration file on O&M system through MML command DLD

CFGFILE.

5) 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-7

4.5.3 Applying Data by Executing Equivalent MML Command

I. Overview

Target To apply the data while avoiding configuration file download and NodeB reset

Applicationoccasion

The NodeB configuration type has not been changed.

Prerequisite All the property-modifying operations in configuration management system haveequivalent MML commands.

II. Points for Attention

When a board is added through an equivalent MML command, it will be restartedautomatically, and the restarting process will last for up to three minutes. Commands ofmodifying properties of the board can be executed only after the board restartssuccessfully. If a batch file contains MML commands of adding a board and modifyingthe properties of the board immediately after, split the batch file into two files.

General

Executing MML commands modifies not only the running parameters but also theproperties in the NodeB configuration file. Therefore, it is necessary to back up theconfiguration file.

Verificationcommand

None

III. Procedure

Follow the procedure below to applying data by executing equivalent MML commands:

1) Modify the properties in configuration management system.

2) 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-8

Figure 4-3 Browsing Equivalent MML command

3) 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) Execute the equivalent MML commands on O&M system.

5) 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-9

4.6 Checking Consistency between Configuration File Dataand Running Data

4.6.1 Overview

Target To make sure the configuration modification has taken effect.

Applicationoccasion

The following situations will cause inconsistency between configuration file datastored in NodeB and NodeB running Data:

-The configuration file has been downloaded, but the NodeB has not been restartedyet.

-The static configuration command has been executed, but the NodeB has not beenrestarted yet.

Prerequisite None


General Resetting NodeB interrupts the service of the NodeB.

Verificationcommand

None

4.6.3 Procedure

Follow the procedure below to check consistency between configuration file data and

running data:

1) Carry out MML command CHK DATA on O&M system.

2) If there is inconsistency between configuration file data stored in NodeB and

NodeB running data, reset the NodeB through the MML command RST SYS.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 5 Local Cell Configuration Procedures

5-1

Chapter 5 Local Cell Configuration Procedures

5.1 Selecting/Modifying NodeB Configuration Type

5.1.1 Overview

Target To create a new configuration file for a new NodeB configuration type by selecting atemplate

NodeB initial configuration

In-service property modification involves NodeB configuration type properties

Application

occasion

Configuration tasks, such as adding/deleting cell, adding/deleting sector, andadding/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:

Sector*Frequency

Receive diversity mode

Transmit diversity mode

NDRU connect mode

NDRU work mode




5-2


After configuring the NodeB configuration type with a template, do not modifyNodeB configuration type properties. To modify the NodeB configuration type

properties, select another template to create a new configuration file.

General

Make the same modifications to RNC.

For initialconfiguratio

n

Figure 3-2 illustrates the location of this procedure in the NodeB initialconfiguration process.

Modifying a NodeB configuration type entails downloading configuration fileand resetting NodeB, and thus interrupts services of the NodeB.

Forin-serviceproperty

modification To add or remove a cell or sector, select another template. Avoid using thefollowing 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 RFmodules, still exist. This operation may result in inconsistency betweenconfiguration data.

Verificationcommand

None

5.1.3 Procedure

Follow the procedure below to select/modify NodeB configuration type:


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) Select [File/New By Template] in configuration management system.

4) 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-3

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) Click main menu [File/Save] in the configuration management system to save theconfiguration file.

9) 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 To modify Local cell ID, cell radius, and cell inner handover radius



Prerequisite None


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 thecell belongs. Be sure to select the right cell.

General

Make the corresponding modifications to RNC

For initialconfiguration


Forin-serviceproperty

modification

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 cellhas restored its service.

Verificationcommand

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:





5-4

2) Click main menu [File/Open] in the configuration management system to open the

configuration file to be edited.

3) 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) Click main menu [File/Save] in the configuration management system to save the

configuration file.






5-5

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) Start configuration management system. Refer to section 4.1 .

2) Upload the data configuration file through the MML command ULD CFGFILE on

O&M system.



4) If the properties to be modified include Local cell ID (Cell No.), go to step 6).

Otherwise, go to step 5).

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) Right-click [BTS3802C/ No. n local Cell] in the MIT navigation tree, and then select

[Delete Local Cell] in the shortcut menu.

7) 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.


configuration file.

9) To apply the data now, refer to section “4.5.3 Applying Data by Executing

Equivalent MML Command”. Otherwise, this procedure ends.




5-6

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 To modify NDRU work mode and connect mode

Applicationoccasion

In-service property modification, NodeB configuration type is to be changedaccording to network optimization.

Prerequisite None


General Select another template to modify these NDRU properties.

Do not modify these properties in this way: Right-click NDRU in the equipmentpanel or MIT navigation tree, and then select [Modify NDRU Board] to modifythe NDRU properties.

For in-serviceproperty

modification

Modifying a NodeB configuration type entails downloading configuration fileand resetting NodeB, and thus interrupts services of the NodeB.

Verificationcommand

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 .



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 6 Transport Configuration Procedures

6-1

Chapter 6 Transport Configuration Procedures

6.1 Configuring E1/T1 as E1 or T1

6.1.1 Overview

Target To configure E1/T1 work mode as E1 or T1

Applicationoccasion


Prerequisite The E1/T1 work mode must be consistent with the settings of the NMCU DIPswitches.


General Perform the operation on the peer node (upper level NodeB, lower level NodeBor RNC) also.

NMBU E1 ports 2 and 3, which connect with the NASU E1 Port, cannot be

configured as T1 port.


The E1/T1 work mode is a NodeB-level property and has effect on the entireNodeB.

For initial

configuration

The transport bandwidth, frame structure, and line code of E1 and T1 aredifferent. The transport bandwidth, frame structure, and line code are changedalong with the E1/T1 work mode.

Verificationcommand

DSP E1T1WORKMODE

6.1.3 Procedure

Follow the procedure below to configure E1/T1 work mode as E1 mode or T1 mode :





3) Click main menu [File/Open] to open the configuration file to be edited.




6-2

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.




6.2 Adding a UNI Link

6.2.1 Overview

Target To add a UNI link



Prerequisite The E1/T1 line is ready.


General Perform the operation on the peer node (upper level NodeB, lower level NodeB

or RNC) also.




modification

After a UNI is added, allocate PVCs, such as NCP, CCP, AAL2PATH, ALCAP,IPoA, Treelink PVC, and CES on the UNI link.

Verificationcommand

LST UNILNK, DSP UNILNK

6.2.3 Procedure

Follow the procedure below to add a UNI link:






4) Set NMBU E1/T1 Port Properties




6-3

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:

“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-4

Figure 6-2 UNI properties

Note:

"UNI Link No." defines the E1/T1 port of the link.


configuration file.



Note:







6-5

6.3 Adding a Fractional ATM Link

6.3.1 Overview

Target To add a Fractional ATM link



Prerequisite The E1/T1 line is ready.


General Perform the operation on the peer node (upper level NodeB, lower level NodeBor RNC) also.




modification

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.

Verificationcommand

LST FRAATM, DSP FRAATM

6.3.3 Procedure

Follow the procedure below to add a Fractional ATM link:






4) Set NMBU E1/T1 Port Properties


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

Figure 6-3 NMBU E1/T1 properties

Note:

In the tab of the E1/T1 ports, set [Clock Work Mode] to:

“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>.


configuration file.






6-7

Figure 6-4 Fractional ATM properties

Note:




6.4 Adding an NCP Port

6.4.1 Overview

Target To add an NCP port

Applicationoccasion


Prerequisite The ATM physical layer bearer (UNI link, or fractional ATM link) is ready




6-8


Only one NCP can be added for a NodeB.

Perform the operation on the RNC also.



Verificationcommand

LST CP, DSP CP

6.4.3 Procedure

Follow the procedure below to add an NCP port:



3) 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.

4) Modify NCP properties in the dialog box, and then click <OK>.

Figure 6-5 NCP properties


configuration file.




6-9



Note:


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 To add a CCP port



Prerequisite The ATM physical layer bearer (UNI link, or fractional ATM link) is ready


A NodeB must have at least one CCP port and can have more.General





modification

On all of the upper-level NodeBs, add Treelink PVCs for the CCP PVC of the localNodeB when this local NodeB is cascaded under other NodeBs.

Verificationcommand

LST CP, DSP CP

6.5.3 Procedure

Follow the procedure below to add a CCP port:





6-10




3) Click main menu [File/Open] to open the configuration file to be edited.4) Right-click [Transmission Object Tree/CCP Set] on the MIT navigation tree, and

then select [Add CCP] to display the [Add CCP] dialog box.

5) Modify the CCP properties and then click <OK>.


configuration file.



Note:




6.6 Adding an ALCAP Node

6.6.1 Overview

Target To add an ALCAP node

Applicationoccasion


Prerequisite The ATM physical layer bearer (UNI link, IMA group, STM-1 link, or fractional ATMlink) is ready


A NodeB has only one ALCAP node.




Verificationcommand

LST AAL2NODE, DSP AAL2NODE




6-11

6.6.3 Procedure

Follow the procedure below to add an ALCAP node:

1) Start configuration management system. Refer to section 4.1 .2) Click main menu [File/Open] to open the configuration file to be edited.

3) 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) Modify the ALCAP properties and then click <OK>.


configuration file.



Note:







6-12

6.7 Adding an AAL2 PATH

6.7.1 Overview

Target To add an AAL2PATH under an ALCAP node



The ATM physical layer bearer (UNI link or fractional ATM link) is readyPrerequisite

The ALCAP exists


A NodeB must have at least one AAL2PATH and can have more.General




Before adding an AAL2PATH, add/expand the ATM physical layer bearer (add UNIlink or Fractional ATM link) on the Iub interface to bear the AAL2PATH.


modification

On all of the upper-level NodeBs, add Treelink PVCs for the AAL2PATH PVC of thelocal NodeB when this local NodeB is cascaded under other NodeBs.

Verificationcommand

LST AAL2PATH, DSP AAL2PATH

6.7.3 Procedure

Follow the procedure below to add an AAL2 PATH:






4) 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.

5) Modify the AAL2 PATH properties in the dialog box, and then click <OK>.




6-13

Figure 6-7 Adding an AAL2PATH

For details of the properties, click <Help> on the dialog box.




Note:







6-14

6.8 Expanding Iub Transport Capacity

6.8.1 Overview

Target To expand Iub transport capacity

Applicationoccasion


Prerequisite 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.


The operation adds new ATM physical layer bearers, or increases the bandwidth ofan ATM physical layer bearer. If there are multiple ATM physical layer bearers, itmay 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.


modification

Before expanding operation, perform the "Upper level node configuration" shownin Figure 3-2.

Verificationcommand

None

6.8.3 Procedure

Follow the procedure below to expand Iub transport capacity:

1) 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".

2) Add AAL2 PATH

Add AAL2PATH under ALCAP node. See 6.7 "Adding an AAL2 PATH".




6-15

6.9 Adding a Transparent Link

6.9.1 Overview

Target Add a Transparent Link



NASU exists.Prerequisite

E1/T1 0, which corresponds to NASU E1 port 3, or E1/T1 1, which corresponds toNASU E1 port 4 is available for connecting to the lower level equipment.





modification

None

Verificationcommand

LST TRPLNK, DSP TRPLNK

6.9.3 Procedure

Follow the procedure below to add a transparent link:






4) 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>.


configuration file.






6-16

Note:




6.10 Adding an SDT CES Channel

6.10.1 Overview

Target To add an SDT CES channel



Prerequisite The NMCU E1/T1 port 0 or 1 connects to the lower level equipment


For initial

configuration

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 bandwidthcarefully. Refer to section 14.6.5.


modificationOn all of the upper-level NodeBs, add Treelink PVCs for the CES PVC of thelocal NodeB when this local NodeB is cascaded under other NodeBs.

Verificationcommand

LST UDTCES, LST SDTCES

6.10.3 Procedure

Follow the procedure below to add an SDT CES channel:






4) Set properties of NMCU E1/T1 ports connected with lower level node (2G BTS or

monitoring device)




6-17

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

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.


configuration file.



Note:







6-19

6.11 Adding a Treelink PVC

6.11.1 Overview

Target To add a treelink PVC for lower level NodeB



Prerequisite None




On all of the upper-level NodeBs, add Treelink PVCs for the PVCs of the localNodeB when this local NodeB is cascaded under other NodeBs.


modificationTreelink PVCs added must provide ATM switch route for all the PVCs of the localNodeB. PVCs of the local NodeB include the NCP, CCPs, ALCAP, AAL2PATHs,CES, and IPoA device.

Verificationcommand

LST TREELNKPVC

6.11.3 Procedure

Follow the procedure below to add a Treelink PVC:





3) Click main menu [File/Open] in configuration management system to open the


4) 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-20

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




Note:




6.12 Modifying NCP or ALCAP

6.12.1 Overview

Target To modify properties of NCP or ALCAP

Applicationoccasion


Prerequisite The NCP or ALCAP exists


A NodeB has only one NCP and one ALCAP.

Modifying NCP or ALCAP properties interrupts the services of the entire NodeB.


modification

Make the corresponding modifications to RNC.

Verificationcommand

LST CP

DSP CP

LST AAL2NODE

DSPAAL2NODE




6-21

6.12.3 Procedure

Follow the procedure below to modify NCP or ALCAP:

1) Start configuration management system. Refer to section 4.1 .2) Upload the data configuration file through the MML command ULD CFGFILE on

O&M system.



4) 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>.


configuration file.



6.13 Modifying a CCP or AAL2PATH

6.13.1 Overview

Target To modify properties of CCP or AAL2PATH

Applicationoccasion


Prerequisite The CCP or AAL2PATH exists


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.


modification Make the same modifications to RNC.

Verificationcommand

LST CP, DSP CP

LST AAL2 PATH, DSP AAL2 PATH

6.13.3 Procedure

Follow the procedure below to modify a CCP or AAL2PATH:





6-22


O&M system.


configuration file to be edited.4) 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.


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:

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.


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.


configuration file.






6-23

Note:







Chapter 7Maintenance Channel Configuration Procedures

7-1

Chapter 7 Maintenance Channel Configuration

Procedures

7.1 Modifying Local Maintenance Channel

7.1.1 Overview

Target To modify the NMBU Ethernet port IP address, which is referred as local IP

address


In-service property modification

Prerequisite For a new NodeB, the NMBU has its initial IP address. You need to obtain this IPaddress to log into the NodeB.



General

After modifying NMBU Ethernet IP, relog into the NodeB with the new IPaddress in case of local maintenance.

Verification command LST IP

7.1.3 Procedure

Follow the procedure below to modify the local maintenance channel:







4) 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-2

5) Modify the local IP address and its subnet mask in this dialog box and then click

<OK>.


configuration file.7) To apply the data now, refer to section “4.5.3 Applying Data by Executing


Note:




7.2 Adding IPoA Maintenance Channel

7.2.1 Overview

Target Add an IPoA device

Application occasion NodeB initial configuration

Prerequisite The NodeB has no IPoA device.


Only one IPoA can be added for a NodeB.For initial configuration


Verification command LST IPOA

7.2.3 Procedure

Follow the procedure below to add an IPoA maintenance channel:








7-3

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:

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.


configuration file.

7) To apply the data now, refer to section 4.5.3 "Applying Data by Executing






7-4

7.3 Modifying IPoA Maintenance Channel

7.3.1 Overview

Target To modify the properties of IPoA device, such as IP address andbandwidth of the IPoA

NodeB initial configurationApplication occasion


Prerequisite The IPoA device exists.


Modify the corresponding properties on RNC.

When the IPoA local IP is modified, the far end LMT needs to log intothe NodeB again using the new IPoA local IP.

For in-service propertymodification

IPoA is borne on ATM physical layer bearer. To increase the IPoA cellrate, expand the bandwidth of the existing ATM physical layer bearerfirst.

Verfication command LST IPOA

7.3.3 Procedure

Follow the procedure below to modify the IPoA maintenance channel:



O&M system.


configuration file to be edited.4) Right-click the corresponding node in the configuration navigation tree, and then

select <Modify IPoA> in the shortcut menu.

5) Modify the IPoA properties and then click <OK>.


configuration file.







7-5

Note:




7.4 Modifying SNTP Properties

7.4.1 Overview

Target To modify the properties of SNTP



Prerequisite 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 None

Verfication

command

LST SNTPCLTPARA

7.4.3 Procedure

Follow the procedure below to modify SNTP properties:


2) 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-6



4) 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) 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.


configuration file.







7-7

Note:




7.5 Modifying NASU O&M Mode mode

7.5.1 Overview

Target To configure the NASU O&M mode as local mode or remote mode



NMCU has built-in NASU.Prerequisite

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 NASUoperation and maintenance.

Verficationcommand

LST DIALBACK

7.5.3 Procedure

Follow the procedure below to modify the NASU O&M mode:1) Start configuration management system. Refer to section 4.1 .






4) 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-8

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) 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-9

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.


configuration file.



Note:

When the configuration file is closed in the configuration management system, the equivalent MMLcommands recorded are cleared. In that case, the only way to apply the properties modified is to download




Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 8 Supplementary Configuration Procedures

8-1

Chapter 8 Supplementary Configuration

Procedures

8.1 Selecting Clock Source

8.1.1 Overview

Target To select GPS clock or Iub clock as the clock source



Prerequisite Before selecting "GPS Clock", install GPS clock equipment.


General None

Verification command DSP IUBCLK

8.1.3 Procedure

Follow the procedure below to select the clock source:







4) 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-2

Figure 8-1 Selecting a synchronization clock source

5) If GPS clock source is selected, go to step 8). If Iub clock source is selected, go to

next step.

6) Select E1/T1 Port as Iub Clock Source


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

Figure 8-2 Selecting NMCU Iub clock source


configuration file.



Note:







8-4

8.2 Configuring External Alarm Ports

8.2.1 Overview

Target To enable external alarm ports


NodeB in-service property modification

Prerequisite None


General The cable connections of the external alarm ports and external devices must beconsistent with the data configuration.

Verficationcommand

LST INFALMTYPE

8.2.3 Procedure

Follow the procedure below to configure external alarm ports:







4) 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) 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-5

Figure 8-3 Alarm collection type definition


configuration file.



Note:







8-6

8.3 Configuring Power Supply Mode

8.3.1 Overview

Target To configure power supply mode



Prerequisite External Alarm interface 1 must be defined to collect Mains Failure alarms, andExternal 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.

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 None

Verificationcommand

LST PWSAVE

8.3.3 Procedure

Follow the procedure below to set the power supply mode:










8-8

Note:



the configuration file. To save the MML commands, refer to 4.5.3 .

8.4 Configuring Module Temperature Thresholds

8.4.1 Overview

Target To configure NodeB module temperature threshold



Prerequisite 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.

T1 T2 T3T1: Over Temperature Lower Limit

T2: Over Temperature Middle Limit

T3: Over Temperature Upper Limit

Temperaturerises

Temperature

drops

T4 T5

When the temperature drops to T4, a minor

alarm occurs.When the temperature rises to T5, this alarm

is cleared.

T4: Under temperature lower Limit

T5: Under 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.

Figure 8-5 Temperature thresholds




8-9


General None

Verificationcommand

LST BRDTEMPTHD

8.4.3 Procedure

Follow the procedure below to configure module temperature thresholds:



in-service property modification, upload the data configuration file through theMML command ULD CFGFILE on O&M system.



4) 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-10

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. Defaultvalues are recommended.

Figure 8-7 Setting temperature thresholds of NDRU and power amplifier


configuration file.

7) To apply the data now, refer to “4.5.3 Applying Data by Executing Equivalent MML

Command”. Otherwise, this procedure ends.

Note:







8-11

8.5 Modifying Engineering Parameters

8.5.1 Overview

Target To store the engineering parameters in NodeB for quick reference during NodeBmaintenance



Prerequisite None


General Engineering parameters are not running parameters. Instead, they serve asreference for maintenance only. There is no need to restart a NodeB after anengineering parameter file is downloaded to the NodeB.

Verificationcommand

None

8.5.3 Procedure

Follow the procedure below to modify engineering parameters:




MML command ULD FILE on O&M system.

3) Click main menu [File/Edit Engineering Parameters] in the configuration

management system to open the engineering parameter file to be edited.

4) 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, thedialog box shown in Figure 8-8 is displayed.

5) Set the engineering parameters in the tabs in this dialog box.

6) 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-12

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.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 9 Local Cell Properties

9-1

Chapter 9 Local Cell Properties

9.1 Overview of Local Cell Properties

This chapter describes local cell properties including:

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.

Cells in the same sector

Two antennas corresponding to one sector

(in case of 2-way receive diversity)

Antenna mast

Frequency a

Frequency b

Cells with the same frequency

Two s ectors

Sector B

Sector A

RNC

BTS3802C

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

Table 9-1 Properties of NodeB configuration type

NodeB configuration type Example

Receive diversity 2-way receive diversity

Number of sectors 1

Number of frequencies 2

Transmit diversity No transmit diversity

Table 9-2 Correspondence between sectors, frequencies and Local Cell IDs

Sector A Sector B

Frequency a Local Cell ID Aa Local Cell ID Ba

Frequency b Local Cell ID Ab

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:

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

Table 9-4 Local cell logical properties

Localcell

Local cell logicalproperties

Source of the data Peer to beconsistent

with

example

Local Cell ID1 The data depends on network planning.

All the cells of a NodeB belong to a cell group.

RNC 1

NDRU used For no transmit diversity, it is necessary to specifythe NDRU that the cell uses.

For transmit diversity, one local cell uses both theNDRUs.

None NDRU0

Cell radius

(Unit: m)

Decided by network planning RNC 1000

Cell inner handoverradius

(Unit: m)

Decided by network planning

Cell Inner Handover Radius should be at least78.125m (that is 1chip) less than Cell Radius

RNC 0

Localcell 1

Maximum transmitpower

Unit: dBm

Range: 0 - 50

Step: 0.1 dB

This value must be not less than the maximumtransmitting power defined in the networkplanning.

This value cannot be larger than the capacity ofthe power amplification module of the NodeB. Forthe information about the maximum of variouspower amplification modules, refer to the onlinehelp.

RNC 370

Local Cell ID2 … …NDRU … …

Cell radius … …

Cell inner handoverradius

… …

Localcell 2

Maximum transmitpower

… …

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.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 10 Transport Properties

10-1

Chapter 10 Transport Properties

10.1 Overview of Transport Properties

This chapter describes the following aspects:

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.

STM-1 0 STM-1 1 E1(T1) 0E1(T1) 1

NMBU E1 2

NMBU E1 3

NMCU

A B

Transparenttransport switch

NASU E1 1

NASU E1 2

NASU E1 3

NASU E1 4

NASU

NMBU E1/T1 1

NMBU E1/T1 0 A B NMBU

Non-transparent

transport mode

Transparenttransport mode

NMBU: NodeB Maintenance and Baseband UnitNASU: NodeB Access Unit

Non-transparent link mode: Turn the transparent link switch to BTransparent 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-2

Table 10-1 lists the applications of the transport ports.

Table 10-1 Applications of BTS3802C transport ports

NASUstatus

AvailablePort

Transparent linkmode

Connected equipment Application

E1(T1) 0 Non-transparentlink

Connecting NMBU andexternal equipment

UNI, Fractional ATM or Connectingwith a cascading node in SDT CES

NoNASU

E1(T1) 1 Non-transparentlink



Non-transparentlink



E1(T1) 0

Transparent link As No. 3 E1 on NASU, this portconnects NASU and externalequipment.

E1 from STM-1

Non-transparentlink



E1(T1) 1

Transparent link As No. 4 E1 on NASU, this portconnects NASU and externalequipment.

E1 From STM-1

E1 2 Connecting NMBU and NASU E1 From STM-1, configured as UNI

E1 3 Connecting NMBU and NASU E1 From STM-1, configured as UNI

STM-1 0 Connecting NASU and externalequipment

STM-1

Built-inNASU

STM-1 1 Connecting NASU and externalequipment

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

BTS3802C (A)

NASU

RNC

BTS3802C

BTS3802C (B)

NASU

ATM physical layer link (UNI)

ATM layer PVC

AAL layer and the higher layer

Physical medium (No. 0, 1 E1/T1)

Optical fiber

No.0 and No.1 E1/T1

AA

AA


ATM layer PVC


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 betweenBTS3802C(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-4

ATM phy sical layer link（UNI）

ATM lay er (PVC)

RNCBTS3802C (A) BTS3802C (B)

AAA

Physical medium(E1/T1)

AAL lay er and the higher layer

ATM phy sical layer link (UNI)

ATM lay er PVC

Physical medium(E1/T1 )

T RE E L I NK P V C

D

No.0 or 1 E1/T1 No.0 or 1 E1/T1

Figure 10-3 Treelink PVC and the protocol architecture of each segment

Transparenttransport

A

AAL layer and higher layer


ATM layer PVC


NASU

Physical Medium(E1)

D

Optical

fiber No.0, 1 E1

Figure 10-4 Transparent link networking and the protocol architecture of each segment




10-5

A

RNC 2G BSC BTS3802C2G BTS


ATM physical layer link (Fractional ATM)

ATM layer (PVC)

Physical medium(E1/T1 timeslot)2G equipment

cross channel

No.0 and No.1 E1/T1

(some timeslots)

Physical medium

FE

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.

E1/T1 line

C

E1/T1 line

ATM physical layer link

A


RNC2G BSC

C E S

C HANNE L

D

AAL layer and higher layer

ATM layer (PVC)

2G BTSNo.1 or 0 E1No.0 or No.1 E1

EF

BTS3802C

C E S

C HANNE L

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

BTS3802C

NASU

Optical

fiber

Optical

fiber RNC2G BSC 2G BTS

E1 line

C

Figure 10-7 SDH network shared with 2G BTS and transport protocol architecture of each segment

RNC/ADMBTS3802C(A)

2G BTS

NASU

Optical

fiber

No.0 or 1 E12G BSC

CD

E1 lineTransparent transport

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 networkingmode

Transport bandwidth Configuration method

Using optical fiber

(BTS3802C(A) and (B) inFigure 10-2)

Each node can be configured with at

most two UNI links.

Each node exclusively occupies itsUNI link transport bandwidth.

The configuration is made on NASU through

transport manager.

No special configuration is needed onBTS3802C (B).

Using transparent links(Figure 10-4)

Each node can be configured with atmost two UNI links.

Each node exclusively occupies itsUNI link transport bandwidth.

Apart from the configuration on NASU bytransport manager, configuration oftransparent channel on BTS3802C (A) inFigure 10-4 is also needed.

Using treelink PVC

(Figure 10-3)

The NodeB and the neighboring lowerlevel NodeB share the upper level linkby statistic multiplex mode and thussave the transport bandwidth.

Configure treelink PVCs for all PVCs ofBTS3802C (B) on all the upper NodeBs.BTS3802C (A) is illustrated as an upperNodeB




10-7

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 Transport bandwidth Configuration method

SDH networking

(Figure 10-7)

The transport bandwidth depends on thetransport bandwidth of SDH STM-1.

Configure on NASU through transportmanager. No more configurations are neededon BTS3802C.

Transparent channel(Figure 10-8)

A BTS3802C provides at most twotransparent link E1s.

Apart from the configuration on NASU throughtransport manager, configure transparentchannel on BTS3802C.

SDT CES channel(Figure 10-6)

A BTS3802C provides at most two CESchannels.

In a CES channel, only parts of E1/T1timeslots are available.

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:

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 onthe 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:

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 layerand 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-8

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 Properties10.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 Port

UNI link NMBU E1/T1 0 to 3 can be configured as UNI links.

Fractional ATM link 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)

E1/T1 properties Link property Port on RNC/ upper NodeBUNI No.

(E1/T1 port)

E1/T1mode Clockmode Framestructure Linecode Scramblemode Board Slot E1/T1 Port

UNI 2 E1 Slave CRC-4 HDB3 Enable Slot n Port m

UNI 3 E1 Slave CRC-4 HDB3 Enable Slot n Port m

Note:

Line properties and link properties: The properties on both sides of an E1/T1 must be the same except for the clockmode.

Clock mode: The port connecting with the upper level node must be set as "Slave mode", and the one connecting thelower 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-9

Fractional ATM

VPI,VCI

2G BSC--RNC

VPI,VCI

Available timeslots

..

(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

Fractional ATM ·link

BTS3802C—2G BTS

Fractional ATM

..

Unavailable timeslots

NMBU E1/T1 0 or 1

Figure 10-9 Architecture of Fractional ATM link

Table 10-6 lists the Fractional ATM link properties.

Table 10-6 Fractional ATM link properties

E1/T1 Line property Link property Port on RNC/ upperNodeB

Fractional ATMlink No.

(E1/T1 No.) E1/T1mode

Clockmode

Framestructure

Linecode

Scramble mode

Timeslot

BoardSlot

E1/T1 Port

Fractional ATM link0

E1 Slave CRC-4 HDB3

Enable 1~10 Slot n Port m

Note:

Line properties and link properties: The properties on both sides of E1/T1 must be the same except for the clockmode.

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 thelower 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-10

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:

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

(VPI, VCI) for CCP2 (optional)

(VPI, VCI) for AAL2PATH1

(VPI, VCI) f or AAL2PATH2 (optional)

(VPI, VCI) for ALCAP

...

A T M

l a y e

r

A T M

l a y e

r

ATM physical layer link

(UNI/Fractional ATM)NodeBRNC/upper 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 Explanation Relationship between objects

PVC (ATM Physical Layer Bearer, (VPI, VCI)) defines aPVC channel.

A PVC channel must be unique within a NodeB,namely, (ATM Physical Layer Bearer, (VPI, VCI))must be unique.

If PVCs are borne on the same ATMphysical link, the total bandwidth of thePVCs should be smaller than thebandwidth of this link.

NCP,CCP, ALCAP, AL2PATH, IPoA

A NodeB must have an NCP, an ALCAP, one ortwo CCPs, one or two AAL2 PATHs, and an IPoA.

An Iub interface transport object (NCP,CCP, ALCAP, or AAL2PATH)corresponds to one PVC channel.




10-11

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)

PVC AAL and the higher layerIub transportobjects

Bearing link identifieron NodeB

VPI VCI Peakrate

(kbit/s)

Address Other Properties

IPoA UNI0 6 90 64 Local IP,

Peer IP,

Service Type,

Sustaining Cell Rate

NCP UNI0 6 91 64

CCP1 UNI0 6 93 64

CCP2 UNI0 6 94 64

ALCAP node UNI0 6 92 64 ATMaddress

Timer_CC,Timer_POLL,Timer_No_Response, Timer_Keep_Alive,

Max ConnectionControl Count,

Max Poll Data Count,

Max STAT Count.

AAL2 PATH 0

(path id = 1)

UNI 1 6 60 1920

AAL2 PATH 1

(path id = 2)

Sustaining Cell Rate,

Max Burst Size,

Cell Delay VariationTolerance

Note:

The CCP ID and AAL2PATH IDmust be identicalon the NodeBand RNC

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 thepeer.

Note:

These properties must be consistent with theRNC.

10.4.4 Determine Iub Transport Object Properties

The procedure of determining Iub transport object properties is as follows:




10-12

1) 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.

2) 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 Table10-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:

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

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 E1 port on the NodeB

( E1 0 or E1 1)

E1 port on the cascading equipment

Transparent link A E1 0 E1 n

Transparent link B … …

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:

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.

Upper level node (RNCor NodeB)Lower level equipment (2G BTS)

U NI, Fr ac tional ATM link U NI, Fr ac tional ATM link

VPI, VC I

I u b phys ical portE1/T1 port

... ...

VPI, VC I

CESchannel

NC P

CC P

ALCAPIPoA

AAL2 PATH

networking PVC

Channel to lowerlevel equipment

Channel to upperlevel node

CES chann el

NC P

CC P

ALCAPIPoA

AAL2 PATH

networking PVC

..

BTS3802C NMCU

available t imeslots onNMBU E1/T1 0,1

Figure 10-11 SDT CES channel




10-14

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" aredescribed 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 Upper Level NodeChannel to Lower Level Node

ATM Physical Layer Bearer ATM layer and the higher layer

Properties described in Table 10-11

Negotiate with the lower levelequipment.


Negotiate with the upper level node.


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)

E1/T1 properties on NodeB sideCESchannel

No. E1/T1 No.

(E1/T1 0 or 1)

E1/T1mode

Linkcode

Framestructure

Clock mode Timeslotavailable

E1/T1 on Cascadingequipment

0 E1/T1 0 E1 HDB3

CRC-4 Master mode 0, 1 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/T1peer (cascading equipment).

The clock mode must be configured as master mode. The clock mode on the peer must be configured as slavemode.




10-15

Table 10-12 Properties of CES channel to upper level equipment (ATM layer and the higher layer)

CES channelNo.

Bearing linkidentifier on NodeB

VPI VCI ATM cell filling degree

0 UNI 0 6 40 47

Note:

A BTS3802Ccan support atmost two CESchannel

Note:

The configuration must be consistent with theupper node (upper NodeB or RNC).

(VPI, VCI) must be unique among the PVCs onthe same ATM Physical Layer Bearer.

Note:

It must be consistent with the setting on RNC.

The filling degree must be larger than thenumber 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.

RNC or upper NodeB

UNI/Fractional ATM

(VPI, VCI)1

...

(VPI, VCI)2

...

Cascading NodeB Local BTS3802C

(VPI, VCI)1

...

(VPI, VCI)2

...

Treelink PVC

(ATM ro ute table)

E1/T1 port

UNI/Frac ti onal AT M UNI/Frac ti onal AT M UNI/Frac ti onal AT M

E1/T1 portE1/T1 portE1/T1 port

(VPI,VCI) for NCP(VPI,VCI) for CCP

(VPI,VCI) for ALCAPVPI ,VCI) for AAL2PATH

(VPI,VCI) for IPoA(VPI,VCI) for CES

(VPI,VCI) for Treelink PVC

Lower level NodeB PVCs

Neighboring lower le vel NodeB PVCs

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

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".

ATM physical lay er link (UNI)

ATM lay er PVC

Physical medium(E1/T1 )

AAL lay er and higher lay er

ATM phy sical lay er link（UNI）


AAA


T RE E L I NK P V C

D

No.0 or 1 E1/T1 No.0 or 1 E1/T1

VPIs, except that ofnetworking PVC, are 6

BTS3802C (C)



ATM lay er (PVC)

Figure 10-13 VPI planning

10.7.4 Bandwidth Planning for Treelink PVC

The transport bandwidth should be carefully planned. For the calculation and planningof 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)

destination port(to the upper level node)

ATM layer PVC

Refer to Table 10-5 to create such a tablefor the lower level NodeB

Record in Table 10-5 of the local NodeB Described in Table 10-14

Negotiate the properties of the ATM Physical Layer Bearer first.




10-17

Table 10-14 Properties of Treelink PVC (ATM route table) (The data serves as examples)

Source port Destination portPVCs on the Iub interfaceof the lower level NodeB

ATM PhysicalLayer Bearer onthe local NodeB

PVC

(VPI, VCI)

ATM PhysicalLayer Bearer onthe local NodeB

PVC

(VPI, VCI)

Bandwidth

(kbit/s)

Treelink PVC0

(for neighboring lower levelNodeB NCP)

No.1 UNI (7, 91) No.0 UNI (7,91) 64

Treelink PVC1

(for neighboring lower levelNodeB CCP1)

No.1 UNI (7, 93) No.0 UNI (7, 93) 64

… … … … …

Treelink PVC3

(for neighboring lower levelNodeB ALCAP)

No.1 UNI (7, 92) No.0 UNI (7, 92) 64

Treelink PVC4 (forneighboring lower levelNodeB AAL2 PATH 1)

No.1 UNI (7, 60) No.0 UNI (7, 60) 1920

… … … … …

Treelink PVC6

(for neighboring lower levelNodeB IPoA)

No.1 UNI (7, 90) No.0 UNI (7, 90) 64

Treelink PVC7

(for neighboring lower levelNodeB CES channel 1)

No.1 UNI (7, 40) No.0 UNI (7, 40) 64

… … … … …

Treelink PVC10

(for neighboring lower levelNodeB treelink PVC1)

No.1 UNI (8, 90) No.0 UNI (8, 90) 64

… … … … …

the peer is the lower level NodeB,"A" in Figure 10-13

"AA" in Figure10-13

"D" in Figure 10-13Note

(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 Table10-8 of BTS3802C (B).

BTS3802C supports up to 24 treelink PVCs and up to five levels of cascade.




10-18

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) Configure segment "AA" or "A" first.

2) 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.

Physical Layer

VPI-10

VPI-20

VCI-100

VCI-101

VCI-100

VCI-101

ATM Cell

segmentation packing

Iub data

CBR

E1/T1/SDH(STM-1)

ATM Layer AAL Layer

VBR-NRT

AAL5 AAL1 AAL2

VBR-RT

VPI-10

CES

AAL2 PATH

NCP or CCP or ALCAP or IPoA

IMA/UNI/STM-1

Figure 10-14 Transport channels in the NodeB

The data configuration sequence is as follows:

1) Configure the E1/T1 ports.




10-19

2) Configure the UNI or Fractional ATM.

3) Configure the NCP, CCP, ALCAP, AAL2 path, IPoA, and treelink PVC.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 11 Maintenance Channel Properties

11-1

Chapter 11 Maintenance Channel Properties

11.1 Overview of Maintenance Channel Configuration

This chapter provides information on the following subjects:

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.

NASURSTNMBU

M_ETH

A_ETH

B A

NASU board IP (IP1)

NASU O&M switch: A: IPoA maintenance

B: Local maintenance

NASU Ethernet port

NMBU Ethernet port IP (IP0

NMCU panel

NMCU

NASU O&M IP (IP2)

NASU IPoA maintenance channel

IPoA device

NASU local

maintenance channel

NMBU local

maintenance channel

NMBU IPoA maintenance channel

IPoA local I P (IP1)

(IPoA peer IP is IP3)

Figure 11-1 Architecture of NASU maintenance channel




11-2

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".

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 Maintenance channel Description

NMBU localmaintenance channel

Log into BTS3802C through the NMBU Ethernet port on BTS3802C NMCUNodeBmaintenancechannels

NMBU IPoAmaintenance channel

Log into BTS3802C through the IPoA between BTS3802C and RNC

NASU localmaintenance channel

Log into NASU through NASU Ethernet port on NMCU by using NASUboard IP (not NASU O&M IP)

NASU IPoAmaintenance channel:

Log into NASU through the IPoA between BTS3802C and RNC

NASUmaintenancechannels

SDH internalmaintenance channel The channel is the SDH inband Data Communication Channel (DCC).This maintenance channel is introduced in the manual of NASU transportmanager. This manual does not provide the related information

11.3 IP Planning

11.3.1 IP networking

Figure 11-2 illustrates the BTS3802C IP networking.




11-3

RNC

LMT 1Transport manager(Optix Navigator)

SNTP server

M2000 centralizednetwork manager

subnet4 subnet6

subnet5

NASU

BTS3802C

Transport managerOptix NES iManage

LMT 2

NMCU

subnet2

IPoA peer IP

NASU board IP

subnet3NMBUsubnet1

NASU O&M IP

IPoA local IP

RNC BAM IP

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 IP name Location Application Selected value

NASU board IP NASU 129.9.1.1/16

Optix Navigatortransportmanager IP

Transportmanager

When NASU is configured as local maintenance,NASU board IP is the NASU Ethernet port IP onNMCU. In this case, the NASU Ethernet portconnects with NASU transport manager usingcrossover network cable.

129.9.1.2/16

1

NASU O&M IP NMBU Ethernet port IP of NMBU for the interconnectionwith NASU.

129.9.8.1/16

NMBU Ethernetport IP

NMBU 17. 21.2.15/162

LMT1 IP LMT1

NMBU Ethernet port connects with LMT usingcrossover Ethernet cable for NodeB localmaintenance.

17. 21.148.14/16

IPoA local IP NMBU 12.13.11.1/163

IPoA peer IP RNC

Interconnection with RNC for maintenance ofBTS3802C and its NASU from Far RNC throughIub interface. 12.13.1.4/16

LMT2 IP LMT2 IPoA maintenance through LMT2 to BTS3802C 192.13.13.2/16

Optix iManagertransportmanager IP

Transportmanager

IPoA maintenance through Optix iManage to NASU 192.13.13.3/16

4

RNC BAM IP RNC BAM IP Gateway for far end equipment (LMT, M2000 orSNTP server) to access BTS3802C

192.13.13.4/24

5 SNTP server IP Server For time synchronization of BTS3802C with theSNTP server

10.150.22.33/16

6 M2000 IP M2000 For centralized network management of 10.160.22.13/16




11-4

Subnet IP name Location Application Selected value

BTS3802C

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:

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

Maintenancechannel

From To IP Gateway

LMT2 NMBU IPoA local IP RNC BAM IP address in Figure 11-2NMBU IPoAmaintenancechannel NMBU LMT2 IPoA peer IP address in Figure 11-2

Optix NESiManage

NASU RNC BAM IP address in Figure 11-2NASU IPoAmaintenancechannel

NASU Optix NES iManager 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.

M2000 NMBU IPoA local IP IP address of the router Port to which M2000 is connectedNMBU IPoAmaintenancechannel NMBU M2000 IPoA peer IP address




11-5

Maintenancechannel

From To IP Gateway

NMBU SNTP IPoA peer IP addressNMBU IPoAmaintenancechannel SNTP 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.

Local BTS3802C

IP1

Lower levelNode B

RNC LMT

IP4IP3

IP0NMBU ETH IP

IP2

IP5IP6

The route to LMT(IP4), SNTP Server,

gateway: I P2(A) Configure IPoA

local IP: IP1

IPoA peer

IP: IP2 (C) Configure LMT

Ethernet IP: IP4

(D) Configure theroute to BTS3802C

(IP1), gateway:IP3

Configure the route tolower NodeB (IP6),

gateway:IP3

(B) Configurenetworking PVC

IPoA peerIP:IP5

The route toLMT(IP4),

gateway:IP5

Configure IPoAlocal IP: IP6

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 Position Operation

Configurationon NodeB

Configure IPoA device (A in Figure 11-3).

The corresponding IPoA should also be configured on RNC

Configurationon LMT (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.

Configure LocalBTS3802C IPoAmaintenance channel

Configurationon RNC

(1) Configure IPoA device for the local BTS3802C.

(2)Configure the routes on RNC for IP communication between NodeBand far end LMT.

Configurationon lower levelNodeB

Configure IPoA device.

The corresponding IPoA should also be configured on RNC

Configure LowerLevel NodeB IPoAmaintenancechannel

Configurationon Local

BTS3802C

Configure a treelink PVC for the lower node IPoA, namely (B) in Figure11-3.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 12 Transport Bandwidth Planning

12-1

Chapter 12 Transport Bandwidth Planning

12.1 Planning Transport Bandwidth

VPI-10

RNC or upper NodeB

PVC bandwidth

VPI-10

ATM phy sical lay er link bandwidth

Nod eB

Service t raff ic

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:

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,

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

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 Bandwidth of UNI link Bandwidth of Fractional ATM link

E1 1.92 Mbit/s;

E1 overhead: (1 – 1.920 Mbit/s / 2.048 Mbit/s) x 100%= 6.25%

0.064 Mbit/s x timeslot occupied

T1 1.536 Mbit/s 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 Sub-formula

Voice service traffic = 12.2 kbit/s x N (number of voice subscribers) / (1 - FPoverhead) / (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 voicesubscribers) / (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 traffic =

voice service traffic + voice

channel associated signalingtraffic + Voice signaling partcontrol frame traffic.

Voice signaling part control frame traffic = 1.09 kbit/s ×N (number of voicesubscribers) / (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 service traffic = 64.4 kbit/s × M (number of data subscribers) / (1 - FPoverhead) / (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 voicesubscribers) / (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 traffic =

data service traffic + datachannel associated signalingtraffic + Data signaling controlframe traffic.

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

N=Number of voice subscribers + data subscribers

VAD Voice Activity Detection factor




12-3

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:

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,

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:

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 togetherwith 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 CESChannel

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

The following configurations are advisable to meet the CES channel bandwidth

demand:

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.



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Appendix Acronyms and Abbreviations

F-1

Appendix Acronyms and Abbreviations

A

AAL ATM Adaptation Layer

AAL1 ATM Adaptation Layer Type 1

AAL2 ATM Adaptation Layer type 2



ALCAP Access Link Control Application Protocol

AMR Adaptive MultiRate

ATM Asynchronous Transfer Mode

B

BSC Base Station Controller

C

CBR Constant Bit Rate

CCP Communication Control Port

CES Circuit Emulation Service

CID Channel Identifier

F

FACH Forward Access Channel

FLASH FLASH memory

FP Frame protocol

FPGA Field Programmable Gate Array

I

IP Internet Protocol

IPoA Internet Protocols over ATM

L




F-2

LMT Local Maintenance Terminal

M

MIT Management Information Tree

MML Man Machine Language

N

NBAP NodeB Application Part

NCP NodeB Control Port

NASU NodeB Access SDH Unit

NMBU NodeB Maintenance and Baseband unit

NMCU NodeB Maintenance and Control unit

NPSU NodeB Power Supply Unit

NTRU NodeB Transceiver Unit

NDRU NodeB Digital and Radio Unit

NDRF NodeB Duplexer and Rx Filter

NHPA NodeB High Power Amplifier

NEPA NodeB Enhanced Power Amplifier

NAPA NodeB Advanced Power Amplifier

NDUP NodeB Duplexer Unit

O

O&M Operation Administration and Maintenance

P

PDH Plesiochronous Digital Hierarchy

PM Physical Medium sub-layer

PVC Permanent Virtual Channel

R

RNC Radio link controller

RT Real time

RX Receiver




F-3

S

SAAL Signaling ATM Adaptation Layer

SAR Segmentation And Reassembly

SDH Synchronous Digital Hierarchy

SDT Structured Data Transfer

SDU Service Data Unit

STM Synchronous Transfer Mode

STM-1 Synchronous Transfer Mode 1

T

TC Transmission Convergence Sub-layer

TRX Transceiver

TS Time Slot

TX Transmit

U

UDT Unstructured Data Transfer

UNI User Network Interface

V

VBR Variable Bit Rate

VBR-RT Real Time Variable Bit Rate

VC Virtual Channel

VCI Virtual Channel Identifier

VP Virtual Path

VPI Virtual Path Identifier

W

WCDMA Wide(band) Code Division Multiple Access



Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Index

i-1

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


Iub transport,10-10

local cell, 9-1

maintenance channel, 11-1


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

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

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

E

E1/T1 work mode

configuring, 6-1

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

F

far end maintenance channel. see IPoA

maintenance channel

file data and running data

checking consistency, 4-9

fractional ATM link

adding, 6-5

architecture, 10-9

networking, 10-5

property, 10-8

fractional ATM networking

protocol, 10-5

G

guideline

IPoA maintenance channel, 11-5

transport configuration, 10-19

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

K

key properties of template, 2-3

L

local cell

architecture, 9-1

configuring, 5-1

local cell logical property

modifying, 5-3




i-3

property, 9-3

local cell property, 9-1

local cell logical property, 9-3


local maintenance channel

modifying, 7-1

M

maintenance channel

architecture, 11-1

MIT navigation tree, 1-2

MML command


modifying

AAL2PATH, 6-21

ALCAP, 6-20

CCP, 6-21

IPoA, 7-4


local maintenance channel, 7-1

NASU O&M mode, 7-7

NCP, 6-20

NDRU property,5-6


SNTP, 7-5

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


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

O

operations with no equivalent MML commands, 2-4

P

peers of transport protocol, 10-7

planning

AAL2PATH, 12-3

IP network, 11-2


transport bandwidth, 12-1

VPI, 10-17

power amplifier


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


IPoA, 10-12

Iub transport object, 10-9

local cell, 9-1


NCP, 10-12



transparent link, 10-13

transport, 10-1

Treelink PVC, 10-17

UNI link, 10-8

property in configuration file





R

running datachecking 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

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

U

bts3802c operation manual-data configuration.pdf

Documents