This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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..........................
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.....................
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...............................................................................................
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.................
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.9 Adding a Transparent Link 6-15.....................................................................6.9.1 Overview 6-15........................................................................................
6.9.2 Points for Attention 6-15.........................................................................
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.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.................................................................
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
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Table of Contents
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.4.2 Points for Attention.................................................................................................. 4-4 4.4.3 Procedure................................................................................................................ 4-4
4.5 Applying Configuration File Data ....................................................................................... 4-5 4.5.1 Overview of Applying Configuration File Data ........................................................ 4-5 4.5.2 Applying Data by Downloading Configuration File.................................................. 4-5 4.5.3 Applying Data by Executing Equivalent MML Command........................................ 4-7
4.6 Checking Consistency between Configuration File Data and Running Data .................... 4-9 4.6.1 Overview ................................................................................................................. 4-9 4.6.2 Points for Attention.................................................................................................. 4-9 4.6.3 Procedure................................................................................................................ 4-9
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
Chapter 9 Local Cell Properties................................................................................................... 9-1 9.1 Overview of Local Cell Properties...................................................................................... 9-1 9.2 Architecture of Local Cells................................................................................................. 9-1
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Table of Contents
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
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Table of Contents
vi
11.3.2 IP addresses ....................................................................................................... 11-3 11.3.3 IP routes.............................................................................................................. 11-4
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
Chapter 1Introduction to Configuration Management System
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:
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 2 Overview of NodeB Data Configuration
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.
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 2 Overview of NodeB Data Configuration
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.
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.
Chapter 4Common Procedures-Configuration File and Applying Data
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
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:
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:
1) Start configuration management system. Refer to section 4.1 .
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.
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
NodeB initial configurationApplicationoccasion
In-service property modification during network optimization
Prerequisite None
5.2.2 Points for Attention
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
Figure 3-2 illustrates the location of this procedure in the NodeB initialconfiguration process.
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:
1) Start configuration management system. Refer to section 4.1 .
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) To apply the data now, refer to section “4.5.2 Applying Data by Downloading
Configuration File”. Otherwise, this procedure ends.
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
5.3.2 Points for Attention
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
NodeB initial configuration
Prerequisite The E1/T1 work mode must be consistent with the settings of the NMCU DIPswitches.
6.1.2 Points for Attention
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.
Figure 3-2 illustrates the location of this procedure in the NodeB initialconfiguration process.
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 :
1) Start configuration management system. Refer to section 4.1 .
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) Click main menu [File/Open] to open the configuration file to be edited.
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 6 Transport Configuration Procedures
6-10
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) 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>.
6) Click main menu [File/Save] in the configuration management system to save the
configuration file.
7) To apply the data now, refer to section “4.5.3 Applying Data by Executing
Equivalent MML Command”. Otherwise, this procedure ends.
Note:
When the configuration file is closed in the configuration management system, the equivalent MML
commands recorded are cleared. In that case, the only way to apply the properties modified is to download
the configuration file. To save the MML commands, refer to section 4.5.3 .
6.6 Adding an ALCAP Node
6.6.1 Overview
Target To add an ALCAP node
Applicationoccasion
NodeB initial configuration
Prerequisite The ATM physical layer bearer (UNI link, IMA group, STM-1 link, or fractional ATMlink) is ready
6.6.2 Points for Attention
A NodeB has only one ALCAP node.
Perform the operation on the RNC also.
For initialconfiguration
Figure 3-2 illustrates the location of this procedure in the NodeB initialconfiguration process.
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 6 Transport Configuration Procedures
6-14
6.8 Expanding Iub Transport Capacity
6.8.1 Overview
Target To expand Iub transport capacity
Applicationoccasion
In-service property modification during network optimization
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.
6.8.2 Points for Attention
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.
For in-serviceproperty
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".
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 6 Transport Configuration Procedures
6-16
Note:
When the configuration file is closed in the configuration management system, the equivalent MML
commands recorded are cleared. In that case, the only way to apply the properties modified is to download
the configuration file. To save the MML commands, refer to section 4.5.3 .
6.10 Adding an SDT CES Channel
6.10.1 Overview
Target To add an SDT CES channel
NodeB initial configurationApplicationoccasion
In-service property modification during network optimization
Prerequisite The NMCU E1/T1 port 0 or 1 connects to the lower level equipment
6.10.2 Points for Attention
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.
For in-serviceproperty
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:
1) Start configuration management system. Refer to section 4.1 .
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) Click main menu [File/Open] to open the configuration file to be edited.
4) Set properties of NMCU E1/T1 ports connected with lower level node (2G BTS or
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 6 Transport Configuration Procedures
6-19
6.11 Adding a Treelink PVC
6.11.1 Overview
Target To add a treelink PVC for lower level NodeB
NodeB initial configurationApplicationoccasion
In-service property modification during network optimization
Prerequisite None
6.11.2 Points for Attention
For initialconfiguration
Figure 3-2 illustrates the location of this procedure in the NodeB initialconfiguration process.
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.
For in-serviceproperty
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:
1) Start configuration management system. Refer to section 4.1 .
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) Click main menu [File/Open] in configuration management system to open the
configuration file to be edited.
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
3) Click main menu [File/Open] in the configuration management system to open the
configuration file to be edited.
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.
6) Click main menu [File/Save] in the configuration management system to save the
configuration file.
7) To apply the data now, refer to section “4.5.3 Applying Data by Executing
Equivalent MML Command”. Otherwise, this procedure ends.
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 .
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
NodeB initial configurationApplicationoccasion
In-service property modification during network optimization
NMCU has built-in NASU.Prerequisite
Add IPoA device before modifying the NASU O&M mode as remote mode
7.5.2 Points for attention
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 .
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) Click main menu [File/Open] in the configuration management system to open the
configuration file to be edited.
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
The NASU O&M IP resides in the NMBU for direct communication with the NASU board IP when the
NASU O&M mode is configured as remote. Because the NASU board IP is often set as 129.9.*.*, configure
the NASU O&M IP in this subnet.
7) Click main menu [File/Save] in the configuration management system to save the
configuration file.
8) To apply the data now, refer to section “4.5.3 Applying Data by Executing
Equivalent MML Command”. Otherwise, this procedure ends.
Note:
When the configuration file is closed in the configuration management system, the equivalent MMLcommands 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 .
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).
8.3.2 Points for Attention
General None
Verificationcommand
LST PWSAVE
8.3.3 Procedure
Follow the procedure below to set the power supply mode:
1) Start configuration management system. Refer to section 4.1 .
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) Click main menu [File/Open] in the configuration management system to open the
Target To store the engineering parameters in NodeB for quick reference during NodeBmaintenance
NodeB initial configurationApplicationoccasion
In-service property modification during network optimization
Prerequisite None
8.5.2 Points for Attention
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:
1) Start configuration management system. Refer to section 4.1 .
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 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>.
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 9 Local Cell Properties
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.
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.
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 10 Transport Properties
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
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 10 Transport Properties
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
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.
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
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-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
Operation Manual-Data ConfigurationBTS3802C WCDMA NodeB Chapter 12 Transport Bandwidth Planning
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.