Vous êtes sur la page 1sur 397

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


Copyright © Huawei Technologies Co., Ltd
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.2 Creating a Logical NodeB (Initial)..................................................................................................................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.1 Creating a Logical NodeB (Initial)..................................................................................................................6-3
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


Copyright © Huawei Technologies Co., Ltd
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.3.11 Adding an ALD (Initial).....................................................................................................................6-80
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.4.7 Adding an ALD (Initial).....................................................................................................................6-112
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)


Copyright © Huawei Technologies Co., Ltd
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


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide Figures

Figures

Figure 4-1 Physical NodeB Basic Information window......................................................................................4-6


Figure 4-2 Physical NodeB Basic Information window......................................................................................4-7
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-1 Physical NodeB Basic Information window......................................................................................5-6
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-1 Physical NodeB Basic Information window......................................................................................6-6
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


Copyright © Huawei Technologies Co., Ltd
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)


Copyright © Huawei Technologies Co., Ltd
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


Copyright © Huawei Technologies Co., Ltd
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-8 Negotiation and planned data of the UL/DL baseband resource group.............................................2-18
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


Copyright © Huawei Technologies Co., Ltd
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-1 Negotiation and planned data of the NodeB........................................................................................4-3
Table 4-2 Description of the configuration pane..................................................................................................4-7
Table 4-3 Description of the configuration pane................................................................................................4-12
Table 5-1 Negotiation and planned data of the NodeB........................................................................................5-3
Table 5-2 Description of the configuration pane................................................................................................5-12
Table 6-1 Negotiation and planned data of the NodeB........................................................................................6-3
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-5 Negotiation and planned data of the UL/DL baseband resource group.............................................6-21
Table 6-6 Description of the configuration pane................................................................................................6-23
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-10 Negotiation and planned data of the ALD.......................................................................................6-41
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-19 Negotiation and planned data of the ALD.......................................................................................6-81
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)


Copyright © Huawei Technologies Co., Ltd
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-30 Description of the configuration pane............................................................................................6-125
Table 6-31 Negotiation and planned data of the UNI links..............................................................................6-126
Table 6-32 Description of the configuration pane............................................................................................6-130
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-36 Description of the configuration pane............................................................................................6-140
Table 6-37 Description of the configuration pane............................................................................................6-141
Table 6-38 Negotiation and planned data of the timeslot cross links...............................................................6-142
Table 6-39 Description of the configuration pane............................................................................................6-143
Table 6-40 Negotiation and planned data of the transmission resource group (over ATM)............................6-144
Table 6-41 Description of the configuration pane............................................................................................6-146
Table 6-42 Negotiation and planned data of the SAAL links..........................................................................6-147
Table 6-43 Description of the configuration pane............................................................................................6-150
Table 6-44 Negotiation and planned data of the NBAP...................................................................................6-151
Table 6-45 Description of the configuration pane............................................................................................6-152
Table 6-46 Negotiation and planned data of the ALCAP................................................................................6-153
Table 6-47 Description of the configuration pane............................................................................................6-155
Table 6-48 Negotiation and planned data of the AAL2 PATH........................................................................6-156
Table 6-49 Description of the configuration pane............................................................................................6-159
Table 6-50 Negotiation and planned data of the OMCH (ATM).....................................................................6-161
Table 6-51 Description of the configuration pane............................................................................................6-163
Table 6-52 Negotiation and planned data of the treelink PVC.........................................................................6-164
Table 6-53 Description of the configuration pane............................................................................................6-168
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-56 Description of the configuration pane............................................................................................6-179
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-59 Description of the configuration pane............................................................................................6-185
Table 6-60 Negotiation and planned data of the timeslot cross links...............................................................6-187
Table 6-61 Description of the configuration pane............................................................................................6-188
Table 6-62 Negotiation and planned data of the IP route.................................................................................6-189
Table 6-63 Description of the configuration pane............................................................................................6-190
Table 6-64 Negotiation and planned data of the SCTP links...........................................................................6-191
Table 6-65 Description of the configuration pane............................................................................................6-193
Table 6-66 Description of the configuration pane............................................................................................6-194
Table 6-67 Negotiation and planned data of the IPCP.....................................................................................6-195

Issue 01 (2008-06-25) Huawei Proprietary and Confidential xi


Copyright © Huawei Technologies Co., Ltd
NodeB
Tables NodeB Initial Configuration Guide

Table 6-68 Description of the configuration pane............................................................................................6-197


Table 6-69 Negotiation and planned data of the transmission resource group (over IP).................................6-198
Table 6-70 Description of the configuration pane............................................................................................6-200
Table 6-71 Negotiation and planned data of the IP PATH...............................................................................6-201
Table 6-72 Description of the configuration pane............................................................................................6-203
Table 6-73 Description of the configuration pane............................................................................................6-204
Table 6-74 Negotiation and planned data of the OMCH (IP)..........................................................................6-206
Table 6-75 Description of the configuration pane............................................................................................6-207
Table 6-76 Negotiation and planned data of the transmission resource group whose destination IP network segment
is bound.............................................................................................................................................................6-209
Table 6-77 Description of the configuration pane............................................................................................6-211
Table 6-78 Negotiation and planned data of the IP clock links........................................................................6-212
Table 6-79 Description of the configuration pane............................................................................................6-213
Table 6-80 Description of the configuration pane............................................................................................6-214
Table 6-81 Negotiation and planned data of the IPQoS...................................................................................6-215
Table 6-82 Description of the configuration pane............................................................................................6-219
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-86 Description of the configuration pane............................................................................................6-232
Table 6-87 Description of the configuration pane............................................................................................6-233
Table 6-88 Description of the configuration pane............................................................................................6-235
Table 6-89 Description of the configuration pane............................................................................................6-236
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 6-92 Description of the configuration pane............................................................................................6-245
Table 6-93 Description of the configuration pane............................................................................................6-246
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)


Copyright © Huawei Technologies Co., Ltd
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


Copyright © Huawei Technologies Co., Ltd
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)


Copyright © Huawei Technologies Co., Ltd
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

Convention Description

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


Copyright © Huawei Technologies Co., Ltd
NodeB
About This Document NodeB Initial Configuration Guide

Convention Description

[ 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

Convention Description

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

Convention Description

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)


Copyright © Huawei Technologies Co., Ltd
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


Copyright © Huawei Technologies Co., Ltd
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)


Copyright © Huawei Technologies Co., Ltd
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 1-3


Copyright © Huawei Technologies Co., Ltd
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-1


Copyright © Huawei Technologies Co., Ltd
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

2-2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Exampl Source


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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-3


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Exampl Source


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)

2-4 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example 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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-5


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.
l The SNTP server of the NodeB
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

2-6 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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
Value range: 0 through 255

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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-7


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
Optional parameters:
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:
l REDUNDANCY (active and
standby backup): No sub-board
can be added. Only the
baseboard held in slot 14 can be
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.

2-8 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-9


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


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)
l 120 (E1 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.

2-10 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-4 Negotiation and planned data of the UL/DL baseband resource group
Input Field Description Example Source
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
baseband Id is, the HBBI/NBBI, EBBI/EBOI,
resource and HDLP/NDLP, cannot process
group baseband services.
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


Input Field Name Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-11


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
Value range: 0 through 2

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.
Value range: 0 through 1

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 -


number BBU that is connected to the RRU
in the chain or ring. This parameter
is valid for only the ring topology.
Value range: 0 through 2

2-12 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-13


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Break Break Position Second position of the break point -


position 2 2 only for the ring topology
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 the RRU ring, two break points
can be set. After the setting of
break point, the RRU chain is
divided into three parts:
l The first part refers to the
section between the head the of
RRU ring and the first break
point. This part of RRU service
can be affected.
l The second part refers to the
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.

2-14 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-6 Negotiation and planned data of the RRU


Input Field Name Description Example Source
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.
Value range: 0 through 249

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.
Value range: 0 through 7

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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-15


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
carrier RRU support)
l MINUS_75M (only four
carrier RRU support)
l PLUS_75M (only four
carrier RRU support)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

2-16 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

Table 2-7 Negotiation and planned data of the RHUB


Input Field Name Description Example Source
Data

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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-17


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

Equipment Layer Data of the Distributed NodeB

Table 2-8 Negotiation and planned data of the UL/DL baseband resource group
Input Field Description Example Source
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
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 such as the HBBU or the 0 Internal


DL rceGroup HBBUC that is not added to the planning
baseband Id UL baseband resource group
resource cannot process baseband services.
group 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.

2-18 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-9 Negotiation and planned data of the BBU


Input Field Name Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-19


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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

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

2-20 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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.
Optional parameters:
l HIGH (alarms related to high
impedance)
l LOW (alarms related to low
impedance)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-21


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Table 2-10 Negotiation and planned data of the RRU Chain


Input Field Name Description Example Source
Data

Chain Chain Type RRU topology structure Optional CHAIN


type parameters:
l CHAIN (chain topology)
l RING (ring topology)

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

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
Internal
Value range: 0 through 2
planning
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.
Value range: 0 through 1

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 -


number BBU that is connected to the RRU
in the chain or ring. This parameter
is valid for only the ring topology.
Value range: 0 through 2

2-22 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-23


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Break Break Position Second position of the break point -


position 2 2 only for the ring topology
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 the RRU ring, two break points
can be set. After the setting of
break point, the RRU chain is
divided into three parts:
l The first part refers to the
section between the head the of
RRU ring and the first break
point. This part of RRU service
can be affected.
l The second part refers to the
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.

2-24 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-11 Negotiation and planned data of the RRU


Input Field Name Description Example Source
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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-25


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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:
l Number of Carrier: 0 to 3
(MRRU/WRFU), 0 to 1
(PRRU)
l RX channel number: 0
through 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
carrier RRU support)
l MINUS_75M (only four
carrier RRU support)
l PLUS_75M (only four
carrier RRU support)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

2-26 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

Table 2-12 Negotiation and planned data of the RHUB


Input Field Name Description Example Source
Data

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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-27


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

ALD Data

Table 2-13 Negotiation and planned data of the ALD


Input Field Name Description Example Source
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

2-28 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-29


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.
l AISG2.0 The subunit number of
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
range: 0 through 255.

2-30 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-31


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

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
Input Field Name Description Example Source
Data

Slot No. SlotNo Number of slot where the NDTI or 14


NUTI is held (Slots 14 and 15 hold
only the NUTI)
Value range: 12 through 15

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.
Optional parameters:
l D32
l D64
l D128
l D256

2-32 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


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
CoverBoard, the value range is 1
through 8.
l When SubBdType is Channelled
CoverBoard, the value range is 1
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.
Value range: 4 through 100

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.
Optional parameters:
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-33


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
l When SubBdType is E1
CoverBoard, the value range is 0
through 7.
l When SubBdType is Channelled
CoverBoard, the value range is 0
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
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 Internal
used in compliance with the R6 planning
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.

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 through 20

2-34 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


Data

Discard HsdpaDR The link is not congested when frame 1


rate loss ratio is not higher than this
threshold threshold.
Value range: 0 through 1000

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


Input Field Name Description Example Source
Data

Slot No. SlotNo Number of slot where the NDTI 12


or NUTI is held (Slots 14 and 15
hold only the NUTI)
Value range: 12 through 15

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
l Channelled CoverBoard:
channelized optical sub-board

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.
l When SubBdType is E1
CoverBoard, the value range is
0 through 7.
l When SubBdType is
Channelled CoverBoard, the
value range is 0 through 62.

Scramble ScrambleMo Optional parameters: ENABLE


mode de l DISABLE (unavailable, the
scramble mode is disabled)
Internal
l ENABLE (The scramble mode planning
must be enabled if the E1/T1
transmission uses AMI line
codes.)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-35


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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

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 through 20

2-36 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


Data

Discard HsdpaDR The link is not congested when 1


rate frame loss ratio is not higher than
threshold this threshold.
Value range: 0 through 1000

Table 2-17 Negotiation and planned data of the fractional ATM links
Input Field Name Description Example Source
Data

Slot No. SlotNo Number of slot where the NDTI or 13


NUTI is held (Slots 14 and 15 hold
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

Scramble ScrambleMo Optional parameters: ENABLE


mode de l DISABLE (unavailable, the
scramble mode is disabled)
Internal
l ENABLE (The scramble mode planning
must be enabled if the E1/T1
transmission uses AMI line
codes.)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-37


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

HSDPA HsdpaSwitch Optional parameters: AUTO_A


switch l SIMPLE_FLOW_CTRL: Based DJUST_F
on the configured Iub bandwidth LOW_CT
and the bandwidth occupied by RL
R99 users, traffic is allocated to
HSDPA users when the physical
bandwidth restriction is taken
into account.
l AUTO_ADJUST_FLOW_CTR
L: 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.
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.

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 through 20

Discard HsdpaDR The link is not congested when 1


rate frame loss ratio is not higher than
threshold this threshold.
Value range: 0 through 1000

2-38 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-18 Negotiation and planned data of the timeslot cross links
Input Field Description Example Source
Data Name

Source slot SlotNo Number of the slot that holds 13


No. the NDTI or NUTI
Value range: 12 through 15

Source PortNo Number of the source E1/T1 3


port No. ports for timeslot cross links
Value range: 2 through 3

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)
Value range: 12 through 15

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


Input Field Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-39


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


Data Name

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


No. the SDT CES channel
Value range: 0 through 1

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)
Value range: 12 through 15

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 E1 CoverBoard: E1 coverboard
l Channelled CoverBoard:
channelized optical sub-board
l Unchannelled CoverBoard:
unchannelized optical sub-board

2-40 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Example Source


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
SubBdType(destination sub-board
type) is BaseBoard or E1
CoverBoard, the value range is 0
through 7.
l When Type is set to UNI and
SubBdType(destination sub-board
type) is Channelled CoverBoard,
the value range is 0 through 62.

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.
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
SubBdType(destination sub-board
type) is BaseBoard or E1
CoverBoard, the value range is 0
through 7.
l When Type is set to UNI and
SubBdType(destination sub-board
type) is Channelled CoverBoard,
the value range is 0 through 62.
l When Type is set to IMA and
SubBdType(destination sub-board
type) is BaseBoard or E1
CoverBoard, the value range is 0
through 3.
l When Type is set to IMA and
SubBdType(destination sub-board
type) is Channelled CoverBoard,
the value range is 0 through 1.
l When Type is STM1, the value
range is 0 through 1.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-41


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


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


channel SDT CES channel.
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


Input Field Description Example Source
Data Name

Port type Type Type of the interface that carries the IMA
UDT CES channel Optional
parameters:
l IMA
l STM1

Source slot PortNo Number of the slot that holds the NDTI 12
No. Value range: 12 through 13 Internal
planning
Source SubBdTyp Type of the sub-board where the BaseBoar
sub-board e source E1/T1 port is located by the d
type UDT CES channel Optional
parameters: Baseboard

Source port PortNo Number of the source E1/T1 ports for 1


No. the UDT CES channel
Value range: 0 through 1

2-42 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Example Source


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.
Value range: 4 through 47

Tx Clock TxClockM Optional parameters: ACM


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

Destinatio SlotNo Number of slot where the NDTI or 14


n slot No. NUTI is held (Slots 14 and 15 hold
only the NUTI)
Value range: 12 through 15

Destinatio SubBdTyp Type of the sub-board where the Channelle


n sub- e destination E1/T1 port is located by d
board type the UDT CES channel Optional CoverBoa
parameters: rd
l Baseboard
l E1 CoverBoard: E1 coverboard
l Channelled CoverBoard:
channelized optical sub-board
l Unchannelled CoverBoard:
unchannelized optical sub-board

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-43


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


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.
l When Type is set to IMA and
SubBdType(destination sub-board
type) is BaseBoard or E1
CoverBoard, the value range is 0
through 3.
l When Type is set to IMA and
SubBdType(destination sub-board
type) is Channelled CoverBoard,
the value range is 0 through 1.
l When Type is STM1, the value
range is 0 through 1.

Virtual VPI Identifier of the virtual channel for the 1


channel UDT 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


channel UDT CES channel.
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-21 Negotiation and planned data of the transmission resource group (over ATM)
Input Field Description Exampl Source
Data Name e

Port type Type Type of the interface that carries the IMA
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

2-44 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Exampl Source


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.
Value range: 32 through 15800

Receive RxBandwid Receive bandwidth of the resource 5000


bandwidth th group.
Value range: 30 through 20000

Table 2-22 Negotiation and planned data of the SAAL links


Input Field Description Exampl Source
Data Name e

Port type Type Type of the interface that carries the IMA
SAAL links Optional parameters:
l FRAATM
l IMA
l UNI
l STM1

Virtual VPI Identifier of the virtual channel for the 1


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

Virtual VCI Identifier of the virtual channel for the 34


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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-45


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Exampl Source


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.
Optional parameters:
l CBR (applicable to the CES
channel)
l RTVBR (applicable to services
carried on the AAL2 path)
l NRTVBR (applicable to services
carried on the AAL5 path)
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+.
Value range: 30 through 6759

Sustainable SCR The value of the SCR of the ATM 180


cell rate channel should be smaller than that of
the PCR. This parameter is valid only
when the service type is RTVBR or
NRTVBR
Value range: 30 through 6759

2-46 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Exampl Source


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
Value range: 0 through 65535 the
SAAL SAALNo SAAL number that carries the 2 destinati
number CCP on
Value range: 0 through 63

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-47


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Data Field Description Exampl Source


Name e

Flag Flag Master/slave flag for the MASTE


transmission channels Optional R
parameters: Internal
planning
l SLAVE
l MASTER

Table 2-24 Negotiation and planned data of the ALCAP


Input Field Description Example Source
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

Value range: 0 through 31

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


number Value range: 0 through 63

2-48 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

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


Input Field Description Example Source
Data Name

Port type Type Type of the interface that carries the IMA
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

Virtual VPI Identifier of the virtual channel for the 1


channel AAL2 path.
identifier Value range:
l Macro NodeB: 0 through 31 (six
Negotiat
successive values from 0 to 31)
ion with
l Distributed NodeB: 0 through 29 the
destinati
Virtual VCI Identifier of the virtual channel for the 37 on
channel AAL2 path.
identifier Value range:
l Macro NodeB: 32 through 255
(NDTI) or 32 through 127 (NUTI)
l Distributed NodeB: 32 through 127

Service ServiceTyp Optional parameters: RTVBR


type e l CBR (applicable to the CES
channel)
l RTVBR (applicable to services
carried on the AAL2 path)
l NRTVBR (applicable to services
carried on the AAL5 path)
l UBR+ (unspecified bit rate,
provides cell rate guarantee)
l UBR (unspecified bit rate)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-49


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


Data Name

Peak cell PCR Peak cell rate of the ATM channel 1920
rate When the service type is RTVBR,
NRTVBR or UBR+, the value of this
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.
l When the sub-board type is
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
the PCR. This parameter is valid only
when the service type is RTVBR or
NRTVBRThis parameter should be
one of the bandwidth parameters for the
transmission direction.
l When sub-board type is BaseBoard,
the value range is 30 through 15799.
l When the sub-board type is
Channelled CoverBoard or
Unchannelled CoverBoard, the
value range is 30 through 6759.

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.
Value range: 64 through 20000

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

2-50 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Example Source


Data Name

Resource RscgrpNo Number of the ATM transmission 1


group resource group
number Value range: 0 through 3

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
l Distributed NodeB: 0 through 29
Negotiati
Virtual VCI Virtual channel for the OMCH 33 on with
channel the
Value range: destinati
identifier
l Macro NodeB: 32 through 255 on
(NDTI) or 32 through 127 (NUTI)
l Distributed NodeB: 32 through 127

Service type ServiceTy Optional parameters: CBR


pe l CBR (applicable to the CES
channel)
l RTVBR (applicable to services
carried on the AAL2 path)
l NRTVBR (applicable to services
carried on the AAL5 path)
l UBR+ (unspecified bit rate,
provides cell rate guarantee)
l UBR (unspecified bit rate)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-51


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Data Field Description Example Source


Name

Peak cell PCR Peak cell rate of the ATM channel 512
rate When the service type is RTVBR,
NRTVBR or UBR+, the value of this
parameter should be greater than that of
the SCR.
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.

Sustainable SCR The value of the SCR of the ATM -


cell rate channel should be smaller than that of
the PCR. This parameter is valid only
when the service type is RTVBR or
NRTVBR
Value range: 30 through 6759

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

Join the JoinRscgrp Specify whether AAL2 path should be ENABLE


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

Resource RscgrpNo Number of the ATM transmission 2 Internal


group resource group planning
number Value range: 0 through 3

Flag Flag Master/slave flag for the remote OM MASTE


channels Optional parameters: R
l SLAVE
l MASTER

2-52 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

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
Optional parameters:
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
Optional parameters:
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-53


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Exampl Source


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.
l For the VC switching, the SourVPI
and the DestVPI must meet the
conditions of the source board and
the destination board respectively.

Destinatio DestVCI Identifier of the virtual channel for the 32


n VCI lower-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

Service ServiceType Optional parameters: RTVBR


type l RTVBR
l NRTVBR
l UBR (unspecified bit rate)
l UBR+ (unspecified bit rate,
provides cell rate guarantee)

2-54 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Exampl Source


Data e

Peak cell PCR Peak cell rate of the ATM channel 400
rate When the service type is RTVBR,
NRTVBR or UBR+, the value of this
parameter should be greater than that
of the SCR.
l When the service type is 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.

Sustainabl SCR The value of the SCR of the ATM 380


e cell rate channel should be smaller than that of
the PCR. This parameter is valid only
when the service type is RTVBR or
NRTVBR
Value range: 30 through 6759

Transport Layer Data (over IP)

Table 2-28 Negotiation and planned data of the ppp links


Input Field Name Description Example Source
Data

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


NUTI
Value range: 12 through 15

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


links
Value range: 0 through 7

Link LinkNo Each PPP link and each MLPPP link 0


Internal
number must have a unique number.
planning
Value range: 0 through 15

Authentica AuthType Optional parameters: NONAU


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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-55


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Example Source


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

2-56 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


Data

Protocol PFC Optional parameters: ENABLE


field l ENABLE
compress
l DISABLE

Address & ACFC Optional parameters: ENABLE


control l ENABLE
field
compress l DISABLE

HSDPA HsdpaSwitch Optional parameters: AUTO_A


switch l SIMPLE_FLOW_CTRL: Based DJUST_F
on the configured Iub bandwidth LOW_CT
and the bandwidth occupied by RL
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.
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.

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 through 20

Discard HsdpaDR The link is not congested when frame 1


rate loss ratio is not higher than this
threshold threshold.
Value range: 0 through 1000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-57


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Table 2-29 Negotiation and planned data of the MLPPP group and MLPPP links
Input Field Name Description Exampl Source
Data e

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


NUTI
Value range: 12 through 15

MLPPP GroupNo MLPPP group number 0


group Value range: 0 through 3
number

Authentica AuthType Optional parameters: NONAU


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

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

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
Value range: 0 through 7

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.
Value range: 0 through 15

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

2-58 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Exampl Source


Data e

IP header IPHC Optional parameters: ENABL


compressi l DISABLE: The IP header of the E
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

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

Restart RestartTimer Value range: 1 through 65535 3000


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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-59


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Name Description Exampl Source


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

Time delay HsdpaTD When the time delay is lower than this 4
threshold threshold, you can infer that the link is
not congested.
Value range: 0 through 20

Discard HsdpaDR The link is not congested when frame 1


rate loss ratio is not higher than this
threshold threshold.
Value range: 0 through 1000

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


Input Field Description Exampl Source
Data Name e

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

2-60 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Exampl Source


Data Name e

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


link
Value range: 0 through 1

Authentica AuthType Optional parameters: NONAU


tion type l NONAUTH (without authentication) TH

l PAP (with PAP authentication)


l CHAP (with CHAP authentication)

User name UserName This parameter is valid only when -


AuthType is set to PAP or CHAP.
Value range: not greater than 64
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

IP header IPHC Optional parameters: ENABL


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

PPP PPPMux Optional parameters: DISABL


multiframe l ENABLE E
multiplexi
ng l DISABLE

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-61


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Exampl Source


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

Time delay HsdpaTD When the time delay is lower than this 4
threshold threshold, you can infer that the link is
not congested.
Value range: 0 through 20

Discard HsdpaDR The link is not congested when frame 1


rate loss ratio is not higher than this
threshold threshold.
Value range: 0 through 1000

Table 2-31 Negotiation and planned data of the DEVIP


Input Field Description Exampl Source
Data Name e

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

2-62 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Description Exampl Source


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

Table 2-32 Negotiation and planned data of the timeslot cross links
Input Field Description Example Source
Data Name

Source slot SlotNo Number of the slot that holds 13


No. the NUTI
Value range: 12 through 15

Source PortNo Number of the source E1/T1 2 Internal


port No. ports for timeslot cross links planning
Value range: 2 through 3

Source TSBitMap Value range: TS1 to TS31 TS16 to TS23


timeslots

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-63


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


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)
Value range: 12 through 15

Destinatio DestPortN Number of the destination 0


n port No. o E1/T1 ports for timeslot
cross links
Value range: 0

Table 2-33 Negotiation and planned data of the IP route

Input Field Name Description Exampl Source


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.

2-64 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

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


Input Data Field Description Example Source
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.
The IP address 0.0.0.0 indicates that
this address is not in use.

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-65


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Table 2-35 Negotiation and planned data of the IPCP


Input Data Field Description Exampl Source
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
Value range: 0 through 19 the
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

Port No. PortNo Number of the CCP port. This 0


parameter is valid only when
PortType is set to CCP. Negotiati
on with
Value range: 0 through 65535 the
CCP SCTP SCTPNo SCTP number that carries the 2 destinati
number CCP on
Value range: 0 through 19

Flag Flag Master/slave flag for the MASTE Internal


transmission channels Optional R planning
parameters:
l SLAVE
l MASTER

2-66 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-36 Negotiation and planned data of the transmission resource group (over IP)
Input Field Description Example Source
Data Name

Port type ItfType Type of the interface that carries the IP ETH
transmission resource group Optional
parameters:
l ETH
l MLPPP
l PPP
l PPPoE

Resource RscgrpNo Value range: 0 through 3 0


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
value range is 8 through 31744.
l When the port type is PPP, the value
range is 8 through 1984.
l When the port type is PPPoE, the
value range is 8 through 100000.

Receive RxBandwi Receive bandwidth of the resource 10000


bandwidth dth group.
l When the port type is ETH, the
value range is 8 through 100000.
l When the port type is MLPPP, the
value range is 8 through 31744.
l When the port type is PPP, the value
range is 8 through 1984.
l When the port type is PPPoE, the
value range is 8 through 100000.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-67


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

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


Input Field Name Description Example Source
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
value range is 8 through 1984.
l When the port type is PPPoE, the
value range is 8 through 100000.
l When the port type is MLPPP, the
value range is 8 through 31744.
l When the port type is ETH, the
value range is 8 through 100000.

2-68 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Field Name Description Example Source


Data

Transmit TxBandwith When PATH joins the resource 1000


bandwidth group, the receive bandwidth does
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.
l When the port type is PPP, the
value range is 8 through 1984.
l When the port type is PPPoE, the
value range is 8 through 100000.
l When the port type is MLPPP, the
value range is 8 through 31744.
l When the port type is ETH, the
value range is 8 through 100000.

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


group resource group
number Value range: 0 through 3

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-69


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

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


Input Field Description Example Source
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
l MASTER (primary mode)
planning
l SLAVE (secondary mode)

2-70 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Table 2-39 Negotiation and planned data of the transmission resource group whose destination
IP network segment is bound
Input Field Description Example Source
Data Name

Port type ItfType Type of the interface that carries the ETH
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
Value range: 0 through 3 planning

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


Input Field Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-71


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Field Description Example Source


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.
Value range: 0 through 1

Table 2-41 Negotiation and planned data of the IPQoS


Input Field Description Example Source
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

Table 2-42 Negotiation and planned data of the NodeB


Input Field Name Description Example Source
Data

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

2-72 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-73


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Data Field Name Description Example Source

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)

2-74 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Cell Data

Table 2-44 Negotiation and planned data of the cell


Input Data Field Name Description Example Source

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
Value range: 0 through 65535
l Band 1
Common frequencies: 9612
through 9888 inclusive.
Offset:0
Special frequencies: None.
Offset: 0
l Band 2
Common frequencies: 9262
through 9538 inclusive.
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
through 1288 inclusive.
Offset:1525
Special frequencies: None.
Offset:0
l Band 4
Common frequencies: 1312
through 1513 inclusive.
Offset:1450
Special frequencies: {1662,
1687, 1712, 1737, 1762,
1787, 1812, 1837, 1862}.
Offset:1380.1
l Band 5
Common frequencies: 4132
through 4233 inclusive.
Offset:0
Special frequencies: {782,
787, 807, 812, 837, 862}.
Offset:670.1
l Band 6

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-75


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Data Field Name Description Example Source

Common frequencies: 4162


through 4188 inclusive.
Offset:0
Special frequencies:
{812,837}. Offset:670.1
l Band 7
Common frequencies: 2012
through 2338 inclusive.
Offset:2100
Special frequencies: {2362,
2387, 2412, 2437, 2462,
2487, 2512, 2537, 2562,
2587, 2612, 2637, 2662,
2687}. Offset:2030.1
l Band 8
Common frequencies: 2712
through 2863 inclusive.
Offset:340
Special frequencies: None.
Offset:0
l Band 9
Common frequencies: 8762
through 8912 inclusive.
Offset:0
Special frequencies: None.
Offset:0

2-76 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Data Field Name Description Example Source

Downlink UARFCNDo The UL and DL frequencies of 10562


frequency wnLink a cell must be at the same
frequency band.
Frequency (MHz) =
(Frequency / 5) + offset
Value range: 0 through 65535
l Band 1
Common frequencies:
10562 through 10838
inclusive. Offset:0
Special frequencies: None.
Offset:0
l Band 2
Common frequencies: 9662
through 9938 inclusive.
Offset:0
Special frequencies: {412,
437, 462, 487, 512, 537,
562, 587, 612, 637, 662,
687}. Offset:1850.1
l Band 3
Common frequencies: 1162
through 1513 inclusive.
Offset:1575
Special frequencies: None.
Offset:0
l Band 4
Common frequencies: 1537
through 1738 inclusive.
Offset:1805
Special frequencies: {1887,
1912, 1937, 1962, 1987,
2012, 2037, 2062, 2087}.
Offset:1735.1
l Band 5
Common frequencies: 4357
through 4458 inclusive.
Offset:0
Special frequencies: {1007,
1012, 1032, 1037, 1062,
1087}. Offset:670.1
l Band 6
Common frequencies: 4387
through 4413 inclusive.
Offset:0
Special frequencies: {1037,
1062}. Offset:670.1

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-77


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Data Field Name Description Example Source

l Band 7
Common frequencies: 2237
through 2563 inclusive.
Offset:2175
Special frequencies: {2587,
2612, 2637, 2662, 2687,
2712, 2737, 2762, 2787,
2812, 2837, 2862, 2887,
2912}. Offset:2105.1
l Band 8
Common frequencies: 2937
through 3088 inclusive.
Offset:340
Special frequencies: None.
Offset:0
l Band 9
Common frequencies: 9237
through 9387 inclusive.
Offset:0
Special frequencies: None.
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.

2-78 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB 2 Data Planning and Negotiation of NodeB Initial
NodeB Initial Configuration Guide Configuration

Input Data Field Name Description Example Source

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]
l When the sector works in
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].
Value range: 0 through 500

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
recommended to be set as
designed according to the
network planning.
Value range: 0 through 180000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 2-79


Copyright © Huawei Technologies Co., Ltd
2 Data Planning and Negotiation of NodeB Initial NodeB
Configuration NodeB Initial Configuration Guide

Input Data Field Name Description Example Source

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.
Value range: 0 through 30

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
consistent with that at the
RNC. Optional parameters:
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

2-80 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 3-1


Copyright © Huawei Technologies Co., Ltd
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-1


Copyright © Huawei Technologies Co., Ltd
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.

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-2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

Prerequisite
The RSS or the RBS is already configured.

Preparation

Table 4-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
Negotiati
l SHARED: indicates that all network
on with
operators can browse the information
the
of this logical NodeB and that of the
destinati
corresponding physical NodeB.
on
l NON_SHARED: indicates that only
the network operator specified by the
CnOpIndex parameter can browse
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-3


Copyright © Huawei Technologies Co., Ltd
NodeB
4 Adding a NodeB Through the Template File (Initial) NodeB Initial Configuration Guide

Input Field Description Exampl Source


Data Name e

Resource RscMngM Defines the resource management mode SHARE


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

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

4-4 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)

Input Field Description Exampl Source


Data Name e

Satellite SatelliteInd Identifies the satellite transmission on FALSE


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

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

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-5


Copyright © Huawei Technologies Co., Ltd
NodeB
4 Adding a NodeB Through the Template File (Initial) NodeB Initial Configuration Guide

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.

Scenario NodeB initial configuration

4-6 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)

Mandatory/ Mandatory
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 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 Click . The Physical NodeB Basic Information window is displayed, as shown in Figure
4-2.

Figure 4-2 Physical NodeB Basic Information window

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-7


Copyright © Huawei Technologies Co., Ltd
NodeB
4 Adding a NodeB Through the Template File (Initial) NodeB Initial Configuration Guide

Sequence of data Description


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

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.

Scenario NodeB initial configuration


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.
After the physical NodeB is created through the template or the configuration file, you need to manually
reconfigure the radio layer data according to the actual network planning. The reconfiguration involves
cell frequencies, uplink/downlink resource groups, and power.

4-8 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)

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).
l Reconfigure the equipment layer data.
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)
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.

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-9


Copyright © Huawei Technologies Co., Ltd
NodeB
4 Adding a NodeB Through the Template File (Initial) NodeB Initial Configuration Guide

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

4-10 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-11


Copyright © Huawei Technologies Co., Ltd
NodeB
4 Adding a NodeB Through the Template File (Initial) NodeB Initial Configuration Guide

Figure 4-5 NodeB Selection window

Table 4-3 Description of the configuration pane


Sequence of data Description
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.

4-12 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 4 Adding a NodeB Through the Template File (Initial)

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 4-13


Copyright © Huawei Technologies Co., Ltd
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.
5.2 Creating a Logical NodeB (Initial)
This describes how to create a logical NodeB. The RNC uses the logical NodeB to identify the
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.
5.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.
5.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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-1


Copyright © Huawei Technologies Co., Ltd
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.

5.2 Creating a Logical NodeB (Initial)


This describes how to create a logical NodeB. The RNC uses the logical NodeB to identify the
NodeB.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

Prerequisite
The RSS or the RBS is already configured.

5-2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (Initial)

Preparation

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-3


Copyright © Huawei Technologies Co., Ltd
NodeB
5 Adding a NodeB Through the Configuration File (Initial) NodeB Initial Configuration Guide

Input Field Description Exampl Source


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

5-4 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (Initial)

Input Field Description Exampl Source


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

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-5


Copyright © Huawei Technologies Co., Ltd
NodeB
5 Adding a NodeB Through the Configuration File (Initial) NodeB Initial Configuration Guide

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

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.

Scenario NodeB initial configuration

5-6 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (Initial)

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

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 logical NodeB on the left of the window. Click . The Import NodeB window is
displayed, as shown in Figure 5-2.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-7


Copyright © Huawei Technologies Co., Ltd
NodeB
5 Adding a NodeB Through the Configuration File (Initial) NodeB Initial Configuration Guide

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

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

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

5-8 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (Initial)

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.
After the physical NodeB is created through the template or the configuration file, you need to manually
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
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).
l Reconfigure the equipment layer data.
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

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-9


Copyright © Huawei Technologies Co., Ltd
NodeB
5 Adding a NodeB Through the Configuration File (Initial) NodeB Initial Configuration Guide

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

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

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

5-10 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (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).

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-11


Copyright © Huawei Technologies Co., Ltd
NodeB
5 Adding a NodeB Through the Configuration File (Initial) NodeB Initial Configuration Guide

Figure 5-4 NodeB Selection window

Table 5-2 Description of the configuration pane


Sequence of data Description
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 5-5.

5-12 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 5 Adding a NodeB Through the Configuration File (Initial)

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 5-13


Copyright © Huawei Technologies Co., Ltd
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
6.1 Creating a Logical NodeB (Initial)
This describes how to create a logical NodeB. The RNC uses the logical NodeB to identify the
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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-1


Copyright © Huawei Technologies Co., Ltd
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.7 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.
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-2 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

6.1 Creating a Logical NodeB (Initial)


This describes how to create a logical NodeB. The RNC uses the logical NodeB to identify the
NodeB.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

Prerequisite
The RSS or the RBS is already configured.

Preparation

Table 6-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 Negotiati
the RNC. Optional parameters: on with
the
l ATM_TRANS destinati
l IP_TRANS on
l ATMANDIP_TRANS

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-3


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Description Exampl Source


Data Name e

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.
l NON_SHARED: indicates that only
the network operator specified by the
CnOpIndex parameter can browse
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

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

6-4 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Description Exampl Source


Data Name e

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

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-5


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

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

6-6 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-7


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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
baseband processing interface unit, and is inserted in slots 8
and 9 in the baseband subrack.
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)

6-8 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.

6.2.1 Manually Creating a Physical NodeB (Initial)


This describes how to manually configure the basic information for the NodeB.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-9


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Preparation

Table 6-3 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)

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

6-10 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

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)

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.
l The SNTP server of the NodeB
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 Network
demodulation mode) planning
l DEM_4_CHAN (four-way
demodulation mode)
l DEM_ECON_4_CHAN (four-
way economical demodulation
mode)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-11


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

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

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
Value range: 0 through 255

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 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
Optional parameters:
l AU3
l AU4

6-12 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

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)

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 Internal
or the NUTI, in slots 12 and 13 planning
Optional parameters:
l REDUNDANCY (active and
standby backup): The board
Iub
must be the NUTI. No sub-
interface
board can be added. Only the
board
baseboard held in slot 12 can be
group
used. The attributes of the board
backup
held in slot 13 remain
mode
unchanged.
l SHARING (load sharing): The
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-13


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

IUBGroup2 Group backup mode of the Iub SHARIN


interface board, namely the NUTI, G
in slots 14 and 15 Optional
parameters:
l REDUNDANCY (active and
standby backup): No sub-board
can be added. Only the
baseboard held in slot 14 can be
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.

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

Figure 6-3 Create Physical NodeB dialog box

6-14 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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
displayed, as shown in Figure 6-4.

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.

Step 8 Click to save the settings.

----End

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-15


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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.

Scenario NodeB initial configuration


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

Table 6-4 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 Internal


monitoring controller and provides Boolean value NMON is planning
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
configuration, select applicable configured
baseband boards. in slots 0
and 1.

6-16 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Description Example Source


Data Name

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

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)
l 120 (E1 working mode)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-17


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Description Example Source


Data Name

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.

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 Equipment Layer window is
displayed.

6-18 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-19


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Option Description

Add channelized optical sub-board. Right-click the NUTI and choose Add Channelled
Coverboard... from the shortcut menu.
The 63 optical E1 ports on the channelized optical
sub-board are used for the following elements:
l IMA links in the IMA group
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
sub-board are used for the following elements:
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)
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.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

6-20 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

Table 6-5 Negotiation and planned data of the UL/DL baseband resource group

Input Field Description Example Source


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.
Internal
l An uplink baseband resource
planning
group can process a maximum of
six cells.
l Insufficient uplink baseband
resources may result in a cell
setup failure.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-21


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Description Example Source


Data Name

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


DL rceGroup DL baseband resource group, that
baseband Id is, the HBBI/NBBI, EBBI/EBOI,
resource and HDLP/NDLP, cannot process
group baseband services.
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.

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.

6-22 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Figure 6-6 Adding an uplink baseband resource group

Table 6-6 Description of the configuration pane

Sequence of data Description


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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-23


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

6.2.4 Adding an RRU (Initial, Macro 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.

Scenario NodeB initial configuration


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

6-24 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Preparation

Table 6-7 Negotiation and planned data of the RRU Chain


Input Field Name Description Example Source
Data

Chain Chain Type RRU topology structure Optional CHAIN


type parameters:
l CHAIN (chain topology)
l RING (ring topology)

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

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
Internal
Value range: 0 through 2
planning
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.
Value range: 0 through 1

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 -


number BBU that is connected to the RRU
in the chain or ring. This parameter
is valid for only the ring topology.
Value range: 0 through 2

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-25


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.

6-26 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

Break Break Position Second position of the break point -


position 2 2 only for the ring topology
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 the RRU ring, two break points
can be set. After the setting of
break point, the RRU chain is
divided into three parts:
l The first part refers to the
section between the head the of
RRU ring and the first break
point. This part of RRU service
can be affected.
l The second part refers to the
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-27


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Table 6-8 Negotiation and planned data of the RRU


Input Field Name Description Example Source
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.
Value range: 0 through 249

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.
Value range: 0 through 7

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)

6-28 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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
carrier RRU support)
l MINUS_75M (only four
carrier RRU support)
l PLUS_75M (only four
carrier RRU support)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-29


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

Table 6-9 Negotiation and planned data of the RHUB


Input Field Name Description Example Source
Data

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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

6-30 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-7.

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-31


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

6.2.5 Adding RF Modules (Initial)


This describes how to add RF modules, that is, the MAFU and MTRU modules.

Scenario NodeB initial configuration


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.

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 HBBI or NBBI is configured. For details, refer to Adding Boards in the Baseband Subrack
(Initial).

Preparation
None.

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 Equipment Layer window is
displayed.

Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-8.

6-32 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

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.

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

Prerequisite
The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-33


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Step 2 Click . The Physical NodeB Basic Information window is displayed.

Step 3 Select a physical NodeB, and then click . The NodeB Equipment Layer window is
displayed.

Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-9.

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.

Scenario NodeB initial configuration

6-34 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Mandatory/ Mandatory
Optional

NOTE

The NCMU is used only for the BTS3812AE, and is configured in subrack 8.

Prerequisite
The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-10.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-35


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

6.2.8 Adding an NPMU (Initial, Macro NodeB)


This describes how to add an NodeB Power Monitoring Unit (NPMU).

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

Prerequisite
The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

6-36 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.

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

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 Basic Info tab. Click in the PowerType editing box, the NPMU
Attribute is displayed, as shown in Figure 6-12.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-37


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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)


This describes how to configure the NodeB Power Supply Unit (NPSU) for the macro NodeB,
that is, the BTS3812AE or BTS3812A.

Scenario NodeB initial configuration


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
The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

6-38 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-13.

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.

Scenario NodeB initial configuration


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
The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical
NodeB (Initial).

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-39


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Preparation
None.

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-14.

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

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.

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

6-40 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

Table 6-10 Negotiation and planned data of the ALD


Input Field Name Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-41


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.

6-42 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.
l AISG2.0 The subunit number of
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
range: 0 through 255.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-43


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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

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 Equipment Layer window is
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.

6-44 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.

Step 7 Click the STMA tab, and click . Set related parameters based on the prepared data, and click

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-45


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Figure 6-16 BTS3812E panel

Table 6-11 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 Fan Provides the function of a fan, and is configured in subrack 1.

6-46 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Sequen Module/ Description


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
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
baseband processing interface unit, and is inserted in slots 8
and 9 in the baseband subrack.
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.

6.3.1 Manually Creating a Physical NodeB (Initial)


This describes how to manually configure the basic information for the NodeB.
6.3.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.3.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.3.4 Adding an RRU (Initial, Macro 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.3.5 Adding RF Modules (Initial)
This describes how to add RF modules, that is, the MAFU and MTRU modules.
6.3.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.3.7 Adding an NEMU (Initial, BTS3812E)
This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for the
BTS3812E.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-47


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

6.3.8 Adding an NPMU (Initial, Macro NodeB)


This describes how to add an NodeB Power Monitoring Unit (NPMU).
6.3.9 Adding NPSUs (Initial, BTS3812E)
This describes how to configure the NodeB Power Supply Unit (NPSU) for the macro NodeB,
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.
6.3.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.

6.3.1 Manually Creating a Physical NodeB (Initial)


This describes how to manually configure the basic information for the NodeB.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

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

Preparation

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

6-48 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example 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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-49


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.
l The SNTP server of the NodeB
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

6-50 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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
Value range: 0 through 255

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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-51


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
Optional parameters:
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:
l REDUNDANCY (active and
standby backup): No sub-board
can be added. Only the
baseboard held in slot 14 can be
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.

6-52 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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 logical NodeB on the left of the window, and then click . The Create Physical
NodeB dialog box is displayed, as shown in Figure 6-17.

Figure 6-17 Create Physical NodeB dialog box

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
displayed, as shown in Figure 6-18.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-53


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Figure 6-18 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.

Step 8 Click to save the settings.

----End

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

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

6-54 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.3.1 Manually Creating a Physical
NodeB (Initial).

Preparation

Table 6-13 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.
Internal
Baseboard - According to the capacity of the HBBI/ The HBOI planning
NBBI, EBBI/EBOI, HULP/EULP, and and the
HDLP/NDLP and the expected NodeB EBOI are
configuration, select applicable configured
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-55


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Description Example Source


Data Name

Bearer BearMod This parameter is valid only when the IPV4


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

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)
l 120 (E1 working mode)

6-56 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Description Example Source


Data Name

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.

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 Equipment Layer window is
displayed.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-57


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-19.

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


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

6-58 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Option Description

Add channelized optical sub-board. Right-click the NUTI and choose Add Channelled
Coverboard... from the shortcut menu.
The 63 optical E1 ports on the channelized optical
sub-board are used for the following elements:
l IMA links in the IMA group
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
sub-board are used for the following elements:
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.3.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.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-59


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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.3.2 Adding the Boards in the Baseband Subrack
(Initial).

Preparation

Table 6-14 Negotiation and planned data of the UL/DL baseband resource group

Input Field Description Example Source


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.
Internal
l An uplink baseband resource
planning
group can process a maximum of
six cells.
l Insufficient uplink baseband
resources may result in a cell
setup failure.

6-60 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Description Example Source


Data Name

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


DL rceGroup DL baseband resource group, that
baseband Id is, the HBBI/NBBI, EBBI/EBOI,
resource and HDLP/NDLP, cannot process
group baseband services.
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.

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-61


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Figure 6-20 Adding an uplink baseband resource group

Table 6-15 Description of the configuration pane

Sequence of data Description


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-20, and configure SrcCellId, SrcFachId, DestCellId, and
DestFachId.

6-62 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

6.3.4 Adding an RRU (Initial, Macro 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.

Scenario NodeB initial configuration


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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-63


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Preparation

Table 6-16 Negotiation and planned data of the RRU Chain


Input Field Name Description Example Source
Data

Chain Chain Type RRU topology structure Optional CHAIN


type parameters:
l CHAIN (chain topology)
l RING (ring topology)

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

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
Internal
Value range: 0 through 2
planning
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.
Value range: 0 through 1

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 -


number BBU that is connected to the RRU
in the chain or ring. This parameter
is valid for only the ring topology.
Value range: 0 through 2

6-64 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-65


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Break Break Position Second position of the break point -


position 2 2 only for the ring topology
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 the RRU ring, two break points
can be set. After the setting of
break point, the RRU chain is
divided into three parts:
l The first part refers to the
section between the head the of
RRU ring and the first break
point. This part of RRU service
can be affected.
l The second part refers to the
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.

6-66 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Table 6-17 Negotiation and planned data of the RRU


Input Field Name Description Example Source
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.
Value range: 0 through 249

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.
Value range: 0 through 7

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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-67


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
carrier RRU support)
l MINUS_75M (only four
carrier RRU support)
l PLUS_75M (only four
carrier RRU support)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

6-68 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

Table 6-18 Negotiation and planned data of the RHUB


Input Field Name Description Example Source
Data

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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-69


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-21.

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

6-70 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

6.3.5 Adding RF Modules (Initial)


This describes how to add RF modules, that is, the MAFU and MTRU modules.

Scenario NodeB initial configuration


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.

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 HBBI or NBBI is configured. For details, refer to Adding Boards in the Baseband Subrack
(Initial).

Preparation
None.

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 Equipment Layer window is
displayed.

Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-22.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-71


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

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

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

Prerequisite
The physical NodeB is configured. For details, refer to 6.3.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

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.

6-72 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Step 2 Click . The Physical NodeB Basic Information window is displayed.

Step 3 Select a physical NodeB, and then click . The NodeB Equipment Layer window is
displayed.

Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-23.

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)


This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for the
BTS3812E.

Scenario NodeB initial configuration

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-73


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Mandatory/ Optional
Optional

NOTE

The NEMU is applicable only to the BTS3812E.

Prerequisite
The physical NodeB is configured. For details, refer to 6.3.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-24.

6-74 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

6.3.8 Adding an NPMU (Initial, Macro NodeB)


This describes how to add an NodeB Power Monitoring Unit (NPMU).

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

Prerequisite
The physical NodeB is configured. For details, refer to 6.3.1 Manually Creating a Physical
NodeB (Initial).

Preparation
None.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-75


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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.

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

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 Basic Info tab. Click in the PowerType editing box, the NPMU
Attribute is displayed, as shown in Figure 6-26.

6-76 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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)


This describes how to configure the NodeB Power Supply Unit (NPSU) for the macro NodeB,
that is, the BTS3812E.

Scenario NodeB initial configuration


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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-77


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-27.

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

6-78 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.

Scenario NodeB initial configuration


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 The physical NodeB is configured. For details, refer to 6.3.1 Manually Creating a
Physical NodeB (Initial).
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

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-28.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-79


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

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

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

6-80 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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

Table 6-19 Negotiation and planned data of the ALD


Input Field Name Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-81


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.

6-82 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.
l AISG2.0 The subunit number of
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
range: 0 through 255.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-83


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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

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 Equipment Layer window is
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-29.

6-84 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Figure 6-29 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.

Step 7 Click the STMA tab, and click . Set related parameters based on the prepared data, and click

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-85


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Figure 6-30 DBS3800 panel

Table 6-20 Module information

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.1 Manually Creating a Physical NodeB (Initial)


This describes how to manually configure the basic information for the NodeB.
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)
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.4.5 Adding an NEMU (Initial, Distributed NodeB)

6-86 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for the
DBS3800.
6.4.6 Adding an NPMU (Initial, Distributed NodeB)
This describes how to add a NodeB Power Monitoring Unit (NPMU) of the DBS3800.
6.4.7 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.

6.4.1 Manually Creating a Physical NodeB (Initial)


This describes how to manually configure the basic information for the NodeB.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

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

Preparation

Table 6-21 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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-87


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example 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)

6-88 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.
l The SNTP server of the NodeB
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-89


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
Value range: 0 through 255

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)

6-90 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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
Optional parameters:
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:
l REDUNDANCY (active and
standby backup): No sub-board
can be added. Only the
baseboard held in slot 14 can be
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-91


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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 logical NodeB on the left of the window, and then click . The Create Physical
NodeB dialog box is displayed, as shown in Figure 6-31.

Figure 6-31 Create Physical NodeB dialog box

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
displayed, as shown in Figure 6-32.

6-92 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Figure 6-32 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.

Step 8 Click to save the settings.

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

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-93


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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
The physical NodeB is configured. For details, refer to 6.4.1 Manually Creating a Physical
NodeB (Initial).

Preparation

Table 6-22 Negotiation and planned data of the BBU


Input Field Name Description Example Source
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)

6-94 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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:
l MASTER (primary mode)
l SLAVE (secondary mode)

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)

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-95


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

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

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

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

6-96 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.
Optional parameters:
l HIGH (alarms related to high
impedance)
l LOW (alarms related to low
impedance)

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-97


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Step 3 Select a physical NodeB, and then click . The NodeB Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-33.

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

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

6-98 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

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
The BBU is configured. For details, refer to 6.4.2 Adding a BBU (Initial).

Preparation

Table 6-23 Negotiation and planned data of the UL/DL baseband resource group
Input Field Description Example Source
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 Internal
group can process a maximum of planning
six cells.
l Insufficient uplink baseband
resources may result in a cell
setup failure.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-99


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Description Example Source


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
baseband Id UL baseband resource group
resource cannot process baseband services.
group 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.

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

6-100 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Figure 6-34 Adding an uplink baseband resource group

Table 6-24 Description of the configuration pane


Sequence of data Description
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-34, and configure SrcCellId, SrcFachId, DestCellId, and
DestFachId.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-101


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

6.4.4 Adding an RRU (Initial, Distributed 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.

Scenario NodeB initial configuration


Mandatory/ Mandatory
Optional

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.

Prerequisite
The BBU is configured. For details, refer to 6.4.2 Adding a BBU (Initial).

Preparation

Table 6-25 Negotiation and planned data of the RRU Chain


Input Field Name Description Example Source
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

6-102 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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
Value range: 0 through 2

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.
Value range: 0 through 1

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 -


number BBU that is connected to the RRU
in the chain or ring. This parameter
is valid for only the ring topology.
Value range: 0 through 2

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-103


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.

6-104 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

Break Break Position Second position of the break point -


position 2 2 only for the ring topology
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 the RRU ring, two break points
can be set. After the setting of
break point, the RRU chain is
divided into three parts:
l The first part refers to the
section between the head the of
RRU ring and the first break
point. This part of RRU service
can be affected.
l The second part refers to the
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-105


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Table 6-26 Negotiation and planned data of the RRU


Input Field Name Description Example Source
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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

6-106 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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:
l Number of Carrier: 0 to 3
(MRRU/WRFU), 0 to 1
(PRRU)
l RX channel number: 0
through 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
carrier RRU support)
l MINUS_75M (only four
carrier RRU support)
l PLUS_75M (only four
carrier RRU support)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-107


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

Table 6-27 Negotiation and planned data of the RHUB


Input Field Name Description Example Source
Data

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.
Value range: 0 through 249

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.
Value range: 0 through 7

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 planning
the RRU ring)
l BRANCH (under the
RHUB node)

Floor Floor Floor for installing the RRU 0


Value range: -100 through
+1000

6-108 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

Vertical Vertical Vertical position of the RRU 0


Value range: 0 through 1000

Horizontal Horizontal Horizontal position of the 0


RRU
Value range: 0 through 1000

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 Equipment Layer window is
displayed.

Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-35.

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.

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-109


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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

6.4.5 Adding an NEMU (Initial, Distributed NodeB)


This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for the
DBS3800.

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

NOTE

The NEMU can be configured only in slot 00 of subrack 0.

Prerequisite
The BBU is configured. For details, refer to 6.4.2 Adding a BBU (Initial).

Preparation
None.

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 Equipment Layer window is
displayed.
Step 4 Click the Device Panel tab. The tab page is displayed, as shown in Figure 6-36.

6-110 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

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.

Scenario NodeB initial configuration


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

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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-111


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Step 2 Click . The Physical NodeB Basic Information window is displayed.

Step 3 Select a physical NodeB, and then click . The NodeB Equipment Layer window is
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

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

6-112 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

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

Table 6-28 Negotiation and planned data of the ALD


Input Field Name Description Example Source
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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-113


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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.

6-114 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.
l AISG2.0 The subunit number of
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
range: 0 through 255.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-115


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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

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 Equipment Layer window is
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-39.

6-116 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Figure 6-39 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.

Step 7 Click the STMA tab, and click . Set related parameters based on the prepared data, and click

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-117


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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)

6-118 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (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.
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.

Scenario NodeB initial configuration


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
coverboard does not exceed eight.
l The total number of IMA groups and UNI links on the same channelized optical subboard does not
exceed two.

Prerequisite
l The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a
Physical NodeB (Initial).
l The NDTI/NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the
Boards in the Baseband Subrack (Initial).

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-119


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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
Input Field Name Description Example Source
Data

Slot No. SlotNo Number of slot where the NDTI or 14


NUTI is held (Slots 14 and 15 hold
only the NUTI)
Value range: 12 through 15

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.
Optional parameters:
l D32
l D64
l D128
l D256

6-120 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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
CoverBoard, the value range is 1
through 8.
l When SubBdType is Channelled
CoverBoard, the value range is 1
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.
Value range: 4 through 100

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.
Optional parameters:
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.

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-121


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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
l When SubBdType is E1
CoverBoard, the value range is 0
through 7.
l When SubBdType is Channelled
CoverBoard, the value range is 0
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
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 Internal
used in compliance with the R6 planning
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.

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 through 20

6-122 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


Data

Discard HsdpaDR The link is not congested when frame 1


rate loss ratio is not higher than this
threshold threshold.
Value range: 0 through 1000

Procedure
l Add the IMA group and the IMA link individually.

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-123


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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.

6-124 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Figure 6-42 Configuring the IMA links in batches

Table 6-30 Description of the configuration pane


Sequence of data Description
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.

Scenario NodeB initial configuration


Mandatory/ Optional
Optional

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-125


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

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
coverboard does not exceed eight.
l The total number of IMA links, UNI links and Fractional ATM links on the same baseboard or E1
coverboard does not exceed eight.
l The total number of IMA groups and UNI links on the same channelized optical subboard does not
exceed two.

Prerequisite
l The physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a
Physical NodeB (Initial).
l The NDTI/NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the
Boards in the Baseband Subrack (Initial).
l The BBU of the distributed NodeB is configured, as described in 6.4.2 Adding a BBU
(Initial).

Preparation

Table 6-31 Negotiation and planned data of the UNI links


Input Field Name Description Example Source
Data

Slot No. SlotNo Number of slot where the NDTI 12


or NUTI is held (Slots 14 and 15
hold only the NUTI)
Value range: 12 through 15

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
l Channelled CoverBoard:
channelized optical sub-board

6-126 Huawei Proprietary and Confidential Issue 01 (2008-06-25)


Copyright © Huawei Technologies Co., Ltd
NodeB
NodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)

Input Field Name Description Example Source


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.
l When SubBdType is E1
CoverBoard, the value range is
0 through 7.
l When SubBdType is
Channelled CoverBoard, the
value range is 0 through 62.

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

Issue 01 (2008-06-25) Huawei Proprietary and Confidential 6-127


Copyright © Huawei Technologies Co., Ltd
NodeB
6 Manually Adding a NodeB (Initial) NodeB Initial Configuration Guide

Input Field Name Description Example Source


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