NodeB Initial Configuration Guide

NodeB
V100R010
NodeB Initial Configuration Guide
Issue 01
Date 2008-06-25
Part Number
Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Proprietary and Confidential

NodeB
NodeB Initial Configuration Guide Contents
Contents
About This Document.....................................................................................................................1

1 Introduction to NodeB Initial Configuration.......................................................................1-1
1.1 Definition of NodeB Initial Configuration......................................................................................................1-2
1.2 NodeB Initial Configuration Scenarios...........................................................................................................1-2
1.3 NodeB Initial Configuration Tool...................................................................................................................1-2
1.4 NodeB Initial Configuration Methods.............................................................................................................1-2
2 Data Planning and Negotiation of NodeB Initial Configuration.....................................2-1

2.1 NodeB Basic Data...........................................................................................................................................2-2
2.2 NodeB Equipment Layer Data........................................................................................................................2-4
2.3 NodeB Transport Layer Data........................................................................................................................2-32
2.4 NodeB Radio Layer Data..............................................................................................................................2-72
3 NodeB Initial Configuration....................................................................................................3-1

4 Adding a NodeB Through the Template File (Initial)........................................................4-1
4.1 NodeB Template File......................................................................................................................................4-2
4.2 Creating a Logical NodeB (Initial)..................................................................................................................4-2
4.3 Creating a Physical NodeB by Importing the Template File (Initial).............................................................4-6
4.4 Reconfiguring NodeB Data (Initial)................................................................................................................4-8
4.5 Refreshing the Transport Layer Data of the NodeB (Initial)..........................................................................4-9
5 Adding a NodeB Through the Configuration File (Initial)...............................................5-1

5.1 NodeB Configuration File...............................................................................................................................5-2
5.3 Creating a Physical NodeB by Importing a Configuration File (Initial).........................................................5-6
5.4 Reconfiguring NodeB Data (Initial)................................................................................................................5-8
5.5 Refreshing the Transport Layer Data of the NodeB (Initial)..........................................................................5-9
6 Manually Adding a NodeB (Initial).......................................................................................6-1

6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial).......................................................6-7
6.2.1 Manually Creating a Physical NodeB (Initial).......................................................................................6-9
6.2.2 Adding the Boards in the Baseband Subrack (Initial)..........................................................................6-16
6.2.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Macro NodeB)........6-20
6.2.4 Adding an RRU (Initial, Macro NodeB)..............................................................................................6-24
Issue 01 (2008-06-25) Huawei Proprietary and Confidential i

NodeB
Contents NodeB Initial Configuration Guide
6.2.5 Adding RF Modules (Initial)................................................................................................................6-32

6.2.6 Adding an NGRU (Initial)....................................................................................................................6-33
6.2.7 Adding an NCMU (Initial, BTS3812AE)............................................................................................6-34
6.2.8 Adding an NPMU (Initial, Macro NodeB)...........................................................................................6-36
6.2.9 Adding NPSUs (Initial, BTS3812AE/BTS3812A)..............................................................................6-38
6.2.10 Adding Batteries (Initial, BTS3812AE/BTS3812A).........................................................................6-39
6.2.11 Adding an ALD (Initial).....................................................................................................................6-40
6.3 Adding Equipment Layer Data of the BTS3812E (Initial)...........................................................................6-45
6.3.1 Manually Creating a Physical NodeB (Initial).....................................................................................6-48
6.3.2 Adding the Boards in the Baseband Subrack (Initial)..........................................................................6-54
6.3.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Macro NodeB)........6-59
6.3.4 Adding an RRU (Initial, Macro NodeB)..............................................................................................6-63
6.3.5 Adding RF Modules (Initial)................................................................................................................6-71
6.3.6 Adding an NGRU (Initial)....................................................................................................................6-72
6.3.7 Adding an NEMU (Initial, BTS3812E)...............................................................................................6-73
6.3.8 Adding an NPMU (Initial, Macro NodeB)...........................................................................................6-75
6.3.9 Adding NPSUs (Initial, BTS3812E)....................................................................................................6-77
6.3.10 Adding Batteries (Initial, BTS3812E)................................................................................................6-79
6.4 Adding Equipment Layer Data of the DBS3800 (Initial).............................................................................6-85
6.4.1 Manually Creating a Physical NodeB (Initial).....................................................................................6-87
6.4.2 Adding a BBU (Initial).........................................................................................................................6-93
6.4.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Distributed NodeB)
.......................................................................................................................................................................6-98
6.4.4 Adding an RRU (Initial, Distributed NodeB)....................................................................................6-102
6.4.5 Adding an NEMU (Initial, Distributed NodeB).................................................................................6-110
6.4.6 Adding an NPMU (Initial, Distributed NodeB).................................................................................6-111
6.5 Manually Adding the Transport Layer Data of the NodeB (over ATM)....................................................6-117
6.5.1 Adding Links at the Physical Layer (Initial)......................................................................................6-118
6.5.2 Adding Transmission Resource Group (Initial, over ATM)..............................................................6-144
6.5.3 Adding SAAL Links (Initial).............................................................................................................6-146
6.5.4 Adding an NBAP (Initial)..................................................................................................................6-150
6.5.5 Adding an ALCAP (Initial)................................................................................................................6-153
6.5.6 Adding AAL2 Path Data (Initial).......................................................................................................6-155
6.5.7 Adding an OMCH of the NodeB (Initial, over ATM).......................................................................6-160
6.5.8 Adding a Treelink PVC (Initial).........................................................................................................6-164
6.6 Manually Adding Transport Layer Data of the NodeB (over IP)...............................................................6-168
6.6.1 Adding a Link at the Data Link Layer (Initial)..................................................................................6-169
6.6.2 Adding an IP Route (Initial)...............................................................................................................6-188
6.6.3 Adding SCTP Links (Initial)..............................................................................................................6-191
6.6.4 Adding an IPCP (Initial)....................................................................................................................6-195
6.6.5 Adding Transmission Resource Group (Initial, over IP)...................................................................6-197
ii Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide Contents
6.6.6 Adding IP Path Data (Initial).............................................................................................................6-200

6.6.7 Adding an OMCH of the NodeB (Initial, over IP).............................................................................6-205
6.6.8 Adding A Bound Destination Network Segment to the Transmission Resource Group (Initial, IP)
.....................................................................................................................................................................6-209
6.6.9 Adding IP Clock Links (Initial).........................................................................................................6-211
6.6.10 Modifying IP QoS Data (Initial)......................................................................................................6-215
6.7 Refreshing the Transport Layer Data of the NodeB (Initial)......................................................................6-216
6.8 Adding Radio Layer Data...........................................................................................................................6-220
6.8.1 Adding Sites.......................................................................................................................................6-221
6.8.2 Adding Sectors and Cells (Macro NodeB).........................................................................................6-222
6.8.3 Adding Sectors and Cells (Distributed NodeB).................................................................................6-236
7 Related Concepts of NodeB Initial Configuration..............................................................7-1

7.1 Cell Related Concepts.....................................................................................................................................7-2
7.1.1 Sector, Carrier, and Cell.........................................................................................................................7-2
7.1.2 Physical Resources of Cells...................................................................................................................7-3
7.1.3 Local Cell and Logical Cell...................................................................................................................7-6
7.2 ATM Protocol-Related Terms.........................................................................................................................7-6
7.2.1 ATM User Plane, ATM Control Plane, and ATM Management Plane.................................................7-7
7.2.2 ATM Physical Layer, ATM Layer, and AAL........................................................................................7-7
7.3 IP Protocol-Related Terms..............................................................................................................................7-8
7.3.1 Data Link Layer Protocols.....................................................................................................................7-9
7.3.2 IP..........................................................................................................................................................7-11
7.3.3 SCTP....................................................................................................................................................7-14
7.4 NodeB Treelink PVC....................................................................................................................................7-15
7.5 NodeBs in Direct/Cascading Connections....................................................................................................7-17
7.5.1 Definitions of NodeBs in Direct/Cascading Connections....................................................................7-17
7.5.2 Configuration Differences Between NodeBs in Direct/Cascading Connections.................................7-18
Issue 01 (2008-06-25) Huawei Proprietary and Confidential iii

NodeB
NodeB Initial Configuration Guide Figures
Figures
Figure 4-1 Physical NodeB Basic Information window......................................................................................4-6

Figure 4-3 Create Physical NodeB dialog box.....................................................................................................4-8
Figure 4-4 Matching relations............................................................................................................................4-10
Figure 4-5 NodeB Selection window.................................................................................................................4-12
Figure 4-6 Port Match window..........................................................................................................................4-13
Figure 5-2 NodeB Data Configuration File..........................................................................................................5-8
Figure 5-3 Matching relations............................................................................................................................5-10
Figure 5-4 NodeB Selection window.................................................................................................................5-12
Figure 5-5 Port Match window..........................................................................................................................5-13
Figure 6-2 BTS3812AE/BTS3812A panel...........................................................................................................6-7
Figure 6-3 Create Physical NodeB dialog box...................................................................................................6-14
Figure 6-4 NodeB Equipment Layer window....................................................................................................6-15
Figure 6-5 Adding the boards in the baseband subrack.....................................................................................6-19
Figure 6-6 Adding an uplink baseband resource group......................................................................................6-23
Figure 6-7 Adding the RRU (BTS3812AE/BTS3812A/BTS3812E).................................................................6-31
Figure 6-8 Adding the MTRU and MAFU........................................................................................................6-33
Figure 6-9 Adding the NGRU (BTS3812AE/BTS3812A for instance).............................................................6-34
Figure 6-10 Adding an NCMU..........................................................................................................................6-36
Figure 6-11 Adding an NPMU...........................................................................................................................6-37
Figure 6-12 Modifying the NPMU attributes.....................................................................................................6-38
Figure 6-13 Adding an NPSU............................................................................................................................6-39
Figure 6-14 Adding Batteries.............................................................................................................................6-40
Figure 6-15 Adding the ALD.............................................................................................................................6-45
Figure 6-16 BTS3812E panel.............................................................................................................................6-46
Figure 6-17 Create Physical NodeB dialog box.................................................................................................6-53
Figure 6-18 NodeB Equipment Layer window..................................................................................................6-54
Figure 6-19 Adding the boards in the baseband subrack...................................................................................6-58
Figure 6-20 Adding an uplink baseband resource group....................................................................................6-62
Figure 6-21 Adding the RRU (BTS3812AE/BTS3812A/BTS3812E)...............................................................6-70
Figure 6-22 Adding the MTRU and MAFU......................................................................................................6-72
Issue 01 (2008-06-25) Huawei Proprietary and Confidential v

NodeB
Figures NodeB Initial Configuration Guide
Figure 6-23 Adding the NGRU (BTS3812AE/BTS3812A for instance)...........................................................6-73

Figure 6-24 Adding an NEMU...........................................................................................................................6-75
Figure 6-25 Adding an NPMU...........................................................................................................................6-76
Figure 6-26 Modifying the NPMU attributes.....................................................................................................6-77
Figure 6-27 Adding an NPSU............................................................................................................................6-78
Figure 6-28 Adding Batteries.............................................................................................................................6-80
Figure 6-29 Adding the ALD.............................................................................................................................6-85
Figure 6-30 DBS3800 panel...............................................................................................................................6-86
Figure 6-31 Create Physical NodeB dialog box.................................................................................................6-92
Figure 6-32 NodeB Equipment Layer window..................................................................................................6-93
Figure 6-33 Adding the BBU.............................................................................................................................6-98
Figure 6-34 Adding an uplink baseband resource group..................................................................................6-101
Figure 6-35 Adding an RRU (DBS3800).........................................................................................................6-109
Figure 6-36 Adding an NEMU.........................................................................................................................6-111
Figure 6-37 Adding an NPMU in the DBS3800 cabinet..................................................................................6-112
Figure 6-38 Adding the NPMU for the RRU...................................................................................................6-112
Figure 6-39 Adding the ALD...........................................................................................................................6-117
Figure 6-40 Configuring the IMA group and the IMA link individually.........................................................6-123
Figure 6-41 Search Iub Board window............................................................................................................6-124
Figure 6-42 Configuring the IMA links in batches..........................................................................................6-125
Figure 6-43 Configure the UNI links individually...........................................................................................6-129
Figure 6-44 Configure the UNI links in batches..............................................................................................6-130
Figure 6-45 Adding a fractional ATM link......................................................................................................6-133
Figure 6-46 Configuring the SDT CES links...................................................................................................6-140
Figure 6-47 Configuring the UDT CES links..................................................................................................6-141
Figure 6-48 Configuring the timeslot cross channel........................................................................................6-143
Figure 6-49 Configuring the transmission resource group...............................................................................6-146
Figure 6-50 Configuring the SAAL.................................................................................................................6-149
Figure 6-51 Configuring the NCP and the CCP...............................................................................................6-152
Figure 6-52 Adding the AAL2 node................................................................................................................6-155
Figure 6-53 Configuring the AAL2 PATH......................................................................................................6-159
Figure 6-54 Adding an OMCH........................................................................................................................6-163
Figure 6-55 NodeB ATM Transport Layer (Treelink PVC) window..............................................................6-167
Figure 6-56 Adding a PPP link.........................................................................................................................6-174
Figure 6-57 Adding the MLPPP group and the MLPPP link...........................................................................6-178
Figure 6-58 Search Iub Board window............................................................................................................6-179
Figure 6-59 Adding a PPPoE link....................................................................................................................6-183
Figure 6-60 Configuring the DEVIP................................................................................................................6-185
Figure 6-61 Configuring the timeslot cross channel........................................................................................6-188
Figure 6-62 Adding an IP route........................................................................................................................6-190
Figure 6-63 Adding an SCTP link....................................................................................................................6-193
Figure 6-64 Configuring the destination IP address of the SCTP link.............................................................6-194
vi Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide Figures
Figure 6-65 Configuring the NCP and the CCP...............................................................................................6-197

Figure 6-66 Adding the IP transmission resource group..................................................................................6-199
Figure 6-67 Configuring the IP PATH.............................................................................................................6-203
Figure 6-68 Configuring the destination IP address of the IP PATH..............................................................6-204
Figure 6-69 Adding an OMCH........................................................................................................................6-207
Figure 6-70 Adding a destination IP address of the OMCH............................................................................6-208
Figure 6-71 Adding a bound destination network segment to the transmission resource group (initial, over IP)
...........................................................................................................................................................................6-210
Figure 6-72 Adding an IPCLKLNK link.........................................................................................................6-213
Figure 6-73 Configuring the IP address at the IP clock link server.................................................................6-214
Figure 6-74 Configuring the Diffserv priority on the transport layer .............................................................6-216
Figure 6-75 Matching relations........................................................................................................................6-217
Figure 6-76 NodeB Selection window.............................................................................................................6-219
Figure 6-77 Port Match window......................................................................................................................6-220
Figure 6-78 Adding Sites.................................................................................................................................6-222
Figure 6-79 Configuring local sectors and cells...............................................................................................6-232
Figure 6-80 Modifying Mac-hs and Mac-e related parameters........................................................................6-233
Figure 6-81 Configuring remote sectors and cells...........................................................................................6-234
Figure 6-82 Configure distributed sectors and cells.........................................................................................6-235
Figure 6-83 Configuring remote sectors and cells...........................................................................................6-245
Figure 6-84 Configure distributed sectors and cells.........................................................................................6-246
Figure 7-1 Relations among a sector, carrier, and cell.........................................................................................7-3
Figure 7-2 Physical RF resources mapped from sectors onto NodeB..................................................................7-4
Figure 7-3 Rules of the mapping between NodeB sectors and MAFUs or MTRUs............................................7-5
Figure 7-4 Reference model of the ATM protocol...............................................................................................7-6
Figure 7-5 Hierarchy of the PPP........................................................................................................................7-10
Figure 7-6 Five classes of IP addresses..............................................................................................................7-12
Figure 7-7 SCTP Message Structure..................................................................................................................7-15
Figure 7-8 Treelink PVC....................................................................................................................................7-16
Figure 7-9 Treelink PVC principles...................................................................................................................7-16
Figure 7-10 Direct and cascading connections...................................................................................................7-18
Issue 01 (2008-06-25) Huawei Proprietary and Confidential vii

NodeB
NodeB Initial Configuration Guide Tables
Tables
Table 1-1 DBS3800 initial configuration methods and scenarios........................................................................1-3

Table 2-1 Negotiation and planned data of the NodeB........................................................................................2-2
Table 2-2 Negotiation and planned data of the physical NodeB..........................................................................2-4
Table 2-3 Negotiation and planned data of the BBU........................................................................................... 2-9
Table 2-4 Negotiation and planned data of the UL/DL baseband resource group.............................................2-11
Table 2-5 Negotiation and planned data of the RRU Chain...............................................................................2-11
Table 2-6 Negotiation and planned data of the RRU.........................................................................................2-15
Table 2-7 Negotiation and planned data of the RHUB......................................................................................2-17
Table 2-9 Negotiation and planned data of the BBU.........................................................................................2-19
Table 2-10 Negotiation and planned data of the RRU Chain.............................................................................2-22
Table 2-11 Negotiation and planned data of the RRU.......................................................................................2-25
Table 2-12 Negotiation and planned data of the RHUB....................................................................................2-27
Table 2-13 Negotiation and planned data of the ALD.......................................................................................2-28
Table 2-14 Data of the Iub transmission sharing function.................................................................................2-31
Table 2-15 Negotiation and planned data of the IMA group and IMA links.....................................................2-32
Table 2-16 Negotiation and planned data of the UNI links................................................................................2-35
Table 2-17 Negotiation and planned data of the fractional ATM links..............................................................2-37
Table 2-18 Negotiation and planned data of the timeslot cross links.................................................................2-39
Table 2-19 Negotiation and planned data of the SDT CES................................................................................2-39
Table 2-20 Negotiation and planned data of the UDT CES...............................................................................2-42
Table 2-21 Negotiation and planned data of the transmission resource group (over ATM)..............................2-44
Table 2-22 Negotiation and planned data of the SAAL links............................................................................2-45
Table 2-23 Negotiation and planned data of the NBAP.....................................................................................2-47
Table 2-24 Negotiation and planned data of the ALCAP..................................................................................2-48
Table 2-25 Negotiation and planned data of the AAL2 PATH..........................................................................2-49
Table 2-26 Negotiation and planned data of the OMCH (ATM).......................................................................2-51
Table 2-27 Negotiation and planned data of the treelink PVC...........................................................................2-53
Table 2-28 Negotiation and planned data of the ppp links.................................................................................2-55
Table 2-29 Negotiation and planned data of the MLPPP group and MLPPP links...........................................2-58
Table 2-30 Negotiation and planned data of the PPPoE links............................................................................2-60
Table 2-31 Negotiation and planned data of the DEVIP....................................................................................2-62
Table 2-32 Negotiation and planned data of the timeslot cross links.................................................................2-63
Issue 01 (2008-06-25) Huawei Proprietary and Confidential ix

NodeB
Tables NodeB Initial Configuration Guide
Table 2-33 Negotiation and planned data of the IP route...................................................................................2-64

Table 2-34 Negotiation and planned data of the SCTP links.............................................................................2-65
Table 2-35 Negotiation and planned data of the IPCP.......................................................................................2-66
Table 2-36 Negotiation and planned data of the transmission resource group (over IP)...................................2-67
Table 2-37 Negotiation and planned data of the IP PATH.................................................................................2-68
Table 2-38 Negotiation and planned data of the OMCH (IP)............................................................................2-70
Table 2-39 Negotiation and planned data of the transmission resource group whose destination IP network segment
is bound...............................................................................................................................................................2-71
Table 2-40 Negotiation and planned data of the IP clock links..........................................................................2-71
Table 2-41 Negotiation and planned data of the IPQoS.....................................................................................2-72
Table 2-42 Negotiation and planned data of the NodeB....................................................................................2-72
Table 2-43 Negotiation and planned data of the sector......................................................................................2-73
Table 2-44 Negotiation and planned data of the cell..........................................................................................2-75
Table 4-2 Description of the configuration pane..................................................................................................4-7
Table 4-3 Description of the configuration pane................................................................................................4-12
Table 6-2 Module information.............................................................................................................................6-8
Table 6-3 Negotiation and planned data of the physical NodeB........................................................................6-10
Table 6-4 Negotiation and planned data of the BBU.........................................................................................6-16
Table 6-7 Negotiation and planned data of the RRU Chain...............................................................................6-25
Table 6-8 Negotiation and planned data of the RRU.........................................................................................6-28
Table 6-9 Negotiation and planned data of the RHUB......................................................................................6-30
Table 6-11 Module information.........................................................................................................................6-46
Table 6-12 Negotiation and planned data of the physical NodeB......................................................................6-48
Table 6-13 Negotiation and planned data of the BBU.......................................................................................6-55
Table 6-14 Negotiation and planned data of the UL/DL baseband resource group...........................................6-60
Table 6-15 Description of the configuration pane..............................................................................................6-62
Table 6-16 Negotiation and planned data of the RRU Chain.............................................................................6-64
Table 6-17 Negotiation and planned data of the RRU.......................................................................................6-67
Table 6-18 Negotiation and planned data of the RHUB....................................................................................6-69
Table 6-20 Module information.........................................................................................................................6-86
Table 6-21 Negotiation and planned data of the physical NodeB......................................................................6-87
Table 6-22 Negotiation and planned data of the BBU.......................................................................................6-94
Table 6-23 Negotiation and planned data of the UL/DL baseband resource group...........................................6-99
Table 6-24 Description of the configuration pane............................................................................................6-101
Table 6-25 Negotiation and planned data of the RRU Chain...........................................................................6-102
x Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide Tables
Table 6-26 Negotiation and planned data of the RRU.....................................................................................6-106

Table 6-27 Negotiation and planned data of the RHUB..................................................................................6-108
Table 6-28 Negotiation and planned data of the ALD.....................................................................................6-113
Table 6-29 Negotiation and planned data of the IMA group and IMA links...................................................6-120
Table 6-31 Negotiation and planned data of the UNI links..............................................................................6-126
Table 6-33 Negotiation and planned data of the fractional ATM links............................................................6-131
Table 6-34 Negotiation and planned data of the SDT CES..............................................................................6-134
Table 6-35 Negotiation and planned data of the UDT CES.............................................................................6-137
Table 6-38 Negotiation and planned data of the timeslot cross links...............................................................6-142
Table 6-40 Negotiation and planned data of the transmission resource group (over ATM)............................6-144
Table 6-42 Negotiation and planned data of the SAAL links..........................................................................6-147
Table 6-44 Negotiation and planned data of the NBAP...................................................................................6-151
Table 6-46 Negotiation and planned data of the ALCAP................................................................................6-153
Table 6-48 Negotiation and planned data of the AAL2 PATH........................................................................6-156
Table 6-50 Negotiation and planned data of the OMCH (ATM).....................................................................6-161
Table 6-52 Negotiation and planned data of the treelink PVC.........................................................................6-164
Table 6-54 Negotiation and planned data of the ppp links...............................................................................6-170
Table 6-55 Negotiation and planned data of the MLPPP group and MLPPP links.........................................6-175
Table 6-57 Negotiation and planned data of the PPPoE links..........................................................................6-180
Table 6-58 Negotiation and planned data of the DEVIP..................................................................................6-184
Table 6-60 Negotiation and planned data of the timeslot cross links...............................................................6-187
Table 6-62 Negotiation and planned data of the IP route.................................................................................6-189
Table 6-64 Negotiation and planned data of the SCTP links...........................................................................6-191
Table 6-67 Negotiation and planned data of the IPCP.....................................................................................6-195
Issue 01 (2008-06-25) Huawei Proprietary and Confidential xi

NodeB
Tables NodeB Initial Configuration Guide

Table 6-69 Negotiation and planned data of the transmission resource group (over IP).................................6-198
Table 6-71 Negotiation and planned data of the IP PATH...............................................................................6-201
Table 6-74 Negotiation and planned data of the OMCH (IP)..........................................................................6-206
Table 6-76 Negotiation and planned data of the transmission resource group whose destination IP network segment
is bound.............................................................................................................................................................6-209
Table 6-78 Negotiation and planned data of the IP clock links........................................................................6-212
Table 6-81 Negotiation and planned data of the IPQoS...................................................................................6-215
Table 6-83 Negotiation and planned data of the NodeB..................................................................................6-221
Table 6-84 Negotiation and planned data of the sector....................................................................................6-224
Table 6-85 Negotiation and planned data of the cell........................................................................................6-226
Table 6-90 Negotiation and planned data of the sector....................................................................................6-237
Table 6-91 Negotiation and planned data of the cell........................................................................................6-239
Table 7-1 Functions of the ATM user plane, ATM control plane, and ATM management plane.......................7-7
Table 7-2 Layers and functions of the reference model of the ATM protocol.....................................................7-7
Table 7-3 Classification and range of IP addresses............................................................................................7-13
Table 7-4 Configuration differences between NodeBs in direct/cascading connections...................................7-18
xii Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide About This Document
About This Document
This describes how to use the CME to configure a new site, that is, the NodeB, during network
construction or network optimization.
Purpose
NOTE
This document describes the following models of NodeBs: BTS3812E, BTS3812A, BTS3812AE,
DBS3800, and iDBS3800.
During network deployment or network optimization, you need to prepare the configuration file
for each NodeB and load the file to the NodeB in commissioning so as to ensure that the NodeB
works as designed.
This document serves as a guideline on how to configure the initial data for the NodeB. The
content involves two parts. That is, how to prepare data for NodeB initial configuration and how
to add data to the NodeB through manual operations, template files, and configuration files. In
addition, this document also provides the reference information for the configuration.
Versions
Product Names Versions
WRAN CME V100R005
NodeB Versions
Product Names Versions
BTS3812A V100R010
BTS3812AE V100R010
BTS3812E V100R010
DBS3800 V100R010
iDBS3800 V100R010
Issue 01 (2008-06-25) Huawei Proprietary and Confidential 1

NodeB
About This Document NodeB Initial Configuration Guide
Intended Audience
This document is intended for:
l Field engineers
l Network operators
l System engineers
Before you read this guide, it is recommended that you reference the CME User Guide.
Change History
For details, refer to Changes in NodeB Initial Configuration Guide.
Organization
1 Introduction to NodeB Initial Configuration
This provides the definition and describes the scenarios, tools, and methods of NodeB initial
configuration.
2 Data Planning and Negotiation of NodeB Initial Configuration
This describes the preparations you must make before configuring initial data to the NodeB. The
preparations must be based on the network planning, connections with other devices, bandwidth
resources, and the NodeB hardware resources.
3 NodeB Initial Configuration
This describes how to add a NodeB on the CME.
4 Adding a NodeB Through the Template File (Initial)
This describes how to configure the NodeB through the template file if the configuration type
of the NodeB is one of the typical configuration types of the template file.
5 Adding a NodeB Through the Configuration File (Initial)
This describes how to add a NodeB through a configuration file if the configuration file is
applicable to the NodeB.
6 Manually Adding a NodeB (Initial)
This describes how to manually add a NodeB. This method is used to adjust the data after a
template file or a configuration file is imported.
7 Related Concepts of NodeB Initial Configuration
This provides the related concepts to be referenced during the process of the NodeB initial
configuration.
Conventions
1. Symbol Conventions
The following symbols may be found in this document. They are defined as follows
2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide About This Document
Symbol Description
Indicates a hazard with a high level of risk that, if not avoided,

will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which, if

not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation that, if not avoided,

could cause equipment damage, data loss, and performance
CAUTION degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save your
time.
NOTE Provides additional information to emphasize or supplement

important points of the main text.
2. General Conventions
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files,directories,folders,and users are in boldface. For

example,log in as user root .
Italic Book titles are in italics.
Courier New Terminal display is in Courier New.
3. Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are optional.
{x | y | ...} Alternative items are grouped in braces and separated by vertical

bars.One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets and

separated by vertical bars.One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by vertical

bars.A minimum of one or a maximum of all can be selected.
Issue 01 (2008-06-25) Huawei Proprietary and Confidential 3

NodeB
About This Document NodeB Initial Configuration Guide
[ x | y | ... ] * Alternative items are grouped in braces and separated by vertical

bars.A minimum of zero or a maximum of all can be selected.
4. GUI Conventions
Boldface Buttons,menus,parameters,tabs,window,and dialog titles are in

boldface. For example,click OK.
> Multi-level menus are in boldface and separated by the ">" signs.
For example,choose File > Create > Folder .
5. Keyboard Operation
Key Press the key.For example,press Enter and press Tab.
Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+A

means the three keys should be pressed concurrently.
Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the two
keys should be pressed in turn.
6. Mouse Operation
Action Description
Click Select and release the primary mouse button without moving the
pointer.
Double-click Press the primary mouse button twice continuously and quickly
without moving the pointer.
Drag Press and hold the primary mouse button and move the pointer
to a certain position.
4 Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide 1 Introduction to NodeB Initial Configuration
1 Introduction to NodeB Initial Configuration
About This Chapter
This provides the definition and describes the scenarios, tools, and methods of NodeB initial
configuration.
1.1 Definition of NodeB Initial Configuration

NodeB initial configuration is the process of preparing and configuring the data after the NodeB
hardware components are installed. The configuration is based on the NodeB hardware
components, network planning, and data negotiation between the NodeB and other equipment.
After the configuration, a data configuration file in .xml format is generated.
1.2 NodeB Initial Configuration Scenarios
This describes the scenarios of the NodeB initial configuration.
1.3 NodeB Initial Configuration Tool
WRAN CME, a tool for NodeB initial configuration, provides an integrated solution to RAN
data configuration. In addition, this tool can be used for initial configuration and data
reconfiguration for the NodeB and the RNC.
1.4 NodeB Initial Configuration Methods
This describes three methods of the NodeB initial configuration. You can perform the NodeB
initial configuration through any of the following methods: Adding a NodeB through a template
file, adding a NodeB through a configuration file, and manually adding a NodeB. Select an
appropriate configuration method depending on the scenario.
Issue 01 (2008-06-25) Huawei Proprietary and Confidential 1-1

NodeB
1 Introduction to NodeB Initial Configuration NodeB Initial Configuration Guide
1.1 Definition of NodeB Initial Configuration

NodeB initial configuration is the process of preparing and configuring the data after the NodeB
hardware components are installed. The configuration is based on the NodeB hardware
components, network planning, and data negotiation between the NodeB and other equipment.
After the configuration, a data configuration file in .xml format is generated.
The configuration file must meet the following requirements:
l The data is intact, correct, and compatible with the physical configuration of the equipment.
l The Iub interface data at the transport layer is consistent with that at the RNC. This ensures
normal data exchange between the NodeB and the RNC.
1.2 NodeB Initial Configuration Scenarios

This describes the scenarios of the NodeB initial configuration.
The scenarios are as follows:
l A new NodeB is required during the initial phase of network construction.
l A new NodeB is required during network optimization.
NOTE
During network optimization, reconfigure the data in online configuration mode to expand the capacity of
existing NodeBs. For details about data reconfiguration, refer to RAN Reconfiguration Guide (CME-
Based).
1.3 NodeB Initial Configuration Tool

WRAN CME, a tool for NodeB initial configuration, provides an integrated solution to RAN
data configuration. In addition, this tool can be used for initial configuration and data
reconfiguration for the NodeB and the RNC.
The GUI-based CME provides the operating platform for RAN data configuration. For details
on how to use the WRAN CME, refer to the CME User Guide.
1.4 NodeB Initial Configuration Methods

This describes three methods of the NodeB initial configuration. You can perform the NodeB
initial configuration through any of the following methods: Adding a NodeB through a template
file, adding a NodeB through a configuration file, and manually adding a NodeB. Select an
appropriate configuration method depending on the scenario.
Table 1-1 lists the methods and scenarios of the NodeB initial configuration.
1-2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)

NodeB
NodeB Initial Configuration Guide 1 Introduction to NodeB Initial Configuration
Table 1-1 DBS3800 initial configuration methods and scenarios

Method Scenario
4 Adding a NodeB The actual configuration type is the same as or similar to the template
Through the file.
Template File
(Initial)
5 Adding a NodeB If you need to configure multiple NodeBs with the same or similar
Through the configurations, you can create a typical configuration file for a
Configuration File NodeB, and then configure the other NodeBs by modifying the
(Initial) configuration file.
6 Manually Adding After the template file or configuration file is imported, you are
a NodeB (Initial) recommended to manually perform data reconfiguration if required.

NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration
2 Data Planning and Negotiation of NodeB

Initial Configuration
About This Chapter
This describes the preparations you must make before configuring initial data to the NodeB. The
preparations must be based on the network planning, connections with other devices, bandwidth
resources, and the NodeB hardware resources.
2.1 NodeB Basic Data

This lists the basic data for configuring logical NodeBs.
2.2 NodeB Equipment Layer Data
This describes the data to be prepared for configuring the NodeB equipment layer.
2.3 NodeB Transport Layer Data
This describes the data to be prepared for configuring the NodeB transport layer in the ATM
and the IP mode.
2.4 NodeB Radio Layer Data
This describes the data to be prepared for configuring the NodeB radio layer.

2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide
2.1 NodeB Basic Data

This lists the basic data for configuring logical NodeBs.
Table 2-1 Negotiation and planned data of the NodeB

Input Field Description Exampl Source
Data Name e
NodeB ID NodeB_Id The NodeB ID is automatically 1

allocated. You can define the logical
NodeB before configuring it as a
physical NodeB. Network
Name of NodeB_Na This parameter indicates the name of the NodeB_ planning
the NodeB me NodeB. You are recommended to name 1
the NodeB according to its geographical
location.
Bearer type IubBearerT Identify the transmission type of the Iub ATM_T
ype interface for the RNC. The type must RANS
match the type of the interface board at
the RNC. Optional parameters:
l ATM_TRANS
l IP_TRANS
l ATMANDIP_TRANS
Sharing SharingSup Whether to share NodeB information NON_S

support port Optional parameters: HARED
l SHARED: indicates that all network
operators can browse the information
of this logical NodeB and that of the
corresponding physical NodeB. Negotiati
on with
l NON_SHARED: indicates that only
the
the network operator specified by the
destinati
CnOpIndex parameter can browse
on
the information of this logical NodeB
and the that of the corresponding
physical NodeB
Telecom CnOpIndex This parameter is valid only when the 0

operator SharingSupport parameter is set to
index NON_SHARED.
Value range: 0 through 3
Resource RscMngM Defines the resource management mode SHARE

manageme ode when the bandwidth is allocated
nt mode Optional parameters:
l SHARE
l EXCLUSIVE


Data Name e
ATM NSAP The NodeB relevant ATM address in H'39010

Address hexadecimal format. This parameter is 1010101
invalid when IubBearerType is set to 01
IP_TRANS. 0101010
You need to set the first byte of the ATM 1010101
address to H'45 (indicating an E.164 01
address), H'39 (indicating a DCC 0101010
address) or H'47 (indicating an ICD 101
address).
If the first byte is H'45, the following
seven and a half bytes (that is, 15 digits)
must be a BCD code. If the following
part, called DSP, are all 0s, this address
is called E.164e. If the DSP are not all
0s, this address is called E.164A. The
ATM addresses are allocated in the
ATM network and cannot be repeated.
Value range: 42 bytes (including the
prefix H')
Hybrid IPTransAp Identifies whether hybrid transport is -

transport artInd supported over the Iub interface. This
flag parameter is valid only when
IubBearerType is set to IP_TRANS or
ATMANDIP_TRANS. Optional
parameters:
l SUPPORT
l NOT_SUPPORT
Transmissi TransDelay Initial round-trip transmission delay on 10

on delay on the Iub interface in ATM circuit
the Iub transport or IP dedicated transport
interface Value range: 0 through 65535
Transmissi IPApartTra Initial round-trip transmission delay on -

on delay on nsDelay the Iub interface in hybrid IP transport.
the Iub This parameter is valid only when
interface in TransDelay is set to SUPPORT.
hybrid IP Value range: 0 through 65535
transport
Satellite SatelliteInd Identifies the satellite transmission on FALSE

transmissio the Iub interface. Optional parameters:
n indication l TRUE
l FALSE


Data Name e
NodeB NodeBTyp Identifies the type of the logical NodeB. NORMA

type e Optional parameters: L
l NORMAL
l PICO_TYPE1
l PICO_TYPE2
Protocol ProtocolVe Protocol version of the NodeB. R6

Version r Optional parameters:
l R99
l R4
l R5
l R6
2.2 NodeB Equipment Layer Data

This describes the data to be prepared for configuring the NodeB equipment layer.
Data of the Physical NodeB
Table 2-2 Negotiation and planned data of the physical NodeB

Input Field Name Description Example Source
Data
Working E1T1WorkMod The working mode of E1/T1 links E1

mode of e depends on the state of DIP
E1/T1 switches on the BBU or NUTI and
links the configuration file.
Clock ClockSource This parameter is valid only when LINE

source ClockWorkMode is set to Negotiati
MANUAL. Optional parameters: on with
l GPSCARD (GPS card clock the
source) destinatio
l BITS (BITS clock source): The n
outdoor BBU (HBBUC) cannot
use this clock source.
l LINE (clock source extracted
from the Iub interface line)
l IP (IP clock source)


Data
Working ClockWorkMod Working mode of the system clock MANUA

mode of e Optional parameters: L
the clock l MANUAL (manual mode): In
this mode, the user specifies the
clock source, and automatically
switching the system clock to
other clock sources is not
allowed. Even if the specified
clock source is faulty, such
switching is not allowed.
l FREE (free-run mode): The Network
free-run mode is the working planning
mode for the clock source at an
initial phase.
Working IPClockMode This parameter is valid only when -

mode of ClockSource is set to IP. Optional
the IP parameters:
clock l AUTO (default value)
l MANUAL (This parameter is
configured when the IP clock is
already configured.)
GPS GPSCableDelay Delay of the GPS feeder 0 Internal

feeder Value range: 0 through 1000 planning
delay
SNTP SNTPSwitch Synchronization switch Optional ON Network

switch parameters: planning
l ON (SNTP client requires time
synchronization)
l OFF (SNTP client does not
require time synchronization)


Data
IP address SNTPServerIP The SNTP server is used to 10.11.1.1 Negotiati

of the synchronize the time of multiple on with
SNTP SNTP clients, which is important the
server for centralized maintenance, destinatio
especially for alarm management. n
For example, when an E1 link is
disconnected, the NodeB and the
RNC report the alarm at the same
time based on SNTP. This helps
fault locating.
The SNTP server of the NodeB can
be either the M2000 or the RNC.
l The SNTP server of the NodeB
is the RNC (recommended): set
SNTPServerIP to the BAM
internal IP address.
is the M2000: set
SNTPServerIP to the M2000
host external IP address.
Synchroni SyncPeriod The period in which nodes are 10

zation synchronized.
period Value range: 1 through 525600
Demodula DemMode Demodulation mode of the NodeB DEM_2_

tion mode Optional parameters: CHAN
l DEM_2_CHAN (two-way
demodulation mode)
l DEM_4_CHAN (four-way
demodulation mode)
l DEM_ECON_4_CHAN (four-
way economical demodulation Network
mode) planning
High BER HighThreshold Optional parameters: 1E-5

thresholds l 1E-3
of E1/T1
l 1E-4
l 1E-5
l 1E-6
Smooth SMTHPWRSwi Optional parameters: CLOSE

power tch l OPEN
switch
l CLOSE


Data
LowerLimit Disabling the lower limit of the 0

Lower and time range for the transmitter
upper Value range: 0 through 255
limits of
timer UpperLimit Disabling the upper limit of the 0
setting time range for the transmitter
NodeB ResAllocateRul Optional parameters: PERFFI

resource e l PERFFIRST (handover RST
distributio performance priority mode)
n mode
l CAPAFIRST (capacity priority
mode)
NodeB IP LocalIP IP address of the NodeB for local 17.21.2.1

address maintenance 5
Subnet LocalIPMask Subnet mask of the NodeB IP 255.255.

mask address for local maintenance 0.0
NMPT NMPTBackup This parameter is available only ENABLE Internal

backup Mode for the macro NodeB. planning
mode
NAOIFrameMo Frame structure of the optical port -

de (macro chip Optional parameters:
STM-1 NodeB) l FRAMEMODE_SONET (in
frame
STM1FrameMo SONET mode) FRAME
mode
de (distributed l FRAMEMODE_SDH (in SDH MODE_
NodeB) mode) SDH
Managem Au This parameter is valid only for the AU3 Negotiati

ent unit channelized optical interface. on with
Optional parameters: the
l AU3 destinatio
n
l AU4
Bypass Tu This parameter is valid only for the TU12

unit channelized optical interface.
Optional parameters:
l TU11 (the E1/T1 mode is T1)
l TU12 (the E1/T1 mode is E1)


Data
Power type PowerType Configuring the power type for the -48 V DC
of the NodeB. This parameter is
macro available only for the macro
NodeB NodeB. Optional parameters:
l -48 V DC
l 24 V DC
l 220 V AC
Report CHRSwitch When the NodeB CHR report OFF

switch for switch is on, the NodeB uploads
call history the CHR log to the FTP server that
record is at the NodeB side.
IUBGroup1 Group backup mode of the Iub SHARIN

interface board, namely the NDTI G
or the NUTI, in slots 12 and 13
l REDUNDANCY (active and
standby backup): The board
must be the NUTI. No sub-
board can be added. Only the
baseboard held in slot 12 can be
used. The attributes of the board Internal
held in slot 13 remain planning
unchanged.
l SHARING (load sharing): The
Iub NDTI and NUTI can be inserted
interface in either slot 12 or 13. Both the
board board of the baseband subrack
group and the sub-board can be used.
backup IUBGroup2 Group backup mode of the Iub SHARIN
mode interface board, namely the NUTI, G
in slots 14 and 15 Optional
parameters:
standby backup): No sub-board
can be added. Only the
used. The attributes of the board
held in slot 15 remain
unchanged.
l SHARING (load sharing): Only
the sub-board added to the
NUTI held in slots 14 and 15
can be used.

Macro NodeB Equipment Layer Data
Table 2-3 Negotiation and planned data of the BBU

Input Field Description Example Source
Data Name
NMPT NMPT l When the NMPT needs a backup, If backup is

configure two NMPTs. The active not
NMPT is configured in slot 10, and required,
the standby NMPT is configured in configure
slot 11. the NMPT
l When the NMPT does not need a in slot 10.
backup, configure one NMPT. The
NMPT is configured in slot 10.
NodeB NMON The NMON controls the RET The

monitoring controller and provides Boolean value NMON is
unit monitoring interfaces such as the 32- configured
line Boolean input interface and 7-line in slot 16.
Boolean output interface.
Baseboard - According to the capacity of the HBBI/ The HBOI

NBBI, EBBI/EBOI, HULP/EULP, and and the
HDLP/NDLP and the expected NodeB EBOI are
Internal
configuration, select applicable configured
planning
baseband boards. in slots 0
and 1.
Transport - Optional parameters: The NUTI

boards l NDTI: One NDTI provides eight E1/ is
T1 ports. configured
in slot 13.
l NUTI: One NUTI provides eight E1/
T1 ports and two FE ports. If the E1/
T1 sub-board is added to the NUTI,
the NUTI can provide more E1/T1
ports.
Bearer BearMod This parameter is valid only when the IPV4

mode e transport board is the NUTI. Optional
parameters:
l ATM
l IPV4


Data Name
IP clock IPClock You need to set the IP clock switch on ENABLE

switch Switch the NUTI baseboard to ENABLE if you
plan to use the FE ports on the NUTI
board to receive the IP clock signals.
(This parameter is valid only when
BearMode is set to IPV4.) Optional
parameters:
l ENABLE
l DISABLE
Line LineImp Line impedance of the E1 line Optional 75

impedance edance parameters:
l 75 (E1 working mode)
l 100 (T1 working mode)
HSDPA HsdpaS This parameter is available when the

switch witch NUTI is configured or the
unchannelized optical sub-board is
configured on the NUTI. Optional
parameters:
l SIMPLE_FLOW_CTRL: Based on
the configured Iub bandwidth and
the bandwidth occupied by R99
users, traffic is allocated to HSDPA
users when the physical bandwidth
restriction is taken into account.
l AUTO_ADJUST_FLOW_CTRL:
According to the flow control of
SIMPLE_FLOW_CTRL, traffic is AUTO_A
allocated to HSDPA users when the DJUST_F
delay and packet loss on the Iub LOW_CT
interface are taken into account. The RL
RNC uses the R6 switch to perform
this function. It is recommended that
the RNC be used in compliance with
the R6 protocol.
l NO_FLOW_CTRL: The NodeB
does not allocate bandwidth
according to the configuration or
delay on the Iub interface. The RNC
allocates the bandwidth according to
the bandwidth on the Uu interface
reported by the NodeB. To perform
this function, the reverse flow
control switch must be enabled by
the RNC.

Table 2-4 Negotiation and planned data of the UL/DL baseband resource group
Data Name
ID of the ULResou l A board that is not added to the 1

UL rceGroup UL baseband resource group, that
baseband Id is, the HBBI/NBBI, EBBI/EBOI,
resource and HULP/EULP, cannot process
group baseband services.
l An uplink baseband resource
group can process a maximum of
six cells.
l Insufficient uplink baseband
resources may result in a cell
setup failure.
ID of the DLResou l A board that is not added to the 0 Internal

DL rceGroup DL baseband resource group, that planning
resource and HDLP/NDLP, cannot process
l The downlink processing units
within the downlink resource
group should belong to an uplink
resource group.
l The amount of local cells
supported by the resource group
is determined by the amount and
the specifications of the boards
within the resource group.
Table 2-5 Negotiation and planned data of the RRU Chain

Data
Chain Chain Type RRU topology structure Optional CHAIN

type parameters:
l CHAIN (chain topology)
l RING (ring topology) Internal
planning
Chain/ Head Subrack Number of the subrack that holds 0
Ring head No. the head BBU in the chain or ring
subrack Value range: 0 through 1
number


Data
Chain/ Head Board No. Number of the slot that holds the 0
Ring head head BBU in the chain or ring
board Optional parameters:0
number
Head port Head Port No. Number of the port on the head 0
number BBU that is connected to the RRU
in the chain or ring
End End Subrack Number of the subrack that holds -

subrack No the end BBU in the ring. This
number parameter is applicable only to the
ring topology.
End board End Board No Number of the slot that holds the -
number end BBU in the ring. This
parameter is valid for only the ring
topology.
Optional parameters:0
End port End Port No Number of the port on the end -

in the chain or ring. This parameter
is valid for only the ring topology.


Data
Break Break Position This parameter indicates the OFF

position 1 1 position of the first break point.
When you add and delete an RRU
at a particular position in the
current RRU topology (ring or
chain), set a break point at this
position. After the RRU is added
or deleted, delete the break point to
resume the data.
For RRU chain, only one break
point can be set. After the setting
of break point, the RRU chain is
divided into two parts:
l The first part refers to the
section between the head of
RRU chain and the break point.
This part of RRU service is not
affected.
l The second part refers to the
post-break point section of the
RRU chain. This part of RRU
service is disrupted because it is
in separate status.


Data
Break Break Position Second position of the break point -

position 2 2 only for the ring topology
resume the data.
For the RRU ring, two break points
can be set. After the setting of
break point, the RRU chain is
divided into three parts:
section between the head the of
RRU ring and the first break
point. This part of RRU service
can be affected.
section between two break
points of the RRU ring. This
part of RRU service is disrupted
because it is in separate status.
l The third part refers to the
section between the second
break point and the end of the
RRU ring. This part of RRU
service can be affected.
For the RRU ring, when only one
break point is set, the actual case is
that two break points are set in the
same position, that is, two break
points overlap.

Table 2-6 Negotiation and planned data of the RRU

Data
RF - l In 1 x 1 configuration, Configure
Module configure one RF module. either the
l In 3 x 1 configuration, RRU or the
configure three RF WRFU
modules. Network
l In 3 x 2 configuration, planning
configure three or six RF
modules.
l In 6 x 1 configuration,
configure six RF modules.
RRU name RRUName Name of the MRRU Name
RRU chain RRUChainNo This parameter indicates the 0

number number of the chain to which
the RRU is connected.
RRU RRUNo The TRUNK position 2

number indicates that the RRU is at
the cascaded position of the
main chain or ring. The
BRANCH position indicates Internal
that the RRU is at the planning
cascaded position where the
parent node is located. The
parent node refers to the
RHUB.
Board BoardStatus Blocking status of the RRU UnBlock

status Optional parameters:
l Block
l Unblock
Topology ToPoPosition Optional parameters: TRUNK Network

position of l TRUNK (in the main ring) planning
the RRU
l BRANCH (under the
RHUB node)


Data
Initial RTWPofCarrie Set the initial correction 0

correction rCarrier value for the RTWP of the
value for numberonRx carrier and TX channel
the RTWP RX channel specified by the RRU. Value
number range:
l Number of Carrier: 0 to 3
(MRRU/WRFU), 0 to 1
(PRRU)
l RX channel number:0 to 1
l Initial correction value for
the RTWP: -130 to +130,
unit: 0.1 dB
RRU IF IFOffset Offset direction of the MIDDLE

offset Intermediate Frequency (IF)
filter Optional parameters:
l BOTTOM: Offset to
bottom, that is, to the
minimum value (The
interference signal
frequency is greater than
or equal to the current
receive frequency.)
l MIDDLE: Offset to
middle, that is, no offset
(no interference)
l TOP: Offset to top, that is,
to the maximum value
(The interference signal
frequency is smaller than
the current receive
frequency.)
l MINUS_50M (only four
carrier RRU support)
l PLUS_50M (only four
Floor Floor Floor for installing the RRU 0

Value range: -100 through
+1000


Data
Vertical Vertical Vertical position of the RRU 0

Horizontal Horizontal Horizontal position of the 0

RRU
Table 2-7 Negotiation and planned data of the RHUB

Data


RHUB.

l Block
l Unblock

position of l TRUNK (in the main planning
the RRU ring)
l BRANCH (under the
RHUB node)

+1000


Data


RRU
Equipment Layer Data of the Distributed NodeB
Data Name
ID of the ULResou l A board such as the HBBU or the 1

UL rceGroup HBBUC that is not added to the
baseband Id UL baseband resource group
resource cannot process baseband services.
group l An uplink baseband resource
six cells.
setup failure.
ID of the DLResou l A board such as the HBBU or the 0 Internal

DL rceGroup HBBUC that is not added to the planning
group l The downlink processing units
resource group.


Data
Board BoardStatus Blocking status of the board Optional UnBlock

status parameters:
l Block
l Unblock
Internal
Clock ClockSource E1/T1 ports for extracting the Iub Port 0 planning
source 8K interface clock signals. Optional
parameters:
l None
l Port 0 to port 7
Bearer BearMode Optional parameters: ATM

mode l ATM: If the bearer mode is ATM,
the IP transport layer cannot use
the E1/T1 ports, that is, you cannot
configure the PPP or MP links.
l IPv4: If the bearer mode is IPv4, Negotiati
the ATM transport layer cannot on with
use the E1/T1 ports, that is, you the
cannot configure the physical destinatio
links. n
HSUPA HSUPA Optional parameters: DISABL
switch l ENABLE (The HSUPA is E
supported)
l DISABLE (The HSUPA is not
supported)
Clock ClockMode For the cascaded NodeBs, the clock SLAVE Network
Mode of the upper-level NodeB is set to planning
MASTER and that of the lower-level
NodeB is set to SLAVE. If the value
is not specified, the original clock
mode is retained. Optional
parameters:
l MASTER (primary mode)
l SLAVE (secondary mode)
Line Code LineCode Optional parameters: HDB3 Negotiati

l HDB3 (for E1 mode) on with
the
l AMI (for E1 or T1 mode) destinatio
l B8ZS (for T1 mode) n


Data
Frame FrameStru Optional parameters: E1_CRC

Structure l E1_DOUBLE_FRAME (double 4_MULT
frame, for E1 mode) I_FRAM
E
l E1_CRC4_MULTI_FRAME
(CRC-multiframe, for E1 mode)
l T1_SUPER_FRAME (super
frame, for T1 mode)
l T1_EXTENDED_SUPER_FRA
ME (extended super frame, for T1
mode)
HSDPA HsdpaSwitch Optional parameters: AUTO_A

switch l SIMPLE_FLOW_CTRL: Based DJUST_
on the configured Iub bandwidth FLOW_C
and the bandwidth occupied by TRL
R99 users, traffic is allocated to
HSDPA users when the physical
bandwidth restriction is taken into
account.
l AUTO_ADJUST_FLOW_CTRL
: According to the flow control of
SIMPLE_FLOW_CTRL, traffic
is allocated to HSDPA users when
the delay and packet loss on the
Iub interface are taken into
account. The RNC uses the R6
switch to perform this function. It
is recommended that the RNC be
used in compliance with the R6
protocol.
delay on the Iub interface. The
RNC allocates the bandwidth
according to the bandwidth on the
Uu interface reported by the
NodeB. To perform this function,
the reverse flow control switch
must be enabled by the RNC.
Time delay HsdpaTD When the time delay is lower than 4

threshold this threshold, you can infer that the
link is not congested.
Value range:0 to 20


Data
Discard HsdpaDR The link is not congested when frame 1

rate loss ratio is not higher than this
threshold threshold.
Value range:0 to 1000
Working WorkMode Optional parameters: OFF

Mode l OFF (inhibited mode): indicates
that the port works in inhibited
mode, that is, the port does not
detect the alarms. All ports work
in such mode by default.
l Default (default mode): indicates
that the system detects and reports
the alarms in default mode. In such
mode, the UE cannot set the alarm
ID of this port or other parameters
related to this port. The system
reports alarms based on its own
fixed setting rather than the user-
defined setting.
Internal
l CUSTOM (customized mode):
planning
indicates that the UE can change
the binding relation, that is, the
system reports the alarm and set
the alarm Bool based on the
customer specified ID.
Alarm ID AlarmId This parameter is valid only when -

WorkMode is set to CUSTOM.
Alarm ALarmVolta This parameter is valid only when -

voltage ge WorkMode is set to CUSTOM.
l HIGH (alarms related to high
impedance)
l LOW (alarms related to low
impedance)


Data

type parameters:
l RING (ring topology)

number
number
Internal
planning
ring topology.
topology.



Data

resume the data.
affected.
in separate status.


Data

resume the data.
can be affected.
points overlap.


Data
modules.
Network
modules.
configure six RF
modules.


RHUB.

l Block
l Unblock

the RRU ring)
l BRANCH (under the
RHUB node)


Data
Initial RTWPofCarrier Set the initial correction 0

correction Carrier value for the RTWP of the
value for numberonRxRX carrier and TX channel
the RTWP channel number specified by the RRU. Value
range:
(MRRU/WRFU), 0 to 1
(PRRU)
l RX channel number: 0
through 1
the RTWP: -130 to +130,
unit: 0.1 dB

l BOTTOM: Offset to
minimum value (The
interference signal
receive frequency.)
l MIDDLE: Offset to
(no interference)
the current receive
frequency.)

+1000


Data


RRU

Data


RHUB.

l Block
l Unblock

the RRU ring)
l BRANCH (under the
RHUB node)

+1000


Data


RRU
ALD Data
Table 2-13 Negotiation and planned data of the ALD

Data
Antenna AntennaNo In the 2G extended scenario, this N0A Network

connector parameter is unavailable. planning
number When dual-polarized RET is
configured and the value is NOA;
when single-polarized RET or STMA
is configured, the value is NOA or
NOB.
Device DeviceName Name of the ALD. The maximum RET 1 Internal

Name length is a string of 31 characters. planning


Data
Scenario UseCase Scenario of the antenna Optional REGULA

parameters: R
l REGULAR: Regular installation,
that is, only one dual polarization
RET can be installed to an
ANT_Tx/RxA port, and this RET
is controlled through this port.
l SECTOR_SPLITTING: Sector
splitting, that is, a maximum of six
RETs can be installed to an
ANT_Tx/RxA port through a
splitter, and these RETs are
controlled through this port.
l DAISY_CHAIN: Antenna
cascading, that is, a maximum of
six RETs installed to different
ports can be cascaded to an
ANT_Tx/RxA port through
control signal cables, and these
RETs are controlled through this Network
port. planning
l 2G_EXTENSION: 2G extension.
The 2G RET is controlled through
the NodeB. It is an extended mode
of cascaded NodeBs.
Antenna RETType When the device type is either DUAL

polarizatio SINGLE_RET or MULTI_RET
n type supported by the AISG protocol, this
parameter is valid. Optional
parameters:
l In the scenario of antenna
cascaded application, the
parameter value can be set to either
DUAL (dual polarization antenna)
or SINGLE (single polarization
antenna).
l In other scenarios other than
antenna cascading, the value of
this parameter can only be DUAL.
Vendor VendorCode Vendor code of the ALD. The length -

code is a 2-byte letter or number.
Internal
For details about the relation between planning
the vendor code and vendor name of
the ALD, refer to the AISG protocol.


Data
Equipmen SerialNo Serial number of the ALD. The -

t serial maximum length is a 17-byte letter or
number number.
Antenna SubUnit Select different subunit numbers 0

subunit according to different antenna device
number types:
l AISG1.1 The subunit number of
STMA can only be 0.
STMA and SASU can be 1 or 2.
l When multiple antennas support 6
subunits, the subunit number
ranges from 1 to 6. When multiple
antennas do not support 6 subunits,
the subunit number ranges from 1
to 2.
l The subunit number for a single
antenna is not displayed, and is 0
by default. Network
Antenna AntTilt Downtilt of the RET antenna 0 planning
tilt angle Value range: -100 through +300
Working BypassMode Optional parameters: NORMA

mode of l NORMAL (normal mode) L
the STMA
l Bypass mode
SASU l GSMGain According to different types of 0

gain l UMTSGa channels, the SASU gain can be
in divided into the following two types:
l GSMGain indicates the SASU
gain in the GSM channel. Value
range: 0 through 255.
l UMTSGain indicates the SASU
gain in the UMTS channel. Value


Data
DC switch DCSwitch DC switch (on the SASU antenna UMTS

on the connector) status When the status is
SASU set to GSM, the DC power load of the
antenna SASU GSM cannot be started.
connector Optional parameters:
l GSM (The GSM feeder supplies
the power)
l UMTS (The UMTS feeder
supplies the power)
l OFF
SASU DCload The DC power load is applied to the 20

GSM DC TMA that simulates the GSM system.
power load The SASU needs to inform the GSM
that a TMA is connected to the BTS
antenna when the UE sets a relatively
high gain for the GSM Rx channel
through the WCDMA NodeB. The
easiest method is that you add a DC
load to the GSM BTS. In this
situation, the GSM BTS is informed
of the TMA connected to the antenna
by checking the DC power of the
antenna.
STMA Gain Value range: 0 through 255 0

gain
Data of the Iub Transmission Sharing Function
Table 2-14 Data of the Iub transmission sharing function

Input Data Field Description Source
Name
Source logical SrcCellId Value range: 0

cell ID through 65535
Source FACH SrcFachId Value range: 0

ID through 255
Network planning
Destination DestCellId Value range: 0
logical cell ID through 65535
Destination DestFachId Value range: 0

FACH ID through 255

2.3 NodeB Transport Layer Data

This describes the data to be prepared for configuring the NodeB transport layer in the ATM
and the IP mode.
Transport Layer Data (over ATM)
Table 2-15 Negotiation and planned data of the IMA group and IMA links
Data
Slot No. SlotNo Number of slot where the NDTI or 14

NUTI is held (Slots 14 and 15 hold
only the NUTI)
Sub-board SubBdType Type of the sub-board where the E1/ Channelle

type T1 port used by the IMA link is d
located Optional parameters: CoverBoa
l Baseboard rd
l E1 CoverBoard: E1 coverboard
l Channelled CoverBoard:
channelized optical sub-board
IMA group IMAId l When SubBdType is BaseBoard, 0

ID the value range is 0 through 3.
l When SubBdType is E1 Internal
CoverBoard, the value range is 0 planning
through 3.
l When SubBdType is Channelled
CoverBoard, the value range is 0
through 1.
Transmit IMATxFram Longer transmit frame can enhance D128

frame eLength transmission efficiency but reduces
length error sensitivity. Therefore, the
default value is recommended.
l D32
l D64
l D128
l D256


Data
Minimum IMAMinAct Threshold for identifying the 1

active links iveLinks availability of the IMA group For
example, if the value is 3, there are at
least three active IMA links in an
IMA group and thus this group is
available. If there are less than three
active links, the IMA group is
unavailable.
l When SubBdType is BaseBoard,
the value range is 1 through 8.
l When SubBdType is E1
through 8.
through 32.
Differentia IMADiffMa Different transmission links in an 25

l maximum xDelay IMA group may result in different
delay transmission delays. Thus, there is a
change in the relative delay between
links, which is called link differential
delay. The LODS alarms are reported
when the link differential delay
occurs.
Scramble ScrambleMo Optional parameters: ENABLE

mode de l DISABLE (unavailable, the
scramble mode is disabled)
l ENABLE (The scramble mode
must be enabled if the E1/T1
transmission uses AMI line
codes.)
Timeslot TimeSlot16 The channelized optical sub-board DISABLE

16 support does not support this function.
l ENABLE
l DISABLE
After this parameter is enabled, the
bandwidth of each IMA link in the
IMA group is added by 64 kbit/s.


Data
Link LinkNo Number of the E1/T1 ports for the 0, 1, 2 Negotiati

number links in an IMA group. on with
l When SubBdType is BaseBoard, the
the value range is 0 through 7. destinati
on
through 7.
through 62.
HSDPA HsdpaSwitc Optional parameters: AUTO_A

switch h l SIMPLE_FLOW_CTRL: Based DJUST_F
on the configured Iub bandwidth LOW_CT
and the bandwidth occupied by RL
account.
is recommended that the RNC be Internal
used in compliance with the R6 planning
protocol.



Data

Table 2-16 Negotiation and planned data of the UNI links

Data
Slot No. SlotNo Number of slot where the NDTI 12

or NUTI is held (Slots 14 and 15
hold only the NUTI)
Sub-board SubBdType Type of the sub-board where the BaseBoard

type E1/T1 port is located by the UNI Internal
link Optional parameters: planning
l Baseboard
l E1 CoverBoard: E1
coverboard
Link LinkNo Number of the E1/T1 ports for 3 Negotiation

number UNI links with the
l When SubBdType is destination
BaseBoard, the value range is
0 through 7.
CoverBoard, the value range is
0 through 7.
l When SubBdType is
Channelled CoverBoard, the
value range is 0 through 62.

Internal
l ENABLE (The scramble mode planning
codes.)


Data
Timeslot TimeSlot16 The channelized optical sub- DISABLE

16 support board does not support this
function. Optional parameters:
l ENABLE
l DISABLE
After this parameter is enabled,
the bandwidth of the UNI link is
added by 64 kbit/s.
HSDPA HsdpaSwitc Optional parameters: AUTO_AD

switch h l SIMPLE_FLOW_CTRL: JUST_FLO
Based on the configured Iub W_CTRL
bandwidth and the bandwidth
occupied by R99 users, traffic
is allocated to HSDPA users
when the physical bandwidth
restriction is taken into
account.
l AUTO_ADJUST_FLOW_CT
RL: According to the flow
control of
SIMPLE_FLOW_CTRL,
traffic is allocated to HSDPA
users when the delay and
packet loss on the Iub interface
are taken into account. The
RNC uses the R6 switch to
perform this function. It is
recommended that the RNC be
protocol.
l NO_FLOW_CTRL: The
NodeB does not allocate
bandwidth according to the
configuration or delay on the
Iub interface. The RNC
allocates the bandwidth
according to the bandwidth on
the Uu interface reported by
the NodeB. To perform this
function, the reverse flow
control switch must be enabled
by the RNC.

threshold this threshold, you can infer that
the link is not congested.


Data
Discard HsdpaDR The link is not congested when 1

rate frame loss ratio is not higher than
threshold this threshold.
Table 2-17 Negotiation and planned data of the fractional ATM links
Data

only the NUTI)
Value range: 12 through 15 Internal
planning
Sub-board SubBdType Type of the sub-board with the E1/ BaseBoar
type T1 port available for the fractional d
ATM link Optional parameters:
Baseboard
Port No. E1T1No Number of the E1/T1 port available 0 Negotiatio

for the fractional ATM link n with the
Value range: 0 through 1 destinatio
n
Link LinkNo Value range: 0 through 7 1 Internal

number planning
Timeslots TSBitMap The fractional ATM link provides TS24 to

timeslots for the 3G equipment. If TS31 Negotiatio
port 0 is configured, the timeslots n with the
must be reserved for timeslot cross destinatio
connection. n
Value range: TS1 to TS31

Internal
l ENABLE (The scramble mode planning
codes.)


Data

switch l SIMPLE_FLOW_CTRL: Based DJUST_F
bandwidth restriction is taken
into account.
l AUTO_ADJUST_FLOW_CTR
L: According to the flow control
of SIMPLE_FLOW_CTRL,
users when the delay and packet
loss on the Iub interface are taken
into account. The RNC uses the
R6 switch to perform this
function. It is recommended that
the RNC be used in compliance
with the R6 protocol.
the Uu interface reported by the
NodeB. To perform this
function, the reverse flow control
switch must be enabled by the
RNC.



Table 2-18 Negotiation and planned data of the timeslot cross links
Data Name
Source slot SlotNo Number of the slot that holds 13

No. the NDTI or NUTI
Source PortNo Number of the source E1/T1 3

port No. ports for timeslot cross links
Source TSBitMap Value range: TS1 to TS31 TS16 to TS23

timeslots
Internal
Destinatio DestSlotN Number of the slot that holds 13 planning
n slot No. o the NDTI or NUTI (The
number must be identical
with that of the SlotNo)
Destinatio DestPortN Number of the destination 0

n port No. o E1/T1 ports for timeslot
cross links
Value range: 0
Table 2-19 Negotiation and planned data of the SDT CES

Data Name
Port type Type Type of the interface that carries the FRAATM
SDT CES channels Optional
parameters:
l FRAATM
l IMA
l UNI
l STM1 Internal
planning
Source slot PortNo Number of the slot that holds the NDTI 12
No. Value range: 12 through 13
Source SubBdTyp Type of the sub-board where the BaseBoar

sub-board e source E1/T1 port is located by the d
type SDT CES channel Optional
parameters: Baseboard


Data Name
Source port PortNo Number of the source E1/T1 ports for 0

No. the SDT CES channel
Partial fill PFL ATM cell has 48-byte payloads. 47

level Except for the first byte, the other 47
bytes can be used to transmit timeslot
signals. Each timeslot occupies one
byte. The number of filling bytes is
that of valid bytes filled in each ATM
cell.
Value range: 4 through 47, and the
value should be greater than the
number of selected timeslots except
for slot 0.
Timeslots TSBitMap Timeslot 0 is unavailable. TS1 to

Value range: TS1 to TS31 TS7
Destinatio SlotNo Number of slot where the NDTI or 13

n slot No. NUTI is held (Slots 14 and 15 hold
only the NUTI)
Destinatio SubBdTyp Type of the sub-board where the BaseBoar

n sub- e destination E1/T1 port is located by d
board type the SDT CES channel Optional
parameters:
l Baseboard
l Unchannelled CoverBoard:
unchannelized optical sub-board


Data Name
Destinatio E1T1No Number of the destination E1/T1 port 0

n port No. for the SDT CES channel (This
parameter is valid only when Type is
set to FRAATM or UNI).
l When Type is set to FRAATM and
SubBdType(destination sub-board
type) is BaseBoard, the value range
is 0 through 7.
l When Type is set to UNI and
type) is BaseBoard or E1
through 7.
type) is Channelled CoverBoard,
Link No./ LinkNo/ Number of the fractional ATM or UNI 0

IMA ID IMAId link, of the IMA group, or of the STM1
optical port that carries the SDT CES
channel.
is 0 through 7.
through 7.
l When Type is set to IMA and
through 3.
l When Type is STM1, the value
range is 0 through 1.


Data Name
Virtual VPI Identifier of the virtual channel for the 1

channel SDT CES channel.
identifier Value range: 0 through 31 (six
successive values from 0 to 31)
Virtual VCI Identifier of the virtual channel for the 32

identifier l When the interface board is the
NDTI, the value range is 32 through
255.
l When the interface board is the
NUTI, the value range is 32 through
127.
Table 2-20 Negotiation and planned data of the UDT CES

Data Name
Port type Type Type of the interface that carries the IMA
UDT CES channel Optional
parameters:
l IMA
l STM1
No. Value range: 12 through 13 Internal
planning
type UDT CES channel Optional

No. the UDT CES channel


Data Name
Partial fill PFL The value of the partial fill level 47

level affects both the transmission
bandwidth and the transmission delay.
When the value reaches the maximum
of 47, the transmission bandwidth is
not affected, and the transmission
delay reaches the maximum value;
when the value is smaller than 47, the
transmission bandwidth equals to the
original transmission bandwidth x (53/
PFL), and the transmission delay is
reduced. In order not to affect the
transmission bandwidth, set the
default value to 47.
Tx Clock TxClockM Optional parameters: ACM

Mode ode l NOACM (non-adaptive clock
mode)
l NOACM (adaptive clock mode)

only the NUTI)
Destinatio SubBdTyp Type of the sub-board where the Channelle

board type the UDT CES channel Optional CoverBoa
parameters: rd
l Baseboard


Data Name
Optical LinkNo/ Number of the IMA group or STM1 0

port No./ IMAId optical port that carries the UDT CES
IMA ID channel.
through 3.

channel UDT CES channel.

255.
127.
Table 2-21 Negotiation and planned data of the transmission resource group (over ATM)
Data Name e
transmission resource group Optional
parameters:
l FRAATM
l IMA
Internal
l UNI planning
l STM1
Resource RscgrpNo Value range: 0 through 3 1

group
number


Data Name e
Transmit TxBandwidt The transmit bandwidth of the resource 5000

bandwidth h group cannot exceed the bandwidth of
the port to which the resource group
belong.
Receive RxBandwid Receive bandwidth of the resource 5000

bandwidth th group.
Table 2-22 Negotiation and planned data of the SAAL links

Data Name e
SAAL links Optional parameters:
l FRAATM
l IMA
l UNI
l STM1

channel SAAL links. Negotiati
identifier on with
Value range:
the
l Macro NodeB: 0 through 31 (six destinatio
successive values from 0 to 31) n
l Distributed NodeB: 0 through 29

channel SAAL links.
identifier Value range:
l Macro NodeB: 32 through 255
(NDTI) or 32 through 127 (NUTI)


Data Name e
Service ServiceTyp When this parameter is set to CBR or RTVBR

type e UBR, you need to set only the
parameter PCR; when this parameter
is set to RTVBR or NRTVBR, you
need to set parameters SCR and PCR;
when this parameter is set to UBR+,
you need to set parameters PCR and
MCR.
l CBR (applicable to the CES
channel)
l RTVBR (applicable to services
carried on the AAL2 path)
l NRTVBR (applicable to services
l UBR+ (unspecified bit rate,
provides cell rate guarantee)
l UBR (unspecified bit rate)
Peak cell PCR Peak cell rate of the ATM channel 200
rate When the service type is RTVBR,
NRTVBR or UBR+, the value of this
parameter should be greater than that
of the SCR or MCR.
l When the service type is CBR or
UBR, the value range is 30 to 6760.
l When the service type is RTVBR,
NRTVBR or UBR+, the value range
is 31 to 6760.
Minimum MCR The value of the MCR of the ATM -

cell rate channel should be smaller than that of
the PCR. This parameter is valid only
when the service type is UBR+.
Sustainable SCR The value of the SCR of the ATM 180

when the service type is RTVBR or
NRTVBR


Data Name e
Join the JoinRscgrp Specify whether this link should be ENABL

resource added to the resource group. Optional E
group parameters:
l DISABLE
Internal
l ENABLE planning
Resource RscgrpNo Number of the ATM transmission 1
group resource group
number Value range: 0 through 3
Table 2-23 Negotiation and planned data of the NBAP

Input Data Field Description Exampl Source
Name e
Port type PortType Optional parameters: NCP

Internal
l NCP
planning
l CCP
SAAL SAALNo SAAL number that carries the 1 Negotiati

number NCP on with
Value range: 0 through 63 the
NCP destinati
on
Flag Flag Master/slave flag for the MASTE

transmission channels Optional R
parameters: Internal
planning
l SLAVE
l MASTER
Port type PortType Optional parameters: CCP

Internal
l NCP
planning
l CCP
Port No. PortNo Number of the CCP port. This 0

parameter is valid only when
CCP Negotiati
PortType is set to CCP.
on with
SAAL SAALNo SAAL number that carries the 2 destinati
number CCP on


Name e

planning
l SLAVE
l MASTER
Table 2-24 Negotiation and planned data of the ALCAP

Data Name
Node type NodeType The exchange node must be configured LOCAL

before configuring the adjacent node.
The exchange node cannot be carried on
the SAAL link on the NDTI. Optional
parameters:
l LOCAL (peer node)
l HUB (switch node, indicating that
the NodeB has a lower-level NodeB)
l ADJNODE (adjacent node,
indicating the lower-level NodeB)
Adjacent ANI Identify an adjacent node. This -

node parameter is valid only when the
identifier parameter NodeType is set to Internal
ADJNODE. planning
Network NSAP The full name is: Net service access H'390101
service point. 01010101
access When the NodeB uses ATM 01010101
point transmission, the NSAP is the address 01010101
of the NodeB that is connected to the 01010101
AAL2 path. The address is a 01
hexadecimal with a length of 20 bytes
(excluding the prefix H').
SAAL SAALNo SAAL number that carries the ALCAP 3


Table 2-25 Negotiation and planned data of the AAL2 PATH

Data Name
AAL2 PATH Optional parameters:
l FRAATM
l IMA
l UNI
l STM1
PATH type PathType Type of the AAL2 path, which RT

indicates the desired service type
carried on the path. Optional
parameters: RT, NRT, HSPA_RT,
HSPA_NRT

channel AAL2 path.
l Macro NodeB: 0 through 31 (six
Negotiat
ion with
l Distributed NodeB: 0 through 29 the
destinati
Virtual VCI Identifier of the virtual channel for the 37 on
channel AAL2 path.
Service ServiceTyp Optional parameters: RTVBR

type e l CBR (applicable to the CES
channel)


Data Name
parameter should be greater than that of
the SCR. This parameter should be one
of the bandwidth parameters for the
transmission direction.
l When the sub-board type is
BaseBoard, and the service type is
CBR or UBR, the value range is 30
through 15800.
Channelled CoverBoard or
Unchannelled CoverBoard, and the
service type is RTVBR,
NRTVBR,or UBR+, the value range
is 31 through 15800.
Sustainabl SCR The value of the SCR of the ATM 960

e cell rate channel should be smaller than that of
NRTVBRThis parameter should be
one of the bandwidth parameters for the
l When sub-board type is BaseBoard,
Unchannelled CoverBoard, the
Received RCR This parameter must be consistent with 2048

cell rate the downlink bandwidth configured by
the RNC. This parameter acts as an
important factor in flow control by the
NodeB receive bandwidth. Whether or
not this parameter is correctly
configured will affect the effect of flow
control.
Join the JoinRscgrp Specify whether AAL2 path should be ENABLE

resource added to the resource group. Optional
group parameters: Internal
planning
l DISABLE
l ENABLE


Data Name

Table 2-26 Negotiation and planned data of the OMCH (ATM)

Input Data Field Description Example Source
Name
Port type Type Type of the interface that carries the UNI
OMCH Optional parameters:
l FRAATM
l IMA
l UNI
l STM1
Virtual VPI Virtual channel for the OMCH 1

channel Value range:
identifier
l Macro NodeB: 1 or within the VPI
range of the actual board
configuration
Negotiati
Virtual VCI Virtual channel for the OMCH 33 on with
channel the
Value range: destinati
identifier
l Macro NodeB: 32 through 255 on
Service type ServiceTy Optional parameters: CBR

pe l CBR (applicable to the CES
channel)


Name
the SCR.
is 31 to 6760.
Sustainable SCR The value of the SCR of the ATM -

NRTVBR
Local IP LocalIP IP address for NodeB remote 10.1.2.10

address of maintenance
the OMCH
Destination DestIP Destination IP address for NodeB 10.1.2.1

IP address remote maintenance, that is, the IP
of the address configured on the ATM
OMCH interface board at the RNC.
Destination DestIPMas Subnet mask of the destination IP 255.255.

subnet mask k address for NodeB remote maintenance 255.0
of the
OMCH

group parameters:
l DISABLE
l ENABLE
Resource RscgrpNo Number of the ATM transmission 2 Internal

group resource group planning
Flag Flag Master/slave flag for the remote OM MASTE

channels Optional parameters: R
l SLAVE
l MASTER

Table 2-27 Negotiation and planned data of the treelink PVC

Input Field Name Description Exampl Source
Data e
Source port SourceType Type of the interface that carries the FRAAT
type source port of the treelink PVC M
l FRAATM
l IMA
l UNI
l STM1
Destinatio DestinationT Type of the interface that carries the UNI

n port type ype destination port of the treelink PVC
l FRAATM
l IMA
l UNI Internal
planning
l STM1
ByPassMo ByPassMode When the NodeB is powered off or DISABL

de exceptions occur to the NodeB, the E
E1/T1 can be connected to the lower
node by switching to the
ByPassMode. The treelink PVC is set
using the ByPassMode that thus
guarantees the connection between
the lower node and the RNC. Optional
parameters:
l DISABLE (disable the
ByPassMode)
l ENABLE (enable the
ByPassMode)
Source VPI SourVPI Virtual channel used by the upper 1

level network link
l For the VP switching, the source
port VPI must be beyond the VPI
configured to the board, and the
value cannot be 1. Negotiati
on with
l For the VC switching, the source the
port VPI must be within the VPI destinatio
configured to the board, and the n
value can be 1.
l For the VC switching, the SourVPI
and the DestVPI must meet the
conditions of the source board and
the destination board respectively.


Data e
Source SourVCI Identifier of the virtual channel for the 33

VCI upper-level links. This parameter is
valid for VC switching.
l For the macro NodeB, the value
range is 32 through 255 (NDTI) or
32 through 127 (NUTI)
l For the distributed NodeB, the
value range is 32 through 127
Destinatio DestVPI Virtual channel used by the lower- 1

n VPI level network link
l For the VP switching, the
destination port VPI must be
beyond the VPI configured to the
board, and the value cannot be 1.
l For the VC switching, the
destination port VPI must be within
the VPI configured to the board,
and the value can be 1.
Destinatio DestVCI Identifier of the virtual channel for the 32

n VCI lower-level links. This parameter is
Service ServiceType Optional parameters: RTVBR

type l RTVBR
l NRTVBR


Data e
of the SCR.
l When the service type is UBR, the
value range is 30 to 6760.
NRTVBR or UBR+, the value
range is 31 to 6760.

NRTVBR
Transport Layer Data (over IP)
Table 2-28 Negotiation and planned data of the ppp links

Data
Slot No. SlotNo Number of the slot that holds the 13

NUTI
Port No. PortNo Number of the E1/T1 ports for PPP 0

links
Link LinkNo Each PPP link and each MLPPP link 0

Internal
number must have a unique number.
planning
Authentica AuthType Optional parameters: NONAU

tion type l NONAUTH (without TH
authentication)
l PAP (with PAP authentication)
l CHAP (with CHAP
authentication)


Data
User name UserName When AuthType is not set to -

NONAUTH, this field is mandatory,
otherwise, the authentication fails.
Value range: not greater than 64
characters
Timeslot TSBitMap A map of the timeslots for PPP links. TS1 to

map The map is presented in binary TS15
format or the chart. If a timeslot is
selected, it is in use. Otherwise, it is
not in use.
Local IP LocalIP Local IP address of the PPP link. 17.17.17.

address When the value is 0.0.0.0, it indicates 111
that the parameter needs to be Negotiati
negotiated with the RNC. on with
the
Destinatio PeerIP Destination IP address of the PPP 17.17.17. destinatio
n IP link 17 n
address l In cascading mode, this parameter
specifies the IP address of a lower-
level cascaded node.
l In non-cascading mode, when the
value is 0, it indicates that the
parameter needs to be negotiated
with an upper-level node.
IP header IPHC Optional parameters: ENABLE

compressi l DISABLE: The IP header of the
on peer end is not compressed.
l ENABLE: The UDP/IP header of
the peer end is compressed.
PPP PPPMux Optional parameters: DISABL

multiframe l ENABLE E
multiplexi
ng l DISABLE Internal
planning
Maximum MRU Expected value sent from the peer 1500
received end
unit Value range: 128 through 1500
Restart RestartTimer Value range: 1 through 65535 3000

timer of
packet
request
response


Data
Protocol PFC Optional parameters: ENABLE

field l ENABLE
compress
l DISABLE
Address & ACFC Optional parameters: ENABLE

control l ENABLE
field
compress l DISABLE

account.
protocol.



Table 2-29 Negotiation and planned data of the MLPPP group and MLPPP links
Data e

NUTI
MLPPP GroupNo MLPPP group number 0

group Value range: 0 through 3
number

tion type l NONAUTH (without TH Internal
authentication) planning
l CHAP (with CHAP authentication)

characters
Local IP LocalIP Local IP address of the MLPPP group 16.16.16.

address 111
Negotiati
Local LocalMask Subnet mask of the local IP address for 255.255.
on with
subnet the MLPPP group 255.0
the
mask
destinati
Destinatio PeerIP Peer IP address of the MLPPP group 16.16.16. on
n IP 16
address
Port No. PortNo Number of the E1/T1 ports for 0

MLPPP links
Link LinkNo Number of the MLPPP link that joins 1 Internal

number the MLPPP group. Each MLPPP and planning
each PPP link must have a unique
number.
Timeslot TSBitMap A map of the timeslots for MLPPP TS24 to Negotiati

map links. The map is presented in binary TS31 on with
format or the chart. If a timeslot is the
selected, it is in use. Otherwise, it is destinati
not in use. on


Data e
IP header IPHC Optional parameters: ENABL

compressi l DISABLE: The IP header of the E

multiplexi
ng l DISABLE
Multi-class MCPPP Optional parameters: ENABL

PPP l ENABLE (using the MCPPP) E
l DISABLE (not using the MCPPP)
Maximum MRU Expected value sent from the peer end 1500 Internal
received Value range: 128 through 1500 planning
unit

timer of
packet
request
response
Protocol PFC Optional parameters: ENABL

field l ENABLE E
compress
l DISABLE
Address & ACFC Optional parameters: ENABL

control l ENABLE E
field
compress l DISABLE


Data e
HSDPA HsdpaSwitch Optional parameters: AUTO_

switch l SIMPLE_FLOW_CTRL: Based on ADJUST
the configured Iub bandwidth and _FLOW
the bandwidth occupied by R99 _CTRL
SIMPLE_FLOW_CTRL, traffic is
allocated to HSDPA users when the
delay and packet loss on the Iub
interface are taken into account.
The RNC uses the R6 switch to
recommended that the RNC be used
in compliance with the R6 protocol.
Time delay HsdpaTD When the time delay is lower than this 4
threshold threshold, you can infer that the link is
not congested.

Table 2-30 Negotiation and planned data of the PPPoE links

Data Name e
Slot No. SlotNo Number of the slot that holds the NUTI 13 Internal
Value range: 12 through 15 planning


Data Name e
Port No. PortNo Number of the FE port for the PPPoE 0

link

tion type l NONAUTH (without authentication) TH

User name UserName This parameter is valid only when -

AuthType is set to PAP or CHAP.
characters
Local IP LocalIP Local IP address of the PPPoE link 12.3.0.1 Negotiati

address on with
Local LocalMask Subnet mask of the local IP address 255.255. the
subnet 255.0 destinati
mask on

compressio l DISABLE: The IP header of the peer E
n end is not compressed.
l ENABLE: The UDP/IP header of the
peer end is compressed.
Maximum MRU Expected value sent from the peer end 1450
received Value range: 128 through 1500
unit
Internal
Restart RestartTim Value range: 1 through 65535 3000 planning
timer of er
packet
request
response

multiplexi
ng l DISABLE


Data Name e
HSDPA HsdpaSwit Optional parameters: AUTO_

switch ch l SIMPLE_FLOW_CTRL: Based on ADJUST
the configured Iub bandwidth and the _FLOW_
bandwidth occupied by R99 users, CTRL
traffic is allocated to HSDPA users
interface are taken into account. The
the R6 protocol.
this function, the reverse flow control
switch must be enabled by the RNC.
not congested.

Table 2-31 Negotiation and planned data of the DEVIP

Data Name e
Slot No. SlotNo Number of the slot that holds the NUTI 13 Internal


Data Name e
Port No. PortNo l For the PPP link, the MLPPP group, 0
and the PPPoE link, PortNo
represents the port number for the
configured PPP link, the MLPPP
group, and the PPPoE link.
l For the ETH link, the port value
ranges from 0 to 1.
Port type PortType The port types consist of the following ETH
items:
l ETH: indicates the available FE port
on the NUTI.
l MLPPP: indicates the configured
MLPPP group.
l PPP: indicates the configured PPP
link.
l PPPoE: indicates the configured
PPPoE link.
Local IP LocalIP Local IP address of the device IP 12.11.12.

address 12 Negotiati
on with
Subnet LocalMask If the network is not divided into 255.255. the
mask of the subnets, use the default mask. 255.0 destinatio
local IP n
address
Data Name

No. the NUTI
Source PortNo Number of the source E1/T1 2 Internal

port No. ports for timeslot cross links planning

timeslots


Data Name
Destinatio DestSlotN Number of the slot that holds 13

n slot No. o the NUTI (The number must
be identical with that of the
SlotNo)

cross links
Value range: 0
Table 2-33 Negotiation and planned data of the IP route

Data e
Port type ItfType Interface type of the route Optional ETH

parameters:
l ETH
l MLPPP
l PPP
l PPPoE
Destinatio DestNet This parameter must meet all the 17.18.17.

n network following requirements: Valid 0
network address, except the default
route 0.0.0.0 IP AND mask must be
equal to the IP address.
Destinatio DestMask This parameter must meet all the 255.255. Network
n mask following requirements: IP AND 255.0 planning
mask must be equal to the IP address.
If the mask is converted into binary
value, 0 is not allowed to precede 1.
Next hop NextHop This parameter is valid only when the 12.11.12.
IP address parameter InsertFlag is set to ETH. 1
This parameter meets the following
requirements:
l Stays on the same network segment
as the LocalIP of the bearer link.
l Has valid IP address of classes A,
B, and C.
l The value cannot be
255.255.255.255.

Table 2-34 Negotiation and planned data of the SCTP links

Name
Port type ItfType Type of the interface that carries the PPP Internal
SCTP links Optional parameters: planning
l ETH
l MLPPP
l PPP
l PPPoE
Local IP LocalIP At the NodeB, the IP address of the 17.17.17.

address primary physical link that carries the 111
SCTP link.
Destination DestIP At the RNC, the IP address of the 14.1.1.4

IP address primary physical link that carries the
SCTP link.
The second SecLocalIP At the NodeB, the IP address of the 0.0.0.0

local IP standby physical link that carries the
address SCTP link.
The IP address 0.0.0.0 indicates that
Negotiatio
this address is not in use.
n with the
The second SecDestIP At the RNC, the IP address of the 0.0.0.0 destinatio
destination standby physical link that carries the n
IP address SCTP link.
Local port LocalPort Local port number of the SCTP 1024

number and Value range: 1024 through 65535
destination
port number
Destination DestPort Destination port number of the SCTP 8021

port number Value range: 1024 through 65535
Automatical IPAutoCha After the fault of the master IP ENABLE Internal

ly switches nge address is rectified, the services can planning
back to the be automatically switched back to
master IP the master IP address. Optional
address parameters:
l ENABLE
l DISABLE

Table 2-35 Negotiation and planned data of the IPCP

Name e
Port type PortType Optional parameters: NCP Internal

l NCP planning
l CCP
SCTP SCTPNo SCTP number that carries the 1 Negotiati

number NCP on with
NCP destinati
on
Flag Flag Master/slave flag for the MASTE Internal

transmission channels Optional R planning
parameters:
l SLAVE
l MASTER
Port type PortType Optional parameters: CCP Internal

l NCP planning
l CCP

PortType is set to CCP. Negotiati
on with
CCP SCTP SCTPNo SCTP number that carries the 2 destinati
number CCP on

parameters:
l SLAVE
l MASTER

Table 2-36 Negotiation and planned data of the transmission resource group (over IP)
Data Name
Port type ItfType Type of the interface that carries the IP ETH
parameters:
l ETH
l MLPPP
l PPP
l PPPoE

group
number
Transmit TxBandwi The transmit bandwidth of the 10000

bandwidth dth resource group cannot exceed the
bandwidth of the port to which the
resource group belong.
l When the port type is ETH, the
value range is 8 through 100000. Internal
planning
l When the port type is MLPPP, the
l When the port type is PPP, the value
l When the port type is PPPoE, the
Receive RxBandwi Receive bandwidth of the resource 10000

bandwidth dth group.

Table 2-37 Negotiation and planned data of the IP PATH

Data
Port type ItfType Type of the interface that carries the ETH Internal
IP PATH Optional parameters: planning
l ETH
l MLPPP
l PPP
l PPPoE
Destinatio DestIP Destination IP address of the IP path 17.18.17. Negotiati

n IP 121 on with
address the
destinatio
n
DSCP DSCP Value range: 0 through 63 60 Network

priority planning
Service TrafficType Optional parameters: RT

type l RT
l NRT
l HSPA_RT
l HSPA_NRT
Receive RxBandwith When PATH joins the resource 1000

bandwidth group, the receive bandwidth does
not exceed the bandwidth of the Negotiati
resource group; when PATH does on with
not join the resource group, the the
receive bandwidth doe not exceed the destinatio
bandwidth of the physical port. n
l When the port type is PPP, the


Data
Transmit TxBandwith When PATH joins the resource 1000

not exceed the bandwidth of the
resource group; when PATH does
not join the resource group, the
receive bandwidth doe not exceed the
bandwidth of the physical port.
Transmit TxCBS Value range: 15000 to 155000000. 500000

committed The recommended value is 1/2 of the
burst size transmit bandwidth.
Unit: bit
Transmit TxEBS Value range: 0 through 155000000 1000000

excessive Unit: bit
burst size
Path check PathCheck Optional parameters: DISABL

l ENABLE: Path check is enabled. E
Internal
l DISABLE: Path check is disabled. planning
Join the JoinRscgrp Specify whether the IP PATH should ENABLE

resource be added to the resource group.
group Optional parameters:
l DISABLE
l ENABLE
Resource RscgrpNo Number of the IP transmission 0


Table 2-38 Negotiation and planned data of the OMCH (IP)

Data Name
Bind the BindRoute Determine whether to bind the route. YES

route Valid Route binding is necessary when the
peer IP address of the OMCH is on
different network segments from the
DestNet in the 6.6.2 Adding an IP
Route (Initial). Optional parameters:
l NO
l YES
Port type ItfType Type of the interface that carries the ETH
bound routes Optional parameters:
l ETH
l MLPPP
l PPP
l PPPoE
Bound IP BindDestIP This parameter is valid only when the 11.11.10. Negotiati
address on parameter BindRouteValid is set to 0 on with
the YES. the
destination destinatio
network n
Bound BindDestIP This parameter is valid only when the 255.255.

destination Mask parameter BindRouteValid is set to 255.0
mask YES.
Bound next NextHop This parameter is valid only when the 12.11.12.
hop IP port type is ETH. 1
address
Local IP LocalIP IP address at the NodeB for the OMCH 11.11.12.

address 12
Local Mask Mask of the IP address at the NodeB 255.255.

subnet for the OMCH 0.0
mask
Destinatio DestIP Destination IP address of the OMCH, 11.11.11.

n IP that is, the IP address of the LMT or the 12
address M2000.
Flag Flag Optional parameters: MASTE

R Internal
planning

Table 2-39 Negotiation and planned data of the transmission resource group whose destination
IP network segment is bound
Data Name
resource group Optional parameters:
l ETH
l MLPPP
l PPP
l PPPoE
Resource RscgrpNo Number of the IP transmission resource 0

group group that corresponds to the physical
number bearer port Internal
Destinatio DestIP Bound destination IP address, that is, 11.11.10.1

n IP the IP address on the same network 0
address segment with BindDestIP in 6.6.7
Adding an OMCH of the NodeB
(Initial, over IP) or the destination IP
address of the SCTP link of 6.6.3
Adding SCTP Links (Initial).
Destinatio IPMask Bound destination mask 255.255.2

n mask 55.255
Table 2-40 Negotiation and planned data of the IP clock links

Data Name
Port type ItfType Type of the interface that carries the IP PPPoE Internal
clock links Optional parameters: planning
l ETH
l MLPPP
l PPP
l PPPoE
IP address ClientIP Obtain the NodeB IP address of the IP 12.3.0.1

at the client clock
Network
IP address ServerIP IP address at the IP clock server 12.3.0.10 planning
at the
server


Data Name
Priority Priority The clock links that has the highest 0

priority is used first. The number is in
a negative relation with the priority
level.
Table 2-41 Negotiation and planned data of the IPQoS

Data Name
Priority rule PriRule Optional parameters: IPPRECE

l IPPRECEDENCE DENCE
l DSCP
Signaling SigPri l In IPPRECEDENCE rule, the value 7

priority range is 0 through 7.
Network
l In DSCP rule, the value range is 0
planning
through 63.
Operation OMPri l In IPPRECEDENCE rule, the value 7

and range is 0 through 7.
Maintenanc l In DSCP rule, the value range is 0
e (OM) through 63.
priority
2.4 NodeB Radio Layer Data

This describes the data to be prepared for configuring the NodeB radio layer.
Site Data

Data
Site name Site Name The site is usually named after Shanghai Network
the geographical location. planning

Sector Data
Table 2-43 Negotiation and planned data of the sector

Input Data Field Name Description Example Source
Number of RxAntennaN The number of RX antennas in 2

RX antennas um a sector is associated with the
parameter DemMode set at
the NodeB equipment layer..
You can define the number of
RX antennas before
configuring antenna channels
for the sectors. You need to,
however, adhere to the
following principles:
l If DemMode is set to four-
way demodulation mode or
four-way economical
demodulation mode, only
one or four RX antennas can
be configured.
l If DemMode is set to two-
way demodulation mode,
only one or two RX
antennas can be configured. Network
planning
Transmit TxDiversity Diversity mode of the sector, TX_DIVE
diversity Mode which can be configured RSITY
mode before the antenna channel is
configured. Optional
parameters:
l NO_TX_DIVERSITY (no
transmit diversity): one
sector uses one TX channel.
l TX_DIVERSITY (transmit
diversity): one sector uses
two TX channels.
l HALFFREQ (0.5/0.5
frequency mode, which can
be configured only in
remote sectors)
When the number of
configured RX antennas is
one, the sector can work only
in no transmit diversity mode.

Coverage Cover Type This parameter is required for -

type the remote sector. It is valid
only when the transmit
diversity mode is
HALFFREQ. Optional
parameters:
l SAMEZONE (same
coverage type)
l DIFFZONE (different
coverage type)

Cell Data
Table 2-44 Negotiation and planned data of the cell

Uplink UARFCNUp The UL and DL frequencies of 9612

frequency Link a cell must be at the same
frequency band.
Frequency (MHz) =
(Frequency / 5) + offset
l Band 1
Common frequencies: 9612
through 9888 inclusive.
Offset:0
Special frequencies: None.
Offset: 0
l Band 2
Offset: 0
Special frequencies: {12,
37, 62, 87, 112, 137, 162,
187, 212, 237, 262, 287}.
Offset:1850.1
l Band 3 Network
Common frequencies: 937 planning
Offset:1525
Offset:0
l Band 4
Offset:1450
1687, 1712, 1737, 1762,
1787, 1812, 1837, 1862}.
Offset:1380.1
l Band 5
Offset:0
787, 807, 812, 837, 862}.
Offset:670.1
l Band 6


Offset:0
Special frequencies:
{812,837}. Offset:670.1
l Band 7
Offset:2100
2387, 2412, 2437, 2462,
2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662,
2687}. Offset:2030.1
l Band 8
Offset:340
Offset:0
l Band 9
Offset:0
Offset:0

Downlink UARFCNDo The UL and DL frequencies of 10562

frequency wnLink a cell must be at the same
frequency band.
Frequency (MHz) =
l Band 1
Common frequencies:
10562 through 10838
inclusive. Offset:0
Offset:0
l Band 2
Offset:0
437, 462, 487, 512, 537,
562, 587, 612, 637, 662,
687}. Offset:1850.1
l Band 3
Offset:1575
Offset:0
l Band 4
Offset:1805
1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087}.
Offset:1735.1
l Band 5
Offset:0
1012, 1032, 1037, 1062,
1087}. Offset:670.1
l Band 6
Offset:0
1062}. Offset:670.1

l Band 7
Offset:2175
2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887,
2912}. Offset:2105.1
l Band 8
Offset:340
Offset:0
l Band 9
Offset:0
Offset:0
Uplink ULResource The cells within an uplink 0

resource GroupId resource group share the
group ID uplink resources. One UL
resource group has a
maximum of six cells. If the
UL resource group has high-
speed movement cells, it
supports a maximum of three
cells.
Downlink DLResource When adding local cells, you 0

resource GroupId need to select the downlink
group ID resource group. One local cell
is only carried on a board of its
downlink resource group.
Baseband BbPoolType Optional parameters: GEN_POO

resource pool GEN_POOL: general resource L
type pool, which consists of the
boards located at slot 0 through
slot 9.

Maximum MaxTxPower The maximum transmit power 430

transmit of a local or remote cell refers
power to that on the TOC. The
transmit power must be within
the range that is supported by
the power amplifier lest the
cell is unavailable.
l When the sector works in
NO_TX_DIVERSITY
mode, the maximum
transmit power range of the
cell is:
[TOC maximum output
power of the power
amplifier - 10 dB, TOC
maximum output power of
the power amplifier]
transmit diversity mode or
0.5/0.5 frequency mode, the
maximum transmit power
range of the cell is:
An intersection of [TOC1
maximum output power - 7
dB, TOC1 maximum output
power + 3 dB] and [TOC2
maximum output power -
7dB, TOC2 maximum
output power + 3 dB].
Cell radius CellRadius The coverage is affected by the 29000

cell radius, which is
recommended to be set as
designed according to the
network planning.
Value range: 150 through
180000
Inner CellInnerHan The inner handover radius of 0

handover doverRadidus the cell should not be greater
radius than the cell radius. It is
network planning.

Desensitizati Desensy This parameter needs to be set 0

on intensity only in cells of local and
remote sectors. It is the ratio of
uplink noise intensity to
background noise of the
receiver. This value is not used
when the sector is a distributed
one. The data is determined in
the network planning, and it is
consistent with that at the
RNC.
High-speed Hispm The data is determined in the FALSE

movement network planning, and it is
mode consistent with that at the
RNC. Optional parameters:
l FALSE (not high speed)
l TRUE (high speed)
Rate in high- Spr This parameter is valid when -

speed the Hispm is set to TRUE. The
movement data is determined in the
mode network planning, and it is
l 250
l 400
l 500
Ratio of the DefPowerLvl Cells in distributed sectors 100

default need the configuration.
transmit Value range: 10 through 100
power to the
RRU

NodeB
NodeB Initial Configuration Guide 3 NodeB Initial Configuration
3 NodeB Initial Configuration
This describes how to add a NodeB on the CME.
Procedure
Step 1 Start the CME applications.
Step 2 Create an RNS.
Step 3 Open the RNS.
Step 4 Add a NodeB.
Option Description
4 Adding a NodeB Through the Template If the configuration type of the NodeB is one
File (Initial) of the typical configuration types defined in
template files, this configuration mode is
preferred.
5 Adding a NodeB Through the If a configuration file that is applicable to the

Configuration File (Initial) NodeB is available, this configuration mode
is preferred.
6 Manually Adding a NodeB (Initial) Manually reconfigure the data after the
template file or the configuration file is
imported. If you are familiar with the RAN
configuration, this configuration mode is
preferred.
----End

NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)
4 Adding a NodeB Through the Template File

(Initial)
About This Chapter
This describes how to configure the NodeB through the template file if the configuration type
of the NodeB is one of the typical configuration types of the template file.
4.1 NodeB Template File

This defines the NodeB template file and describes the scenarios for using the file, the method
of obtaining the file, and the role of the file in the CME.
4.2 Creating a Logical NodeB (Initial)
This describes how to create a logical NodeB. The RNC uses the logical NodeB to identify the
NodeB.
4.3 Creating a Physical NodeB by Importing the Template File (Initial)
This describes how to create a physical NodeB by importing a NodeB template file. The physical
NodeB corresponds to an actual NodeB.
4.4 Reconfiguring NodeB Data (Initial)
This describes how to reconfigure the equipment layer data, the transport layer data, and the
radio layer data of the physical NodeB based on the negotiated and planned data after you create
the physical NodeB by importing the template file or configuration file.
4.5 Refreshing the Transport Layer Data of the NodeB (Initial)
This describes how to refresh the transport layer data of the NodeB. The CME can simultaneously
update the Iub data at the RNC and the NodeB sides. If the Iub interface data is configured at
the RNC side, the data at the NodeB side is updated at the same time. Thus, the Iub data at both
the RNC and the NodeB sides can be consistent.

NodeB
4 Adding a NodeB Through the Template File (Initial) NodeB Initial Configuration Guide
4.1 NodeB Template File

This defines the NodeB template file and describes the scenarios for using the file, the method
of obtaining the file, and the role of the file in the CME.
Definition
A NodeB template file contains a set of recommended data that is predefined with common
configuration types, demodulation modes, and Iub transmission modes to simplify NodeB data
configuration.
The NodeB template file contains a large number of default parameters.
The NodeB template file is of the following two types:
l Template file provided with the CME software. It cannot be deleted.
l User-defined template file. After configuring the NodeB data, you can save the data
configuration as a template, which serves as a data source for future data configuration.
WARNING
The default NodeB template provided by the CME cannot be modified.
Application Scenario
During NodeB initial configuration on the CME, import a NodeB template file according to the
NodeB type. The NodeB template file facilitates NodeB data configuration.
Obtaining Method
The NodeB template file is provided with the CME software. The file is available at CME
installation directory\WRANCMEV100R005\template\NodeB.
The NodeB template file is named in the form of transport protocol type_demodulation
mode_sector quantity_frequency quantity_transmit diversity mode.xml, for example,
ATM_2-Channels Demodulation_3_1_Transmitter Non_diversity.xml.
You can also name a NodeB template file in your own way.
You can reconfigure a NodeB template file and export it. For details, refer to Exporting a NodeB
Template File.
Role in the CME

The NodeB template file can be a data source for NodeB data configuration on the CME.

NodeB.

NodeB
Scenario NodeB initial configuration

Mandatory/ Mandatory
Optional
Prerequisite
The RSS or the RBS is already configured.
Preparation

Data Name e

location.
l ATM_TRANS
l IP_TRANS
l ATMANDIP_TRANS

Negotiati
on with
the
destinati
corresponding physical NodeB.
on
physical NodeB

index NON_SHARED.

NodeB

Data Name e

l SHARE
l EXCLUSIVE

IP_TRANS. 0101010
address).
prefix H')

parameters:
l SUPPORT
l NOT_SUPPORT


transport

NodeB

Data Name e

n indication l TRUE
l FALSE

l NORMAL
l PICO_TYPE1
l PICO_TYPE2

l R99
l R4
l R5
l R6
Procedure
Step 1 On the main interface of the CME, click , and then click NodeB CM Express in the
configuration task pane. The NodeB CM Express window is displayed.
Step 2 Double-click the editing box on the left. The NodeB Basic Information window is displayed,
as shown in Figure 4-1.

NodeB
Figure 4-1 Physical NodeB Basic Information window
NOTE
The RAN Sharing Flag parameter is described as follows:

l If the RAN Sharing Flag is set to YES, that is, when RAN sharing is supported, parameters
SharingSupport and CnOpIndex are configured according to scenarios. (Parameter CnOpIndex is
valid only when SharingSupport is set to NON_SHARED.
l If the RAN Sharing Flag is set to NO, that is, when RAN sharing is not supported, parameters
SharingSupport and CnOpIndex do not need to be configured.
For details, refer to Adding Basic Data of the RNC (Initial, CME).
Step 3 Select NodeBId, and click to add a NodeB record. According to the prepared data, set the
information such as NodeBName, IubBearer Type, and NSAP.
Step 4 Click to save the settings.

Step 5 Repeat Step 3 through Step 4 to add more NodeB records.
----End
4.3 Creating a Physical NodeB by Importing the Template

File (Initial)
This describes how to create a physical NodeB by importing a NodeB template file. The physical
NodeB corresponds to an actual NodeB.

NodeB
Optional
Prerequisite
l The logical NodeB is configured. For details, refer to 4.2 Creating a Logical NodeB
(Initial).
l The NodeB template file with the same or similar configuration type acts as the data source.
Procedure
Step 2 Click . The Physical NodeB Basic Information window is displayed, as shown in Figure
4-2.
Table 4-2 Description of the configuration pane
Sequence of data Description

configuration
1 Logical NodeB list
2 "Create a physical NodeB" button
3 "Delete a physical NodeB" button

NodeB

configuration
4 Physical NodeB list
Step 3 Select a logical NodeB in area 1, and then click . The Create Physical NodeB dialog
box is displayed, as shown in Figure 4-3.
Figure 4-3 Create Physical NodeB dialog box
Step 4 Select the values in the Series and Version drop-down lists based on the prepared data, and then
select a template similar to the actual NodeB configuration in the Template drop-down list.
Step 5 Click OK. The CME starts importing the template file, and the import progress is displayed in
the NodeB Creating dialog box.
Step 6 After the template file is imported, the Information dialog box is displayed. Click OK, and
information related to the configured physical NodeB is displayed in area 4.
----End


Mandatory/ Optional
Optional
NOTE
After the physical NodeB is created through the template or the configuration file, you need to manually
reconfigure the equipment layer data according to the actual network planning. The reconfiguration
involves physical NodeB basic information, interface board addition or deletion, and RF modules or RRU
addition or deletion.
reconfigure the radio layer data according to the actual network planning. The reconfiguration involves
cell frequencies, uplink/downlink resource groups, and power.

NodeB
Prerequisite
The NodeB is created by importing a template file or a configuration file. For details, refer to
the following information:
l 4.3 Creating a Physical NodeB by Importing the Template File (Initial).
l 5.3 Creating a Physical NodeB by Importing a Configuration File (Initial).
Preparation
l To reconfigure the equipment layer data, refer to Macro NodeB Equipment Layer
Data or Equipment Layer Data of the Distributed NodeB by the NodeB type.
l To reconfigure the transport layer data, refer to 2.3 NodeB Transport Layer Data.
l To reconfigure the radio layer data, refer to 2.4 NodeB Radio Layer Data.
Procedure
l Reconfigure the equipment layer data.
The equipment layer data is reconfigured according to the NodeB type. For details, refer
to:
– 6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial).
– 6.3 Adding Equipment Layer Data of the BTS3812E (Initial).
– 6.4 Adding Equipment Layer Data of the DBS3800 (Initial).
For details, refer to 6.5 Manually Adding the Transport Layer Data of the NodeB (over
ATM) or 6.6 Manually Adding Transport Layer Data of the NodeB (over IP).
l Reconfigure the radio layer data.
For details, refer to 6.8 Adding Radio Layer Data.
----End
4.5 Refreshing the Transport Layer Data of the NodeB

(Initial)
Scenario NodeB initial configuration (The RNC and the NodeB is directly connected
without ATM switch inbetween.)
Mandatory/ Optional. This function is customized. Therefore, it is not applied to all scenarios.
Optional

NodeB
NOTE
l Whether to connect the RNC and the NodeB directly depends on actual scenarios. The Iub refreshing
function does not check whether the RNC and the NodeB are directly connected.
l When data on both the RNC and the NodeB is carried over E1/T1 or optical port in the ATM transport
mode and the RNC is connected to the NodeB through an ATM switch. The Iub refreshing function
determines that the NodeB and the RNC are directly connected. The Iub refreshing function is
supported. The accuracy of refreshed data, however, cannot be guaranteed owing to the ATM switch.
Therefore, use the ATM switch with caution.
l Before the refreshing, consistency check will be executed over the Iub interface. That is, check that the
version of the RNC matches that of the NodeB. If the versions on both the NodeB and the RNC sides
match, the data over the Iub interface on the RNC side can be synchronized to the NodeB side. For the
matching relations, refer to Figure 4-4.
Figure 4-4 Matching relations
Prerequisite
l The Iub interface data at the RNC is configured. For details, refer to Adding Iub Interface
Data to the RNC (Initial, over ATM, CME).
l To execute the refresh function, the physical NodeB is configured. For details, refer to
6.2.1 Manually Creating a Physical NodeB (Initial).
l Ensure that the VPI of the PVC at the RNC side is in the VPI value range defined in the
baseband interface board at the NodeB side.
l If the optical interface board is adopted, ensure that the NUTI is configured with the
corresponding sub-board.
Preparation
l For the macro NodeB, the equipment layer is configured with the NDTI or the NUTI with
bearer type of ATM or IPv4. For details, refer to 6.2.2 Adding the Boards in the Baseband
Subrack (Initial).
l For the distributed NodeB, the equipment layer is configured with the BBU with bearer
type of ATM or IPv4. For details, refer to 6.4.2 Adding a BBU (Initial).

NodeB
Procedure
Step 1 On the main interface of the CME, click in the configuration object pane, and then click
NodeB CM Express in the configuration task pane. The NodeB CM Express window is
displayed.
Step 2 Click . The Physical NodeB Basic Information window is displayed.
Step 3 Select a physical NodeB, and then click . The NodeB Selection window is displayed.
Step 4 Determine the target NodeB to be refreshed.
Option Description
Only one target NodeB can be refreshed Go to Step 5.

at a time.
More than one target NodeB needs to be 1. In the NodeB Selection dialog box, click
refreshed at a time. Filter. The Select NodeB window is
displayed, as shown in Figure 4-5.
2. In area 2, select multiple physical NodeBs,
and click . The physical NodeBs
are added to area 1.
3. Click Close to return to the NodeB
Selection window.

NodeB
Figure 4-5 NodeB Selection window

configuration
1 List of candidate physical NodeBs
2 List of target physical NodeBs
Step 5 Click Next. The PortMatch window is displayed, as shown in Figure 4-6.

NodeB
Figure 4-6 Port Match window
NOTE
l The data in dark blue refers to the data at the RNC side, and that in green refers to the data at the NodeB
side.
l Before the Iub refreshing, the CME automatically allocates the interconnection data such as NCN
(cabinet number), NSBN(subrack number), NSN (slot number), and NPN (port number) at the NodeB
side. You can also reallocate the data as required.
Step 6 (Optional) Select NCN, and click to modify the interconnection data at the NodeB side.
Step 7 Click Next, and the Confirmation dialog box is displayed.Click OK to execute data
synchronization. The Finish dialog box is displayed telling that the data is successfully refreshed.
Step 8 Click Finish to return to the Physical NodeB Basic Information window.
----End

NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (Initial)
5 Adding a NodeB Through the Configuration

File (Initial)
About This Chapter
This describes how to add a NodeB through a configuration file if the configuration file is
applicable to the NodeB.
5.1 NodeB Configuration File

This defines the NodeB configuration file and describes the scenarios for using the file, the
method of obtaining the file, and the role of the file in the CME.
NodeB.
5.3 Creating a Physical NodeB by Importing a Configuration File (Initial)
This describes how to create a physical NodeB by importing a configuration file. The physical
NodeB corresponds to an installed NodeB.

NodeB
5 Adding a NodeB Through the Configuration File (Initial) NodeB Initial Configuration Guide
5.1 NodeB Configuration File

This defines the NodeB configuration file and describes the scenarios for using the file, the
method of obtaining the file, and the role of the file in the CME.
Definition
A NodeB configuration file contains a complete set of NodeB configuration data for proper
operation of the NodeB.
The NodeB configuration file, also called NodeB XML file, is saved in .xml format.
Application Scenario
The NodeB configuration file is used in the following scenarios:
l Export the NodeB configuration file to the NodeB LMT after the RAN configuration is
complete on the CME. Then load the file onto the NodeB and validate the file.
l Before reconfiguring the RAN on the CME, import the NodeB configuration file to the
CME server to synchronize the NodeB data in the CME with that on the existing network.
Obtaining Method
You can obtain the NodeB configuration file by exporting all the NodeB data from the CME or
obtain the file from the NodeB LMT.
Role in the CME

The NodeB configuration file can be loaded to the NodeB. The file can be a data source for
NodeB configuration on the CME.

NodeB.

Optional
Prerequisite

NodeB
Preparation

Data Name e

location.
l ATM_TRANS
l IP_TRANS
l ATMANDIP_TRANS

corresponding physical NodeB. Negotiati
on with
the
destinati
on
physical NodeB

index NON_SHARED.

l SHARE
l EXCLUSIVE

NodeB

Data Name e

IP_TRANS. 0101010
address).
prefix H')

parameters:
l SUPPORT
l NOT_SUPPORT


transport

n indication l TRUE
l FALSE

NodeB

Data Name e

l NORMAL
l PICO_TYPE1
l PICO_TYPE2

l R99
l R4
l R5
l R6
Procedure

NodeB
NOTE


----End
5.3 Creating a Physical NodeB by Importing a Configuration

File (Initial)
This describes how to create a physical NodeB by importing a configuration file. The physical
NodeB corresponds to an installed NodeB.

NodeB
Optional
NOTE
l To import a NodeB configuration file, you have to conform to the following principle: A logical NodeB
is available for each matching NodeB name in the configuration file to be imported. If the logical
NodeB that corresponds to the NodeB name in the importing NodeB configuration is unavailable, the
CME automatically creates a logical NodeB, and then import this NodeB configuration file.
l If the NodeB name in the configuration file is the same as an existing physical NodeB, the imported
configuration data will overwrite the data of the existing physical NodeB.
Prerequisite
l The logical NodeB is configured. For details, refer to 5.2 Creating a Logical NodeB
(Initial).
l The NodeB configuration file of the same or similar configuration type acts as the data
source.
Procedure
displayed.
Step 3 Select a logical NodeB on the left of the window. Click . The Import NodeB window is

NodeB
Figure 5-2 NodeB Data Configuration File
Step 4 In the navigation tree of the left pane, select the save path of the NodeB configuration file, and
then click Search. The valid configuration file is displayed in the upper right pane, and the
invalid configuration file is displayed in the lower right pane.
NOTE
l The invalid configuration file cannot be imported.

l If a valid NodeB configuration file is found, but the corresponding logical NodeB does not exist, a
dialog box is displayed to ask whether to create the logical NodeB. Click OK, and then enter the subrack
number of the NodeB and SPUa subsystem number to create the logical NodeB.
Step 5 Select the valid NodeB configuration file, and then click Import. After the file is imported, the
Information dialog box is displayed. Click OK to return to the Import NodeB window.
Step 6 The imported NodeB is displayed on the right part of the Physical NodeB Basic Information
window.
----End


Mandatory/ Optional
Optional

NodeB
NOTE
reconfigure the equipment layer data according to the actual network planning. The reconfiguration
involves physical NodeB basic information, interface board addition or deletion, and RF modules or RRU
addition or deletion.
reconfigure the radio layer data according to the actual network planning. The reconfiguration involves
cell frequencies, uplink/downlink resource groups, and power.
Prerequisite
The NodeB is created by importing a template file or a configuration file. For details, refer to
the following information:
l 4.3 Creating a Physical NodeB by Importing the Template File (Initial).

l 5.3 Creating a Physical NodeB by Importing a Configuration File (Initial).
Preparation
l To reconfigure the equipment layer data, refer to Macro NodeB Equipment Layer
Data or Equipment Layer Data of the Distributed NodeB by the NodeB type.
l To reconfigure the transport layer data, refer to 2.3 NodeB Transport Layer Data.
l To reconfigure the radio layer data, refer to 2.4 NodeB Radio Layer Data.
Procedure
The equipment layer data is reconfigured according to the NodeB type. For details, refer
to:
– 6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial).
– 6.3 Adding Equipment Layer Data of the BTS3812E (Initial).
– 6.4 Adding Equipment Layer Data of the DBS3800 (Initial).
For details, refer to 6.5 Manually Adding the Transport Layer Data of the NodeB (over
ATM) or 6.6 Manually Adding Transport Layer Data of the NodeB (over IP).
l Reconfigure the radio layer data.
For details, refer to 6.8 Adding Radio Layer Data.
----End

(Initial)

NodeB
Optional
NOTE
Prerequisite
Preparation
Subrack (Initial).

NodeB
Procedure
displayed.
Option Description

at a time.
Selection window.

NodeB

configuration

NodeB
NOTE
side.
----End

NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)
6 Manually Adding a NodeB (Initial)
About This Chapter
This describes how to manually add a NodeB. This method is used to adjust the data after a
template file or a configuration file is imported.
Procedure
Step 1 6.1 Creating a Logical NodeB (Initial).
Step 2 NodeB Equipment Layer Data
l 6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial).
l 6.4 Adding Equipment Layer Data of the DBS3800 (Initial).
Step 3 NodeB Transport Layer Data

l 6.5 Manually Adding the Transport Layer Data of the NodeB (over ATM).
l 6.6 Manually Adding Transport Layer Data of the NodeB (over IP).
Step 4 6.8 Adding Radio Layer Data.
----End
NodeB.
6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial)
This describes how to configure the equipment layer data of the BTS3812AE or BTS3812A.
6.3 Adding Equipment Layer Data of the BTS3812E (Initial)
This describes how to configure the equipment layer data of the BTS3812E.
6.4 Adding Equipment Layer Data of the DBS3800 (Initial)
This describes how to configure the equipment layer data of the distributed NodeB.
6.5 Manually Adding the Transport Layer Data of the NodeB (over ATM)
This describes how to configure the transport layer data of the NodeB in ATM transport mode.
6.6 Manually Adding Transport Layer Data of the NodeB (over IP)

NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide
This describes how to configure the transport layer data of the NodeB in IP transport mode.
6.8 Adding Radio Layer Data
This describes how to configure radio network layer data for the NodeB. The related activities
involve adding sites, adding sectors, and adding local cells.

NodeB

NodeB.

Optional
Prerequisite
Preparation

Data Name e

location.
match the type of the interface board at Negotiati
the RNC. Optional parameters: on with
the
l ATM_TRANS destinati
l IP_TRANS on
l ATMANDIP_TRANS

NodeB

Data Name e

corresponding physical NodeB.
physical NodeB

index NON_SHARED.

l SHARE
l EXCLUSIVE

IP_TRANS. 0101010
address).
prefix H')

NodeB

Data Name e

parameters:
l SUPPORT
l NOT_SUPPORT


transport

n indication l TRUE
l FALSE

l NORMAL
l PICO_TYPE1
l PICO_TYPE2

l R99
l R4
l R5
l R6

NodeB
Procedure
NOTE


----End

NodeB
6.2 Adding Equipment Layer Data of the BTS3812AE/

BTS3812A (Initial)
This describes how to configure the equipment layer data of the BTS3812AE or BTS3812A.
Context
On the CME client, Figure 6-2 shows the panel of the BTS3812AE/BTS3812A.
Figure 6-2 BTS3812AE/BTS3812A panel

NodeB
Table 6-2 Module information

Sequen Module/ Description
ce Board Type
Number
1 RF Module l One RF module consists of the MAFU and MTRU.

l The MTRU is configured in subrack 2, and the MAFU is
configured in subrack 3. The MAFU and MTRU must exist
in pairs.
2 NCMU NodeB Climate Monitoring Unit, and is installed in subrack 8.
3 Fan Provides the function of a fan, and is configured in subrack 1.
4 Baseboard l NMPT: NodeB Main Processing and Timing Unit, and is

installed in slots 10 and 11 of the baseband subrack.
l NMON: NodeB Monitoring Unit, and is installed in slot 16
of the baseband subrack.
l NBBI\HBBI\EBBI\EBOI: NodeB HSDPA supported
baseband processing interface unit, and is inserted in slots 0
and 1 in the baseband subrack.
l HULP/EULP: NodeB HSDPA supported uplink baseband
processing interface unit, and is inserted in slots 2 and 7 in
the baseband subrack.
l HDLP/NDLP: NodeB HSDPA supported downlink
l NDTI: NodeB Digital Trunk Interface Unit, and is installed
in slots 12 and 13 of the baseband subrack.
l NUTI: NodeB Universal Transport Interface Unit, and is
installed in slots from 12 to 15 of the baseband subrack.
5 Power module l NPSU: Power supply module

l NPMU: Power monitoring module
6 Battery The battery is configured in subrack 9.
6.2.1 Manually Creating a Physical NodeB (Initial)

This describes how to manually configure the basic information for the NodeB.
6.2.2 Adding the Boards in the Baseband Subrack (Initial)
This describes how to configure the boards in the baseband subrack of the macro NodeB. The
boards consist of the NMPT, NBBI/HBBI, EBBI/EBOI, HULP/EULP, NDLP/HDLP, NDTI/
NUTI, and NMON.
6.2.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Macro
NodeB)
This describes how to add an uplink or an downlink baseband resource group so as to reasonably
allocate the uplink or downlink baseband resources of the NodeB.
6.2.4 Adding an RRU (Initial, Macro NodeB)

NodeB
This describes how to add an RRU. The RRU is the outdoor RF remote unit. It is used to perform
functions such as the modulation and demodulation of baseband and RF signals, data processing,
transferring data of the cascaded RRUs, and providing the multiplexing functions of the RF
channels for receiving and transmitting signals. Adding an RRU includes two parts: adding the
RRU chain and adding the RRU module.
6.2.5 Adding RF Modules (Initial)
This describes how to add RF modules, that is, the MAFU and MTRU modules.
6.2.6 Adding an NGRU (Initial)
The NodeB GPS Receiving Unit (NGRU) is a peripheral device used to position the UE and
provide the clock source for the NodeB. This describes how to add an NGRU.
6.2.7 Adding an NCMU (Initial, BTS3812AE)
NCMU is a board to control the temperature of the air conditioner and heat exchanger. This
describes how to add an NCMU for the BTS3812AE.
6.2.8 Adding an NPMU (Initial, Macro NodeB)
This describes how to add an NodeB Power Monitoring Unit (NPMU).
6.2.9 Adding NPSUs (Initial, BTS3812AE/BTS3812A)
This describes how to configure the NodeB Power Supply Unit (NPSU) for the macro NodeB,
that is, the BTS3812AE or BTS3812A.
6.2.10 Adding Batteries (Initial, BTS3812AE/BTS3812A)
This describes how to configure batteries for the macro NodeB (BTS3812AE/BTS3812A). The
batteries are backup power facilities of the NodeB.
6.2.11 Adding an ALD (Initial)
This describes how to add an ALD. The ALD consists of the SINGEL_RET, the MULTI_RET,
the STMA, the SASU, and the RET_2G.


Optional
Prerequisite
The logical NodeB is configured. For details, refer to 6.1 Creating a Logical NodeB (Initial).

NodeB
Preparation

Data


source) destinatio

initial phase.

the IP parameters:

delay

NodeB

Data

synchronization)

fault locating.
is the M2000: set


l DEM_2_CHAN (two-way Network
demodulation mode) planning
demodulation mode)
way economical demodulation
mode)

NodeB

Data

thresholds l 1E-3
of E1/T1
l 1E-4
l 1E-5
l 1E-6

power tch l OPEN
switch
l CLOSE

limits of

n mode
mode)



mode

frame
mode Negotiati
de (distributed l FRAMEMODE_SDH (in SDH MODE_ on with
NodeB) mode) SDH the
Managem Au This parameter is valid only for the AU3 destinatio
ent unit channelized optical interface. n
l AU3
l AU4

NodeB

Data

l -48 V DC
l 24 V DC
l 220 V AC


interface board, namely the NDTI G Internal
or the NUTI, in slots 12 and 13 planning
Iub
interface
board
group
backup
mode
unchanged.
NDTI and NUTI can be inserted
in either slot 12 or 13. Both the
board of the baseband subrack
and the sub-board can be used.

NodeB

Data

interface board, namely the NUTI, G
parameters:
unchanged.
can be used.
Procedure
displayed.
Step 3 Select a logical NodeB on the left of the window, and then click . The Create Physical
NodeB dialog box is displayed, as shown in Figure 6-3.

NodeB
Step 4 Based on the prepared data, select Series and Version. From the drop-down list of Template,
select Do not use template, click OK to start importing the file, and the NodeB Creating dialog
box shows the importing progress.
Step 5 After the NodeB configuration file is imported, the Information dialog box is displayed. Click
OK to return to the Physical NodeB Basic Information window. The information of the
configured physical NodeB is displayed on the right of the window.
Step 6 Select a physical NodeB, and then click . The NodeB Equipment Layer window is
Figure 6-4 NodeB Equipment Layer window
Step 7 Click the Basic Info tab. Set the basic information of the NodeB.
l Click the Basic tab. Set or modify the related parameters such as IP Attribute and FTPS
Policy based on the prepared data.
l Click the More tab. Set or modify the related parameters such as Frame Mode and CHR
Switch based on the prepared data.
l Click the DST tab. Set the time zone and DST-related parameters.
----End

NodeB

NUTI, and NMON.

Optional
NOTE
l Subrack 0 is for the baseband subrack.
l When configuring the NDTI/NUTI, ensure that the difference between MaxVPI and MinVPI is less
than or equal to 5.
l The bearer mode for the NUTIs in slots 14 and 15 cannot be set to IPV4.
Prerequisite
The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical
NodeB (Initial).
Preparation

Data Name

slot 11. the NMPT
NodeB NMON The NMON controls the RET The Internal

monitoring controller and provides Boolean value NMON is planning
Baseboard - According to the capacity of the HBBI/ The HBOI

and 1.

NodeB

Data Name

in slot 13.
ports.

parameters:
l ATM
l IPV4

parameters:
l ENABLE
l DISABLE


NodeB

Data Name

parameters:
the R6 protocol.
the RNC.
Procedure
displayed.
displayed.

NodeB
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-5.
Figure 6-5 Adding the boards in the baseband subrack
Step 5 In subrack 0, right-click slots 10 and 11 to add the NMPTs.
CAUTION
The NMPT must be configured before other boards are configured.
Step 6 In subrack 0, right-click slots 00 and 01 to add the NBBI/HBBI or EBBI/EBOI.

NOTE
The NBBI/HBBI or EBBI/EBOI can be inserted in either slot 00 or 01.
Step 7 Configure the uplink/downlink processing board.

l In subrack 0, right-click slots 02 through 07 to add the HULPs or EULPs.
l In subrack 0, right-click slots 08 and 09 to add the NDLPs or HDLPs.
Step 8 In subrack 0, right-click slots 12 and 13 to add the NDTIs or NUTIs.

NOTE
l The NUTI and NDTI can be inserted in either slot 12 or 13.
l The method of adding the sub-board to NUTIs in slots 12 and 13 is the same as that in slots 14 and 15.
Step 9 In subrack 0, right-click slots 14 and 15 to add the NUTIs.
Option Description
Add the E1 sub-board Right-click the NUTI and choose Add E1

Coverboard... from the shortcut menu.
The eight E1 ports on the E1 sub-board can be used
for only the following elements:
l IMA links in the IMA group
l UNI link
l TreeLink PVC

NodeB
Option Description
Add channelized optical sub-board. Right-click the NUTI and choose Add Channelled
The 63 optical E1 ports on the channelized optical
sub-board are used for the following elements:
l UNI link
l TreeLink PVC
Add unchannelized optical sub-board. Right-click the NUTI and choose Add
UnChannelled Coverboard... from the shortcut
menu.
The two optical ports on the channelized optical
l Upper-level bandwidth for the SDT link or the
UDT link
l TreeLink PVC
Step 10 In subrack 0, right-click slot 16 to add the NMON.

In the Board window, click the NMON Bool External Alarm tab, and then set WorkMode on
the tab page to CUSTOM. Now you can enter the alarm ID for this port.
----End
6.2.3 Adding an Uplink/Downlink Baseband Resource Group and

the CMB (Initial, Macro NodeB)

Optional

NodeB
NOTE
l When configuring the downlink resource group, check that local cells pertaining to this resource group
should be added to boards within the range of the resource group.
l The downlink processing units involved in the downlink resource group should pertain to an uplink
resource group. Otherwise, the alarm, informing that the downlink resource group is not a subset of
the uplink resource group, will be reported.
l A maximum of six cells can be processed in a single uplink or downlink baseband resource group.
When more than six cells are to be processed, you need to divide the baseband resources into groups
by adhering to the following policies:
l Each uplink resource group processes a maximum of six cells.
l Softer handover occurs between the cells that belong to one uplink resource group. Intra-frequency
cells should be allocated in the same uplink resource group.
l When the previous policies are met, the number of resource groups should be as small as possible.
For instance, it is unnecessary to divide the 3 x 2 configuration into two resource groups. In this
case, only one resource group is required. That is, one resource group consisting of two carriers,
six cells in total.
NOTE
When using the CMB, CMB data source such as TV channels of all or part of the cells within a NodeB is
the same. If all data sources are transferred over the Iub interface, it is a waste for the Iub resource. With
the duplication function of the CME FACH, identical data sources are overlapped and will be transferred
over the Iub interface as one data source. The NodeB fulfills the duplication of the CMB data between
cells. One source FACH and several corresponding destination FACHs form a CMB FACH group.
Prerequisite
One of the following boards is added:
l the HULP/EULP and the HDLP/NDLP

l the NBBI, HBBI, EBBI, or EBOI
For the configuration method, refer to 6.2.2 Adding the Boards in the Baseband Subrack
(Initial).
Preparation

Data Name

Internal
planning
six cells.
setup failure.

NodeB

Data Name
ID of the DLResou l A board that is not added to the 0

DL rceGroup DL baseband resource group, that
resource group.
Procedure
l Add an uplink/downlink baseband resource group.
1. On the main interface of the CME, click in the configuration object pane,
and then click NodeB CM Express in the configuration task pane. The NodeB CM
Express window is displayed.
2. Click . The Physical NodeB Basic Information window is displayed.
3. Select a physical NodeB, and then click . The NodeB Equipment Layer window
is displayed.
4. Click the Other Info tab. The tab page is displayed, as shown in Figure 6-6.

NodeB
Figure 6-6 Adding an uplink baseband resource group

configuration
1 List of uplink baseband resource groups
2 List of uplink baseband resources
3 List of uplink baseband resources added to the uplink

resource group
5. Click ULGroup, and in area 1, select ULResourceGroupId. Then, click to add

one or multiple baseband resource groups.
6. Click to save the settings.

7. Select an uplink resource group in area 1, and select an uplink resource item in area
2. Click , the selected item is added to the selected uplink resource group
and is shown in area 3.
8. Click DLGroup. Repeat Step 5 through Step 7 to add one or multiple downlink
resource groups.
l (Optional) Configure the CMB.
1. Click CMB in Figure 6-6, and configure SrcCellId, SrcFachId, DestCellId, and
DestFachId.

NodeB
NOTE
l If the Iub transmission sharing function of the CMB service is required, the NodeB is
required to support this function.
l One source FACH and several corresponding destination FACHs form a CMB FACH
group.
l Before configuring the Iub transmission sharing function at the NodeB, ensure that the
corresponding CMB FACH group data is configured at the RNC. Otherwise, the normal
service may be affected.
l In one CMB FACH group, the source logical cell ID must be different from the destination
logical cell ID.
----End


Mandatory/ Optional
Optional
NOTE
l The RRUs are of the following types: MRRU, RHUB, and PRRU.
l If an RRU is required to be added to the branch, it must be the PRRU (PicoRRU) and the PRRU must
be configured where the RHUB is already configured.
l One MRRU supports one A antenna, one B antenna, and four carriers; one PRRU has only one A
antenna and supports two carriers.
The RRU is similar to the RF module in function. When RF modules such as the MTRU and
MAFU are configured, at least one HBBI or NBBI is required; when the RRU is configured, at
least one EBOI is required. Based on the configured HBBI/NBBI/EBOI in slots 00 through 01
of the baseband subrack, the NodeB can be configured with RF modules or RRUs, or both RF
modules and RRUs.
Prerequisite
The EBOI is configured. For details, refer to Adding Boards in the Baseband Subrack
(Initial).

NodeB
Preparation

Data

type parameters:

number
number
Internal
planning
ring topology.
topology.


NodeB

Data

resume the data.
affected.
in separate status.

NodeB

Data

resume the data.
can be affected.
points overlap.

NodeB

Data
modules. Network
modules.


RHUB.

l Block
l Unblock

the RRU
l BRANCH (under the
RHUB node)

NodeB

Data

number range:
(MRRU/WRFU), 0 to 1
(PRRU)
the RTWP: -130 to +130,
unit: 0.1 dB

l BOTTOM: Offset to
minimum value (The
interference signal
receive frequency.)
l MIDDLE: Offset to
(no interference)
the current receive
frequency.)

+1000

NodeB

Data


RRU

Data


RHUB.

l Block
l Unblock

the RRU ring)
l BRANCH (under the
RHUB node)

+1000

NodeB

Data


RRU
Procedure
displayed.
displayed.
Figure 6-7 Adding the RRU (BTS3812AE/BTS3812A/BTS3812E)
Step 5 Right-click the configured EBOI, and then choose Add RRUChain... from the shortcut menu.
Configure related parameters based on prepared data, and then click OK to display the added
RRU Chain.
Step 6 Right-click the added RRU Chain. Based on the actual network, choose Add MRRU..., Add
RHUB... or Add PRRU... from the shortcut menu. Configure related parameters based on
prepared data, and click OK to display the added MRRU, PRRU or RHUB.

NodeB
Step 7 (Optional) Right-click the added RHUB, and choose Add PicoRRU... from the shortcut menu
so as to add the PRRU on the RHUB.
----End


Mandatory/ Optional
Optional
NOTE
l Subracks 2 and 3 are configured with RF modules.
l MTRUs in subrack 2 and MAFUs in subrack 3 are configured in pairs.
modules and RRUs.
Prerequisite
The HBBI or NBBI is configured. For details, refer to Adding Boards in the Baseband Subrack
(Initial).
Preparation
None.
Procedure
displayed.
displayed.

NodeB
Figure 6-8 Adding the MTRU and MAFU
Step 5 Right-click any slot in subrack 2 or 3, and choose Add RF Module... from the shortcut menu.
Configure related parameters based on prepared data, and click OK to add the MTRU and
MAFU.
----End


Mandatory/ Optional
Optional
Prerequisite
NodeB (Initial).
Preparation
None.
Procedure
displayed.

NodeB
displayed.
Figure 6-9 Adding the NGRU (BTS3812AE/BTS3812A for instance)
Step 5 Right-click in the frame area of the cabinet, and choose Add NGRU... from the shortcut menu.
Configure related parameters based on prepared data, and click OK to add the NGRU.
----End
6.2.7 Adding an NCMU (Initial, BTS3812AE)

NCMU is a board to control the temperature of the air conditioner and heat exchanger. This
describes how to add an NCMU for the BTS3812AE.

NodeB
Optional
NOTE
The NCMU is used only for the BTS3812AE, and is configured in subrack 8.
Prerequisite
NodeB (Initial).
Preparation
None.
Procedure
displayed.
displayed.

NodeB
Figure 6-10 Adding an NCMU.
Step 5 Right-click subrack 8, and choose Add Board... from the shortcut menu. Configure related
parameters based on prepared data, and click OK to add the NCMU.
----End


Mandatory/ Optional
Optional
Prerequisite
NodeB (Initial).
Preparation
None.

NodeB
Procedure
l Add the NPMU to the BTS3812AE/BTS3812A.
NOTE
For the BTS3812A/BTS3812AE, the value of PowerType cannot be changed. You can use only the
default value -48V DC.
is displayed.
4. Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-11.
Figure 6-11 Adding an NPMU
5. Right-click the lower left part of subrack 7, and choose Add Board... from the shortcut
menu. Configure related parameters based on prepared data, and click OK to add the
NPMU.
l Modify the NPMU attributes in the BTS3812E.
is displayed.
4. Click the Basic Info tab. Click in the PowerType editing box, the NPMU
Attribute is displayed, as shown in Figure 6-12.

NodeB
Figure 6-12 Modifying the NPMU attributes
5. Select the button 220V AC, and set related parameters based on prepared data. Click
OK to modify the NPMU attributes.
NOTE
The button -48V DC or 24V DC is selected to set the type of the power supply for the BTS3812E
cabinet. In these two cases, the BTS3812E has no NPMU, and the parameters in the NPMU
Attribute dialog box cannot be set.
----End
6.2.9 Adding NPSUs (Initial, BTS3812AE/BTS3812A)

that is, the BTS3812AE or BTS3812A.

Mandatory/ Optional
Optional
NOTE
The NPSU is configured in any of the seven slots except the one that holds the NPMU of subrack 7. The
NPMU controls the status of the NPSU.
Prerequisite
NodeB (Initial).
Preparation
None.

NodeB
Procedure
displayed.
displayed.
Figure 6-13 Adding an NPSU.
Step 5 Right-click any slot other than the lower leftmost one of subrack 7 on the tab page, and then
choose Add Board... from the shortcut menu to add the NPSU.
----End
6.2.10 Adding Batteries (Initial, BTS3812AE/BTS3812A)

This describes how to configure batteries for the macro NodeB (BTS3812AE/BTS3812A). The
batteries are backup power facilities of the NodeB.

Mandatory/ Optional
Optional
CAUTION
Capacity is the battery capacity parameter. The value of this parameter must be set as that of
the actual capacity of the batteries. Otherwise, the batteries can be damaged. For details about
the actual capacity of the batteries, refer to the related instructions of the batteries.
Prerequisite
NodeB (Initial).

NodeB
Preparation
None.
Procedure
displayed.
displayed.
Figure 6-14 Adding Batteries
Step 5 Right-click subrack 9, and choose Add Board... from the shortcut menu. Configure related
parameters based on prepared data, and click OK to add batteries.
----End


Mandatory/ Optional
Optional

NodeB
NOTE
l Only the ALD that supports protocols such as AISG or 3GPP IUANT needs to be configured. The
ALD can be configured on only the MAFU of subrack 3 for the macro NodeB or on the MRRU for the
distributed NodeB.
l In typical installation scenarios, you can add the ALD without manually entering the vendor codes or
SNs, which can be obtained by scanning. In other installation scenarios, you are required to manually
enter the vendor codes and SNs when adding the ALD. Otherwise, the system cannot communicate
with the ALD. The vendor codes and SNs must be entered at the same time. If only one of them is
entered, the system provides a parameter illegality message.
l In 2G extended application scenarios, you are not required to configure the subrack number, the cabinet
number, or the antenna connector number. In other scenarios, ensure that the configured subrack
number, the cabinet number, or the antenna connector number are consistent with the number of the
equipment that the ALD is connected to. Otherwise, the mapping between the ALD and sector cannot
be determined.
Prerequisite
l The RF module is configured. For details, refer to 6.2.5 Adding RF Modules (Initial).
l The RRU sites are configured. For details, refer to 6.4.4 Adding an RRU (Initial,
Distributed NodeB).
Preparation

Data

NOB.


NodeB

Data

parameters: R
port. planning
of cascaded NodeBs.

parameters:
antenna).

Internal

NodeB

Data

number number.

number types:
STMA can only be 0.
to 2.
by default. Network

the STMA
l Bypass mode


NodeB

Data

the power)
supplies the power)
l OFF

antenna.

gain
Procedure
displayed.
displayed.
Step 4 Click the Device Panel tab, and right-click the added MAFU in subrack 3 or the added MRRU
in the RRUChain subrack. Choose Antenna Line Device from the shortcut menu. The Antenna
Line Device window is displayed, as shown in Figure 6-15.

NodeB
Figure 6-15 Adding the ALD
Step 5 Click the tab SINGLE_RET or MULTI_RET, and click . Configure related parameters
based on prepared data, and then click to add an RET.
Step 6 Click the STMA tab, and click . Set related parameters based on the prepared data, and click
to add an STMA.
to add an SASU.
Step 8 Click the RET_2G tab, and click . Set related parameters based on the prepared data, and
click to add an RET_2G.
----End
6.3 Adding Equipment Layer Data of the BTS3812E (Initial)

This describes how to configure the equipment layer data of the BTS3812E.
Context
On the CME client, Figure 6-16 shows the panel of the BTS3812E.

NodeB
Figure 6-16 BTS3812E panel

ce Board Type
Number
1 RF Module l One RF module consists of the MAFU and MTRU.

l The MTRU is configured in subrack 2, and the MAFU is
configured in subrack 3. The MAFU and MTRU must exist
in pairs.
2 Fan Provides the function of a fan, and is configured in subrack 1.

NodeB

ce Board Type
Number
3 Baseboard l NMPT: NodeB Main Processing and Timing Unit, and is

installed in slots 10 and 11 of the baseband subrack.
l NMON: NodeB Monitoring Unit, and is installed in slot 16
of the baseband subrack.
l NBBI\HBBI\EBBI\EBOI: NodeB HSDPA supported
l HULP/EULP: NodeB HSDPA supported uplink baseband
processing interface unit, and is inserted in slots 2 and 7 in
the baseband subrack.
l HDLP/NDLP: NodeB HSDPA supported downlink
l NDTI: NodeB Digital Trunk Interface Unit, and is installed
in slots 12 and 13 of the baseband subrack.
l NUTI: NodeB Universal Transport Interface Unit, and is
installed in slots from 12 to 15 of the baseband subrack.

NUTI, and NMON.
6.3.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Macro
NodeB)
6.3.7 Adding an NEMU (Initial, BTS3812E)
This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for the
BTS3812E.

NodeB

6.3.9 Adding NPSUs (Initial, BTS3812E)
that is, the BTS3812E.
6.3.10 Adding Batteries (Initial, BTS3812E)
This describes how to configure batteries for the BTS3812E. The batteries are backup power
facilities of the NodeB.


Optional
Prerequisite
Preparation

Data


source) destinatio

NodeB

Data

initial phase.

the IP parameters:

delay

synchronization)

NodeB

Data

fault locating.
is the M2000: set


demodulation mode)
demodulation mode)
mode) planning

thresholds l 1E-3
of E1/T1
l 1E-4
l 1E-5
l 1E-6

power tch l OPEN
switch
l CLOSE

NodeB

Data

limits of

n mode
mode)



mode

frame
mode
NodeB) mode) SDH

l AU3 destinatio
n
l AU4


NodeB

Data
l -48 V DC
l 24 V DC
l 220 V AC


unchanged.
parameters:
unchanged.
can be used.

NodeB
Procedure
displayed.

NodeB
----End

NUTI, and NMON.

Optional

NodeB
NOTE
l Subrack 0 is for the baseband subrack.

l When configuring the NDTI/NUTI, ensure that the difference between MaxVPI and MinVPI is less
than or equal to 5.
l The bearer mode for the NUTIs in slots 14 and 15 cannot be set to IPV4.
Prerequisite
NodeB (Initial).
Preparation

Data Name

slot 11. the NMPT
NodeB NMON The NMON controls the RET The

monitoring controller and provides Boolean value NMON is
Internal
Baseboard - According to the capacity of the HBBI/ The HBOI planning
and 1.

in slot 13.
ports.

NodeB

Data Name

parameters:
l ATM
l IPV4

parameters:
l ENABLE
l DISABLE


NodeB

Data Name

parameters:
the R6 protocol.
the RNC.
Procedure
displayed.
displayed.

NodeB
Figure 6-19 Adding the boards in the baseband subrack
Step 5 In subrack 0, right-click slots 10 and 11 to add the NMPTs.
CAUTION
The NMPT must be configured before other boards are configured.
Step 6 In subrack 0, right-click slots 00 and 01 to add the NBBI/HBBI or EBBI/EBOI.

NOTE
The NBBI/HBBI or EBBI/EBOI can be inserted in either slot 00 or 01.
Step 7 Configure the uplink/downlink processing board.

l In subrack 0, right-click slots 02 through 07 to add the HULPs or EULPs.
l In subrack 0, right-click slots 08 and 09 to add the NDLPs or HDLPs.
Step 8 In subrack 0, right-click slots 12 and 13 to add the NDTIs or NUTIs.

NOTE
l The NUTI and NDTI can be inserted in either slot 12 or 13.
l The method of adding the sub-board to NUTIs in slots 12 and 13 is the same as that in slots 14 and 15.
Step 9 In subrack 0, right-click slots 14 and 15 to add the NUTIs.
Option Description
Add the E1 sub-board Right-click the NUTI and choose Add E1

The eight E1 ports on the E1 sub-board can be used
for only the following elements:
l UNI link
l TreeLink PVC

NodeB
Option Description
Add channelized optical sub-board. Right-click the NUTI and choose Add Channelled
The 63 optical E1 ports on the channelized optical
l UNI link
l TreeLink PVC
Add unchannelized optical sub-board. Right-click the NUTI and choose Add
UnChannelled Coverboard... from the shortcut
menu.
The two optical ports on the channelized optical
l Upper-level bandwidth for the SDT link or the
UDT link
l TreeLink PVC
Step 10 In subrack 0, right-click slot 16 to add the NMON.

In the Board window, click the NMON Bool External Alarm tab, and then set WorkMode on
the tab page to CUSTOM. Now you can enter the alarm ID for this port.
----End

the CMB (Initial, Macro NodeB)

Optional

NodeB
NOTE
six cells in total.
NOTE
Prerequisite
One of the following boards is added:
l the HULP/EULP and the HDLP/NDLP

l the NBBI, HBBI, EBBI, or EBOI
For the configuration method, refer to 6.3.2 Adding the Boards in the Baseband Subrack
(Initial).
Preparation

Data Name

Internal
planning
six cells.
setup failure.

NodeB

Data Name
ID of the DLResou l A board that is not added to the 0

DL rceGroup DL baseband resource group, that
resource group.
Procedure
is displayed.

NodeB

configuration

resource group


resource groups.
DestFachId.

NodeB
NOTE
group.
logical cell ID.
----End


Mandatory/ Optional
Optional
NOTE
l If an RRU is required to be added to the branch, it must be the PRRU (PicoRRU) and the PRRU must
be configured where the RHUB is already configured.
l One MRRU supports one A antenna, one B antenna, and four carriers; one PRRU has only one A
antenna and supports two carriers.
modules and RRUs.
Prerequisite
The EBOI is configured. For details, refer to Adding Boards in the Baseband Subrack
(Initial).

NodeB
Preparation

Data

type parameters:

number
number
Internal
planning
ring topology.
topology.


NodeB

Data

resume the data.
affected.
in separate status.

NodeB

Data

resume the data.
can be affected.
points overlap.

NodeB

Data
modules. Network
modules.


RHUB.

l Block
l Unblock

the RRU
l BRANCH (under the
RHUB node)

NodeB

Data

number range:
(MRRU/WRFU), 0 to 1
(PRRU)
the RTWP: -130 to +130,
unit: 0.1 dB

l BOTTOM: Offset to
minimum value (The
interference signal
receive frequency.)
l MIDDLE: Offset to
(no interference)
the current receive
frequency.)

+1000

NodeB

Data


RRU

Data


RHUB.

l Block
l Unblock

the RRU ring)
l BRANCH (under the
RHUB node)

+1000

NodeB

Data


RRU
Procedure
displayed.
displayed.
Figure 6-21 Adding the RRU (BTS3812AE/BTS3812A/BTS3812E)
Step 5 Right-click the configured EBOI, and then choose Add RRUChain... from the shortcut menu.
Configure related parameters based on prepared data, and then click OK to display the added
RRU Chain.

NodeB
----End


Mandatory/ Optional
Optional
NOTE
l Subracks 2 and 3 are configured with RF modules.
l MTRUs in subrack 2 and MAFUs in subrack 3 are configured in pairs.
modules and RRUs.
Prerequisite
The HBBI or NBBI is configured. For details, refer to Adding Boards in the Baseband Subrack
(Initial).
Preparation
None.
Procedure
displayed.
displayed.

NodeB
Figure 6-22 Adding the MTRU and MAFU
Step 5 Right-click any slot in subrack 2 or 3, and choose Add RF Module... from the shortcut menu.
Configure related parameters based on prepared data, and click OK to add the MTRU and
MAFU.
----End


Mandatory/ Optional
Optional
Prerequisite
NodeB (Initial).
Preparation
None.
Procedure
displayed.

NodeB
displayed.
Figure 6-23 Adding the NGRU (BTS3812AE/BTS3812A for instance)
Step 5 Right-click in the frame area of the cabinet, and choose Add NGRU... from the shortcut menu.
Configure related parameters based on prepared data, and click OK to add the NGRU.
----End
6.3.7 Adding an NEMU (Initial, BTS3812E)

BTS3812E.

NodeB
Mandatory/ Optional
Optional
NOTE
The NEMU is applicable only to the BTS3812E.
Prerequisite
NodeB (Initial).
Preparation
None.
Procedure
displayed.
displayed.

NodeB
Figure 6-24 Adding an NEMU
Step 5 Right-click in the frame area of the cabinet, and choose Add NEMU... from the shortcut menu.
Configure related parameters based on prepared data, and click OK to add the NEMU.
----End


Mandatory/ Optional
Optional
Prerequisite
NodeB (Initial).
Preparation
None.

NodeB
Procedure
l Add the NPMU to the BTS3812AE/BTS3812A.
NOTE
For the BTS3812A/BTS3812AE, the value of PowerType cannot be changed. You can use only the
default value -48V DC.
is displayed.
4. Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-25.
Figure 6-25 Adding an NPMU
5. Right-click the lower left part of subrack 7, and choose Add Board... from the shortcut
menu. Configure related parameters based on prepared data, and click OK to add the
NPMU.
l Modify the NPMU attributes in the BTS3812E.
is displayed.
4. Click the Basic Info tab. Click in the PowerType editing box, the NPMU
Attribute is displayed, as shown in Figure 6-26.

NodeB
Figure 6-26 Modifying the NPMU attributes
5. Select the button 220V AC, and set related parameters based on prepared data. Click
OK to modify the NPMU attributes.
NOTE
The button -48V DC or 24V DC is selected to set the type of the power supply for the BTS3812E
cabinet. In these two cases, the BTS3812E has no NPMU, and the parameters in the NPMU
Attribute dialog box cannot be set.
----End
6.3.9 Adding NPSUs (Initial, BTS3812E)

that is, the BTS3812E.

Mandatory/ Optional
Optional
Prerequisite
l The physical NodeB is configured. For details, refer to 6.3.1 Manually Creating a
Physical NodeB (Initial).
l Before adding the NPSU to the BTS3812E, change the NPMU attributes. For details, refer
to Change the NPMU attribute for the BTS3812E.
Preparation
None.

NodeB
Procedure
displayed.
displayed.
Figure 6-27 Adding an NPSU.
Step 5 Right-click in the blank area beyond the subrack area, and choose NPSU... from the shortcut
menu. The Board window is displayed. Configure related parameters based on prepared data,
and then click OK to add an NPSU.
----End

NodeB
6.3.10 Adding Batteries (Initial, BTS3812E)

This describes how to configure batteries for the BTS3812E. The batteries are backup power
facilities of the NodeB.

Mandatory/ Optional
Optional
CAUTION
Capacity is the battery capacity parameter. The value of this parameter must be set as that of
the actual capacity of the batteries. Otherwise, the batteries can be damaged. For details about
the actual capacity of the batteries, refer to the related instructions of the batteries.
Prerequisite
l Before adding the batteries for the BTS3812E, change the NPMU attributes. For details,
refer to Change the NPMU attributes for the BTS3812E.
Preparation
None.
Procedure
displayed.
displayed.

NodeB
Figure 6-28 Adding Batteries
Step 5 Right-click on the top part of the frame, and choose Add Battery... from the shortcut menu. The
Board window is displayed. Configure related parameters based on prepared data, and then click
OK to add batteries.
----End


Mandatory/ Optional
Optional

NodeB
NOTE
distributed NodeB.
be determined.
Prerequisite
Distributed NodeB).
Preparation

Data

NOB.


NodeB

Data

parameters: R
port. planning
of cascaded NodeBs.

parameters:
antenna).

Internal

NodeB

Data

number number.

number types:
STMA can only be 0.
to 2.
by default. Network

the STMA
l Bypass mode


NodeB

Data

the power)
supplies the power)
l OFF

antenna.

gain
Procedure
displayed.
displayed.

NodeB
to add an STMA.
to add an SASU.
----End
6.4 Adding Equipment Layer Data of the DBS3800 (Initial)

This describes how to configure the equipment layer data of the distributed NodeB.
Context
On the CME client, Figure 6-30 shows the DBS3800 panel.

NodeB
Figure 6-30 DBS3800 panel
Module/Board Description
Type
BBU module l HBBU: indicates that the BBU type is BBU3806, which supports
UBTI and EBBC.
l HBBUC: indicates that the BBU type is BBU3806C, which does not
support UBTI or EBBC.
l UBTI: Universal BBU Transport Interface board, which supports the
channelized optical sub-board and the unchannelized optical sub-
board.
l EBBC: indicates the enhanced baseband card of the HBBU.

6.4.2 Adding a BBU (Initial)
This describes how to add a BBU. The BBU is of two models: HBBU (BBU3806) and HBBUC
(BBU3806C).
6.4.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Distributed
NodeB)
The baseband resources consists of uplink baseband resources and downlink baseband resources.
By specifying the ID of the UL resource group, the uplink baseband resources of the cell are
configured, and by specifying the ID of the DL resource group, the downlink baseband resources
of the cell are configured. This describes how to add an uplink or an downlink baseband resource
group so as to reasonably allocate the uplink or downlink baseband resources of the NodeB.
6.4.4 Adding an RRU (Initial, Distributed NodeB)
6.4.5 Adding an NEMU (Initial, Distributed NodeB)

NodeB
DBS3800.
6.4.6 Adding an NPMU (Initial, Distributed NodeB)
This describes how to add a NodeB Power Monitoring Unit (NPMU) of the DBS3800.


Optional
Prerequisite
Preparation

Data


source) destinatio

NodeB

Data

initial phase.

the IP parameters:

delay

synchronization)

NodeB

Data

fault locating.
is the M2000: set


demodulation mode)
demodulation mode)
mode) planning

thresholds l 1E-3
of E1/T1
l 1E-4
l 1E-5
l 1E-6

power tch l OPEN
switch
l CLOSE

NodeB

Data

limits of

n mode
mode)



mode

frame
mode
NodeB) mode) SDH

l AU3 destinatio
n
l AU4


NodeB

Data
l -48 V DC
l 24 V DC
l 220 V AC


unchanged.
parameters:
unchanged.
can be used.

NodeB
Procedure
displayed.

NodeB
----End
6.4.2 Adding a BBU (Initial)

This describes how to add a BBU. The BBU is of two models: HBBU (BBU3806) and HBBUC
(BBU3806C).

Optional

NodeB
NOTE
l On the Basic Info tab page of the NodeB Equipment Layer window, set the parameter
ClockSource to BITS, and the HBBUC cannot be added.
l The HBBU and the HBBUC should be inserted into their own slots as specified.
Prerequisite
NodeB (Initial).
Preparation

Data
Board BoardStatus Blocking status of the board Optional UnBlock

status parameters:
l Block
l Unblock
Internal
Clock ClockSource E1/T1 ports for extracting the Iub Port 0 planning
source 8K interface clock signals. Optional
parameters:
l None
l Port 0 to port 7
Bearer BearMode Optional parameters: ATM

mode l ATM: If the bearer mode is ATM,
the IP transport layer cannot use
the E1/T1 ports, that is, you cannot
configure the PPP or MP links.
l IPv4: If the bearer mode is IPv4, Negotiati
the ATM transport layer cannot on with
use the E1/T1 ports, that is, you the
cannot configure the physical destinatio
links. n
HSUPA HSUPA Optional parameters: DISABL
switch l ENABLE (The HSUPA is E
supported)
l DISABLE (The HSUPA is not
supported)

NodeB

Data
Clock ClockMode For the cascaded NodeBs, the clock SLAVE Network
Mode of the upper-level NodeB is set to planning
MASTER and that of the lower-level
NodeB is set to SLAVE. If the value
is not specified, the original clock
mode is retained. Optional
parameters:
Line Code LineCode Optional parameters: HDB3

l HDB3 (for E1 mode)
l AMI (for E1 or T1 mode)
l B8ZS (for T1 mode)
Frame FrameStru Optional parameters: E1_CRC Negotiati

Structure l E1_DOUBLE_FRAME (double 4_MULT on with
frame, for E1 mode) I_FRAM the
E destinatio
l E1_CRC4_MULTI_FRAME
n
(CRC-multiframe, for E1 mode)
l T1_SUPER_FRAME (super
frame, for T1 mode)
l T1_EXTENDED_SUPER_FRA
ME (extended super frame, for T1
mode)

NodeB

Data

switch l SIMPLE_FLOW_CTRL: Based DJUST_
on the configured Iub bandwidth FLOW_C
and the bandwidth occupied by TRL
account.
protocol.

Value range:0 to 20

Value range:0 to 1000

NodeB

Data
Working WorkMode Optional parameters: OFF

Mode l OFF (inhibited mode): indicates
that the port works in inhibited
mode, that is, the port does not
detect the alarms. All ports work
in such mode by default.
l Default (default mode): indicates
that the system detects and reports
the alarms in default mode. In such
mode, the UE cannot set the alarm
ID of this port or other parameters
related to this port. The system
reports alarms based on its own
fixed setting rather than the user-
defined setting.
Internal
l CUSTOM (customized mode):
planning
indicates that the UE can change
the binding relation, that is, the
system reports the alarm and set
the alarm Bool based on the
customer specified ID.
Alarm ID AlarmId This parameter is valid only when -

WorkMode is set to CUSTOM.
Alarm ALarmVolta This parameter is valid only when -

voltage ge WorkMode is set to CUSTOM.
l HIGH (alarms related to high
impedance)
l LOW (alarms related to low
impedance)
Procedure
displayed.

NodeB
displayed.
Figure 6-33 Adding the BBU
NOTE
l The DBS3800 supports only 2 cascaded BBUs. The BBUs can be configured in subrack 0 and subrack
1.
l The HBBUC can be configured only in slot 00 of subrack 0.
l The HBBUC can be configured only in subrack 0. Do not add the HBBUC in subrack 1.
Step 5 Right-click slot 00 of subrack 0, and choose Add HBBU... or Add HBBUC... from the shortcut
menu. Configure related parameters based on prepared data, and then click OK to add a BBU.
Step 6 (Optional) Right-click the configured HBBU, and choose Add UBTI... or Add EBBC....
Configure related parameters based on prepared data, and then click OK to add a UBTI or an
EBBC.
NOTE
l The HBBU can be configured with the UBTI and the EBBC plugboards.
l The channelized optical sub-board and the unchannelized optical sub-board can be configured on the
UBTI.
l The HBBUC (BBU3806C) cannot be configured with the UBTI and the EBBC plugboards.
Step 7 (This task is performed only when the plugboard is UBTI.) Right-click the configured UBTI,
and choose Add Channelled Coverboard... or Add UnChannelled Coverboard... from the
shortcut menu. Configure related parameters based on prepared data, and then click OK to add
a channelized optical sub-board or an unchannelized optical sub-board.
----End

the CMB (Initial, Distributed NodeB)
The baseband resources consists of uplink baseband resources and downlink baseband resources.
By specifying the ID of the UL resource group, the uplink baseband resources of the cell are
configured, and by specifying the ID of the DL resource group, the downlink baseband resources

NodeB
of the cell are configured. This describes how to add an uplink or an downlink baseband resource
group so as to reasonably allocate the uplink or downlink baseband resources of the NodeB.

Optional
NOTE
six cells in total.
NOTE
Prerequisite
The BBU is configured. For details, refer to 6.4.2 Adding a BBU (Initial).
Preparation
Data Name
ID of the ULResou l A board such as the HBBU or the 1

UL rceGroup HBBUC that is not added to the
group l An uplink baseband resource Internal
group can process a maximum of planning
six cells.
setup failure.

NodeB

Data Name
ID of the DLResou l A board such as the HBBU or the 0

DL rceGroup HBBUC that is not added to the
group l The downlink processing units
resource group.
Procedure
is displayed.

NodeB

configuration

resource group


resource groups.
DestFachId.

NodeB
NOTE
group.
logical cell ID.
----End
6.4.4 Adding an RRU (Initial, Distributed NodeB)


Optional
l If an RRU is required to be added to the branch, it must be the PRRU (PicoRRU) and the
PRRU must be configured where the RHUB is already configured.
l One MRRU supports one A antenna, one B antenna, and four carriers; one PRRU has only
one A antenna and supports two carriers.
Prerequisite
Preparation

Data

type parameters:
l RING (ring topology) Internal
planning
number

NodeB

Data
number

ring topology.
topology.


NodeB

Data

resume the data.
affected.
in separate status.

NodeB

Data

resume the data.
can be affected.
points overlap.

NodeB

Data
modules.
Network
modules.
configure six RF
modules.


RHUB.

l Block
l Unblock

the RRU ring)
l BRANCH (under the
RHUB node)

NodeB

Data
Initial RTWPofCarrier Set the initial correction 0

correction Carrier value for the RTWP of the
value for numberonRxRX carrier and TX channel
the RTWP channel number specified by the RRU. Value
range:
(MRRU/WRFU), 0 to 1
(PRRU)
l RX channel number: 0
through 1
the RTWP: -130 to +130,
unit: 0.1 dB

l BOTTOM: Offset to
minimum value (The
interference signal
receive frequency.)
l MIDDLE: Offset to
(no interference)
the current receive
frequency.)

+1000

NodeB

Data


RRU

Data


RHUB.

l Block
l Unblock

the RRU ring)
l BRANCH (under the
RHUB node)

+1000

NodeB

Data


RRU
Procedure
displayed.
displayed.
Figure 6-35 Adding an RRU (DBS3800)
Step 5 Right-click the configured HBBU or HBBUC, and then choose Add RRUChain... from the
shortcut menu. Configure related parameters based on prepared data, and then click OK to
display the added RRU Chain.

NodeB
----End
6.4.5 Adding an NEMU (Initial, Distributed NodeB)

DBS3800.

Mandatory/ Optional
Optional
NOTE
The NEMU can be configured only in slot 00 of subrack 0.
Prerequisite
Preparation
None.
Procedure
displayed.
displayed.

NodeB
Figure 6-36 Adding an NEMU
Step 5 Right-click the configured HBBU/HBBUC of subrack 0, and choose Add NEMU... from the
shortcut menu. Configure related parameters based on prepared data, and then click OK to add
an NEMU.
----End
6.4.6 Adding an NPMU (Initial, Distributed NodeB)

This describes how to add a NodeB Power Monitoring Unit (NPMU) of the DBS3800.

Mandatory/ Optional
Optional
NOTE
l You may add the NPMU only in slot 00 of subrack 0 of the DBS3800 cabinet.
l You may the NPMU for the RRU (MRRU). One MRRU, however, can be configured with only one
NPMU.
Prerequisite
l The BBU is configured. For details, refer to 6.4.2 Adding a BBU (Initial).
l The RRU is configured. For details, refer to 6.4.4 Adding an RRU (Initial, Distributed
NodeB).
Preparation
None.
Procedure
displayed.

NodeB
displayed.
Step 4 Click the tab Device Panel, and add an NPMU in the DBS3800 cabinet, as shown in Figure
6-37, and then add an NPMU for the RRU, as shown in Figure 6-38.
Figure 6-37 Adding an NPMU in the DBS3800 cabinet
Figure 6-38 Adding the NPMU for the RRU
Step 5 Add an NPMU.

l Adding an NPMU in the DBS3800 cabinet: Right-click the configured HBBU/HBBUC of
subrack 0, and choose Add NPMU... from the shortcut menu. Configure related parameters
based on prepared data, and then click OK to add an NPMU.
l Adding the NPMU for the RRU: Right-click the configured MRRU, and choose Add
NPMU... from the shortcut menu. Configure related parameters based on prepared data, and
then click OK to add an NPMU for the RRU.
----End


NodeB

Mandatory/ Optional
Optional
NOTE
distributed NodeB.
be determined.
Prerequisite
Distributed NodeB).
Preparation

Data

NOB.


NodeB

Data

parameters: R
port. planning
of cascaded NodeBs.

parameters:
antenna).

Internal

NodeB

Data

number number.

number types:
STMA can only be 0.
to 2.
by default. Network

the STMA
l Bypass mode


NodeB

Data

the power)
supplies the power)
l OFF

antenna.

gain
Procedure
displayed.
displayed.

NodeB
to add an STMA.
to add an SASU.
----End
6.5 Manually Adding the Transport Layer Data of the NodeB

(over ATM)
This describes how to configure the transport layer data of the NodeB in ATM transport mode.
Prerequisite
The data of the equipment layer of the NodeB is configured. For details, refer to:
l 6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial)

l 6.4 Adding Equipment Layer Data of the DBS3800 (Initial)
The process of configuring the NodeB transport layer data over ATM is as follows:

NodeB
6.5.1 Adding Links at the Physical Layer (Initial)

This describes how to configure the physical layer data of the NodeB in ATM transport mode.
The physical layer data consists of the IMA group, IMA link, UNI link, Fractional ATM link,
unstructured CES channel, structured CES channel, and timeslot cross channel. You need to
configure at least one type from among the IMA group, IMA link, UNI link, and Fractional ATM
link. And you can configure only one type or configure all the types.
6.5.2 Adding Transmission Resource Group (Initial, over ATM)
This describes how to add the transmission resource group, which is used to allocates the
bandwidth of the physical link to the transmission resource group for carrying the data on the
control plane, the user plane, and the OM channel. Each group occupies one portion of the
bandwidth and has separate access control, congestion control and HSPA flow control.
6.5.3 Adding SAAL Links (Initial)
This describes how to add SAAL links. The SAAL links are used to carry the NBAP and ALCAP
when the Iub interface is over ATM.
6.5.4 Adding an NBAP (Initial)
This describes how to configure the NodeB Control Port (NCP) and Communication Control
Port (CCP). These two ports are carried on the SAAL links.
6.5.5 Adding an ALCAP (Initial)
This describes how to configure an AAL2 node to the NodeB so that the ALCAP is added at the
NodeB. The ALCAP allocates the micro channels of the AAL2 path.
6.5.6 Adding AAL2 Path Data (Initial)
This describes how to add AAL2 PATH data over ATM. The AAL2 path carries the user plane
data between the RNC and other equipment.
6.5.7 Adding an OMCH of the NodeB (Initial, over ATM)
This describes how to add an Operation and Maintenance Channel (OMCH) of the NodeB.
6.5.8 Adding a Treelink PVC (Initial)
This describes how to add a treelink PVC to the Hub NodeB. When the NodeB are cascaded,
the treelink PVC added to the Hub NodeB can provide the data transmission channel between
the upper-level NE and the lower-level NE.
6.5.1 Adding Links at the Physical Layer (Initial)

This describes how to configure the physical layer data of the NodeB in ATM transport mode.
The physical layer data consists of the IMA group, IMA link, UNI link, Fractional ATM link,
unstructured CES channel, structured CES channel, and timeslot cross channel. You need to
configure at least one type from among the IMA group, IMA link, UNI link, and Fractional ATM
link. And you can configure only one type or configure all the types.
6.5.1.1 Adding an IMA Group and IMA Links (Initial)

This describes how to configure the IMA group and IMA links. The IMA is a transmission mode
over the TC sub-layer of the ATM physical layer. The IMA technology multiplexes multiple
low-speed links for transmitting high-speed ATM cell flows, so as to achieve wideband ATM
transmission.
6.5.1.2 Adding UNI Links (Initial)
The UNI is a transmission mode over the TC sub-layer of the ATM physical layer. A UNI link
uses all the timeslots of an E1/T1 port. This describes how to add UNI links.
6.5.1.3 Adding Fractional ATM Links (Initial)

NodeB
The fractional ATM is a transmission mode over the TC sub-layer of the ATM physical layer
and it is an exceptional case of the UNI link. This describes how to add fractional ATM links.
6.5.1.4 Adding SDT CES or UDT CES Link (Initial)
The Circuit Emulation Service (CES) provides the transmission channel for GSM services to be
transmitted over the 3G network. The CES links use either Structured Data Transfer (SDT) mode
or Unstructured Data Transfer (UDT) mode. This describes how to configure the SDT CES or
UDT CES link. The Circuit Emulation Service (CES) provides the transmission channel for
GSM services to be transmitted over the 3G network. The CES links use either Structured Data
Transfer (SDT) mode or Unstructured Data Transfer (UDT) mode. This describes how to
configure the SDT CES or the UDT CES link. The SDT CES and the UDT CES are only
configured in the macro NodeB.
6.5.1.5 Adding a Timeslot Cross Channel (Initial, over ATM)
This describes how to add a timeslot cross channel for the 2G equipment so as to transmit the
data of services on the 3G network.
Adding an IMA Group and IMA Links (Initial)

This describes how to configure the IMA group and IMA links. The IMA is a transmission mode
over the TC sub-layer of the ATM physical layer. The IMA technology multiplexes multiple
low-speed links for transmitting high-speed ATM cell flows, so as to achieve wideband ATM
transmission.

Mandatory/ Optional
Optional
NOTE
l After the IMA group is created, you can add the IMA links in the IMA group.
l The IMA links and the matching IMA group should be configured on the same baseboard or subboard.
l The E1/T1 ports used by the ATM link, UNI link, fractional ATM link, timeslot cross and CES link
should not conflict.
l A maximum of four IMA groups can be configured on the same baseboard or E1 coverboard. Each
channelized optical coverboard can be configured with up to two IMA groups.
l Each channelized optical coverboard can be configured with a maximum of 63 IMA links. Each IMA
group can be configured with up to 32 IMA links.
l The total number of IMA groups, UNI links and Fractional ATM links on the same baseboard or E1
coverboard does not exceed eight.
l The total number of IMA links, UNI links and Fractional ATM links on the same baseboard or E1
l The total number of IMA groups and UNI links on the same channelized optical subboard does not
exceed two.
Prerequisite
l The NDTI/NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the
Boards in the Baseband Subrack (Initial).

NodeB
l The BBU of the distributed NodeB is configured, as described in 6.4.2 Adding a BBU
(Initial).
Preparation
Table 6-29 Negotiation and planned data of the IMA group and IMA links
Data

only the NUTI)
Sub-board SubBdType Type of the sub-board where the E1/ Channelle

type T1 port used by the IMA link is d
located Optional parameters: CoverBoa
l Baseboard rd
IMA group IMAId l When SubBdType is BaseBoard, 0

ID the value range is 0 through 3.
l When SubBdType is E1 Internal
CoverBoard, the value range is 0 planning
through 3.
through 1.
Transmit IMATxFram Longer transmit frame can enhance D128

frame eLength transmission efficiency but reduces
length error sensitivity. Therefore, the
default value is recommended.
l D32
l D64
l D128
l D256

NodeB

Data
Minimum IMAMinAct Threshold for identifying the 1

active links iveLinks availability of the IMA group For
example, if the value is 3, there are at
least three active IMA links in an
IMA group and thus this group is
available. If there are less than three
active links, the IMA group is
unavailable.
l When SubBdType is BaseBoard,
through 8.
through 32.
Differentia IMADiffMa Different transmission links in an 25

l maximum xDelay IMA group may result in different
delay transmission delays. Thus, there is a
change in the relative delay between
links, which is called link differential
delay. The LODS alarms are reported
when the link differential delay
occurs.

codes.)
Timeslot TimeSlot16 The channelized optical sub-board DISABLE

16 support does not support this function.
l ENABLE
l DISABLE
After this parameter is enabled, the
bandwidth of each IMA link in the
IMA group is added by 64 kbit/s.

NodeB

Data
Link LinkNo Number of the E1/T1 ports for the 0, 1, 2 Negotiati

number links in an IMA group. on with
l When SubBdType is BaseBoard, the
the value range is 0 through 7. destinati
on
through 7.
through 62.
HSDPA HsdpaSwitc Optional parameters: AUTO_A

switch h l SIMPLE_FLOW_CTRL: Based DJUST_F
account.
is recommended that the RNC be Internal
used in compliance with the R6 planning
protocol.


NodeB

Data

Procedure
l Add the IMA group and the IMA link individually.
3. Select a physical NodeB, and then click . The NodeB ATM Transport Layer
window is displayed.
4. Click ATMPort, and then click the IMA tab. The tab page is displayed, as shown in
Figure 6-40.
Figure 6-40 Configuring the IMA group and the IMA link individually
5. Select SubrackNo, and click . The Search Iub Board window is displayed, as
shown in Figure 6-41.

NodeB
Figure 6-41 Search Iub Board window
6. Select one interface board for the macro NodeB or a BBU for the distributed NodeB,
and click OK to return to the NodeB ATM Transport Layer window. Then, click
to add an IMA group.

7. Select LinkNo, and click . The Search E1/T1 Port window is displayed. Select
an E1/T1 port, and then click OK to return to the NodeB ATM Transport Layer
window. Click to add an IMA link.

l Add UNI groups and links in bulk.
1. In the NodeB ATM Transport Layer window, click . The NodeB

ATM Bulk Link CM window is displayed, as shown in Figure 6-42.

NodeB
Figure 6-42 Configuring the IMA links in batches

configuration
1 IMA group list
2 Available E1/T1 port on the interface board where the IMA

group is configured
3 E1/T1 port assigned to the IMA link on the interface board

where the IMA group is configured
2. In area 1, select an IMA group; in area 2, select an E1/T1 port, and then click
to add an IMA link.
----End
Adding UNI Links (Initial)

The UNI is a transmission mode over the TC sub-layer of the ATM physical layer. A UNI link
uses all the timeslots of an E1/T1 port. This describes how to add UNI links.

Mandatory/ Optional
Optional

NodeB
NOTE
l The E1/T1 ports used by the ATM link, UNI link, fractional ATM link, timeslot cross and CES link
should not conflict.
l The total number of IMA groups, UNI links and Fractional ATM links on the same baseboard or E1
l The total number of IMA links, UNI links and Fractional ATM links on the same baseboard or E1
l The total number of IMA groups and UNI links on the same channelized optical subboard does not
exceed two.
Prerequisite
(Initial).
Preparation
Table 6-31 Negotiation and planned data of the UNI links

Data
Slot No. SlotNo Number of slot where the NDTI 12

or NUTI is held (Slots 14 and 15
hold only the NUTI)
Sub-board SubBdType Type of the sub-board where the BaseBoard

type E1/T1 port is located by the UNI Internal
link Optional parameters: planning
l Baseboard
l E1 CoverBoard: E1
coverboard

NodeB

Data
Link LinkNo Number of the E1/T1 ports for 3 Negotiation

number UNI links with the
l When SubBdType is destination
BaseBoard, the value range is
0 through 7.
CoverBoard, the value range is
0 through 7.
l When SubBdType is
Channelled CoverBoard, the

codes.)
Internal
Timeslot TimeSlot16 The channelized optical sub- DISABLE planning
16 support board does not support this
function. Optional parameters:
l ENABLE
l DISABLE
After this parameter is enabled,
the bandwidth of the UNI link is
added by 64 kbit/s.

NodeB

Data
HSDPA HsdpaSwitc Optional parameters: AUTO_AD

switch h l SIMPLE_FLOW_CTRL: JUST_FLO
Based on the configured Iub W_CTRL
bandwidth and the bandwidth
occupied by R99 users, traffic
is allocated to HSDPA users
restriction is taken into
account.
l AUTO_ADJUST_FLOW_CT
RL: According to the flow
control of
SIMPLE_FLOW_CTRL,
users when the delay and
packet loss on the Iub interface
are taken into account. The
RNC uses the R6 switch to
recommended that the RNC be
protocol.
l NO_FLOW_CTRL: The
NodeB does not allocate
bandwidth according to the
configuration or delay on the
Iub interface. The RNC
allocates the bandwidth
the Uu interface reported by
the NodeB. To perform this
function, the reverse flow
control switch must be enabled
by the RNC.

threshold this threshold, you can infer that
the link is not congested.


NodeB
Procedure
l Add the IMA group and the IMA link individually.
4. Click ATMPort, and then click the UNI tab. The tab page is displayed, as shown in
Figure 6-43.
Figure 6-43 Configure the UNI links individually.
5. Select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select
an E1/T1 port, and then click OK to return to the NodeB ATM Transport Layer
window. Click to add an UNI link.

l Add UNI groups and links in bulk.
1. In the NodeB ATM Transport Layer window, click . The NodeB

ATM Bulk Link CM window is displayed, as shown in Figure 6-44.

NodeB
Figure 6-44 Configure the UNI links in batches.

configuration
1 Available E1/T1 port for the UNI link on the configured Iub
interface board
2 E1/T1 port assigned to the UNI link
2. In area 1, select an E1/T1 port, and then click to add one UNI link.
----End
Adding Fractional ATM Links (Initial)

The fractional ATM is a transmission mode over the TC sub-layer of the ATM physical layer
and it is an exceptional case of the UNI link. This describes how to add fractional ATM links.

Mandatory/ Optional
Optional

NodeB
NOTE
l The Fractional ATM link can be configured on only the E1/T1 port 0 through 1 on the baseboards in
slots 12 through 15.
l One E1/T1 port can be configured with multiple Fractional ATM links if the timeslots occupied by the
links do not conflict.
l The total number of IMA groups, UNI links and Fractional ATM links on the same baseboard does
not exceed eight.
l The total number of IMA links, UNI links and Fractional ATM links on the same baseboard does not
exceed eight.
Prerequisite
(Initial).
Preparation
Table 6-33 Negotiation and planned data of the fractional ATM links

Data

only the NUTI)
Value range: 12 through 15 Internal
planning
Sub-board SubBdType Type of the sub-board with the E1/ BaseBoar
type T1 port available for the fractional d
ATM link Optional parameters:
Baseboard
Port No. E1T1No Number of the E1/T1 port available 0 Negotiatio

for the fractional ATM link n with the
Value range: 0 through 1 destinatio
n
Link LinkNo Value range: 0 through 7 1 Internal

number planning
Timeslots TSBitMap The fractional ATM link provides TS24 to

timeslots for the 3G equipment. If TS31 Negotiatio
port 0 is configured, the timeslots n with the
must be reserved for timeslot cross destinatio
connection. n
Value range: TS1 to TS31

NodeB

Data

codes.)

bandwidth restriction is taken
into account.
l AUTO_ADJUST_FLOW_CTR
L: According to the flow control
of SIMPLE_FLOW_CTRL,
users when the delay and packet
loss on the Iub interface are taken
into account. The RNC uses the
R6 switch to perform this Internal
function. It is recommended that planning
the RNC be used in compliance
with the R6 protocol.
the Uu interface reported by the
NodeB. To perform this
function, the reverse flow control
switch must be enabled by the
RNC.



NodeB
Procedure
displayed.
Step 3 Select a physical NodeB, and then click . The NodeB ATM Transport Layer window is
displayed.
Step 4 Click ATMPort, and then click the Fractional ATM tab. The tab page is displayed, as shown
in Figure 6-45.
Figure 6-45 Adding a fractional ATM link
Step 5 Select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select an E1/
T1 port, and click OK to return to the NodeB ATM Transport Layer window.
Step 6 Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the
timeslot to be used, and then click OK to return to the NodeB ATM Transport Layer window.
NOTE
The CME automatically filters the timeslot that is already occupied or reserved on the same E1/T1 port.
The available timeslots appear yellow. The used timeslots appear dark green.
Step 7 Configure other parameters based on the prepared data, and then click to add fractional
ATM links.
----End

NodeB
Adding SDT CES or UDT CES Link (Initial)

The Circuit Emulation Service (CES) provides the transmission channel for GSM services to be
transmitted over the 3G network. The CES links use either Structured Data Transfer (SDT) mode
or Unstructured Data Transfer (UDT) mode. This describes how to configure the SDT CES or
UDT CES link. The Circuit Emulation Service (CES) provides the transmission channel for
GSM services to be transmitted over the 3G network. The CES links use either Structured Data
Transfer (SDT) mode or Unstructured Data Transfer (UDT) mode. This describes how to
configure the SDT CES or the UDT CES link. The SDT CES and the UDT CES are only
configured in the macro NodeB.

Mandatory/ Optional
Optional
NOTE
l The SDT CES and UDT CES can be configured only on E1/T1 0 through 1 of the NDTI baseboard.
l The SDT CES and the UDT CES exclusively occupy an E1/T1 port.
l The bandwidth of the SDT or UDT CES link must be lower than that of the physical bearer link. The
UDT CES link occupies relatively high bandwidth. Only the IMA link can be used as the physical
bearer link.
l The formula (unit: kbit/s, each cell has 53 bytes) to calculate the CES links is as follows:
l UDT CES: 64 x 32 x bytes of a cell/partial fill rate
l SDT CES: 64 x selected timeslots except for slot 0 x bytes of a cell/partial fill rate
Prerequisite
l The NUTI of the macro NodeB is configured, as described in 6.2.2 Adding the Boards in
the Baseband Subrack (Initial).
Preparation
Table 6-34 Negotiation and planned data of the SDT CES

Data Name
Port type Type Type of the interface that carries the FRAATM
SDT CES channels Optional
parameters:
l FRAATM
l IMA Internal
l UNI planning
l STM1
No. Value range: 12 through 13

NodeB

Data Name

type SDT CES channel Optional

No. the SDT CES channel
Partial fill PFL ATM cell has 48-byte payloads. 47

level Except for the first byte, the other 47
bytes can be used to transmit timeslot
signals. Each timeslot occupies one
byte. The number of filling bytes is
that of valid bytes filled in each ATM
cell.
Value range: 4 through 47, and the
value should be greater than the
number of selected timeslots except
for slot 0.
Timeslots TSBitMap Timeslot 0 is unavailable. TS1 to

Value range: TS1 to TS31 TS7

only the NUTI)
Destinatio SubBdTyp Type of the sub-board where the BaseBoar

board type the SDT CES channel Optional
parameters:
l Baseboard

NodeB

Data Name
Destinatio E1T1No Number of the destination E1/T1 port 0

n port No. for the SDT CES channel (This
parameter is valid only when Type is
set to FRAATM or UNI).
is 0 through 7.
through 7.
Link No./ LinkNo/ Number of the fractional ATM or UNI 0

IMA ID IMAId link, of the IMA group, or of the STM1
optical port that carries the SDT CES
channel.
is 0 through 7.
through 7.
through 3.

NodeB

Data Name


255.
127.
Table 6-35 Negotiation and planned data of the UDT CES

Data Name
UDT CES channel Optional
parameters:
l IMA
l STM1
No. Value range: 12 through 13 Internal
planning
type UDT CES channel Optional

No. the UDT CES channel

NodeB

Data Name
Partial fill PFL The value of the partial fill level 47

level affects both the transmission
bandwidth and the transmission delay.
When the value reaches the maximum
of 47, the transmission bandwidth is
not affected, and the transmission
delay reaches the maximum value;
when the value is smaller than 47, the
transmission bandwidth equals to the
original transmission bandwidth x (53/
PFL), and the transmission delay is
reduced. In order not to affect the
transmission bandwidth, set the
default value to 47.
Tx Clock TxClockM Optional parameters: ACM

Mode ode l NOACM (non-adaptive clock
mode)
l NOACM (adaptive clock mode)

only the NUTI)
Destinatio SubBdTyp Type of the sub-board where the Channelle

board type the UDT CES channel Optional CoverBoa
parameters: rd
l Baseboard

NodeB

Data Name
Optical LinkNo/ Number of the IMA group or STM1 0

port No./ IMAId optical port that carries the UDT CES
IMA ID channel.
through 3.


255.
127.
Procedure
l Configure the SDT CES links.
4. Click Network, and then click the SDT tab. The tab page is displayed, as shown in
Figure 6-46.

NodeB
Figure 6-46 Configuring the SDT CES links

configuration
1 Physical bearer link
2 SDT CES configuration area
5. In area 1, select a physical bearer link; In area 2, select SubrackNo and then click
, the Search E1/T1 Port window is displayed. Select an E1/T1 port, and click
OK to return to the NodeB ATM Transport Layer window.
NOTE
The SDT and UDT CES each inclusively occupies an E1/T1 port, and thus the CME
automatically filters the E1/T1 port that is already used by the UDT CES link.
6. Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed.
Select the timeslot to be used, and then click OK to return to the NodeB ATM
Transport Layer window.
NOTE
The CME automatically filters the timeslot that is already occupied or reserved on the same
E1/T1 port. The available timeslots appear yellow. The used timeslots appear dark green.
7. Configure other parameters based on the prepared data, and then click to add an
SDT CES link.
l Configure the UDT CES links.
1. In the NodeB ATM Transport Layer window, click the UDT tab, as shown in Figure
6-47.

NodeB
Figure 6-47 Configuring the UDT CES links

configuration
1 Physical bearer link (The system automatically filters the

IMA link.)
2 UDT CES configuration area
2. In area 1, select an IMA link as the physical bearer link providing bandwidth for the
UDT link. In area 2, select SubrackNo, and click . The Search E1/T1 Port window
is displayed. Select an E1/T1 port, and click OK to return to the NodeB ATM
NOTE
The SDT and UDT CES each inclusively occupies an E1/T1 port, and thus the CME
automatically filters the E1/T1 port that is already used by the SDT CES link.
3. Configure other parameters based on the prepared data, and then click to add an
SDT CES link.
----End
Adding a Timeslot Cross Channel (Initial, over ATM)


NodeB
Mandatory/ Optional
Optional
NOTE
l The timeslot cross channel can be configured on only the E1/T1 port 2 through 3 on the baseboards in
l No IMA or UNI links can be added to the source E1/T1 link where the timeslots cross channel is
configured.
l The source and destination ports of the timeslot cross channel must be different, and the same E1/T1
port cannot be repeatedly used.
l When both E1/T1 2 and 3 use the timeslot cross channel, the timeslots of both links do not conflict.
That is, the fractional ATM link timeslot that is configured to E1/T1 0 cannot conflict with the fractional
ATM link timeslot that is configured to either E1/T1 2 or 3.
Prerequisite
The negotiation and planned data is ready.
Preparation
Data Name



timeslots
Internal

cross links
Value range: 0

NodeB
Procedure
displayed.
displayed.
Step 4 Click Network, and then click the TSCross tab. The tab page is displayed, as shown in Figure
6-48.
Figure 6-48 Configuring the timeslot cross channel

configuration
1 Area for the destination port
2 Configuration area of the timeslot cross channel
Step 5 In area 1, select a destination port; In area 2, select TScrossNo, and then click , the Search
E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB
ATM Transport Layer window.

NodeB
NOTE
Step 7 Configure other parameters based on the prepared data, and then click to add a timeslot
cross channel.
----End
6.5.2 Adding Transmission Resource Group (Initial, over ATM)

bandwidth of the physical link to the transmission resource group for carrying the data on the
control plane, the user plane, and the OM channel. Each group occupies one portion of the
bandwidth and has separate access control, congestion control and HSPA flow control.

Mandatory/ Optional. The configuration is required only when the SAAL links, the AAL2
Optional PATH or the OMCH links join the transmission resource group.
NOTE
l Each physical link can be configured with a maximum of four transmission groups, that is, the total
number of transmission groups over ATM and IP.
l Each Iub interface board or BBU supports a maximum of 16 transmission resource groups over ATM
or 8 transmission resource groups over IP.
l The transmit bandwidth of the transmission resource group should be not greater than the idle
bandwidth at the physical links.
Prerequisite
The physical layer data is configured, refer to 6.5.1 Adding Links at the Physical Layer
(Initial).
Preparation
Table 6-40 Negotiation and planned data of the transmission resource group (over ATM)

Data Name e
parameters:
l FRAATM Internal
planning
l IMA
l UNI
l STM1

NodeB

Data Name e

group
number
Transmit TxBandwidt The transmit bandwidth of the resource 5000

bandwidth h group cannot exceed the bandwidth of
the port to which the resource group
belong.
Receive RxBandwid Receive bandwidth of the resource 5000

bandwidth th group.
Procedure
displayed.
displayed.
Step 4 Click RSCGroup, as shown in Figure 6-49.

NodeB
Figure 6-49 Configuring the transmission resource group

configuration
1 Configured physical link list
2 Configuration area for the transmission resource group
Step 5 In area 1, select a physical bearer link; In area 2, select RscgrpNo and then click .
Step 6 Configure other parameters based on the prepared data, and then click to add a transmission
resource group over ATM.
----End
6.5.3 Adding SAAL Links (Initial)

This describes how to add SAAL links. The SAAL links are used to carry the NBAP and ALCAP
when the Iub interface is over ATM.

Optional

NodeB
NOTE
l The PCR value should be greater than the SCR value for the SAAL.
l The PCR value of the SAAL link should be less than or equal to the available bandwidth of the physical
link that carries this SAAL link.
l If the SAAL is added to the transmission resource group, the PCR of the SAAL should be less than or
equal to the bandwidth of the transmission resource group.
Prerequisite
l The physical layer link is configured, refer to 6.5.1 Adding Links at the Physical Layer
(Initial).
l The transmission resource group is configured, refer to 6.5.2 Adding Transmission
Resource Group (Initial, over ATM).
Preparation
Table 6-42 Negotiation and planned data of the SAAL links

Data Name e
SAAL links Optional parameters:
l FRAATM
l IMA
l UNI
l STM1

channel SAAL links. Negotiati
identifier on with
Value range:
the
l Macro NodeB: 0 through 31 (six destinatio
successive values from 0 to 31) n

channel SAAL links.

NodeB

Data Name e
Service ServiceTyp When this parameter is set to CBR or RTVBR

type e UBR, you need to set only the
parameter PCR; when this parameter
is set to RTVBR or NRTVBR, you
need to set parameters SCR and PCR;
when this parameter is set to UBR+,
you need to set parameters PCR and
MCR.
l CBR (applicable to the CES
channel)
of the SCR or MCR.
is 31 to 6760.
Minimum MCR The value of the MCR of the ATM -

when the service type is UBR+.
Sustainable SCR The value of the SCR of the ATM 180

NRTVBR

NodeB

Data Name e
Join the JoinRscgrp Specify whether this link should be ENABL

resource added to the resource group. Optional E
group parameters:
l DISABLE
Internal
l ENABLE planning
Procedure
displayed.
displayed.
Step 4 Click SAAL, as shown in Figure 6-50.
Figure 6-50 Configuring the SAAL

NodeB

configuration
2 Transmission resource group carried on the corresponding physical

link
3 Configuration area for the SAAL links
Step 5 In area 1, select the physical bearer link. Then the transmission resource group carried on this
physical link is displayed in area 2. In area 3, click SAALNo, and click .
Step 6 (Optional) Set JoinRscgrp to ENABLE. Select RscgrpNo, and click , the Search Resource
Group window is displayed. Select a transmission resource group, and click OK to return to
the NodeB ATM Transport Layer window.
NOTE
The physical bearer type of the transmission resource group is identical with that of the SAAL link. Figure
6-50 and Table 6-43 show the matching relation.
Step 7 Configure other parameters based on the prepared data, and then click to add an SAAL
link.
----End
6.5.4 Adding an NBAP (Initial)

Port (CCP). These two ports are carried on the SAAL links.

Optional
NOTE
l One NodeB can be configured with the active and the standby NCPs or CCPs.
l Each SAAL link can be configured with only one NCP or CCP.
l The active and the standby NCPs or CCPs should be configured on different links. For example, if the
active one is configured on the SAAL, the standby one should be configured on the SCTP. Otherwise
the configuration is invalid.
Prerequisite
The SAAL links are configured, as described in 6.5.3 Adding SAAL Links (Initial).

NodeB
Preparation
Table 6-44 Negotiation and planned data of the NBAP

Name e
Port type PortType Optional parameters: NCP

Internal
l NCP
planning
l CCP
SAAL SAALNo SAAL number that carries the 1 Negotiati

number NCP on with
NCP destinati
on

planning
l SLAVE
l MASTER
Port type PortType Optional parameters: CCP

Internal
l NCP
planning
l CCP

on with
CCP SAAL SAALNo SAAL number that carries the 2 destinati
number CCP on

planning
l SLAVE
l MASTER

NodeB
Procedure
displayed.
displayed.
Step 4 Click NBAP, as shown in Figure 6-51.
Figure 6-51 Configuring the NCP and the CCP

configuration
1 Configured SAAL link list
2 Configuration area of the NBAP
Step 5 In area 1, select an SAAL link; in area 2, select PortType and then click . Configure related
parameters based on prepared data, and then click to add an NCP link.

NodeB
Step 6 In area 1, select an SAAL link; in area 2, select PortType and then click . Configure related
parameters based on prepared data, and then click to add an CCP link.
----End
6.5.5 Adding an ALCAP (Initial)

This describes how to configure an AAL2 node to the NodeB so that the ALCAP is added at the
NodeB. The ALCAP allocates the micro channels of the AAL2 path.

Optional
NOTE
l One NodeB can be configured with multiple adjacent nodes.

l One NodeB can be configured with either one end node or one exchange node.
l The ATM address must begin with 39/45/47 and end with that in accordance with the protocol.
l The distributed NodeB can be configured with only the nodes of type.
Prerequisite
l The SAAL links are configured, as described in 6.5.3 Adding SAAL Links (Initial).
l An exchange node cannot be configured on the SAAL over the NDTI. Therefore, you need
to configure the SAAL over the NUTI before you configure the exchange node if required.
Preparation
Table 6-46 Negotiation and planned data of the ALCAP

Data Name
Node type NodeType The exchange node must be configured LOCAL

before configuring the adjacent node.
The exchange node cannot be carried on
the SAAL link on the NDTI. Optional
l LOCAL (peer node) planning
l HUB (switch node, indicating that
the NodeB has a lower-level NodeB)
l ADJNODE (adjacent node,
indicating the lower-level NodeB)

NodeB

Data Name
Adjacent ANI Identify an adjacent node. This -

node parameter is valid only when the
identifier parameter NodeType is set to
ADJNODE.
Network NSAP The full name is: Net service access H'390101
service point. 01010101
access When the NodeB uses ATM 01010101
point transmission, the NSAP is the address 01010101
of the NodeB that is connected to the 01010101
AAL2 path. The address is a 01
hexadecimal with a length of 20 bytes
(excluding the prefix H').
SAAL SAALNo SAAL number that carries the ALCAP 3

Procedure
displayed.
displayed.
Step 4 Click ALCAP, as shown in Figure 6-52.

NodeB
Figure 6-52 Adding the AAL2 node

configuration
1 Configured SAAL link list
2 Configuration area of the ALCAP
Step 5 In area 1, select an SAAL link; in area 2, select NodeType and then click .
Step 6 In the drop-down list, select the node type of the AAL2 link, and configure other parameters
based on prepared data. Click to add an AAL2 node.

NOTE
l The NodeType is set to :NSAP must be the same as the NSAP of the logical NodeB created at the
RNC side.
l The NodeType is set to :NSAP can be configured only at the NodeB side.
l The NodeType is set to :NSAP needs no configuration.
----End
6.5.6 Adding AAL2 Path Data (Initial)

This describes how to add AAL2 PATH data over ATM. The AAL2 path carries the user plane
data between the RNC and other equipment.

Optional

NodeB
NOTE
l Each NDTI board can be configured with a maximum of 16 AAL2 PATH; Each NUTI board can be
configured with a maximum of 32 AAL2 PATH.
l The sum of the IP paths and AAL2 paths configured on one NodeB should be less than or equal to 16.
l For an AAL2 path, the PCR value should be greater than the SCR value.
l The PCR value of the AAL2 path should be less than or equal to the available bandwidth of the physical
link that carries the AAL2 path.
l If a physical port is configured with the transmission resource groups, all the AAL2 paths should be
added to a certain transmission resource group, and the PCR of the AAL2 path should be less than the
bandwidth of the transmission resource group.
l If a physical port is configured with AAL2 path links or IP path links, and the links are not in a resource
group. No transmission resource group can be added to this physical port.
Prerequisite
l The AAL2 nodes are configured. For details, refer to 6.5.5 Adding an ALCAP (Initial).
Preparation
Table 6-48 Negotiation and planned data of the AAL2 PATH

Data Name
AAL2 PATH Optional parameters:
l FRAATM
l IMA
l UNI
l STM1
PATH type PathType Type of the AAL2 path, which RT Negotiat

indicates the desired service type ion with
carried on the path. Optional the
parameters: RT, NRT, HSPA_RT, destinati
HSPA_NRT on

channel AAL2 path.
l Macro NodeB: 0 through 31 (six

NodeB

Data Name

channel AAL2 path.
Service ServiceTyp Optional parameters: RTVBR

type e l CBR (applicable to the CES
channel)
the SCR. This parameter should be one
of the bandwidth parameters for the
BaseBoard, and the service type is
CBR or UBR, the value range is 30
through 15800.
Unchannelled CoverBoard, and the
service type is RTVBR,
NRTVBR,or UBR+, the value range
is 31 through 15800.

NodeB

Data Name

NRTVBRThis parameter should be
one of the bandwidth parameters for the
l When sub-board type is BaseBoard,
Unchannelled CoverBoard, the
Received RCR This parameter must be consistent with 2048

cell rate the downlink bandwidth configured by
the RNC. This parameter acts as an
important factor in flow control by the
NodeB receive bandwidth. Whether or
not this parameter is correctly
configured will affect the effect of flow
control.

group parameters:
l DISABLE
Internal
l ENABLE planning
Procedure
displayed.

NodeB
displayed.
Step 4 Click AAL2PATH, as shown in Figure 6-53.
Figure 6-53 Configuring the AAL2 PATH

configuration
1 Configured AAL2 node list

link
4 Configuration area for the AAL2 path
Step 5 In area 1, select an AAL2 node; in area 2, select the physical bearer link. Then the transmission
resource group carried on this physical link is displayed in area 3. In area 4, click
AAL2PathId, and click .
NOTE
The physical bearer type of the resource group is the same as that of the AAL2 PATH. Figure 6-53 and
Table 6-49 show the matching relation.

NodeB
Step 7 Configure other parameters based on the prepared data, and then click to add an AAL2
path link.
NOTE
l If the service type is either RTVBR or NRTVBR, the value of the parameter should meet the following
condition: 0 < SCR < PCR ≤ RSCGRP configuration bandwidth.
l If the service type is UBR+, the value of the parameter should meet the following condition: MCR<PCR
and 0<MCR<PCR<=bandwidth configured for the RSCGRP
----End
6.5.7 Adding an OMCH of the NodeB (Initial, over ATM)

This describes how to add an Operation and Maintenance Channel (OMCH) of the NodeB.

Mandatory/ Optional
Optional
NOTE
l In ATM transport mode, only one OMCH can be configured. It can be either active or standby. If the
configured OMCH is active, it takes effect as the active channel; if the configured OMCH is standby,
the configuration does not take effect.
l Local IP addresses of two OMCH channels cannot be on the same network segment.
l The local IP address and the destination IP address of the OMCH must be in the same network segment.
l For an OMCH, the PCR value should be greater than the SCR value.
l The PCR value of the OMCH should be less than or equal to the available bandwidth of the physical
link that carries the OMCH.
l If the OMCH is added to the transmission resource group, the PCR of the OMCH should be less than
or equal to the bandwidth of the transmission resource group.
Prerequisite
l The physical layer link is configured, refer to 6.5.1 Adding Links at the Physical Layer
(Initial).

NodeB
Preparation
Table 6-50 Negotiation and planned data of the OMCH (ATM)

Name
Port type Type Type of the interface that carries the UNI
OMCH Optional parameters:
l FRAATM
l IMA
l UNI
l STM1
Virtual VPI Virtual channel for the OMCH 1

identifier
l Macro NodeB: 1 or within the VPI
range of the actual board
configuration
Virtual VCI Virtual channel for the OMCH 33

identifier
Negotiati
l Distributed NodeB: 32 through 127 on with
Service type ServiceTy Optional parameters: CBR the
pe destinati
l CBR (applicable to the CES on
channel)
the SCR.
is 31 to 6760.

NodeB

Name
Sustainable SCR The value of the SCR of the ATM -

NRTVBR
Local IP LocalIP IP address for NodeB remote 10.1.2.10

address of maintenance
the OMCH
Destination DestIP Destination IP address for NodeB 10.1.2.1

IP address remote maintenance, that is, the IP
of the address configured on the ATM
OMCH interface board at the RNC.
Destination DestIPMas Subnet mask of the destination IP 255.255.

subnet mask k address for NodeB remote maintenance 255.0
of the
OMCH

group parameters:
l DISABLE
l ENABLE
Resource RscgrpNo Number of the ATM transmission 2 Internal

group resource group planning
Flag Flag Master/slave flag for the remote OM MASTE

channels Optional parameters: R
l SLAVE
l MASTER
Procedure
displayed.

NodeB
displayed.
Step 4 Click OMCH, as shown in Figure 6-54.
Figure 6-54 Adding an OMCH

configuration

link
3 OMCH configuration area
Step 5 In area 1, select the physical bearer link. Then the transmission resource group carried on this
physical link is displayed in area 2.
Step 6 In area 3, select LocalIP, and click , the LocalIP & Mask dialog box is displayed. Set the
peer IP address and the mask of the OMCH, and then click OK to return to the NodeB ATM
Step 7 Select DestIP, and click . The IP and IP Mask dialog box is displayed. Set the peer IP address
and the mask of the OMCH, and then click OK to return to the NodeB ATM Transport
Layer window.

NodeB
NOTE
The physical bearer type of the resource group is identical with that of the OMCH. Figure 6-54 and Table
6-51 show the matching relation.
Step 9 Configure other parameters based on the prepared data, and then click to add an OMCH
link.
----End
6.5.8 Adding a Treelink PVC (Initial)

This describes how to add a treelink PVC to the Hub NodeB. When the NodeB are cascaded,
the treelink PVC added to the Hub NodeB can provide the data transmission channel between
the upper-level NE and the lower-level NE.

Mandatory/ Optional
Optional
NOTE
l The source port and the destination port must be different.

l For the treelink PVC, the PCR value should be greater than the SCR value.
l The bandwidth of the treelink PVC should be less than or equal to the bandwidth of the physical port
(such as the types of IMA group and UNI link) that bears the treelink PVC.
Prerequisite
The physical layer link is configured, refer to 6.5.1 Adding Links at the Physical Layer
(Initial).
Preparation
Table 6-52 Negotiation and planned data of the treelink PVC

Data e
Source port SourceType Type of the interface that carries the FRAAT
type source port of the treelink PVC M
l FRAATM Internal
planning
l IMA
l UNI
l STM1

NodeB

Data e
Destinatio DestinationT Type of the interface that carries the UNI

n port type ype destination port of the treelink PVC
l FRAATM
l IMA
l UNI
l STM1
ByPassMo ByPassMode When the NodeB is powered off or DISABL

de exceptions occur to the NodeB, the E
E1/T1 can be connected to the lower
node by switching to the
ByPassMode. The treelink PVC is set
using the ByPassMode that thus
guarantees the connection between
the lower node and the RNC. Optional
parameters:
l DISABLE (disable the
ByPassMode)
l ENABLE (enable the
ByPassMode)
Source VPI SourVPI Virtual channel used by the upper 1

level network link
l For the VP switching, the source
port VPI must be beyond the VPI
value cannot be 1.
l For the VC switching, the source
port VPI must be within the VPI
value can be 1. Negotiati
l For the VC switching, the SourVPI on with
and the DestVPI must meet the the
conditions of the source board and destinatio
the destination board respectively. n
Source SourVCI Identifier of the virtual channel for the 33

VCI upper-level links. This parameter is

NodeB

Data e
Destinatio DestVPI Virtual channel used by the lower- 1

n VPI level network link
l For the VP switching, the
destination port VPI must be
beyond the VPI configured to the
board, and the value cannot be 1.
l For the VC switching, the
destination port VPI must be within
the VPI configured to the board,
and the value can be 1.
Destinatio DestVCI Identifier of the virtual channel for the 32

n VCI lower-level links. This parameter is
Service ServiceType Optional parameters: RTVBR

type l RTVBR
l NRTVBR
of the SCR.
l When the service type is UBR, the
value range is 30 to 6760.
NRTVBR or UBR+, the value
range is 31 to 6760.

NodeB

Data e

NRTVBR
Procedure
displayed.
displayed.
Step 4 Click Network, and then click the TreeLink PVC tab. The tab page is displayed, as shown in
Figure 6-55.
Figure 6-55 NodeB ATM Transport Layer (Treelink PVC) window

NodeB

configuration
1 Source port list: shows all configured physical links
2 Destination port list: shows all configured physical links
3 Treelink PVC configuration area
Step 5 Select a source port in area 1; select a destination port in area 2.
Step 6 In area 3, select VCXNo, and then click to add a TreeLink PVC. The CME automatically
allocates parameters SourVPI, SourVCI, DestVPI, and DestVCI. Set the other parameters
such as VCXType, ServiceType, PCR, and SCR. Click to add a treelink PVC.
NOTE
l For the VP switching, the source port VPI must be out of the VPI range configured to the board, and
the value cannot be 1; The destination port VPI must be out of the VPI range configured to the board,
and the value cannot be 1.
l For the VC switching, the source port VPI must be within the VPI range configured to the board, and
the value can be 1; the destination port VPI must be within the VPI range configured to the board, and
the value can be 1.
----End
6.6 Manually Adding Transport Layer Data of the NodeB

(over IP)
This describes how to configure the transport layer data of the NodeB in IP transport mode.
Prerequisite
NOTE
In the TCP/IP protocol, the reserved IP addresses are as follows:

l 10.0.0.0 to 10.255.255.255
l 172.16.0.0 to 172.31.255.255
l 192.168.0.0 to 192.168.255.255
l 127.*.*.*: local loop address
To configure the distributed NodeB, the CME reserves the following IP addresses:
l 10.22.1.*/24: reserved for inter-BBU communication
l 17.21.2.15/16: reserved for DBS3800 or iDBS3800 local maintenance.
To configure the macro NodeB, the CME reserves the following IP addresses:
l 10.22.1.*/24: reserved for communications between the NMPT and the standby NMPT, between
baseband boards, and between the NMPT and the NodeB Iub interface board.
l 17.21.2.15/16: reserved for BTS3812A/BTS3812E/BTS3812AE local maintenance.
The data of the equipment layer of the NodeB is configured. For details, refer to:

NodeB
l 6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial)

l 6.4 Adding Equipment Layer Data of the DBS3800 (Initial)
The process of configuring the NodeB transport layer data over IP is as follows:
6.6.1 Adding a Link at the Data Link Layer (Initial)
This describes how to configure the data at the data link layer of the NodeB. The data link layer
consists of the PPP link, MLPPP link, PPPoE link, IP address of the FE port, and the timeslot
cross channel. You need to configure at least one type from the PPP link, MLPPP link, PPPoE
link, and IP address of the FE port. And you can configure only one type or configure all the
types.
6.6.2 Adding an IP Route (Initial)
This describes how to add an IP route for transmitting the NodeB IP data of the transmission
control plane, the user plane, and the management plane.
6.6.3 Adding SCTP Links (Initial)
This describes how to add SCTP links. The SCTP links are used to carry the IPCP, that is, the
NBAP at the IP transport layer.
6.6.4 Adding an IPCP (Initial)
Port (CCP). These two ports are carried on the SCTP links.
6.6.5 Adding Transmission Resource Group (Initial, over IP)
bandwidth of the physical link to the transmission resource group for carrying the UE data. Each
resource group has its separate access control, congestion control, and HSPA flow control.
6.6.6 Adding IP Path Data (Initial)
This describes how to add an IP PATH for transmitting the user plane data.
6.6.7 Adding an OMCH of the NodeB (Initial, over IP)
This describes how to configure an OMCH of the NodeB in IP transport mode.
6.6.8 Adding A Bound Destination Network Segment to the Transmission Resource Group
(Initial, IP)
This describes how to add a bound destination network segment to the transmission resource
group. All data to the subnet from the port of the transmission resource group will be calculated
in the transmission resource group.
6.6.9 Adding IP Clock Links (Initial)
This describe how to add IP clock links. The NodeB can obtain the clock signals from the clock
server through the IP link.
6.6.10 Modifying IP QoS Data (Initial)
This describes how to modify the signaling and Operation and Maintenance (OM) priorities.
6.6.1 Adding a Link at the Data Link Layer (Initial)

This describes how to configure the data at the data link layer of the NodeB. The data link layer
consists of the PPP link, MLPPP link, PPPoE link, IP address of the FE port, and the timeslot
cross channel. You need to configure at least one type from the PPP link, MLPPP link, PPPoE
link, and IP address of the FE port. And you can configure only one type or configure all the
types.
6.6.1.1 Adding PPP Link Data (Initial)

NodeB
This describes how to add PPP data. This task is optional when the NodeB uses the E1/T1 cables.
6.6.1.2 Adding MLPPP Data (Initial)
The MLPPP group combines multiple PPP links into a logical link.
6.6.1.3 Adding PPPoE Data (Initial)
This describes how to add PPPoE data when multiple NodeBs connect to the RNC through the
Access Concentration (AC) in PPP over Ethernet network topology.
6.6.1.4 Adding DEVIP Data (Initial)
This describes how to add the device IP address to the IP port. The IP ports can be any of the
following types: PPP, MLPPP, or Ethernet.
6.6.1.5 Adding a Timeslot Cross Channel (Initial, over ATM)
Adding PPP Link Data (Initial)


Mandatory/ Optional
Optional
NOTE
l Local IP addresses of various PPP links cannot be on the same network segment.
l Local IP addresses of the PPP link, the MLPPP group, and the PPPoE link cannot be on the same
network segment.
l One E1/T1 port can be configured with multiple PPP links and MLPPP links if the timeslots occupied
by the links do not conflict.
Prerequisite
l The macro NodeB is configured with the NUTI board, and the bearer type of the NUTI is
set to IPV4. For details, refer to 6.2.2 Adding the Boards in the Baseband Subrack
(Initial)
l The distributed NodeB is configured with the BBU, and the bearer type of the BBU is set
to IPV4. For details, refer to 6.4.2 Adding a BBU (Initial).
Preparation
Table 6-54 Negotiation and planned data of the ppp links

Data

NUTI Internal
planning

NodeB

Data
Port No. PortNo Number of the E1/T1 ports for PPP 0

links
Link LinkNo Each PPP link and each MLPPP link 0

number must have a unique number.

authentication)
l CHAP (with CHAP
authentication)

characters
Timeslot TSBitMap A map of the timeslots for PPP links. TS1 to

map The map is presented in binary TS15
format or the chart. If a timeslot is
selected, it is in use. Otherwise, it is
not in use.
Local IP LocalIP Local IP address of the PPP link. 17.17.17.

address When the value is 0.0.0.0, it indicates 111
that the parameter needs to be Negotiati
negotiated with the RNC. on with
the
Destinatio PeerIP Destination IP address of the PPP 17.17.17. destinatio
n IP link 17 n
address l In cascading mode, this parameter
specifies the IP address of a lower-
level cascaded node.
l In non-cascading mode, when the
value is 0, it indicates that the
parameter needs to be negotiated
with an upper-level node.
IP header IPHC Optional parameters: ENABLE

compressi l DISABLE: The IP header of the
on Internal
peer end is not compressed.
planning

NodeB

Data

multiplexi
ng l DISABLE
Maximum MRU Expected value sent from the peer 1500

received end
unit Value range: 128 through 1500

timer of
packet
request
response
Protocol PFC Optional parameters: ENABLE

field l ENABLE
compress
l DISABLE
Address & ACFC Optional parameters: ENABLE

control l ENABLE
field
compress l DISABLE

NodeB

Data

account.
protocol.



NodeB
Procedure
displayed.
Step 3 Select a physical NodeB, and then click . The NodeB IP Transport Layer window is
displayed.
Step 4 Click IPPort, and then click the PPP tab. The tab page is displayed, as shown in Figure 6-56.
Figure 6-56 Adding a PPP link
Step 5 Select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select an E1/
T1 port, and click OK to return to the NodeB IP Transport Layer window.
timeslot to be used, and then click OK to return to the NodeB IP Transport Layer window.
NOTE
Step 7 Select LocalIP , and click , the LocalIP & LocalMask dialog box is displayed. Set the local
IP address and mask for the PPP link, and then click OK to return to the NodeB IP Transport
Layer window.
Step 8 Select PeerIP, and click , the PeerIP dialog box is displayed. Set the local IP address and
mask for the PPP link, and then click OK to return to the NodeB IP Transport Layer window.

NodeB
Step 9 Configure other parameters based on the prepared data, and then click to add a PPP link.
----End
Adding MLPPP Data (Initial)

The MLPPP group combines multiple PPP links into a logical link.

Mandatory/ Optional
Optional
NOTE
l Local IP addresses of various MLPPP groups cannot be on the same network segment.
network segment.
l One E1/T1 port can be configured with multiple PPP links and MLPPP links if the timeslots occupied
by the links do not conflict.
l Each Iub interface board or BBU can be configured with a maximum of four MLPPP groups, and each
MLPPP group can be configured with a maximum of 16 MLPPP links.
Prerequisite
l The macro NodeB is configured with the NUTI board, and the bearer type of the NUTI is
set to IPV4. For details, refer to 6.2.2 Adding the Boards in the Baseband Subrack
(Initial)
l The distributed NodeB is configured with the BBU, and the bearer type of the BBU is set
to IPV4. For details, refer to 6.4.2 Adding a BBU (Initial).
Preparation
Table 6-55 Negotiation and planned data of the MLPPP group and MLPPP links
Data e

NUTI
MLPPP GroupNo MLPPP group number 0

group Value range: 0 through 3
number Internal
planning
authentication)

NodeB

Data e

characters
Local IP LocalIP Local IP address of the MLPPP group 16.16.16.

address 111
Negotiati
Local LocalMask Subnet mask of the local IP address for 255.255.
on with
subnet the MLPPP group 255.0
the
mask
destinati
Destinatio PeerIP Peer IP address of the MLPPP group 16.16.16. on
n IP 16
address
Port No. PortNo Number of the E1/T1 ports for 0

MLPPP links
Link LinkNo Number of the MLPPP link that joins 1 Internal

number the MLPPP group. Each MLPPP and planning
each PPP link must have a unique
number.
Timeslot TSBitMap A map of the timeslots for MLPPP TS24 to Negotiati

map links. The map is presented in binary TS31 on with
format or the chart. If a timeslot is the
selected, it is in use. Otherwise, it is destinati
not in use. on

compressi l DISABLE: The IP header of the E
PPP PPPMux Optional parameters: DISABL Internal

multiframe l ENABLE E planning
multiplexi
ng l DISABLE
Multi-class MCPPP Optional parameters: ENABL

PPP l ENABLE (using the MCPPP) E
l DISABLE (not using the MCPPP)

NodeB

Data e
unit

timer of
packet
request
response
Protocol PFC Optional parameters: ENABL

field l ENABLE E
compress
l DISABLE
Address & ACFC Optional parameters: ENABL

control l ENABLE E
field
compress l DISABLE
HSDPA HsdpaSwitch Optional parameters: AUTO_

switch l SIMPLE_FLOW_CTRL: Based on ADJUST
the configured Iub bandwidth and _FLOW
the bandwidth occupied by R99 _CTRL
interface are taken into account.
The RNC uses the R6 switch to
recommended that the RNC be used
in compliance with the R6 protocol.

NodeB

Data e
not congested.

Procedure
displayed.
displayed.
Step 4 Click IPPort, and then click the MP tab. The tab page is displayed, as shown in Figure 6-57.
Figure 6-57 Adding the MLPPP group and the MLPPP link

NodeB

configuration
1 Configuration area of the MLPPP group
2 Configuration area of the MLPPP links
Step 5 In area 1, select SubrackNo, and click . The Search Iub Board window is displayed, as
shown in Figure 6-58. Select an interface board, and click OK to return to the NodeB IP
Figure 6-58 Search Iub Board window
NOTE
In the Search Iub Board window, the NUTIs configured to slots 12 and 13 are displayed.
IP address and mask for the MLPPP group, and then click OK to return to the NodeB IP
Step 7 Select PeerIP, and click , the PeerIP dialog box is displayed. Set the local IP address and
mask for the MLPPP group, and then click OK to return to the NodeB IP Transport Layer
window.
Step 8 Configure other parameters based on the prepared data, and then click to add an MLPPP
group.
Step 9 In area 2, select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select
an E1/T1 port, and click OK to return to the NodeB IP Transport Layer window.
timeslot to be used, and then click OK to return to the NodeB IP Transport Layer window.

NodeB
NOTE
Step 11 Configure other parameters based on the prepared data, and then click to add an MLPPP
link.
----End
Adding PPPoE Data (Initial)

This describes how to add PPPoE data when multiple NodeBs connect to the RNC through the
Access Concentration (AC) in PPP over Ethernet network topology.

Mandatory/ Optional
Optional
NOTE
l Local IP addresses of various PPPoE links cannot be on the same network segment.
network segment.
l The PPPoE links are configured to FE port 0 or 1 on the NUTI boards of slots 12 through 15.
l The PPPoE link and the ETH link can use the same FE port.
Prerequisite
l The NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the Boards in
(Initial).
Preparation
Table 6-57 Negotiation and planned data of the PPPoE links

Data Name e
Slot No. SlotNo Number of the slot that holds the NUTI 13
Internal
Port No. PortNo Number of the FE port for the PPPoE 0 planning
link

NodeB

Data Name e

tion type l NONAUTH (without authentication) TH

User name UserName This parameter is valid only when -

AuthType is set to PAP or CHAP.
characters
Local IP LocalIP Local IP address of the PPPoE link 12.3.0.1 Negotiati

address on with
Local LocalMask Subnet mask of the local IP address 255.255. the
subnet 255.0 destinati
mask on

compressio l DISABLE: The IP header of the peer E
n end is not compressed.
l ENABLE: The UDP/IP header of the
peer end is compressed.
unit
Internal
Restart RestartTim Value range: 1 through 65535 3000 planning
timer of er
packet
request
response

multiplexi
ng l DISABLE

NodeB

Data Name e
HSDPA HsdpaSwit Optional parameters: AUTO_

switch ch l SIMPLE_FLOW_CTRL: Based on ADJUST
the configured Iub bandwidth and the _FLOW_
bandwidth occupied by R99 users, CTRL
traffic is allocated to HSDPA users
interface are taken into account. The
the R6 protocol.
this function, the reverse flow control
switch must be enabled by the RNC.
not congested.

Procedure
displayed.

NodeB
displayed.
Step 4 Click IPPort, and then click the PPPoE tab. The tab page is displayed, as shown in Figure
6-59.
Figure 6-59 Adding a PPPoE link
Step 5 Select SubrackNo, and click . The Search Ethernet Port window is displayed. Select an
FE port, and click OK to return to the NodeB IP Transport Layer window.
IP address and mask for the PPPoE link, and then click OK to return to the NodeB IP Transport
Layer window.
Step 7 Configure other parameters based on the prepared data, and then click to add a PPPoE link.
----End
Adding DEVIP Data (Initial)

This describes how to add the device IP address to the IP port. The IP ports can be any of the
following types: PPP, MLPPP, or Ethernet.

Mandatory/ Optional
Optional

NodeB
NOTE
l The four IP port types are: ETH, PPP, MLPPP, and PPPoE.
l A maximum of four IP addresses can be added to one IP port.
l IP addresses for different ports cannot be on the same network segment; IP addresses for the same port
can be on the same network segment.
Prerequisite
l The NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the Boards in
(Initial).
l The PPP link, MLPPP group, and the PPPoE link are configured. For details, refer to 6.6.1
Adding a Link at the Data Link Layer (Initial).
Preparation
Table 6-58 Negotiation and planned data of the DEVIP

Data Name e
Slot No. SlotNo Number of the slot that holds the NUTI 13
Port No. PortNo l For the PPP link, the MLPPP group, 0
and the PPPoE link, PortNo
represents the port number for the
configured PPP link, the MLPPP
group, and the PPPoE link.
l For the ETH link, the port value
ranges from 0 to 1.
Internal
Port type PortType The port types consist of the following ETH planning
items:
l ETH: indicates the available FE port
on the NUTI.
l MLPPP: indicates the configured
MLPPP group.
l PPP: indicates the configured PPP
link.
l PPPoE: indicates the configured
PPPoE link.
Local IP LocalIP Local IP address of the device IP 12.11.12. Negotiati

address 12 on with
the
destinatio
n

NodeB

Data Name e
Subnet LocalMask If the network is not divided into 255.255.

mask of the subnets, use the default mask. 255.0
local IP
address
Procedure
displayed.
displayed.
Step 4 Click IPPort, and then click the DEVIP tab. The tab page is displayed, as shown in Figure
6-60.
Figure 6-60 Configuring the DEVIP

configuration
1 Configuration area for the device IP address

NodeB

configuration
2 Configuration area for the VLAN service priority
Step 5 In area 1, select SubrackNo, and click . The Search Ethernet Port window is displayed.
Select an IP port, and click OK to return to the NodeB IP Transport Layer window.
IP address and mask for the device, and then click OK to return to the NodeB IP Transport
Layer window.
Step 7 Click to add the device IP address.
Step 8 (Optional) In area 2, select TrafficType, and click . Then, Set VLAN service priority
mapping according to the actual network planning. Click to save the settings.
----End
Adding a Timeslot Cross Channel (Initial, over ATM)


Mandatory/ Optional
Optional
NOTE
l The timeslot cross channel can be configured on only the E1/T1 port 2 through 3 on the baseboards in
l No IMA or UNI links can be added to the source E1/T1 link where the timeslots cross channel is
configured.
l The source and destination ports of the timeslot cross channel must be different, and the same E1/T1
port cannot be repeatedly used.
l When both E1/T1 2 and 3 use the timeslot cross channel, the timeslots of both links do not conflict.
That is, the fractional ATM link timeslot that is configured to E1/T1 0 cannot conflict with the fractional
ATM link timeslot that is configured to either E1/T1 2 or 3.
Prerequisite
The negotiation and planned data is ready.

NodeB
Preparation
Data Name



timeslots
Internal

cross links
Value range: 0
Procedure
displayed.
displayed.
Step 4 Click Network, and then click the TSCross tab. The tab page is displayed, as shown in Figure
6-61.

NodeB
Figure 6-61 Configuring the timeslot cross channel

configuration
1 Area for the destination port
2 Configuration area of the timeslot cross channel
Step 5 In area 1, select a destination port; In area 2, select TScrossNo, and then click , the Search
E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB
ATM Transport Layer window.
NOTE
Step 7 Configure other parameters based on the prepared data, and then click to add a timeslot
cross channel.
----End
6.6.2 Adding an IP Route (Initial)

This describes how to add an IP route for transmitting the NodeB IP data of the transmission
control plane, the user plane, and the management plane.

NodeB
Optional
Prerequisite
The physical links at the IP transport layer are configured. For details, refer to 6.6.1 Adding a
Link at the Data Link Layer (Initial).
Preparation
Table 6-62 Negotiation and planned data of the IP route

Data e
Port type ItfType Interface type of the route Optional ETH

parameters:
l ETH
l MLPPP
l PPP
l PPPoE
Destinatio DestNet This parameter must meet all the 17.18.17.

n network following requirements: Valid 0
network address, except the default
route 0.0.0.0 IP AND mask must be
equal to the IP address.
Destinatio DestMask This parameter must meet all the 255.255. Network
n mask following requirements: IP AND 255.0 planning
mask must be equal to the IP address.
If the mask is converted into binary
value, 0 is not allowed to precede 1.
Next hop NextHop This parameter is valid only when the 12.11.12.
IP address parameter InsertFlag is set to ETH. 1
This parameter meets the following
requirements:
l Stays on the same network segment
as the LocalIP of the bearer link.
l Has valid IP address of classes A,
B, and C.
l The value cannot be
255.255.255.255.

NodeB
Procedure
displayed.
displayed.
Step 4 Click IPRoute, as shown in Figure 6-62.
Figure 6-62 Adding an IP route

configuration
1 Physical link list of the configured IP transport layer
2 Configuration area of the IP route on the control plane, the user

plane, and the management plane
Step 5 In area 1, select a physical bearer link; In area 2, select DestNet and then click , the DestNet
& DestMask dialog box is displayed. Set the IP address and the mask for the destination network,
and then click OK to return to the NodeB IP Transport Layer window.

NodeB
NOTE
l DestNet is the IP address of the destination network. Destination IP address AND subnet mask is the
IP address of the destination network, that is DestIP & DestMask = DestNet.
l In area 1, select the physical link, that is, the out port of the route is determined.
Step 6 Select NextHop, and click , the NextHop dialog box is displayed. Set the IP address of the
next hop, and return to the NodeB IP Transport Layer window.
NOTE
If the Iub interface is in layer 3 networking, the next hop IP address is the IP address of the router connecting
to the NodeB, or the IP address of the port on the layer 3 switch connecting to the NodeB.
----End
6.6.3 Adding SCTP Links (Initial)

This describes how to add SCTP links. The SCTP links are used to carry the IPCP, that is, the
NBAP at the IP transport layer.

Optional
NOTE
A complete piece of information of an SCTP link contains the local IP address, the peer IP address, the
local IP address of the second SCTP link, the peer IP address of the second SCTP link, the port number of
the local SCTP link, and the port number of the peer SCTP link. The two SCTP links must be different in
content.
Prerequisite
l The physical links at the IP transport layer are configured. For details, refer to 6.6.1 Adding
a Link at the Data Link Layer (Initial).
l The route to the destination IP address is configured. For details, refer to 6.6.2 Adding an
IP Route (Initial).
Preparation
Table 6-64 Negotiation and planned data of the SCTP links

Name
Port type ItfType Type of the interface that carries the PPP Internal
SCTP links Optional parameters: planning
l ETH
l MLPPP
l PPP
l PPPoE

NodeB

Name
Local IP LocalIP At the NodeB, the IP address of the 17.17.17.

address primary physical link that carries the 111
SCTP link.
Destination DestIP At the RNC, the IP address of the 14.1.1.4

IP address primary physical link that carries the
SCTP link.
The second SecLocalIP At the NodeB, the IP address of the 0.0.0.0

local IP standby physical link that carries the
address SCTP link.
Negotiatio
n with the
The second SecDestIP At the RNC, the IP address of the 0.0.0.0 destinatio
destination standby physical link that carries the n
IP address SCTP link.
Local port LocalPort Local port number of the SCTP 1024

number and Value range: 1024 through 65535
destination
port number
Destination DestPort Destination port number of the SCTP 8021

port number Value range: 1024 through 65535
Automatical IPAutoCha After the fault of the master IP ENABLE Internal

ly switches nge address is rectified, the services can planning
back to the be automatically switched back to
master IP the master IP address. Optional
address parameters:
l ENABLE
l DISABLE
Procedure
displayed.

NodeB
displayed.
Step 4 Click SCTP, as shown in Figure 6-63.
Figure 6-63 Adding an SCTP link

configuration
1 Configuration area for the SCTP links
3 Configured SCTP route list
Step 5 In area 1, click SCTPNo, and click .
Step 6 Select DestIP, and click . The Destination IP Address & Local IP Interface window is
displayed, as shown in Figure 6-64. In area 1, select the network segment route, and set the peer
IP address of the SCTP link in the upper middle part of the window. Click OK to return to the
NodeB IP Transport Layer window.

NodeB
Figure 6-64 Configuring the destination IP address of the SCTP link

configuration
1 Configuration area for the destination IP address of the SCTP
2 Physical link list at the IP transport layer
NOTE
l The local IP address of the SCTP link is the local IP address in area 1 of Figure 6-64. The peer IP
address of the SCTP link is on the same network segment with DestNet.
l After the data link layer is configured, the CME automatically adds the network segment route that is
on the same network segment as the local IP address of the data link. That is, the IP address of the
destination network and the local IP address of the data link are on the same network segment. For
details, refer to area 1 in Figure 6-64. (DestNet and LocalIP use the route of the same network
segment.)
l After the route is determined, the CME automatically traces route related physical link. As shown in
area 2 of Figure 6-64, this physical link cannot be changed.
Step 7 Configure other parameters based on the prepared data, and then click to add an SCTP link.
NOTE
Select the configured SCTP link, and the CME automatically traces the SCTP physical link and its related
SCTP route, as shown in area 2 and 3 of Figure 6-63.
----End

NodeB
6.6.4 Adding an IPCP (Initial)

Port (CCP). These two ports are carried on the SCTP links.

Optional
NOTE
l One NodeB can be configured with the active and the standby NCPs or CCPs.
l Each SCTP link can be configured with only one NCP or CCP.
l The active and the standby NCPs or CCPs should be configured on different links. For example, if the
active one is configured on the SAAL, the standby one should be configured on the SCTP. Otherwise
the configuration is invalid.
Prerequisite
The SCTP links are configured, as described in 6.6.3 Adding SCTP Links (Initial).
Preparation
Table 6-67 Negotiation and planned data of the IPCP

Name e
Port type PortType Optional parameters: NCP Internal

l NCP planning
l CCP
SCTP SCTPNo SCTP number that carries the 1 Negotiati

number NCP on with
NCP destinati
on

parameters:
l SLAVE
l MASTER
Port type PortType Optional parameters: CCP Internal

CCP l NCP planning
l CCP

NodeB

Name e

on with
SCTP SCTPNo SCTP number that carries the 2 destinati
number CCP on

parameters:
l SLAVE
l MASTER
Procedure
displayed.
displayed.
Step 4 Click IPCP, as shown in Figure 6-65.

NodeB
Figure 6-65 Configuring the NCP and the CCP

configuration
1 Configured SCTP link list
2 Configuration area for the IPCP links (NCP, CCP)
Step 5 In area 1, select an SCTP link; in area 2, select PortType and then click . Configure related
parameters based on prepared data, and then click to add an NCP link.
Step 6 In area 1, select an SCTP link; in area 2, select PortType and then click . Configure related
parameters based on prepared data, and then click to add an CCP link.
----End
6.6.5 Adding Transmission Resource Group (Initial, over IP)

bandwidth of the physical link to the transmission resource group for carrying the UE data. Each
resource group has its separate access control, congestion control, and HSPA flow control.
Scenario NodeB Initial Configuration Guide

Mandatory/ Optional. This configuration is required when the IP path joins the transmission
Optional resource group.

NodeB
NOTE
l Each physical link can be configured with a maximum of four transmission groups, that is, the total
number of transmission groups over ATM and IP.
l Each Iub interface board or BBU supports a maximum of 16 transmission resource groups over ATM
or 8 transmission resource groups over IP.
l The transmit bandwidth of the transmission resource group should be not greater than the idle
bandwidth at the physical links.
Prerequisite
The physical links at the IP transport layer are configured. For details, refer to 6.6.1 Adding a
Link at the Data Link Layer (Initial).
Preparation
Table 6-69 Negotiation and planned data of the transmission resource group (over IP)
Data Name
Port type ItfType Type of the interface that carries the IP ETH
parameters:
l ETH
l MLPPP
l PPP
l PPPoE

group
number
Internal
Transmit TxBandwi The transmit bandwidth of the 10000 planning
bandwidth dth resource group cannot exceed the
bandwidth of the port to which the
resource group belong.

NodeB

Data Name
Receive RxBandwi Receive bandwidth of the resource 10000

bandwidth dth group.
Procedure
displayed.
displayed.
Step 4 Click RSCGroup, as shown in Figure 6-66.
Figure 6-66 Adding the IP transmission resource group

NodeB

configuration
2 Configuration area for the transmission resource group
Step 5 In area 1, select a physical bearer link; In area 2, select RscgrpNo and then click .
Step 6 Configure other parameters based on the prepared data, and then click to add a transmission
resource group over IP.
----End
6.6.6 Adding IP Path Data (Initial)

This describes how to add an IP PATH for transmitting the user plane data.

Optional
NOTE
l One Iub interface board can be configured with a maximum of 16 IP paths.

l Each NodeB can be configured with a maximum of 32 IP paths. The total number the configured IP
paths and AAL2 paths of the HSPA type cannot exceed 16.
l The destination IP addresses for the IP PATH configured at the same transport layer link must be the
same.
l The values of the parameters DSCP and TrafficType configured for the IP path in the same transport
layer link must differ.
l If an IP link is configured with a transmission resource group, all IP path links configured at this IP
link must join the transmission resource group of the IP link.
l If a physical port is configured with AAL2 paths or IP paths, and the links are not in a resource group.
No transmission resource group can be added to this physical port.
Prerequisite
l The IP routes to destination addresses are configured, as described in 6.6.2 Adding an IP
Route (Initial).
Resource Group (Initial, over IP).

NodeB
Preparation
Table 6-71 Negotiation and planned data of the IP PATH

Data
Port type ItfType Type of the interface that carries the ETH Internal
IP PATH Optional parameters: planning
l ETH
l MLPPP
l PPP
l PPPoE
Destinatio DestIP Destination IP address of the IP path 17.18.17. Negotiati

n IP 121 on with
address the
destinatio
n
DSCP DSCP Value range: 0 through 63 60 Network

priority planning
Service TrafficType Optional parameters: RT

type l RT
l NRT
l HSPA_RT
l HSPA_NRT
Receive RxBandwith When PATH joins the resource 1000

not exceed the bandwidth of the Negotiati
resource group; when PATH does on with
not join the resource group, the the
receive bandwidth doe not exceed the destinatio
bandwidth of the physical port. n

NodeB

Data
Transmit TxBandwith When PATH joins the resource 1000

not exceed the bandwidth of the
resource group; when PATH does
not join the resource group, the
receive bandwidth doe not exceed the
bandwidth of the physical port.
Transmit TxCBS Value range: 15000 to 155000000. 500000

committed The recommended value is 1/2 of the
burst size transmit bandwidth.
Unit: bit
Transmit TxEBS Value range: 0 through 155000000 1000000

excessive Unit: bit
burst size
Path check PathCheck Optional parameters: DISABL

l ENABLE: Path check is enabled. E
Internal
l DISABLE: Path check is disabled. planning
Join the JoinRscgrp Specify whether the IP PATH should ENABLE

resource be added to the resource group.
group Optional parameters:
l DISABLE
l ENABLE
Resource RscgrpNo Number of the IP transmission 0


NodeB
Procedure
displayed.
displayed.
Step 4 Click IPPath, as shown in Figure 6-67.
Figure 6-67 Configuring the IP PATH

configuration
1 Configuration area for the IP path

link
4 Configured IP path route list

NodeB
Step 5 In area 1, click PathId, and click .
Step 6 Select DestIP, and click . The Destination IP window is displayed, as shown in Figure
6-68. In area 1, select the network segment route, and set the peer IP address of the IP path in
the upper middle part of the window. Click OK to return to the NodeB IP Transport Layer
window.
Figure 6-68 Configuring the destination IP address of the IP PATH

configuration
1 Configuration area for the destination IP address of the IP PATH
NOTE
l The local IP address of the IP PATH is the local IP address in area 1 of Figure 6-68. The peer IP address
of the IP PATH is on the same network segment with DestNet.
segment.)
l After the route is determined, the CME automatically traces route related IP transmission resource
group. As shown in area 2 of Figure 6-68, this IP transmission resource group cannot be changed.

NodeB
the NodeB IP Transport Layer window.
NOTE
The physical bearer type of the resource group is identical with that of the IP path. Figure 6-67 and Table
6-72 show the matching relation.
Step 8 Configure other parameters based on the prepared data, and then click to add an IP path.
NOTE
Select the configured IP path, and then the CME automatically traces the related IP transmission resource
group and the IP path route, as shown in areas 3 and 4 of Figure 6-67.
----End
6.6.7 Adding an OMCH of the NodeB (Initial, over IP)

This describes how to configure an OMCH of the NodeB in IP transport mode.

Optional
NOTE
l A maximum of two OMCH channels are added, that is, the master and the slave channels. You can
also configure only one OMCH channel. If it acts as the master channel, the data takes effect; if it acts
as the slave channel, the data will not take effect.
l Local IP addresses of two OMCH channels cannot be on the same network segment.
Prerequisite
l The IP routes to destination addresses are configured, as described in 6.6.2 Adding an IP
Route (Initial).

NodeB
Preparation
Table 6-74 Negotiation and planned data of the OMCH (IP)

Data Name
Bind the BindRoute Determine whether to bind the route. YES

route Valid Route binding is necessary when the
peer IP address of the OMCH is on
different network segments from the
DestNet in the 6.6.2 Adding an IP
Route (Initial). Optional parameters:
l NO
l YES
bound routes Optional parameters:
l ETH
l MLPPP
l PPP
l PPPoE
Bound IP BindDestIP This parameter is valid only when the 11.11.10. Negotiati
address on parameter BindRouteValid is set to 0 on with
the YES. the
destination destinatio
network n
Bound BindDestIP This parameter is valid only when the 255.255.

destination Mask parameter BindRouteValid is set to 255.0
mask YES.
Bound next NextHop This parameter is valid only when the 12.11.12.
hop IP port type is ETH. 1
address
Local IP LocalIP IP address at the NodeB for the OMCH 11.11.12.

address 12
Local Mask Mask of the IP address at the NodeB 255.255.

subnet for the OMCH 0.0
mask
Destinatio DestIP Destination IP address of the OMCH, 11.11.11.

n IP that is, the IP address of the LMT or the 12
address M2000.
Flag Flag Optional parameters: MASTE

R Internal
planning

NodeB
Procedure
displayed.
displayed.
Step 4 Click OMCH, as shown in Figure 6-69.
Figure 6-69 Adding an OMCH

configuration
1 OMCH configuration area
2 Type of the interface that carries the bound routes
3 Configured OMCH route list
Step 5 (Optional) Set the parameter BandRouteValid to YES. Then, select the parameter
BandDestIP and click , the BandDestIP & BandDestIPMask dialog box is displayed. Set

NodeB
the IP address and the mask for the binding destination network of the OMCH, and then click
OK to return to the NodeB IP Transport Layer window.
NOTE
l The destination network segment of the binding route must differ from the network segment of the
DestNet in 6.6.2 Adding an IP Route (Initial).
l The destination IP address of the OMCH can use the network segment where the binding route is
located.
Step 6 In area 1, select LocalIP, and click , the LocalIP & Mask dialog box is displayed. Set the
local IP address and the mask for the OMCH, and then click OK to return to the NodeB IP
Step 7 Select DestIP, and click . The Destination IP Address window is displayed, as shown in
Figure 6-70. Select the network segment route, and set the peer IP address of the IP OMCH in
the upper middle part of the window. Click OK to return to the NodeB IP Transport Layer
window.
Figure 6-70 Adding a destination IP address of the OMCH
NOTE
l If the BandRouteValid is set to YES(the route is bound), the CME system automatically generates
the route to the bound destination network. For instance, the network IP address of Figure 6-70 is
11.11.10.0, and the interface type is ETH.
l The destination IP address of the OMCH can be either on the same network segment as the DestNet
in 6.6.2 Adding an IP Route (Initial), or on the same network segment as the BandDestIP.
Step 8 Configure other parameters based on the prepared data, and then click to add an OMCH
link.

NodeB
NOTE
Select the configured OMCH, the CME automatically traces the related OMCH route, as shown in area 3
of Figure 6-69.
----End
6.6.8 Adding A Bound Destination Network Segment to the

Transmission Resource Group (Initial, IP)
This describes how to add a bound destination network segment to the transmission resource
group. All data to the subnet from the port of the transmission resource group will be calculated
in the transmission resource group.

Mandatory/ Optional. This configuration is required when the SCTP link or the OMCH link
Optional joins the transmission resource group.
NOTE
l Two transmission resource groups of the same physical port cannot be bound to the same destination
network segment.
l The transmission resource group (IP as the bearer mode) to which the bound destination network
segment is added is already configured. Otherwise, the binding fails to proceed.
Prerequisite
The IP transmission resource group is configured, refer to 6.6.5 Adding Transmission
Resource Group (Initial, over IP).
Preparation
Table 6-76 Negotiation and planned data of the transmission resource group whose destination
IP network segment is bound

Data Name
resource group Optional parameters:
l ETH
l MLPPP
l PPP Internal
l PPPoE planning
Resource RscgrpNo Number of the IP transmission resource 0

group group that corresponds to the physical
number bearer port

NodeB

Data Name
Destinatio DestIP Bound destination IP address, that is, 11.11.10.1

n IP the IP address on the same network 0
address segment with BindDestIP in 6.6.7
Adding an OMCH of the NodeB
(Initial, over IP) or the destination IP
address of the SCTP link of 6.6.3
Adding SCTP Links (Initial).
Destinatio IPMask Bound destination mask 255.255.2

n mask 55.255
Procedure
displayed.
displayed.
Step 4 Click IP2RSCGroup, as shown in Figure 6-71.
Figure 6-71 Adding a bound destination network segment to the transmission resource group
(initial, over IP)

NodeB
Sequence of Description
data
configuration
1 Configured IP transmission resource group
2 Configured route mapping the IP transmission resource group
3 Configuration area for adding a bound destination network segment to the

transmission resource group
Step 5 In area 1, select an IP transmission resource group; in area 2, select the IP address of the bound
destination network.
Step 6 In area 3, click SubrackNo, and click . Select DestIP, and click . The DestIP &
Mask dialog box is displayed. To add a destination IP address, click OK to return to the NodeB
IP Transport Layer window.
NOTE
l DestIP & DestMask = DestNet & DestMask; DestIP & IPMask = DestIP.
l If the SCTP link joins the resource group, the DestIP is the destination IP address of the SCTP link.
l If the OMCH link joins the resource group, the DestIP is the bound destination IP address of the OMCH
link. (The bound destination IP address and BindDestIP are on the same network segment).
Step 7 Configure other parameters based on the prepared data. Click to add a bound destination
network segment to the transmission resource group.
----End
6.6.9 Adding IP Clock Links (Initial)

This describe how to add IP clock links. The NodeB can obtain the clock signals from the clock
server through the IP link.

Mandatory/ Optional
Optional
CAUTION
l The timeslot cross channel over IP cannot be configured to the NUTI that uses the parameter
IPClockSwitch.
l When the IP clock link is added, you need to set the current ClockSource (clock resource
type) to the IP (IP clock resource) mode before the NodeB is used by the IP clock. For details,
refer to 6.2.1 Manually Creating a Physical NodeB (Initial).

NodeB
Prerequisite
l The parameter IPClockSwitch on the NUTI is enabled. For details, refer to 6.2.2 Adding
the Boards in the Baseband Subrack (Initial).
l The IP routes to the server are configured, as described in 6.6.2 Adding an IP Route
(Initial).
Preparation
Table 6-78 Negotiation and planned data of the IP clock links

Data Name
Port type ItfType Type of the interface that carries the IP PPPoE Internal
clock links Optional parameters: planning
l ETH
l MLPPP
l PPP
l PPPoE
IP address ClientIP Obtain the NodeB IP address of the IP 12.3.0.1

at the client clock
IP address ServerIP IP address at the IP clock server 12.3.0.10

at the
server Network
planning
Priority Priority The clock links that has the highest 0
priority is used first. The number is in
a negative relation with the priority
level.
Procedure
displayed.

NodeB
displayed.
Step 4 Click IPCLKLNK, as shown in Figure 6-72.
Figure 6-72 Adding an IPCLKLNK link

configuration
1 Configuration area for the IP clock link
3 Configured IP clock link route list
Step 5 In area 1, click SubrackNo, and click . Select ServerIP, and click . The Destination IP
Address & Local IP Interface window is displayed, as shown in Figure 6-73. In area 1, select
the network segment route, and set the server IP address of the IP clock link in the upper middle
part of the window. Click OK to return to the NodeB IP Transport Layer window.

NodeB
Figure 6-73 Configuring the IP address at the IP clock link server

configuration
1 Configuration area for the destination IP address of the IP clock link
NOTE
l The client IP address of the IP clock link is the local IP address in area 1 of Figure 6-73. The server
IP address of the IP clock link is on the same network segment with DestNet.
segment.)
l After the route is determined, the CME automatically traces route related physical link. As shown in
area 2 of Figure 6-73, this physical link cannot be changed.
Step 6 Configure other parameters based on the prepared data, and then click to add a clock link.
NOTE
Select the configured IP clock link, and the CME automatically traces the IP clock link and its related IP
clock route, as shown in areas 2 and 3 of Figure 6-72.
----End

NodeB
6.6.10 Modifying IP QoS Data (Initial)

This describes how to modify the signaling and Operation and Maintenance (OM) priorities.

Mandatory/ Optional
Optional
NOTE
l IP QoS is an IP network capability to provide specific services over the IP network that
uses multiple bottom-layer network technologies such as MP, FR, ATM, Ethernet, SDH,
and MPLS.
l IP QoS supports the switching between the IP precedence and DSCP. The IP QoS
configuration is flexible depending on actual requirements.
Prerequisite
None.
Preparation
Table 6-81 Negotiation and planned data of the IPQoS

Data Name
Priority rule PriRule Optional parameters: IPPRECE

l IPPRECEDENCE DENCE
l DSCP
Signaling SigPri l In IPPRECEDENCE rule, the value 7

priority range is 0 through 7.
Network
l In DSCP rule, the value range is 0
planning
through 63.
Operation OMPri l In IPPRECEDENCE rule, the value 7

and range is 0 through 7.
Maintenanc l In DSCP rule, the value range is 0
e (OM) through 63.
priority
Procedure
displayed.

NodeB
displayed.
Step 4 Click IPQos, as shown in Figure 6-74.
Figure 6-74 Configuring the Diffserv priority on the transport layer
Step 5 Select PriRule, and select a priority rule from the drop-down list.
Step 6 Select SigPri and OMPri, and then set the signaling and OM priorities.
----End

(Initial)
Optional

NodeB
NOTE
Prerequisite
Preparation
Subrack (Initial).

NodeB
Procedure
displayed.
Option Description

at a time.
Selection window.

NodeB

configuration

NodeB
NOTE
side.
----End
6.8 Adding Radio Layer Data

This describes how to configure radio network layer data for the NodeB. The related activities
involve adding sites, adding sectors, and adding local cells.
6.8.1 Adding Sites

This describes how to add a NodeB site. The NodeB modules that are in the charge of the same
main module are called a NodeB. They can be located in different places and connected to each
other through optical fibers and standard interfaces. Each module at a specific place can be
planned as a site.
6.8.2 Adding Sectors and Cells (Macro NodeB)
This describes how to configure cells in local sectors, remote sectors, and distributed sectors in
a macro NodeB. From the hardware perspective, the local sector needs the support from the
MTRU and MAFU, and the remote and the distributed sector needs the support from the MRRU

NodeB
or the PicoRRU (PRRU). The cells can be configured in the local sectors, remote sectors, or
distributed sectors.
6.8.3 Adding Sectors and Cells (Distributed NodeB)
This describes how to add the remote sectors and distributed sectors for a distributed NodeB.
The distributed NodeB supports only remote and distributed sectors. In terms of hardware
support, the remote sector and the distributed sector need the MRRU or PRRU (PicoRRU) RF
unit. The cells can be configured only in remote sectors or distributed sectors.
6.8.1 Adding Sites

This describes how to add a NodeB site. The NodeB modules that are in the charge of the same
main module are called a NodeB. They can be located in different places and connected to each
other through optical fibers and standard interfaces. Each module at a specific place can be
planned as a site.

Optional
Prerequisite
NodeB (Initial).
Preparation

Data
Site name Site Name The site is usually named after Shanghai Network
the geographical location. planning
Procedure
displayed.
Step 3 Select a physical NodeB, and then click . The NodeB Radio Layer window is displayed,

NodeB
Figure 6-78 Adding Sites
Sequence of data configuration Description
1 Configuration area for sites
Step 4 In area 1, select SiteId, and click . Configure parameters SiteId and Site Name according
to the prepared data.
NOTE
SiteId is unique in one NodeB.
Step 5 Click to add a site.
----End
6.8.2 Adding Sectors and Cells (Macro NodeB)

This describes how to configure cells in local sectors, remote sectors, and distributed sectors in
a macro NodeB. From the hardware perspective, the local sector needs the support from the
MTRU and MAFU, and the remote and the distributed sector needs the support from the MRRU
or the PicoRRU (PRRU). The cells can be configured in the local sectors, remote sectors, or
distributed sectors.

NodeB
Optional
NOTE
l The MAFU or MRRU supports four carrier frequencies and the PRRU supports two carrier frequencies.
l The uplink and downlink frequencies of the cell configured in the same MAFU, MRRU, or PRRU
must be at the same frequency band, and the difference of frequency between cells should meet certain
conditions.
l If the PA supports two carriers, the carriers are on the same PA. The frequency difference between
two local cells should not be smaller than 4.2 MHz (21 x 0.2 MHz), and not greater than 5 MHz
(25 x 0.2 MHz).
l If the PA supports four carriers, the carriers are on the same PA. The frequency difference between
(75 x 0.2 MHz).
l A represents TX/RX antenna.
l B represents RX antenna.
Prerequisite
l The physical NodeB,that is the BTS3812AE, BTS3812A, or BTS3812E is configured. For
details, refer to 6.2.1 Manually Creating a Physical NodeB (Initial).
l The remote and distributed sectors can be configured only when the BTS3812AE,
BTS3812A, or BTS3812E is configured with the MRRU or PRRU (PicoRRU). For details,
refer to 6.2.4 Adding an RRU (Initial, Macro NodeB).
l The local sectors can use only the antenna channel on the MAFU module. For details, refer
to 6.2.5 Adding RF Modules (Initial).
l The sites are configured. For details, refer to 6.8.1 Adding Sites.

NodeB
Preparation


RX antennas before
four-way economical
be configured.
only one or two RX
planning
parameters:
two TX channels.
l HALFFREQ (0.5/0.5
remote sectors)
When the number of

NodeB

diversity mode is
HALFFREQ. Optional
parameters:
l SAMEZONE (same
coverage type)
coverage type)

NodeB


frequency band.
Frequency (MHz) =
l Band 1
Offset:0
Offset: 0
l Band 2
Offset: 0
37, 62, 87, 112, 137, 162,
187, 212, 237, 262, 287}.
Offset:1850.1
l Band 3
Common frequencies: 937 Network
through 1288 inclusive. planning
Offset:1525
Offset:0
l Band 4
Offset:1450
1687, 1712, 1737, 1762,
1787, 1812, 1837, 1862}.
Offset:1380.1
l Band 5
Offset:0
787, 807, 812, 837, 862}.
Offset:670.1
l Band 6
Offset:0

NodeB
{812,837}. Offset:670.1
l Band 7
Offset:2100
2387, 2412, 2437, 2462,
2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662,
2687}. Offset:2030.1
l Band 8
Offset:340
Offset:0
l Band 9
Offset:0
Offset:0

NodeB

frequency band.
Frequency (MHz) =
l Band 1
Common frequencies:
10562 through 10838
inclusive. Offset:0
Offset:0
l Band 2
Offset:0
437, 462, 487, 512, 537,
562, 587, 612, 637, 662,
687}. Offset:1850.1
l Band 3
Offset:1575
Offset:0
l Band 4
Offset:1805
1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087}.
Offset:1735.1
l Band 5
Offset:0
1012, 1032, 1037, 1062,
1087}. Offset:670.1
l Band 6
Offset:0
1062}. Offset:670.1

NodeB
l Band 7
Offset:2175
2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887,
2912}. Offset:2105.1
l Band 8
Offset:340
Offset:0
l Band 9
Offset:0
Offset:0

cells.


slot 9.

NodeB

NO_TX_DIVERSITY
mode, the maximum
cell is:
[TOC maximum output
power of the power
7dB, TOC2 maximum

network planning.
180000

network planning.

NodeB

RNC.

l TRUE (high speed)

l 250
l 400
l 500

power to the
RRU
Procedure
l Configure local sectors and cells.
NOTE
The local sector uses only the RF board, that is, MAFU.
1. In the NodeB Radio Layer window, click the Local Sector tab, and the tab page is

NodeB
Figure 6-79 Configuring local sectors and cells

data
configuration
1 Configuration area for the local sectors
2 Antenna channel list for the local sectors
3 Used antenna channel list
4 Cell configuration areas for the local sectors
5 List of available RF channels for cells
6 Used RF channel list
2. In area 1, click SectorNo, and click . Set parameters based on prepared data. Then,
click to add a local sector.

3. In area 2, the available antenna channels that can be used by the local sectors are
filtered out. Select the antenna channel, and then click to configure
the antenna channel used by the local sector.
4. In area 4, click LoCell, and click .

5. Set parameters UARFCNUpLink and UARFCNDownLink for the cell.

NodeB
6. Select ULResourceGroupId or DLResourceGroupId, and click . The

ULGroup or DLGroup window is displayed. Select an uplink or a downlink resource
group, and click Close to return to the NodeB Radio Layer window.
7. Select INHBOARD, and click . The Mac Params Confige Form window is
displayed, as shown in Figure 6-80. Modify Mac-hs and Mac-e related parameters,
and click . Then, click Close to return to the NodeB Radio Layer window.
Figure 6-80 Modifying Mac-hs and Mac-e related parameters

data
configuration
1 Modify Mac-hs scheduling parameters.
2 Modify Mac-hs resource limit parameters.
3 Modify Mac-hs SPI scheduling parameters.

NodeB
NOTE
l For the BTS3812AE, BTS3812A, or BTS3812E, if the previously mentioned parameters

for the specified local cells are modified, you must select the HSDPA Capability check
box, and the INHBOARD is INHBOARD; if you deselect the HSDPA Capability check
box, the INHBOARD is UNLIMITED.
l For the DBS3800, the status of the HSDPA Capability check box is unchangeable, that is,
the check box can only be selected. The INHBOARD can only be INHBOARD.
8. Configure other parameters based on the prepared data, and then click to add a
cell.
9. In area 5, the available RF channels that can be used by the cell are filtered out. Select
the RF channel, and then click to configure the RF channel used by

the cell.
l Configure remote sectors and cells.
NOTE
l When the number of receive antennas is 2 or 4, only the RX/TX antenna channels on the MRRU
configured on the main line of the RRU chain/ring can be used.
l When the number of receive antennas is 1, only the RX/TX antenna channels on the MRRU/
PRRU configured on the main line of the RRU chain/ring can be used.
1. In the NodeB Radio Layer window, click the Remote Sector tab, the tab page is
Figure 6-81 Configuring remote sectors and cells

NodeB
data
configuration
1 Configuration area for the remote sectors
2 Available antenna channel list for remote sectors
4 Configuration area for the cells of the remote sectors
2. Perform Step 2 through Step 3 to configure remote sectors.

3. Perform Step 4 through Step 9 to configure cells of the remote sectors.
l Configure distributed sectors and cells
NOTE
l The TX/RX mode of distributed sectors is always unidirectional (TX/RX).
l The distributed sector uses only the RX/TX antenna channels on the MRRU or PRRU (including
the PRRU configured on the RHUB) configured on the RRU chain/ring.
1. In the NodeB Radio Layer window, click the Distribute Sector tab, the tab page is
Figure 6-82 Configure distributed sectors and cells

NodeB
data
configuration
1 Configuration area for the distributed sectors
2 Available antenna channel list for distributed sectors
4 Configuration area for the cells of the distributed sectors
2. Perform Step 2 through Step 3 to configure the distributed sectors.

3. Perform Step 4 through Step 9 to configure cells of the distributed sectors.
----End
6.8.3 Adding Sectors and Cells (Distributed NodeB)

This describes how to add the remote sectors and distributed sectors for a distributed NodeB.
The distributed NodeB supports only remote and distributed sectors. In terms of hardware
support, the remote sector and the distributed sector need the MRRU or PRRU (PicoRRU) RF
unit. The cells can be configured only in remote sectors or distributed sectors.

Optional
NOTE
l The MRRU supports four carrier frequencies and the PRRU supports two carrier frequencies.
l The uplink and downlink frequencies of the cell configured in the same MRFU, MRRU, or PRRU must
be at the same frequency band, the uplink frequencies must be smaller than the downlink frequencies,
and the difference of frequency between cells should meet certain conditions.
l If the PA supports two carriers, the carriers are on the same PA. The frequency difference between
(25 x 0.2 MHz).
l If the PA supports four carriers, the carriers are on the same PA. The frequency difference between
(75 x 0.2 MHz).
l A represents TX/RX antenna.
l B represents RX antenna.
Prerequisite
l The DBS3800 related physical NodeB is configured. For details, refer to 6.2.1 Manually
Creating a Physical NodeB (Initial).

NodeB
Distributed NodeB).
l The sites are configured. For details, refer to 6.8.1 Adding Sites.
Preparation

RX antennas before
four-way economical
be configured.
only one or two RX
planning
parameters:
two TX channels.
l HALFFREQ (0.5/0.5
remote sectors)
When the number of

NodeB

diversity mode is
HALFFREQ. Optional
parameters:
l SAMEZONE (same
coverage type)
coverage type)

NodeB


frequency band.
Frequency (MHz) =
l Band 1
Offset:0
Offset: 0
l Band 2
Offset: 0
37, 62, 87, 112, 137, 162,
187, 212, 237, 262, 287}.
Offset:1850.1
l Band 3
Common frequencies: 937 Network
through 1288 inclusive. planning
Offset:1525
Offset:0
l Band 4
Offset:1450
1687, 1712, 1737, 1762,
1787, 1812, 1837, 1862}.
Offset:1380.1
l Band 5
Offset:0
787, 807, 812, 837, 862}.
Offset:670.1
l Band 6
Offset:0

NodeB
{812,837}. Offset:670.1
l Band 7
Offset:2100
2387, 2412, 2437, 2462,
2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662,
2687}. Offset:2030.1
l Band 8
Offset:340
Offset:0
l Band 9
Offset:0
Offset:0

NodeB

frequency band.
Frequency (MHz) =
l Band 1
Common frequencies:
10562 through 10838
inclusive. Offset:0
Offset:0
l Band 2
Offset:0
437, 462, 487, 512, 537,
562, 587, 612, 637, 662,
687}. Offset:1850.1
l Band 3
Offset:1575
Offset:0
l Band 4
Offset:1805
1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087}.
Offset:1735.1
l Band 5
Offset:0
1012, 1032, 1037, 1062,
1087}. Offset:670.1
l Band 6
Offset:0
1062}. Offset:670.1

NodeB
l Band 7
Offset:2175
2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887,
2912}. Offset:2105.1
l Band 8
Offset:340
Offset:0
l Band 9
Offset:0
Offset:0

cells.


slot 9.

NodeB

NO_TX_DIVERSITY
mode, the maximum
cell is:
[TOC maximum output
power of the power
7dB, TOC2 maximum

network planning.
180000

network planning.

NodeB

RNC.

l TRUE (high speed)

l 250
l 400
l 500

power to the
RRU
Procedure
l Configure remote sectors and cells.
NOTE
l When the number of receive antennas is 2 or 4, only the RX/TX antenna channels on the MRRU
configured on the main line of the RRU chain/ring can be used.
l When the number of receive antennas is 1, only the RX/TX antenna channels on the MRRU/
PRRU configured on the main line of the RRU chain/ring can be used.
1. In the NodeB Radio Layer window, click the Remote Sector tab, the tab page is

NodeB
Figure 6-83 Configuring remote sectors and cells

data
configuration
1 Configuration area for the remote sectors
2 Available antenna channel list for remote sectors
4 Configuration area for the cells of the remote sectors
2. Perform Step 2 through Step 3 in the 6.8.2 Adding Sectors and Cells (Macro
NodeB) to add remote sectors.
NodeB) to add cells of the remote sectors.
l Configure distributed sectors and cells
NOTE
l The TX/RX mode of distributed sectors is always unidirectional (TX/RX).

l The distributed sector uses only the RX/TX antenna channels on the MRRU or PRRU (including
the PRRU configured on the RHUB) configured on the RRU chain/ring.
1. In the NodeB Radio Layer window, click the Distribute Sector tab, the tab page is

NodeB
Figure 6-84 Configure distributed sectors and cells

data
configuration
1 Configuration area for the distributed sectors
2 Available antenna channel list for distributed sectors
4 Configuration area for the cells of the distributed sectors
NodeB) to add distributed sectors.
NodeB) to add cells of the distributed sectors.
----End

NodeB
NodeB Initial Configuration Guide 7 Related Concepts of NodeB Initial Configuration
7 Related Concepts of NodeB Initial

Configuration
About This Chapter
This provides the related concepts to be referenced during the process of the NodeB initial
configuration.
7.1 Cell Related Concepts

This provides the cell related concepts, including those of the sectors, carriers, cells, physical
resources of cells, local cells, and logical cells.
7.2 ATM Protocol-Related Terms
This describes the terms related to the ATM protocol. The reference model of the ATM protocol
consists of three planes and three function layers. The three planes are control plane, user plane,
and management plane. The three function layers are physical layer, ATM layer, and ATM
adaptation layer (AAL).
7.3 IP Protocol-Related Terms
This describes the terms related to the protocols of the data link layer, network layer, and
transport network layer when the Iub interface uses the IP transport.
7.4 NodeB Treelink PVC
The function of a NodeB treelink PVC is similar to that of the ATM switching. This describes
how to add a treelink PVC to the NodeB, that is, to add an ATM switching route to the NodeB
(over ATM), so as to switch the PVC from one physical bearer to another.
7.5 NodeBs in Direct/Cascading Connections
This defines the NodeBs in direct and cascading connections. In addition, it describes the
configuration differences between these two connections.

NodeB
7 Related Concepts of NodeB Initial Configuration NodeB Initial Configuration Guide
7.1 Cell Related Concepts

This provides the cell related concepts, including those of the sectors, carriers, cells, physical
resources of cells, local cells, and logical cells.
7.1.1 Sector, Carrier, and Cell

This describes the sector, carrier, and cell. A sector is the smallest radio coverage area unit,
which is covered by one or more radio carriers. Each radio carrier occupies a frequency. A sector
and a carrier form a cell that is the smallest serving unit for UE access.
7.1.2 Physical Resources of Cells
This describes the physical resources of cells from the perspectives of RF resources of sectors
and resource pools of cells.
7.1.3 Local Cell and Logical Cell
This describes local and logical cells. In the 3GPP protocols, a serving cell is called local cell
and logical cell at the implementation layer of physical layer and the management layer of logical
resources respectively.
7.1.1 Sector, Carrier, and Cell

This describes the sector, carrier, and cell. A sector is the smallest radio coverage area unit,
which is covered by one or more radio carriers. Each radio carrier occupies a frequency. A sector
and a carrier form a cell that is the smallest serving unit for UE access.
Sectors are classified into omnidirectional sectors and directional sectors. An omnidirectional
sector is used in small traffic areas. Centered around the omnidirectional RX/TX antenna, the
omnidirectional sector covers 360o circular areas. When the traffic increases, the omnidirectional
sector is split into three or six directional sectors. The directional sectors are covered by
directional antennas. For example, when there are three directional sectors, each set of directional
antenna covers a 120o area. When there are six directional sectors, each set of directional antenna
covers a 60o area. In fact, the azimuth of the antenna is greater than the theoretical value, and
therefore there is overlap between the sectors.
Number of cells supported by a NodeB = number of sectors x number of carriers in each sector.
Figure 7-1 shows the typical 3 x 2 configuration. The area is split into sectors 0, 1, and 2. Each
sector has two carriers, and each carrier forms a cell. There are six cells in total.
Frequency multiplexing is allowed in a WCDMA system if different downlink primary
scrambling codes are used in neighboring cells of different sectors that use the same frequency.
In this way, the inter-cell interference is reduced.

NodeB
Figure 7-1 Relations among a sector, carrier, and cell
7.1.2 Physical Resources of Cells

This describes the physical resources of cells from the perspectives of RF resources of sectors
and resource pools of cells.
RF Resources of Sectors
The NodeB provides RF resources of cells. Figure 7-2 shows the physical RF resources mapped
to a NodeB from sectors. Each sector uses one directional antenna. Each directional antenna
provides 2-way receive channels to enhance the receiving sensitivity, and the two channels work
in mutual receive diversity mode.
l RF modules of a distributed NodeB are the RRU and PicoRRU (PRRU).
l RF modules of a macro NodeB are the MAFU and MTRU. The MAFU and MTRU work
in pairs.

NodeB
Figure 7-2 Physical RF resources mapped from sectors onto NodeB
Figure 7-2 shows the mapping between the sectors and the RF module for a 2-carrier NodeB in
2-way receive diversity mode. The mapping may vary with the NodeB configuration. Figure
7-3 shows the rules of the mapping between BTS3812E sectors and MAFUs and MTRUs.
l 1MAFU+1MTRU for one sector: The NodeB supports 6 sectors. This mode supports 1-
carrier or 2-carrier 1T2R configuration.
l 2MAFUs+2MTRUs for one sector: The NodeB supports three sectors. This mode supports
1-carrier or 2-carrier 1T2R or 2T2R configuration, and 3-carrier or 4-carrier 1T2R

NodeB
configuration. You may change the external interface connections of the MTRUs and
MAFUs so that this sector mode can support 1-carrier or 2-carrier 2T4R configuration.
l 4MAFUs+4MTRUs for one sector: The NodeB supports one to three sectors. A combined
cabinet is required when there are more than one sector. This mode supports 3-carrier or
4-carrier 2T4R configuration.
Figure 7-3 Rules of the mapping between NodeB sectors and MAFUs or MTRUs
Resource Pools of Cells

The macro NodeB sends the uplink or downlink signal processing resources to the resource pool.
Cells in the resource pool can share the resources. When you configure the cell, specify the type
of resource pool that the cell belongs to. Two types of resource pools are as follows:
l GEN_POOL: indicates the uplink and downlink baseband resource pool that consists of
the HBBI, HULP, and HDLP. This type of resource pool is commonly used. When the
resource pool is used, you must specify uplink baseband resource groups.
l GRP_POOL: indicates the uplink and downlink baseband resource pool that consists of the
HBOI in slot 15. When the resource pool is used, you do not need to specify uplink baseband
resource groups.
The NodeB divides the uplink baseband resources into different groups, which are called uplink
baseband resource groups. The uplink baseband resource groups have the following features and
requirements:
l One uplink baseband resource group consists of one or more uplink processing units. One
uplink processing unit corresponds to one HBBI/HBOI/HULP board or one BBU module.
l The cells in one uplink baseband resource group share the uplink resources. Each uplink
baseband resource group supports a maximum of 6 cells in 2-way and enhanced 2-way
modes. Each uplink baseband resource group supports a maximum of three cells in 4-way
and economic 4-way modes.
l The softer handover can be performed between the cells in the same uplink baseband
resource group. You need to add the intra-frequency cells to the same group.
l Keep the number of resource groups as small as possible. For example, for a 3 x 4 NodeB,
divide the resource pool into two groups, each of which supports 6 cells.

NodeB
7.1.3 Local Cell and Logical Cell

This describes local and logical cells. In the 3GPP protocols, a serving cell is called local cell
and logical cell at the implementation layer of physical layer and the management layer of logical
resources respectively.
Local Cell
A local cell is a combination of physical resources, such as hardware and software resources, in
a cell of a NodeB. A local cell is related to the physical implementation of a device.
NodeBs from different vendors have different ways of providing physical resources for cells.
Therefore, the concept of logical cell is proposed in the 3GPP to ensure that the RNC can control
the radio resources in certain cells through the standard Iub interface. These cells are carried on
NodeBs from different vendors.
Logical Cell
A logical cell is a standard logical model that helps the RNC control the radio resources in a
cell. The model is independent of the implementation of local cells in the NodeB, and ensures
that the Iub interface is an open interface.
The parameters of a local cell are configured at and managed by the NodeB. The parameters of
a logical cell are configured at and managed by the RNC. A logical cell and a local cell have the
one-to-one correspondence.
7.2 ATM Protocol-Related Terms

This describes the terms related to the ATM protocol. The reference model of the ATM protocol
consists of three planes and three function layers. The three planes are control plane, user plane,
and management plane. The three function layers are physical layer, ATM layer, and ATM
adaptation layer (AAL).
Figure 7-4 shows the reference model of the ATM protocol.
Figure 7-4 Reference model of the ATM protocol
7.2.1 ATM User Plane, ATM Control Plane, and ATM Management Plane

NodeB
This describes the functions of the ATM user plane, ATM control plane, and ATM management
plane.
7.2.2 ATM Physical Layer, ATM Layer, and AAL
This describes the functions of the physical layer, ATM layer, and AAL.
7.2.1 ATM User Plane, ATM Control Plane, and ATM Management
Plane
This describes the functions of the ATM user plane, ATM control plane, and ATM management
plane.
Table 7-1 describes the functions of the ATM user plane, ATM control plane, and ATM
management plane.
Table 7-1 Functions of the ATM user plane, ATM control plane, and ATM management plane
Plane Function
User plane The user plane transfers user data, such as protocol data and voice
data.
Control plane The control plane transfers signaling messages, such as connection
setup and connection release.
Management Plane The management plane transfers network OM data. This plane is
classified into the layer management part and the plane management
part. The former is responsible for intra-layer management, and the
latter for inter-layer management.
NOTE
As stated in the ATM protocols, the AAL and higher layers process the data on the control plane and the
user plane in different ways. The ATM layer and the physical layer, however, process the data on the two
planes in the same way.
7.2.2 ATM Physical Layer, ATM Layer, and AAL

This describes the functions of the physical layer, ATM layer, and AAL.
Table 7-2 describes the layers and functions of the reference model of the ATM protocol.
Table 7-2 Layers and functions of the reference model of the ATM protocol
Protocol Layer Function
CS The AAL is a higher layer of the ATM layer and

performs the adaptation from the upper layer
applications to the ATM layer. For various types of
AAL
services, the AAL performs the adaptation in different
ways. It segments data from the upper layer into SDUs.
Each SDU has 48 bytes. The AAL reassembles and

NodeB
Protocol Layer Function
SAR restores the SDUs from the ATM layer, and then
transfers them to the upper layer.
The CS layer performs the convergence. The SAR
layer performs the segmentation and reassembly.
ATM layer - ATM switching is a fast packet switching technology.

In ATM switching, each 53-byte packet is called a cell.
At the physical layer, the ATM layer communicates
with the peer layer through ATM cells.
l Generic traffic control
l Cell header generation and extraction
l VPI and VCI translation
l Cell multiplexing and demultiplexing
TC (UNI, IMA, The physical layer provides channels for bit streams of
Fractional ATM cells. During data transmission, the physical
ATM, layer adds the overhead to the ATM cells sent by the
Fractional IMA, ATM layer to form a consecutive bit stream. Then, the
or STM-1 physical layer puts the stream on a transport channel.
mode) During data reception, the physical layer selects valid
ATM cells from the bit stream on the transport channel
PM (PDH over and then transfers these cells to the ATM layer. The
E1/T1, SDH) physical layer consists of the PM sublayer and the TC
sublayer.
The TC sublayer performs the following functions:
Physical layer
l Generation and recovery of transmission frames
l Adaptation of transmission frames

l Cell delimitation
l Generation and verification of HEC header
sequence
l Decoupling of cell rate
The PM sublayer performs the following functions:
l Bit timing
l Physical medium
7.3 IP Protocol-Related Terms

This describes the terms related to the protocols of the data link layer, network layer, and
transport network layer when the Iub interface uses the IP transport.
7.3.1 Data Link Layer Protocols

NodeB
This describes the data link layer protocols related to IP transport.

7.3.2 IP
This describes the Internet Protocol (IP). It provides a connectionless service between networks
and defines the rules and details for data communication. It is used along with the Transmission
Control Protocol (TCP) to provide guaranteed data transfer.
7.3.3 SCTP
This describes the Stream Control Transmission Protocol (SCTP). It is mainly used for
transmitting reliable datagrams through an unreliable network.
7.3.1 Data Link Layer Protocols

This describes the data link layer protocols related to IP transport.
7.3.1.1 PPP
This describes the Point-to-Point Protocol (PPP). The PPP is used at the data link layer. The PPP
provides standard methods for encapsulating the multi-protocol datagrams on point-to-point
links. These datagrams include IP, IPX, and Apple Talk.
7.3.1.2 MP
This describes the Multilink PPP (MP). With the wide application of the PPP, the MP emerges
as an extended protocol of the PPP. The MP provides a large bandwidth to enable quick data
transfer. In addition, the MP dynamically allocates the link resources to effectively save the
valuable resources.
7.3.1.3 PPPoE
This describes the PPPoE protocol. It is a standard that defines how multiple hosts are connected
to a remote Access Concentration (AC) in a broadcasting-type network (for example Ethernet).
When the PPPoE is used in the RAN system, multiple NodeBs are connected to the RNC through
the access equipment.
7.3.1.4 EtherIP
This describes the EtherIP link. It is connected to the Ethernet, and the relay boards use the FE
ports.
PPP
This describes the Point-to-Point Protocol (PPP). The PPP is used at the data link layer. The PPP
provides standard methods for encapsulating the multi-protocol datagrams on point-to-point
links. These datagrams include IP, IPX, and Apple Talk.
Figure 7-5 shows the hierarchy of the PPP.

NodeB
Figure 7-5 Hierarchy of the PPP
The PPP consists of the link control protocol (LCP), network control protocol (NCP), and
extended protocols. They are described as follows:
l LCP: used to configure, test, or remove a data link.
l NCP: used to configure parameters at the network layer for communications between the
equipment.
l Extended protocols, such as the multilink protocol (MP): The PPP combines multiple
physical links into a logical link through the MP, thus providing a large bandwidth and
enabling fast data transfer. Huawei RNC implements the MP by adding MLPPP data.
MP
This describes the Multilink PPP (MP). With the wide application of the PPP, the MP emerges
as an extended protocol of the PPP. The MP provides a large bandwidth to enable quick data
transfer. In addition, the MP dynamically allocates the link resources to effectively save the
valuable resources.
The MP can flexibly arrange multiple independent physical links between point-to-point
systems. It provides a virtual link for the whole system, and the bandwidth of the virtual link is
the sum of bandwidths of the N (N ≥ 1) physical links.
With the development of network technologies, bandwidth is no longer a bottleneck. Therefore,
the extended protocols of the PPP are not required.
PPPoE
This describes the PPPoE protocol. It is a standard that defines how multiple hosts are connected
to a remote Access Concentration (AC) in a broadcasting-type network (for example Ethernet).
When the PPPoE is used in the RAN system, multiple NodeBs are connected to the RNC through
the access equipment.
In this network topology, all hosts can independently initialize PPP protocol stacks, and perform
charging and management for the subscribers on this network. To set up and maintain the point-
to-point relations between hosts and the AC in a broadcasting-type network, each host should
be able to set up a unique point-to-point session with the AC.

NodeB
The procedure for setting up a PPPoE session is as follows:

1. When a host wants to start a PPPoE session, it searches for an AC in the network.
2. If multiple ACs exist on the network, the host selects an AC based on the services provided
by the AC or the settings predefined by the subscribers.
3. After an AC is selected, the host starts to set up a PPPoE session with the AC and assigns
a unique process ID.
4. PPPoE session phase starts after the session is set up. During this phase, the two sides with
point-to-point connection exchange the datagrams by using the PPP to complete a series
of PPP processes, and then transfer the network layer datagrams over this point-to-point
logical channel.
EtherIP
This describes the EtherIP link. It is connected to the Ethernet, and the relay boards use the FE
ports.
When IP_RAN is selected as the transmission mode of the NodeB, the NodeB can be configured
with the following four links:
l PPP
l MP
l PPPoE
l EtherIP
PPP and MP links are connected to the dedicated line network, and the relay boards use the E1/
T1 ports. PPPoE and EtherIP links are connected to the Ethernet, and the relay boards use the
FE ports.
7.3.2 IP
This describes the Internet Protocol (IP). It provides a connectionless service between networks
and defines the rules and details for data communication. It is used along with the Transmission
Control Protocol (TCP) to provide guaranteed data transfer.
IPv4 and IPv6

The current and most popular network layer protocol of the TCP/IP is IPv4, which was launched
in 1981. IPv6, which was launched in 1995, is gradually going to replace IPv4. Compared with
IPv4, IPv6 has much more address space to meet more requirements for IP addresses.
Principles for IP Address Planning

When using the TCP/IP protocol for communication, each communication entity needs an IP
address. In the application of the RAN, comply with the following principles when planning the
IP addresses:
l IP addresses and subnet masks must be valid. The network number is not all-zero and that
the host number is not all-zero or all-one.
l The IP addresses of classes A, B, and C are valid, but those of classes D and E are invalid.
l Do not set the IP address to a loopback address of 127.X.X.X.

NodeB
IP Address Structure
In an IP network, IP addresses should be assigned to hosts. If you connect a computer to the
Internet, you need to apply for an IP address from the Internet Service Provider (ISP).
The length of the IP address is 32 bits. The IP address consists of the following parts:
l Network number (net-id): The first bits are called class segments (class bits) that are used
to identify the class of an IP address.
l Host number (host-id): indicates different hosts in the same network.
IP Address Classification
IP addresses are categorized into five classes, as shown in Figure 7-6. You can identify an IP
address class by its first few bits.
Figure 7-6 Five classes of IP addresses
The IP addresses of classes A, B, and C are most commonly used. IP addresses of class D are
used for multicasting. IP addresses of class E are reserved. For details, refer to the RFC1166
Internet Numbers released by IETF.
IP Address Range
Some IP addresses are reserved for special purposes. Table 7-3 describes the ranges of IP
addresses.

NodeB
Table 7-3 Classification and range of IP addresses

Net Address Range Available Range Description
wor
k
Typ
e
A 0.0.0.0 to 1.0.0.0 to l An all-zero host number means that

127.255.255.255 126.0.0.0 the IP address is the network address
for network routing.
l An all-one host number means that
the IP address is used to broadcast
messages to all the hosts on the
network.
l When the DHCP is used, the local
host can take 0.0.0.0 as the
temporary IP address but never as
the valid destination address.
l The IP address with network
number of 0 represents the current
network that can be referenced by
other computers without knowing
its network number.
l All the IP addresses in the
127.X.X.X format are reserved for
loopback testing. The packets sent
to this address are not sent to lines.
The packets are handled internally
as input packets.
B 128.0.0.0 to 128.0.0.0 to l An all-zero host number means that

network.
C 192.0.0.0 to 192.0.0.0 to l An all-zero host number means that

network.
D 224.0.0.0 to None. IP addresses of class D are used for

239.255.255.255 multicasting.

NodeB
Net Address Range Available Range Description

wor
k
Typ
e
E 240.0.0.0 to None. Reserved. The IP address of

255.255.255.255 255.255.255.255 is used for
broadcasting in the LAN.
7.3.3 SCTP
This describes the Stream Control Transmission Protocol (SCTP). It is mainly used for
transmitting reliable datagrams through an unreliable network.
Advantages of the SCTP Compared with the TCP

Compared with the TCP, the SCTP has the following advantages:
l Supports the transmission of datagrams that are not delimitated by the upper layer.
l Provides better real-time performance.
l Provides higher security.
l Avoids the blocking of line headers.
l Supports the multi-homing function.
Provides the signaling transmission of higher requirements for real-time performance, security,
and reliability.
SCTP Endpoint
The SCTP endpoint is the logical transmitter or receiver of SCTP packets.
The SCTP endpoint on a multi-homing host can be either a group of valid destination transport
addresses for data transmission to the peer host, or a group of valid originating transport
addresses for transmitting SCTP packets.
All the transport addresses used by an SCTP endpoint must use the same port number but can
use multiple IP addresses. The transport address used by an SCTP endpoint at a time must be
unique.
A transport address is defined by the network layer address, transport layer protocols, and port
number. When the SCTP protocol works on the IP transport layer, the transport address is defined
by the IP address and SCTP port number. Then, the SCTP protocol acts as the transport layer
protocol.
SCTP Association
SCTP association is the mapping between two SCTP endpoints. It involves two SCTP endpoints
and protocol status data. The protocol status data includes verification tag and transport sequence
number.

NodeB
SCTP association is uniquely identified by the transport address of the SCTP endpoint that uses
the SCTP association. There is a maximum of one SCTP association between two SCTP
endpoints.
SCTP Message Structure

The SCTP message consists of the common header and the chunks. Figure 7-7 shows the SCTP
message structure.
Figure 7-7 SCTP Message Structure
Multiple chunks can be bundled and transmitted in one datagram, thus saving the bandwidth.
7.4 NodeB Treelink PVC

The function of a NodeB treelink PVC is similar to that of the ATM switching. This describes
how to add a treelink PVC to the NodeB, that is, to add an ATM switching route to the NodeB
(over ATM), so as to switch the PVC from one physical bearer to another.
Networking Principles
If a NodeB is connected to a lower-level NodeB, this parent NodeB must be configured with a
treelink PVC for transferring ATM cells to the lower-level node. The red dashed line in Figure
7-8 represents the treelink PVC.

NodeB
Figure 7-8 Treelink PVC
The purpose of a treelink PVC is to switch the data of the lower-level NodeB to the upper-level
one through a hub NodeB. The treelink PVCs configured on a hub NodeB should be able to
switch all the data of the Iub interface to the upper-level node.
Figure 7-9 Treelink PVC principles
Relations Between Iub PVCs of Lower-Level NodeB and Treelink PVCs

The NCP, CCP, ALCAP, AAL2 PATH, IPoA, CES, and treelink PVC of the lower-level NodeB
correspond to different PVCs. The method of adding a treelink PVC is the same as that of adding
a PVC switching route. You need to add switching routes for all PVCs of the lower-level NodeB.
To add a PVC switching route, you can select either of the following methods:
l Through VCI switching: A treelink PVC corresponds to a PVC switching route. You need
to specify the source (VPI, VCI) and the destination (VPI, VCI).
l Through VPI switching: A treelink PVC corresponds to multiple PVC switching routes.
You need to specify only the source VPI and the destination VPI. The VCI is unchanged.
The amount of treelink PVCs depends on the amount of physical bearers, switching methods
(VP or VC), and the amount of the upper-level applications.
l For VC switching, the amount of treelink PVCs depends on that of the PVCs of the upper-
level node.
l For VP switching, the amount of treelink PVCs depends on that of the PVCs of the upper-
level node and the VPI values of all PVCs. Assume that all the PVCs on the Iub interface

NodeB
of a lower-level NodeB are carried on one ATM physical bearer, that is, the slot number,
link type, link (group) number, and VPI of each PVC are the same as those of other PVCs.
In this case, only one treelink PVC needs to be configured.
NOTE
By adjusting the interface board of a lower-level NodeB or hub NodeB, you can meet the requirements for
the VPIs and VCIs of treelink PVCs.
Comparison Between VP Switching and VC Switching

l The planning and configuration based on VP switching is easier.
l The configuration based on VC switching is more flexible.
7.5 NodeBs in Direct/Cascading Connections

This defines the NodeBs in direct and cascading connections. In addition, it describes the
configuration differences between these two connections.
7.5.1 Definitions of NodeBs in Direct/Cascading Connections

The physical connections between an RNC and a NodeB are of two types: direct and cascading
connections.
7.5.2 Configuration Differences Between NodeBs in Direct/Cascading Connections
NodeBy in cascading connection is connected to NodeBx through E1, in which case NodeBx
works as the transmission equipment between NodeBy and the RNC. In this sense, it is similar
to configure NodeBs in direct or cascading connection. This, however, describes the
configuration differences between direct and cascading connections.
7.5.1 Definitions of NodeBs in Direct/Cascading Connections

The physical connections between an RNC and a NodeB are of two types: direct and cascading
connections.
Direct Connection
In direct connection, the NodeB is connected to the RNC directly or through transport equipment.
Figure 7-10 shows an example of direct connection between NodeBx and the RNC.
Cascading Connection
In cascading mode, the NodeB is connected to the RNC through another NodeB. Figure
7-10shows an example of cascading connection between NodeBy and the RNC. In this case,
NodeBx is called the NodeB that provides cascading connection for NodeBy.

NodeB
Figure 7-10 Direct and cascading connections
NOTE
Multi-level cascading is allowed. In multi-level cascading mode, NodeBy is connected to the RNC through
multiple NodeBs that provide cascading connections. Each cascaded NodeB occupies a portion of the
bandwidth between the RNC and the upper-level NodeB (that is, the NodeB that provides cascading
connection). The bandwidth is also required by the upper-level NodeB. Therefore, multi-level cascading
is not recommended.
7.5.2 Configuration Differences Between NodeBs in Direct/

Cascading Connections
NodeBy in cascading connection is connected to NodeBx through E1, in which case NodeBx
works as the transmission equipment between NodeBy and the RNC. In this sense, it is similar
to configure NodeBs in direct or cascading connection. This, however, describes the
configuration differences between direct and cascading connections.
NodeBx provides the cascading path for NodeBy in either of the following ways:
l NodeBx provides the E1/T1 timeslot cross function.

l NodeBx works as the ATM switching equipment, providing the VP/VC switching function,
which is also called the treelink PVC function.
Table 7-4 lists the configuration differences between NodeBs in direct/cascading connections.
Table 7-4 Configuration differences between NodeBs in direct/cascading connections
Configuration differences
NodeBx Prerequisites for NodeBy
between NodeBy and the
Cascading Path Configuration
NodeB in direct connection
Timeslot cross. The l NodeBx is connected to the RNC l NodeBy must be connected
NodeBx works as through E1/T1, including E1 over to NodeBx over fractional
the equipment that SDH. ATM and occupies only the
provides the l By default, NodeBx must be redundant timeslots of
timeslot cross connected to the RNC over NodeBx.
function. fractional ATM. Besides, there l You need to configure the
are redundant timeslots between timeslot cross connection on
NodeBx and the RNC. NodeBx.

NodeB
Configuration differences
NodeBx Prerequisites for NodeBy
between NodeBy and the
Cascading Path Configuration
NodeB in direct connection
ATM switching Redundant portions of the You need to add a treelink PVC
bandwidth are available between to NodeBx.
NodeBx and the RNC.
As the ATM switching equipment, NodeBx is connected to the RNC by E1/T1 or SDH with the
application as UNI, IMA, or STM-1. NodeBy may also be connected to NodeBx by E1/T1 with
the applications as UNI or IMA. This type of cascading path for the NodeB is recommended.


NodeB Initial Configuration Guide - (V100R010 - 01)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NodeB Initial Configuration Guide - (V100R010 - 01)

Uploaded by

Copyright:

Available Formats

NodeB

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Copyright © Huawei Technologies Co., Ltd. 2008. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

About This Document.....................................................................................................................1

2 Data Planning and Negotiation of NodeB Initial Configuration.....................................2-1

3 NodeB Initial Configuration....................................................................................................3-1

5 Adding a NodeB Through the Configuration File (Initial)...............................................5-1

6 Manually Adding a NodeB (Initial).......................................................................................6-1

Issue 01 (2008-06-25) Huawei Proprietary and Confidential i

6.2.5 Adding RF Modules (Initial)................................................................................................................6-32

ii Huawei Proprietary and Confidential Issue 01 (2008-06-25)

6.6.6 Adding IP Path Data (Initial).............................................................................................................6-200

7 Related Concepts of NodeB Initial Configuration..............................................................7-1

Issue 01 (2008-06-25) Huawei Proprietary and Confidential iii

Figure 4-1 Physical NodeB Basic Information window......................................................................................4-6

Issue 01 (2008-06-25) Huawei Proprietary and Confidential v

Figure 6-23 Adding the NGRU (BTS3812AE/BTS3812A for instance)...........................................................6-73

vi Huawei Proprietary and Confidential Issue 01 (2008-06-25)

Figure 6-65 Configuring the NCP and the CCP...............................................................................................6-197

Issue 01 (2008-06-25) Huawei Proprietary and Confidential vii

Table 1-1 DBS3800 initial configuration methods and scenarios........................................................................1-3

Issue 01 (2008-06-25) Huawei Proprietary and Confidential ix

Table 2-33 Negotiation and planned data of the IP route...................................................................................2-64

x Huawei Proprietary and Confidential Issue 01 (2008-06-25)

Table 6-26 Negotiation and planned data of the RRU.....................................................................................6-106

Issue 01 (2008-06-25) Huawei Proprietary and Confidential xi

Table 6-68 Description of the configuration pane............................................................................................6-197

xii Huawei Proprietary and Confidential Issue 01 (2008-06-25)

About This Document

WRAN CME V100R005

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 1

2 Data Planning and Negotiation of NodeB Initial Configuration

3 NodeB Initial Configuration

This describes how to add a NodeB on the CME.

4 Adding a NodeB Through the Template File (Initial)

5 Adding a NodeB Through the Configuration File (Initial)

6 Manually Adding a NodeB (Initial)

7 Related Concepts of NodeB Initial Configuration

2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)

Indicates a hazard with a high level of risk that, if not avoided,

Indicates a hazard with a medium or low level of risk which, if

Indicates a potentially hazardous situation that, if not avoided,

NOTE Provides additional information to emphasize or supplement

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files,directories,folders,and users are in boldface. For

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...} Alternative items are grouped in braces and separated by vertical

[ x | y | ... ] Optional alternative items are grouped in square brackets and

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 3

[ x | y | ... ] * Alternative items are grouped in braces and separated by vertical

Boldface Buttons,menus,parameters,tabs,window,and dialog titles are in

Key Press the key.For example,press Enter and press Tab.

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+A