NodeB Initial Configuration Guide-(V100R010_01)

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:

[email protected]

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.


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)


i


Contents

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


Issue 01 (2008-06-25)


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)


iii


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)


v


Figures

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


Issue 01 (2008-06-25)


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)


vii


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)


ix


Tables

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


Issue 01 (2008-06-25)


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)


xi


Tables

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


Issue 01 (2008-06-25)


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

Issue 01 (2008-06-25)

Product Names

Versions

BTS3812A

V100R010

BTS3812AE

V100R010

BTS3812E

V100R010

DBS3800

V100R010

iDBS3800

V100R010


1


About This Document

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


Issue 01 (2008-06-25)


About This Document

Symbol

Description

DANGER

WARNING

CAUTION

Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save your time.

TIP

Provides additional information to emphasize or supplement important points of the main text.

NOTE

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

Issue 01 (2008-06-25)

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.


3


About This Document

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

4

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.


Issue 01 (2008-06-25)


1

1 Introduction to NodeB Initial Configuration

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)


1-1



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

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


Issue 01 (2008-06-25)



Table 1-1 DBS3800 initial configuration methods and scenarios

Issue 01 (2008-06-25)

Method

Scenario

4 Adding a NodeB Through the Template File (Initial)

The actual configuration type is the same as or similar to the template file.

5 Adding a NodeB Through the Configuration File (Initial)

If you need to configure multiple NodeBs with the same or similar configurations, you can create a typical configuration file for a NodeB, and then configure the other NodeBs by modifying the configuration file.

6 Manually Adding a NodeB (Initial)

After the template file or configuration file is imported, you are recommended to manually perform data reconfiguration if required.


1-3


2

2 Data Planning and Negotiation of NodeB Initial Configuration

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)


2-1



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 Data

Field Name

Description

Exampl e

NodeB ID

NodeB_Id

The NodeB ID is automatically allocated. You can define the logical NodeB before configuring it as a physical NodeB.

1

Name of the NodeB

NodeB_Na me

This parameter indicates the name of the NodeB. You are recommended to name the NodeB according to its geographical location.

NodeB_ 1

Bearer type

IubBearerT ype

Identify the transmission type of the Iub interface for the RNC. The type must match the type of the interface board at the RNC. Optional parameters:

ATM_T RANS

Sharing support

SharingSup port

l

ATM_TRANS

l

IP_TRANS

l

ATMANDIP_TRANS

Whether to share NodeB information Optional parameters: l

l

Telecom operator index

CnOpIndex

Network planning

NON_S HARED

SHARED: indicates that all network operators can browse the information of this logical NodeB and that of the corresponding physical NodeB.

Negotiati on with the destinati on

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

This parameter is valid only when the SharingSupport parameter is set to NON_SHARED.

Source

0

Value range: 0 through 3 Resource manageme nt mode

2-2

RscMngM ode

Defines the resource management mode when the bandwidth is allocated Optional parameters: l

SHARE

l

EXCLUSIVE


SHARE

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

ATM Address

NSAP

The NodeB relevant ATM address in hexadecimal format. This parameter is invalid when IubBearerType is set to IP_TRANS.

H'39010 1010101 01 0101010 1010101 01 0101010 101

You need to set the first byte of the ATM address to H'45 (indicating an E.164 address), H'39 (indicating a DCC address) or H'47 (indicating an ICD address).

Source

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 transport flag

Issue 01 (2008-06-25)

IPTransAp artInd

Transmissi on delay on the Iub interface

TransDelay

Transmissi on delay on the Iub interface in hybrid IP transport

IPApartTra nsDelay

Satellite transmissio n indication

SatelliteInd

Identifies whether hybrid transport is supported over the Iub interface. This parameter is valid only when IubBearerType is set to IP_TRANS or ATMANDIP_TRANS. Optional parameters: l

SUPPORT

l

NOT_SUPPORT

Initial round-trip transmission delay on the Iub interface in ATM circuit transport or IP dedicated transport

-

10

Value range: 0 through 65535 Initial round-trip transmission delay on the Iub interface in hybrid IP transport. This parameter is valid only when TransDelay is set to SUPPORT.

-

Value range: 0 through 65535 Identifies the satellite transmission on the Iub interface. Optional parameters: l

TRUE

l

FALSE


FALSE

2-3



Input Data

Field Name

Description

Exampl e

NodeB type

NodeBTyp e

Identifies the type of the logical NodeB. Optional parameters:

NORMA L

Protocol Version

ProtocolVe r

l

NORMAL

l

PICO_TYPE1

l

PICO_TYPE2

Protocol version of the NodeB. Optional parameters: l

R99

l

R4

l

R5

l

R6

Source

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

2-4

Input Data

Field Name

Description

Example

Working mode of E1/T1 links

E1T1WorkMod e

The working mode of E1/T1 links depends on the state of DIP switches on the BBU or NUTI and the configuration file.

E1

Clock source

ClockSource

This parameter is valid only when ClockWorkMode is set to MANUAL. Optional parameters:

LINE

l

GPSCARD (GPS card clock source)

l

BITS (BITS clock source): The outdoor BBU (HBBUC) cannot use this clock source.

l

LINE (clock source extracted from the Iub interface line)

l

IP (IP clock source)


Source

Negotiati on with the destinatio n

Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example

Working mode of the clock

ClockWorkMod e

Working mode of the system clock Optional parameters:

MANUA L

Working mode of the IP clock

Issue 01 (2008-06-25)


IPClockMode

GPS feeder delay

GPSCableDelay

SNTP switch

SNTPSwitch

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 free-run mode is the working mode for the clock source at an initial phase.

This parameter is valid only when ClockSource is set to IP. Optional parameters: l

AUTO (default value)

l

MANUAL (This parameter is configured when the IP clock is already configured.)

Delay of the GPS feeder

Network planning

-

0

Internal planning

ON

Network planning

Value range: 0 through 1000 Synchronization switch Optional parameters: l

ON (SNTP client requires time synchronization)

l

OFF (SNTP client does not require time synchronization)


Source

2-5



Input Data

Field Name

Description

Example

Source

IP address of the SNTP server

SNTPServerIP

The SNTP server is used to synchronize the time of multiple SNTP clients, which is important for centralized maintenance, especially for alarm management. 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.

10.11.1.1


The SNTP server of the NodeB can be either the M2000 or the RNC.

Synchroni zation period

SyncPeriod

Demodula tion mode

DemMode

High BER thresholds of E1/T1

Smooth power switch

2-6

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.

The period in which nodes are synchronized.

10

Value range: 1 through 525600

HighThreshold

SMTHPWRSwi tch

Demodulation mode of the NodeB Optional parameters: l

DEM_2_CHAN (two-way demodulation mode)

l

DEM_4_CHAN (four-way demodulation mode)

l

DEM_ECON_4_CHAN (fourway economical demodulation mode)

Optional parameters: l

1E-3

l

1E-4

l

1E-5

l

1E-6


OPEN

l

CLOSE


DEM_2_ CHAN

Network planning 1E-5

CLOSE

Issue 01 (2008-06-25)


Input Data Lower and upper limits of timer setting


Field Name

Description

Example

LowerLimit

Disabling the lower limit of the time range for the transmitter

0

Source

Value range: 0 through 255 UpperLimit

Disabling the upper limit of the time range for the transmitter

0

Value range: 0 through 255 NodeB resource distributio n mode

ResAllocateRul e

NodeB IP address

LocalIP

IP address of the NodeB for local maintenance

17.21.2.1 5

Subnet mask

LocalIPMask

Subnet mask of the NodeB IP address for local maintenance

255.255. 0.0

NMPT backup mode

NMPTBackup Mode

This parameter is available only for the macro NodeB.

ENABLE

NAOIFrameMo de (macro NodeB)

Frame structure of the optical port chip Optional parameters:

-

STM-1 frame mode

Managem ent unit

Bypass unit

Issue 01 (2008-06-25)

STM1FrameMo de (distributed NodeB) Au

Tu


PERFFIRST (handover performance priority mode)

l

CAPAFIRST (capacity priority mode)

l

FRAMEMODE_SONET (in SONET mode)

l

FRAMEMODE_SDH (in SDH mode)

This parameter is valid only for the channelized optical interface. Optional parameters: l

AU3

l

AU4


TU11 (the E1/T1 mode is T1)

l

TU12 (the E1/T1 mode is E1)


PERFFI RST

Internal planning

FRAME MODE_ SDH AU3


TU12

2-7



Input Data

Field Name

Description

Example

Power type of the macro NodeB

PowerType

Configuring the power type for the NodeB. This parameter is available only for the macro NodeB. Optional parameters:

-48 V DC

Report switch for call history record

l

-48 V DC

l

24 V DC

l

220 V AC

CHRSwitch

When the NodeB CHR report switch is on, the NodeB uploads the CHR log to the FTP server that is at the NodeB side.

OFF

IUBGroup1

Group backup mode of the Iub interface board, namely the NDTI or the NUTI, in slots 12 and 13 Optional parameters:

SHARIN G

l

l

Iub interface board group backup mode

2-8

IUBGroup2

REDUNDANCY (active and standby backup): The board must be the NUTI. No subboard can be added. Only the baseboard held in slot 12 can be used. The attributes of the board held in slot 13 remain unchanged.

Source

Internal planning

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.

Group backup mode of the Iub interface board, namely the NUTI, 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.


SHARIN G

Issue 01 (2008-06-25)



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

Field Name

Description

NMPT

NMPT

l

When the NMPT needs a backup, configure two NMPTs. The active NMPT is configured in slot 10, and the standby NMPT is configured in slot 11.

l

When the NMPT does not need a backup, configure one NMPT. The NMPT is configured in slot 10.

NMON

The NMON controls the RET controller and provides Boolean value monitoring interfaces such as the 32line Boolean input interface and 7-line Boolean output interface.

The NMON is configured in slot 16.

Baseboard

-

According to the capacity of the HBBI/ NBBI, EBBI/EBOI, HULP/EULP, and HDLP/NDLP and the expected NodeB configuration, select applicable baseband boards.

The HBOI and the EBOI are configured in slots 0 and 1.

Optional parameters:

The NUTI is configured in slot 13.

Bearer mode

-

BearMod e

l

NDTI: One NDTI provides eight E1/ T1 ports.

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.

This parameter is valid only when the transport board is the NUTI. Optional parameters: l

ATM

l

IPV4


Source

If backup is not required, configure the NMPT in slot 10.

NodeB monitoring unit

Transport boards

Issue 01 (2008-06-25)

Example

Internal planning

IPV4

2-9


Input Data

Field Name

Description

Example

IP clock switch

IPClock Switch

You need to set the IP clock switch on 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:

ENABLE

Line impedance

HSDPA switch

LineImp edance

HsdpaS witch

l

ENABLE

l

DISABLE

Line impedance of the E1 line Optional parameters: l

75 (E1 working mode)

l

100 (T1 working mode)

l


Source

75

This parameter is available when the 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 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

2-10


AUTO_A DJUST_F LOW_CT RL

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.


Issue 01 (2008-06-25)



Table 2-4 Negotiation and planned data of the UL/DL baseband resource group Input Data

Field Name

Description

ID of the UL baseband resource group

ULResou rceGroup Id

l

A board that is not added to the UL baseband resource group, that is, the HBBI/NBBI, EBBI/EBOI, and HULP/EULP, cannot process 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.

l

A board that is not added to the DL baseband resource group, that is, the HBBI/NBBI, EBBI/EBOI, and HDLP/NDLP, cannot process 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.

ID of the DL baseband resource group

DLResou rceGroup Id

Example

Source

1

0

Internal planning

Table 2-5 Negotiation and planned data of the RRU Chain Input Data

Field Name

Description

Example

Chain type

Chain Type

RRU topology structure Optional parameters:

CHAIN

Chain/ Ring head subrack number

Issue 01 (2008-06-25)

Head Subrack No.

l

CHAIN (chain topology)

l

RING (ring topology)

Number of the subrack that holds the head BBU in the chain or ring

0

Source

Internal planning



2-11



Input Data

Field Name

Description

Example

Chain/ Ring head board number

Head Board No.

Number of the slot that holds the head BBU in the chain or ring

0

Head port number

Head Port No.

Source

Optional parameters:0 Number of the port on the head BBU that is connected to the RRU in the chain or ring

0

Value range: 0 through 2 End subrack number

End Subrack No

Number of the subrack that holds the end BBU in the ring. This parameter is applicable only to the ring topology.

-

Value range: 0 through 1 End board number

End Board No

Number of the slot that holds the end BBU in the ring. This parameter is valid for only the ring topology.

-

Optional parameters:0 End port number

End Port No

Number of the port on the end BBU that is connected to the RRU in the chain or ring. This parameter is valid for only the ring topology.

-


2-12


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Break position 1

Break Position 1

This parameter indicates the position of the first break point.

OFF

Source

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:

Issue 01 (2008-06-25)

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.


2-13



Input Data

Field Name

Description

Example

Break position 2

Break Position 2

Second position of the break point only for the ring topology

-

Source

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


Issue 01 (2008-06-25)



Table 2-6 Negotiation and planned data of the RRU Input Data

Field Name

Description

RF Module

-

l

In 1 x 1 configuration, configure one RF module.

l

In 3 x 1 configuration, configure three RF modules.

l

In 3 x 2 configuration, configure three or six RF modules.

l

In 6 x 1 configuration, configure six RF modules.

Example

Source

Configure either the RRU or the WRFU Network planning

RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo

This parameter indicates the number of the chain to which the RRU is connected.

0

Value range: 0 through 249 RRU number

RRUNo

The TRUNK position indicates that the RRU is at the cascaded position of the main chain or ring. The BRANCH position indicates that the RRU is at the cascaded position where the parent node is located. The parent node refers to the RHUB.

2

Internal planning

Value range: 0 through 7 Board status

Topology position of the RRU

Issue 01 (2008-06-25)

BoardStatus

ToPoPosition

Blocking status of the RRU Optional parameters: l

Block

l

Unblock


TRUNK (in the main ring)

l

BRANCH (under the RHUB node)


UnBlock

TRUNK

Network planning

2-15



Input Data

Field Name

Description

Example

Initial correction value for the RTWP

RTWPofCarrie rCarrier numberonRx RX channel number

Set the initial correction value for the RTWP of the carrier and TX channel specified by the RRU. Value range:

0

RRU IF offset

Floor

IFOffset

Floor

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

Offset direction of the 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


l


Floor for installing the RRU

Source

MIDDLE

0

Value range: -100 through +1000

2-16


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Vertical

Vertical

Vertical position of the RRU

0

Source

Value range: 0 through 1000 Horizontal

Horizontal

Horizontal position of the RRU

0


Table 2-7 Negotiation and planned data of the RHUB Input Data

Field Name

Description

Example

RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0

Source


RRUNo


2

Internal planning



Floor

BoardStatus

ToPoPosition

Floor


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

0


Issue 01 (2008-06-25)


2-17



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0


Equipment Layer Data of the Distributed NodeB Table 2-8 Negotiation and planned data of the UL/DL baseband resource group Input Data

Field Name

Description


ULResou rceGroup Id

l

A board such as the HBBU or the HBBUC that is not added to the UL baseband resource group cannot process baseband services.

l


l


l


l


l



2-18

DLResou rceGroup Id


Example

Source

1

0

Internal planning

Issue 01 (2008-06-25)



Table 2-9 Negotiation and planned data of the BBU Input Data

Field Name

Description

Example

Board status

BoardStatus

Blocking status of the board Optional parameters:

UnBlock

Clock source

Bearer mode

HSUPA switch

Clock Mode

Line Code

Issue 01 (2008-06-25)

ClockSource 8K

BearMode

HSUPA

ClockMode

LineCode

l

Block

l

Unblock

E1/T1 ports for extracting the Iub interface clock signals. Optional parameters: l

None

l

Port 0 to port 7


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, the ATM transport layer cannot use the E1/T1 ports, that is, you cannot configure the physical links.


ENABLE (The HSUPA is supported)

l

DISABLE (The HSUPA is not supported)

For the cascaded NodeBs, the clock of the upper-level NodeB is set to 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)


HDB3 (for E1 mode)

l

AMI (for E1 or T1 mode)

l

B8ZS (for T1 mode)


Port 0

Source

Internal planning

ATM

Negotiati on with the destinatio n DISABL E

SLAVE

Network planning

HDB3


2-19



Input Data

Field Name

Description

Example

Frame Structure

FrameStru


E1_CRC 4_MULT I_FRAM E

HSDPA switch

Time delay threshold

HsdpaSwitch

HsdpaTD

l

E1_DOUBLE_FRAME (double frame, for E1 mode)

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)



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


When the time delay is lower than this threshold, you can infer that the link is not congested.

Source

AUTO_A DJUST_ FLOW_C TRL

4

Value range:0 to 20

2-20


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Discard rate threshold

HsdpaDR

The link is not congested when frame loss ratio is not higher than this threshold.

1

Source

Value range:0 to 1000 Working Mode

Issue 01 (2008-06-25)

WorkMode


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

l

CUSTOM (customized mode): 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.

OFF

Internal planning

Alarm ID

AlarmId

This parameter is valid only when WorkMode is set to CUSTOM.

-

Alarm voltage

ALarmVolta ge

This parameter is valid only when WorkMode is set to CUSTOM. Optional parameters:

-

l

HIGH (alarms related to high impedance)

l

LOW (alarms related to low impedance)


2-21



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

Field Name

Description

Example

Chain type

Chain Type


CHAIN


Head Subrack No.


Head Board No.

Head port number

Head Port No.

l


l



0

Value range: 0 through 1 Number of the slot that holds the head BBU in the chain or ring

0


0 Internal planning


Source

End Subrack No


-


End Board No


-


End Port No


-


2-22


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Break position 1

Break Position 1


OFF

Source


Issue 01 (2008-06-25)

l


l



2-23



Input Data

Field Name

Description

Example

Break position 2

Break Position 2


-

Source



l


l



2-24


Issue 01 (2008-06-25)




Field Name

Description

RF Module

-

l


l


l


l


Example

Source


RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0


RRUNo


2

Internal planning



Issue 01 (2008-06-25)

BoardStatus

ToPoPosition


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

2-25



Input Data

Field Name

Description

Example


RTWPofCarrier Carrier numberonRxRX channel number


0

RRU IF offset

Floor

IFOffset

Floor

l


l

RX channel number: 0 through 1

l




l


l


l


l


l


l



Source

MIDDLE

0


2-26


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0



Field Name

Description

Example

RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0

Source


RRUNo


2

Internal planning



Floor

BoardStatus

ToPoPosition

Floor


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

0


Issue 01 (2008-06-25)


2-27



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0


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

2-28

Input Data

Field Name

Description

Example

Source

Antenna connector number

AntennaNo

In the 2G extended scenario, this parameter is unavailable.

N0A

Network planning

Device Name

DeviceName

RET 1

Internal planning

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. Name of the ALD. The maximum length is a string of 31 characters.


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Scenario

UseCase

Scenario of the antenna Optional parameters:

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

l

Antenna polarizatio n type

Vendor code

RETType

VendorCode

Network planning

2G_EXTENSION: 2G extension. The 2G RET is controlled through the NodeB. It is an extended mode of cascaded NodeBs.

When the device type is either SINGLE_RET or MULTI_RET 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 code of the ALD. The length is a 2-byte letter or number. For details about the relation between the vendor code and vendor name of the ALD, refer to the AISG protocol.

Issue 01 (2008-06-25)

Source


DUAL

Internal planning

2-29


2-30


Input Data

Field Name

Description

Example

Equipmen t serial number

SerialNo

Serial number of the ALD. The maximum length is a 17-byte letter or number.

-

Antenna subunit number

SubUnit

Select different subunit numbers according to different antenna device types:

0

Antenna tilt angle

AntTilt

Working mode of the STMA

BypassMode

SASU gain

l

GSMGain

l

UMTSGa in

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.

Downtilt of the RET antenna

Source

Network planning

0

Value range: -100 through +300 Optional parameters: l

NORMAL (normal mode)

l

Bypass mode

According to different types of channels, the SASU gain can be 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.


NORMA L

0

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

DC switch on the SASU antenna connector

DCSwitch

DC switch (on the SASU antenna connector) status When the status is set to GSM, the DC power load of the SASU GSM cannot be started. Optional parameters:

UMTS

l

GSM (The GSM feeder supplies the power)

l

UMTS (The UMTS feeder supplies the power)

l

OFF

SASU GSM DC power load

DCload

The DC power load is applied to the TMA that simulates the GSM system. 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.

20

STMA gain

Gain


0

Source

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

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Source logical cell ID

SrcCellId


Source FACH ID

SrcFachId


Destination logical cell ID

DestCellId


Destination FACH ID

DestFachId


Source

Network planning


2-31



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 Data

Field Name

Description

Example

Slot No.

SlotNo

Number of slot where the NDTI or NUTI is held (Slots 14 and 15 hold only the NUTI)

14

Source

Value range: 12 through 15 Sub-board type

IMA group ID

Transmit frame length

2-32

SubBdType

IMAId

IMATxFram eLength

Type of the sub-board where the E1/ T1 port used by the IMA link is located Optional parameters: l

Baseboard

l

E1 CoverBoard: E1 coverboard

l

Channelled CoverBoard: channelized optical sub-board

l

When SubBdType is BaseBoard, the value range is 0 through 3.

l

When SubBdType is E1 CoverBoard, the value range is 0 through 3.

l

When SubBdType is Channelled CoverBoard, the value range is 0 through 1.

Longer transmit frame can enhance transmission efficiency but reduces error sensitivity. Therefore, the default value is recommended. Optional parameters: l

D32

l

D64

l

D128

l

D256


Channelle d CoverBoa rd

0 Internal planning

D128

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Minimum active links

IMAMinAct iveLinks

Threshold for identifying the 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.

1

Differentia l maximum delay

IMADiffMa xDelay

l


l


l


Different transmission links in an IMA group may result in different 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.

Source

25

Value range: 4 through 100 Scramble mode

Timeslot 16 support

ScrambleMo de

TimeSlot16


DISABLE (unavailable, the scramble mode is disabled)

l

ENABLE (The scramble mode must be enabled if the E1/T1 transmission uses AMI line codes.)

The channelized optical sub-board does not support this function. Optional parameters: l

ENABLE

l

DISABLE

ENABLE

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)


2-33



Input Data

Field Name

Description

Example

Source

Link number

LinkNo

Number of the E1/T1 ports for the links in an IMA group.

0, 1, 2


HSDPA switch

HsdpaSwitc h

l


l


l




l


l


HsdpaTD


Internal planning



4


2-34


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


HsdpaDR


1

Source


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

Field Name

Description

Example

Slot No.

SlotNo


12

Source


Link number

Scramble mode

Issue 01 (2008-06-25)

SubBdType

LinkNo

ScrambleMo de

Type of the sub-board where the E1/T1 port is located by the UNI link Optional parameters: l

Baseboard

l


l


Number of the E1/T1 ports for UNI links l


l


l




l



BaseBoard Internal planning

3

Negotiation with the destination

ENABLE Internal planning

2-35



Input Data

Field Name

Description

Example

Timeslot 16 support

TimeSlot16

The channelized optical subboard does not support this function. Optional parameters:

DISABLE

l

ENABLE

l

DISABLE

Source

After this parameter is enabled, the bandwidth of the UNI link is added by 64 kbit/s. HSDPA switch


HsdpaSwitc h

HsdpaTD



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



AUTO_AD JUST_FLO W_CTRL

4

Value range: 0 through 20 2-36


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


HsdpaDR


1

Source


Table 2-17 Negotiation and planned data of the fractional ATM links Input Data

Field Name

Description

Example

Slot No.

SlotNo


13


Source

Internal planning

Sub-board type

SubBdType

Type of the sub-board with the E1/ T1 port available for the fractional ATM link Optional parameters: Baseboard

BaseBoar d

Port No.

E1T1No

Number of the E1/T1 port available for the fractional ATM link

0

Negotiatio n with the destinatio n Internal planning

Value range: 0 through 1 Link number

LinkNo


1

Timeslots

TSBitMap

The fractional ATM link provides timeslots for the 3G equipment. If port 0 is configured, the timeslots must be reserved for timeslot cross connection.

TS24 to TS31

Negotiatio n with the destinatio n

Value range: TS1 to TS31 Scramble mode

Issue 01 (2008-06-25)

ScrambleMo de



l




2-37



Input Data

Field Name

Description

Example

HSDPA switch

HsdpaSwitch




HsdpaTD

l


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



Source

4

Value range: 0 through 20 Discard rate threshold

HsdpaDR


1


2-38


Issue 01 (2008-06-25)



Table 2-18 Negotiation and planned data of the timeslot cross links Input Data

Field Name

Description

Example

Source slot No.

SlotNo

Number of the slot that holds the NDTI or NUTI

13

Source

Value range: 12 through 15 Source port No.

PortNo

Number of the source E1/T1 ports for timeslot cross links

3

Value range: 2 through 3 Source timeslots

TSBitMap

Destinatio n slot No.

DestSlotN o

Value range: TS1 to TS31 Number of the slot that holds the NDTI or NUTI (The number must be identical with that of the SlotNo)

TS16 to TS23 Internal planning

13

Value range: 12 through 15 Destinatio n port No.

DestPortN o

Number of the destination E1/T1 ports for timeslot cross links

0

Value range: 0

Table 2-19 Negotiation and planned data of the SDT CES

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example

Port type

Type

Type of the interface that carries the SDT CES channels Optional parameters:

FRAATM

Source slot No.

PortNo

Source sub-board type

SubBdTyp e

l

FRAATM

l

IMA

l

UNI

l

STM1

Number of the slot that holds the NDTI

Source

Internal planning 12

Value range: 12 through 13 Type of the sub-board where the source E1/T1 port is located by the SDT CES channel Optional parameters: Baseboard


BaseBoar d

2-39



Input Data

Field Name

Description

Example

Source port No.

PortNo

Number of the source E1/T1 ports for the SDT CES channel

0

Source

Value range: 0 through 1 Partial fill level

PFL

ATM cell has 48-byte payloads. 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.

47

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. Value range: TS1 to TS31


SlotNo


TS1 to TS7 13

Value range: 12 through 15 Destinatio n subboard type

2-40

SubBdTyp e

Type of the sub-board where the destination E1/T1 port is located by the SDT CES channel Optional parameters: l

Baseboard

l


l


l

Unchannelled CoverBoard: unchannelized optical sub-board


BaseBoar d

Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example

Destinatio n port No.

E1T1No

Number of the destination E1/T1 port for the SDT CES channel (This parameter is valid only when Type is set to FRAATM or UNI).

0

Link No./ IMA ID

Issue 01 (2008-06-25)


LinkNo/ IMAId

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.

Number of the fractional ATM or UNI link, of the IMA group, or of the STM1 optical port that carries the SDT CES channel. l


l


l


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.


Source

0

2-41



Input Data

Field Name

Description

Example

Virtual channel identifier

VPI

Identifier of the virtual channel for the SDT CES channel.

1


VCI

Source

Value range: 0 through 31 (six successive values from 0 to 31) Identifier of the virtual channel for the SDT CES channel. 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.

32

Table 2-20 Negotiation and planned data of the UDT CES Input Data

Field Name

Description

Example

Port type

Type

Type of the interface that carries the UDT CES channel Optional parameters:

IMA

l

IMA

l

STM1

Source slot No.

PortNo



SubBdTyp e

Type of the sub-board where the source E1/T1 port is located by the UDT CES channel Optional parameters: Baseboard

BaseBoar d

Source port No.

PortNo

Number of the source E1/T1 ports for the UDT CES channel

1

Source

12


Internal planning


2-42


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Partial fill level

PFL

The value of the partial fill 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.

47

Source

Value range: 4 through 47 Tx Clock Mode


TxClockM ode

SlotNo


NOACM (non-adaptive clock mode)

l

NOACM (adaptive clock mode)


ACM

14


Issue 01 (2008-06-25)

SubBdTyp e

Type of the sub-board where the destination E1/T1 port is located by the UDT CES channel Optional parameters: l

Baseboard

l


l


l




2-43



Input Data

Field Name

Description

Example

Optical port No./ IMA ID

LinkNo/ IMAId

Number of the IMA group or STM1 optical port that carries the UDT CES channel.

0


VPI


VCI

l


l


l


Identifier of the virtual channel for the UDT CES channel.

Source

1

Value range: 0 through 31 (six successive values from 0 to 31) Identifier of the virtual channel for the UDT CES channel. l


l


32

Table 2-21 Negotiation and planned data of the transmission resource group (over ATM) Input Data

Field Name

Description

Exampl e

Port type

Type

Type of the interface that carries the transmission resource group Optional parameters:

IMA

Resource group number

2-44

RscgrpNo

l

FRAATM

l

IMA

l

UNI

l

STM1



Source

Internal planning

1

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

Transmit bandwidth

TxBandwidt h

The transmit bandwidth of the resource group cannot exceed the bandwidth of the port to which the resource group belong.

5000

Source

Value range: 32 through 15800 Receive bandwidth

RxBandwid th

Receive bandwidth of the resource group.

5000


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

Field Name

Description

Exampl e

Port type

Type

Type of the interface that carries the SAAL links Optional parameters:

IMA



Issue 01 (2008-06-25)

VPI

l

FRAATM

l

IMA

l

UNI

l

STM1

Identifier of the virtual channel for the SAAL links.

1

Value range:

VCI

l

Macro NodeB: 0 through 31 (six successive values from 0 to 31)

l

Distributed NodeB: 0 through 29


Source


34

Value range: l

Macro NodeB: 32 through 255 (NDTI) or 32 through 127 (NUTI)

l



2-45



Input Data

Field Name

Description

Exampl e

Service type

ServiceTyp e

When this parameter is set to CBR or 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.

RTVBR

Source


Peak cell rate

Minimum cell rate

PCR

MCR

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 rate of the ATM channel 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.

The value of the MCR of the ATM channel should be smaller than that of the PCR. This parameter is valid only when the service type is UBR+.

200

-

Value range: 30 through 6759 Sustainable cell rate

SCR

The value of the SCR of the ATM channel should be smaller than that of the PCR. This parameter is valid only when the service type is RTVBR or NRTVBR

180


2-46


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

Join the resource group

JoinRscgrp

Specify whether this link should be added to the resource group. Optional parameters:

ENABL E


RscgrpNo

l

DISABLE

l

ENABLE

Number of the ATM transmission resource group

Source

Internal planning 1


Table 2-23 Negotiation and planned data of the NBAP Input Data Port type

SAAL number

Field Name

Description

Exampl e

PortType


NCP

SAALNo

l

NCP

l

CCP

SAAL number that carries the NCP

1


NCP Flag

Flag

Port type

Port No.

PortType

PortNo

CCP

Master/slave flag for the transmission channels Optional parameters: l

SLAVE

l

MASTER


NCP

l

CCP

Number of the CCP port. This parameter is valid only when PortType is set to CCP.

MASTE R

CCP

SAALNo

SAAL number that carries the CCP

Internal planning Negotiati on with the destinati on

Internal planning

Internal planning

0

Value range: 0 through 65535 SAAL number

Source

2



Issue 01 (2008-06-25)


2-47


Input Data Flag


Field Name

Description

Exampl e

Flag

Master/slave flag for the transmission channels Optional parameters:

MASTE R

l

SLAVE

l

MASTER

Source

Internal planning

Table 2-24 Negotiation and planned data of the ALCAP Input Data

Field Name

Description

Example

Node type

NodeType

The exchange node must be configured before configuring the adjacent node.

LOCAL

Source

The exchange node cannot be carried on the SAAL link on the NDTI. Optional parameters:

Adjacent node identifier

ANI

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)

Identify an adjacent node. This parameter is valid only when the parameter NodeType is set to ADJNODE.

Internal planning


2-48

Network service access point

NSAP

SAAL number

SAALNo

The full name is: Net service access point. When the NodeB uses ATM transmission, the NSAP is the address of the NodeB that is connected to the AAL2 path. The address is a hexadecimal with a length of 20 bytes (excluding the prefix H'). SAAL number that carries the ALCAP

H'390101 01010101 01010101 01010101 01010101 01

3



Issue 01 (2008-06-25)



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

Field Name

Description

Example

Port type

Type

Type of the interface that carries the AAL2 PATH Optional parameters:

IMA

FRAATM

l

IMA

l

UNI

l

STM1

PATH type PathType

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

RT


Identifier of the virtual channel for the AAL2 path.

1


Service type

Issue 01 (2008-06-25)

l

VPI

Source

Value range:

VCI

l


l



37

Negotiat ion with the destinati on

Value range:

ServiceTyp e

l


l




l


l


l


l



RTVBR

2-49



Input Data

Field Name

Description

Example

Peak cell rate

PCR

Peak cell rate of the ATM channel 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.

1920

Sustainabl e cell rate

Received cell rate

SCR

RCR

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.

The value of the SCR of the ATM 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.

This parameter must be consistent with 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.

Source

960

2048

Value range: 64 through 20000 Join the resource group

2-50

JoinRscgrp

Specify whether AAL2 path should be added to the resource group. Optional parameters: l

DISABLE

l

ENABLE



Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


RscgrpNo


1

Source


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

Field Name

Description

Example

Port type

Type

Type of the interface that carries the OMCH Optional parameters:

UNI



Service type

Issue 01 (2008-06-25)

VPI

l

FRAATM

l

IMA

l

UNI

l

STM1

Virtual channel for the OMCH

Source

1

Value range:

VCI

l

Macro NodeB: 1 or within the VPI range of the actual board configuration

l



33

Value range:

ServiceTy pe

l


l




l


l


l


l




CBR

2-51



Input Data

Field Name

Description

Example

Peak cell rate

PCR

Peak cell rate of the ATM channel When the service type is RTVBR, NRTVBR or UBR+, the value of this parameter should be greater than that of the SCR.

512

Sustainable cell rate

SCR

l


l



Source

-


2-52

Local IP address of the OMCH

LocalIP

IP address for NodeB remote maintenance

10.1.2.10

Destination IP address of the OMCH

DestIP

Destination IP address for NodeB remote maintenance, that is, the IP address configured on the ATM interface board at the RNC.

10.1.2.1

Destination subnet mask of the OMCH

DestIPMas k

Subnet mask of the destination IP address for NodeB remote maintenance

255.255. 255.0


JoinRscgrp

Specify whether AAL2 path should be added to the resource group. Optional parameters:

ENABLE


RscgrpNo

Flag

Flag

l

DISABLE

l

ENABLE


2

Internal planning

Value range: 0 through 3 Master/slave flag for the remote OM channels Optional parameters: l

SLAVE

l

MASTER


MASTE R

Issue 01 (2008-06-25)



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

Field Name

Description

Exampl e

Source port type

SourceType

Type of the interface that carries the source port of the treelink PVC Optional parameters:

FRAAT M

Destinatio n port type

ByPassMo de

Source VPI

DestinationT ype

ByPassMode

SourVPI

l

FRAATM

l

IMA

l

UNI

l

STM1

Type of the interface that carries the destination port of the treelink PVC Optional parameters: l

FRAATM

l

IMA

l

UNI

l

STM1

When the NodeB is powered off or exceptions occur to the NodeB, the 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)

Virtual channel used by the upper level network link l

Issue 01 (2008-06-25)

For the VP switching, the source port VPI must be beyond the VPI configured to the board, and the value cannot be 1.

l

For the VC switching, the source 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.


Source

UNI

Internal planning DISABL E

1


2-53


Input Data

Field Name

Description

Exampl e

Source VCI

SourVCI

Identifier of the virtual channel for the upper-level links. This parameter is valid for VC switching.

33

Destinatio n VPI

Destinatio n VCI

Service type

2-54


DestVPI

DestVCI

ServiceType

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

Virtual channel used by the lowerlevel 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


Identifier of the virtual channel for the lower-level links. This parameter is valid for VC switching. l


l



RTVBR

l

NRTVBR

l


l



Source

1

32

RTVBR

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

Peak cell rate

PCR

Peak cell rate of the ATM channel When the service type is RTVBR, NRTVBR or UBR+, the value of this parameter should be greater than that of the SCR.

400


SCR

l

When the service type is UBR, the value range is 30 to 6760.

l



Source

380


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

Field Name

Description

Example

Slot No.

SlotNo

Number of the slot that holds the NUTI

13

Source

Value range: 12 through 15 Port No.

PortNo

Number of the E1/T1 ports for PPP links

0


LinkNo

Each PPP link and each MLPPP link must have a unique number.

0

Value range: 0 through 15 Authentica tion type

Issue 01 (2008-06-25)

AuthType


NONAUTH (without authentication)

l

PAP (with PAP authentication)

l

CHAP (with CHAP authentication)


Internal planning

NONAU TH

2-55



Input Data

Field Name

Description

Example

User name

UserName

When AuthType is not set to NONAUTH, this field is mandatory, otherwise, the authentication fails.

-

Source

Value range: not greater than 64 characters Timeslot map

TSBitMap

A map of the timeslots for PPP links. The map is presented in binary format or the chart. If a timeslot is selected, it is in use. Otherwise, it is not in use.

TS1 to TS15

Local IP address

LocalIP

Local IP address of the PPP link. When the value is 0.0.0.0, it indicates that the parameter needs to be negotiated with the RNC.

17.17.17. 111

Destinatio n IP address

PeerIP

Destination IP address of the PPP link

17.17.17. 17

IP header compressi on

2-56

IPHC

PPP multiframe multiplexi ng

PPPMux

Maximum received unit

MRU

Restart timer of packet request response

RestartTimer

l

In cascading mode, this parameter specifies the IP address of a lowerlevel 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.


DISABLE: The IP header of the peer end is not compressed.

l

ENABLE: The UDP/IP header of the peer end is compressed.


ENABLE

l

DISABLE

Expected value sent from the peer end


ENABLE

DISABL E Internal planning 1500

Value range: 128 through 1500 Value range: 1 through 65535


3000

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Protocol field compress

PFC


ENABLE

Address & control field compress

ACFC

HSDPA switch

HsdpaSwitch


HsdpaTD

l

ENABLE

l

DISABLE


ENABLE

l

DISABLE



l


l



Source

ENABLE


4


HsdpaDR


1


Issue 01 (2008-06-25)


2-57



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

Field Name

Description

Exampl e

Slot No.

SlotNo


13

Source

Value range: 12 through 15 MLPPP group number

GroupNo

Authentica tion type

AuthType

User name

MLPPP group number

0


UserName



l


l



NONAU TH

Internal planning

-

Value range: not greater than 64 characters Local IP address

LocalIP

Local IP address of the MLPPP group

16.16.16. 111

Local subnet mask

LocalMask

Subnet mask of the local IP address for the MLPPP group

255.255. 255.0


PeerIP

Peer IP address of the MLPPP group

16.16.16. 16

Port No.

PortNo

Number of the E1/T1 ports for MLPPP links

0



LinkNo

Number of the MLPPP link that joins the MLPPP group. Each MLPPP and each PPP link must have a unique number.

1

Internal planning

TS24 to TS31


Value range: 0 through 15 Timeslot map

2-58

TSBitMap

A map of the timeslots for MLPPP links. The map is presented in binary format or the chart. If a timeslot is selected, it is in use. Otherwise, it is not in use.


Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Exampl e


IPHC


ENABL E


PPPMux

Multi-class PPP

MCPPP

l


l



ENABLE

l

DISABLE


ENABLE (using the MCPPP)

l

DISABLE (not using the MCPPP)


DISABL E

ENABL E


MRU

1500


RestartTimer


3000


PFC


ENABL E


ACFC


l

ENABLE

l

DISABLE


ENABLE

l

DISABLE


Source

Internal planning

ENABL E

2-59



Input Data

Field Name

Description

Exampl e

HSDPA switch

HsdpaSwitch


AUTO_ ADJUST _FLOW _CTRL


HsdpaTD

l


l


l



Source

4


HsdpaDR


1


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

Field Name

Description

Exampl e

Source

Slot No.

SlotNo


13

Internal planning


2-60


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

Port No.

PortNo

Number of the FE port for the PPPoE link

0

Source


User name

AuthType

UserName



l


l


This parameter is valid only when AuthType is set to PAP or CHAP.

NONAU TH

-

Value range: not greater than 64 characters

Issue 01 (2008-06-25)

Local IP address

LocalIP

Local IP address of the PPPoE link

12.3.0.1

Local subnet mask

LocalMask

Subnet mask of the local IP address

255.255. 255.0

IP header compressio n

IPHC


ENABL E

l


l



MRU



RestartTim er


3000


PPPMux


DISABL E


1450


l

ENABLE

l

DISABLE


Internal planning

2-61



Input Data

Field Name

Description

Exampl e

HSDPA switch

HsdpaSwit ch


AUTO_ ADJUST _FLOW_ CTRL


HsdpaTD

l


l


l



Source

4


HsdpaDR


1


Table 2-31 Negotiation and planned data of the DEVIP Input Data

Field Name

Description

Exampl e

Source

Slot No.

SlotNo


13

Internal planning


2-62


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Port No.

PortNo

l

For the PPP link, the MLPPP group, 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

Exampl e

The port types consist of the following 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.

Source

0

ETH

Local IP address

LocalIP

Local IP address of the device IP

12.11.12. 12


LocalMask

If the network is not divided into subnets, use the default mask.

255.255. 255.0


Table 2-32 Negotiation and planned data of the timeslot cross links Input Data

Field Name

Description

Example

Source slot No.

SlotNo


13

Source


PortNo


2

Internal planning


Issue 01 (2008-06-25)

TSBitMap

Value range: TS1 to TS31


TS16 to TS23

2-63



Input Data

Field Name

Description

Example


DestSlotN o

Number of the slot that holds the NUTI (The number must be identical with that of the SlotNo)

13

Source


DestPortN o


0

Value range: 0

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

2-64

Input Data

Field Name

Description

Exampl e

Port type

ItfType

Interface type of the route Optional parameters:

ETH

l

ETH

l

MLPPP

l

PPP

l

PPPoE

Destinatio n network

DestNet

This parameter must meet all the following requirements: Valid network address, except the default route 0.0.0.0 IP AND mask must be equal to the IP address.

17.18.17. 0

Destinatio n mask

DestMask

This parameter must meet all the following requirements: IP AND mask must be equal to the IP address. If the mask is converted into binary value, 0 is not allowed to precede 1.

255.255. 255.0

Next hop IP address

NextHop

This parameter is valid only when the parameter InsertFlag is set to ETH. This parameter meets the following requirements:

12.11.12. 1

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.


Source

Network planning

Issue 01 (2008-06-25)



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

Field Name

Description

Example

Source

Port type

ItfType

Type of the interface that carries the SCTP links Optional parameters:

PPP

Internal planning

l

ETH

l

MLPPP

l

PPP

l

PPPoE

Local IP address

LocalIP

At the NodeB, the IP address of the primary physical link that carries the SCTP link.

17.17.17. 111

Destination IP address

DestIP

At the RNC, the IP address of the primary physical link that carries the SCTP link.

14.1.1.4

The second local IP address

SecLocalIP

At the NodeB, the IP address of the standby physical link that carries the SCTP link.

0.0.0.0

The IP address 0.0.0.0 indicates that this address is not in use. The second destination IP address

SecDestIP

At the RNC, the IP address of the standby physical link that carries the SCTP link.

0.0.0.0


The IP address 0.0.0.0 indicates that this address is not in use.

Issue 01 (2008-06-25)

Local port number and destination port number

LocalPort

Destination port number

DestPort

Automatical ly switches back to the master IP address

IPAutoCha nge

Local port number of the SCTP

1024


Destination port number of the SCTP

8021

Value range: 1024 through 65535 After the fault of the master IP address is rectified, the services can be automatically switched back to the master IP address. Optional parameters: l

ENABLE

l

DISABLE


ENABLE

Internal planning

2-65



Table 2-35 Negotiation and planned data of the IPCP Input Data Port type

SCTP number

Field Name

Description

Exampl e

Source

PortType


NCP

Internal planning

1


MASTE R

Internal planning

CCP

Internal planning

SCTPNo

l

NCP

l

CCP

SCTP number that carries the NCP Value range: 0 through 19

NCP Flag

Flag

Port type

Port No.

PortType

PortNo


SLAVE

l

MASTER


NCP

l

CCP


0 Negotiati on with the destinati on

Value range: 0 through 65535 CCP

SCTP number

SCTPNo

SCTP number that carries the CCP

2

Value range: 0 through 19 Flag

2-66

Flag


SLAVE

l

MASTER


MASTE R

Internal planning

Issue 01 (2008-06-25)



Table 2-36 Negotiation and planned data of the transmission resource group (over IP) Input Data

Field Name

Description

Example

Port type

ItfType

Type of the interface that carries the IP transmission resource group Optional parameters:

ETH

ETH

l

MLPPP

l

PPP

l

PPPoE


RscgrpNo


0

Transmit bandwidth

TxBandwi dth


10000

Receive bandwidth

Issue 01 (2008-06-25)

l

RxBandwi dth

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.

Receive bandwidth of the resource group. l


l


l


l



Source

Internal planning

10000

2-67



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

Field Name

Description

Example

Source

Port type

ItfType

Type of the interface that carries the IP PATH Optional parameters:

ETH

Internal planning

ETH

l

MLPPP

l

PPP

l

PPPoE


DestIP

Destination IP address of the IP path

17.18.17. 121


DSCP priority

DSCP


60

Network planning

Service type

TrafficType


RT

Receive bandwidth

2-68

l

RxBandwith

l

RT

l

NRT

l

HSPA_RT

l

HSPA_NRT

When PATH joins the resource 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


l


l


l



1000 Negotiati on with the destinatio n

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Transmit bandwidth

TxBandwith

When PATH joins the resource 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.

1000

Transmit committed burst size

TxCBS

l


l


l


l


Value range: 15000 to 155000000. The recommended value is 1/2 of the transmit bandwidth.

Source

500000

Unit: bit Transmit excessive burst size

TxEBS

Path check

PathCheck



Issue 01 (2008-06-25)


1000000

Unit: bit

JoinRscgrp

RscgrpNo


ENABLE: Path check is enabled.

l

DISABLE: Path check is disabled.

Specify whether the IP PATH should be added to the resource group. Optional parameters: l

DISABLE

l

ENABLE

Number of the IP transmission resource group

DISABL E

Internal planning

ENABLE

0



2-69



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

Field Name

Description

Example

Bind the route

BindRoute Valid

Determine whether to bind the route. 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:

YES

Port type

2-70

ItfType

l

NO

l

YES

Type of the interface that carries the bound routes Optional parameters: l

ETH

l

MLPPP

l

PPP

l

PPPoE

ETH

Bound IP address on the destination network

BindDestIP

This parameter is valid only when the parameter BindRouteValid is set to YES.

11.11.10. 0

Bound destination mask

BindDestIP Mask


255.255. 255.0

Bound next hop IP address

NextHop

This parameter is valid only when the port type is ETH.

12.11.12. 1

Local IP address

LocalIP

IP address at the NodeB for the OMCH

11.11.12. 12

Local subnet mask

Mask

Mask of the IP address at the NodeB for the OMCH

255.255. 0.0


DestIP

Destination IP address of the OMCH, that is, the IP address of the LMT or the M2000.

11.11.11. 12

Flag

Flag


MASTE R

l


l



Source


Internal planning

Issue 01 (2008-06-25)



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

Field Name

Description

Example

Port type

ItfType

Type of the interface that carries the resource group Optional parameters:

ETH


RscgrpNo

l

ETH

l

MLPPP

l

PPP

l

PPPoE

Number of the IP transmission resource group that corresponds to the physical bearer port

Source

0 Internal planning

Value range: 0 through 3 Destinatio n IP address

DestIP

Bound destination IP address, that is, the IP address on the same network 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).

11.11.10.1 0

Destinatio n mask

IPMask


255.255.2 55.255

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

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example

Source

Port type

ItfType

Type of the interface that carries the IP clock links Optional parameters:

PPPoE

Internal planning

l

ETH

l

MLPPP

l

PPP

l

PPPoE

IP address at the client

ClientIP

Obtain the NodeB IP address of the IP clock

12.3.0.1

IP address at the server

ServerIP

IP address at the IP clock server

12.3.0.10


Network planning

2-71



Input Data

Field Name

Description

Example

Priority

Priority

The clock links that has the highest priority is used first. The number is in a negative relation with the priority level.

0

Source


Table 2-41 Negotiation and planned data of the IPQoS Input Data

Field Name

Description

Example

Priority rule

PriRule


IPPRECE DENCE

Signaling priority

Operation and Maintenanc e (OM) priority

SigPri

OMPri

l

IPPRECEDENCE

l

DSCP

l

In IPPRECEDENCE rule, the value range is 0 through 7.

l

In DSCP rule, the value range is 0 through 63.

l


l


Source

7 Network planning 7

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

2-72

Input Data

Field Name

Description

Example

Source

Site name

Site Name

The site is usually named after the geographical location.

Shanghai

Network planning


Issue 01 (2008-06-25)



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

Field Name

Description

Example

Number of RX antennas

RxAntennaN um

The number of RX antennas in a sector is associated with the parameter DemMode set at the NodeB equipment layer..

2

Source

You can define the number of RX antennas before configuring antenna channels for the sectors. You need to, however, adhere to the following principles:

Transmit diversity mode

TxDiversity Mode

l

If DemMode is set to fourway demodulation mode or four-way economical demodulation mode, only one or four RX antennas can be configured.

l

If DemMode is set to twoway demodulation mode, only one or two RX antennas can be configured.

Diversity mode of the sector, which can be configured 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)

TX_DIVE RSITY

Network planning

When the number of configured RX antennas is one, the sector can work only in no transmit diversity mode.

Issue 01 (2008-06-25)


2-73


2-74


Input Data

Field Name

Description

Example

Coverage type

Cover Type

This parameter is required for 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)


Source

Issue 01 (2008-06-25)



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

Field Name

Description

Example

Uplink frequency

UARFCNUp Link

The UL and DL frequencies of a cell must be at the same frequency band.

9612

Source

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 Common frequencies: 937 through 1288 inclusive. Offset:1525

Network planning

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

Issue 01 (2008-06-25)

Band 6


2-75


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


2-76


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Downlink frequency

UARFCNDo wnLink


10562

Source



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


l


l


l

Band 6 Common frequencies: 4387 through 4413 inclusive. Offset:0 Special frequencies: {1037, 1062}. Offset:670.1

Issue 01 (2008-06-25)


2-77


Input Data

Field Name


Description l

Example

Source


l


l


2-78

Uplink resource group ID

ULResource GroupId

The cells within an uplink resource group share the uplink resources. One UL resource group has a maximum of six cells. If the UL resource group has highspeed movement cells, it supports a maximum of three cells.

0

Downlink resource group ID

DLResource GroupId

When adding local cells, you need to select the downlink resource group. One local cell is only carried on a board of its downlink resource group.

0

Baseband resource pool type

BbPoolType

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

GEN_POO L


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Maximum transmit power

MaxTxPower

The maximum transmit power of a local or remote cell refers 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.

430

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

Source

Value range: 0 through 500 Cell radius

CellRadius

The coverage is affected by the cell radius, which is recommended to be set as designed according to the network planning.

29000

Value range: 150 through 180000 Inner handover radius

CellInnerHan doverRadidus

The inner handover radius of the cell should not be greater than the cell radius. It is recommended to be set as designed according to the network planning.

0


Issue 01 (2008-06-25)


2-79



Input Data

Field Name

Description

Example

Desensitizati on intensity

Desensy

This parameter needs to be set 0 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.

Source

Value range: 0 through 30 High-speed movement mode

Rate in highspeed movement mode

Ratio of the default transmit power to the RRU

2-80

Hispm

Spr

DefPowerLvl

The data is determined in the network planning, and it is consistent with that at the RNC. Optional parameters: l

FALSE (not high speed)

l

TRUE (high speed)

This parameter is valid when the Hispm is set to TRUE. The data is determined in the network planning, and it is consistent with that at the RNC. Optional parameters: l

250

l

400

l

500

Cells in distributed sectors need the configuration.

FALSE

-

100



Issue 01 (2008-06-25)


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


If the configuration type of the NodeB is one of the typical configuration types defined in template files, this configuration mode is preferred.


If a configuration file that is applicable to the NodeB is available, this configuration mode is preferred.


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)


3-1


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)


4-1



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


Issue 01 (2008-06-25)


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 Data

Field Name

Description

Exampl e

NodeB ID

NodeB_Id


1

Name of the NodeB

NodeB_Na me


NodeB_ 1

Bearer type

IubBearerT ype


ATM_T RANS

Sharing support


SharingSup port

CnOpIndex

l

ATM_TRANS

l

IP_TRANS

l

ATMANDIP_TRANS



l



NON_S HARED

Source

Network planning


0

Value range: 0 through 3 Issue 01 (2008-06-25)


4-3



Input Data

Field Name

Description

Exampl e

Resource manageme nt mode

RscMngM ode

Defines the resource management mode when the bandwidth is allocated Optional parameters:

SHARE

ATM Address

NSAP

l

SHARE

l

EXCLUSIVE

The NodeB relevant ATM address in hexadecimal format. This parameter is invalid when IubBearerType is set to IP_TRANS. You need to set the first byte of the ATM address to H'45 (indicating an E.164 address), H'39 (indicating a DCC address) or H'47 (indicating an ICD address).

Source

H'39010 1010101 01 0101010 1010101 01 0101010 101


4-4

IPTransAp artInd


TransDelay


IPApartTra nsDelay


SUPPORT

l

NOT_SUPPORT


-

10


-



Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e


SatelliteInd

Identifies the satellite transmission on the Iub interface. Optional parameters:

FALSE

NodeB type

Protocol Version

NodeBTyp e

ProtocolVe r

l

TRUE

l

FALSE

Identifies the type of the logical NodeB. Optional parameters: l

NORMAL

l

PICO_TYPE1

l

PICO_TYPE2


R99

l

R4

l

R5

l

R6

Source

NORMA L

R6

Procedure

, and then click NodeB CM Express in the Step 1 On the main interface of the CME, click 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)


4-5



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

NodeB initial configuration Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)




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

. The Physical NodeB Basic Information window is displayed, as shown in Figure


Table 4-2 Description of the configuration pane

Issue 01 (2008-06-25)

Sequence of data configuration

Description

1

Logical NodeB list

2

"Create a physical NodeB" button

3

"Delete a physical NodeB" button Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

4-7




Description

4

Physical NodeB list

Step 3 Select a logical NodeB in area 1, and then click box is displayed, as shown in Figure 4-3.

. The Create Physical NodeB dialog

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


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


Issue 01 (2008-06-25)



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

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.

l

Reconfigure the equipment layer data. The equipment layer data is reconfigured according to the NodeB type. For details, refer to:

Preparation

Procedure

–

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)


4-9



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.

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

Preparation

4-10


Issue 01 (2008-06-25)



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 Filter. The Select NodeB window is refreshed at a time. 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)


4-11



Figure 4-5 NodeB Selection window

Table 4-3 Description of the configuration pane Sequence of data configuration

Description

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


Issue 01 (2008-06-25)



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)


4-13


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)


5-1



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




5-2


Issue 01 (2008-06-25)




Field Name

Description

Exampl e

NodeB ID

NodeB_Id


1

Name of the NodeB

NodeB_Na me


NodeB_ 1

Bearer type

IubBearerT ype


ATM_T RANS

Sharing support

SharingSup port

l

ATM_TRANS

l

IP_TRANS

l

ATMANDIP_TRANS


l


CnOpIndex

Network planning

NON_S HARED





Source

0


Issue 01 (2008-06-25)

RscMngM ode


SHARE

l

EXCLUSIVE


SHARE

5-3



Input Data

Field Name

Description

Exampl e

ATM Address

NSAP

The NodeB relevant ATM address in hexadecimal format. This parameter is invalid when IubBearerType is set to IP_TRANS.

H'39010 1010101 01 0101010 1010101 01 0101010 101

You need to set the first byte of the ATM address to H'45 (indicating an E.164 address), H'39 (indicating a DCC address) or H'47 (indicating an ICD address).

Source


5-4

IPTransAp artInd


TransDelay


IPApartTra nsDelay


SatelliteInd


SUPPORT

l

NOT_SUPPORT


-

10


-

Value range: 0 through 65535 Identifies the satellite transmission on the Iub interface. Optional parameters: l

TRUE

l

FALSE


FALSE

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

NodeB type

NodeBTyp e

Identifies the type of the logical NodeB. Optional parameters:

NORMA L

Protocol Version

ProtocolVe r

l

NORMAL

l

PICO_TYPE1

l

PICO_TYPE2


R99

l

R4

l

R5

l

R6

Source

R6

Procedure

, and then click NodeB CM Express in the Step 1 On the main interface of the CME, click 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)


5-5




NOTE



l





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


Issue 01 (2008-06-25)



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

Issue 01 (2008-06-25)


. The Import NodeB window is

5-7



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


Mandatory/ Optional Optional

5-8


Issue 01 (2008-06-25)



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

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.

l

Reconfigure the equipment layer data.

Preparation

Procedure The equipment layer data is reconfigured according to the NodeB type. For details, refer to:

l

–


–

6.3 Adding Equipment Layer Data of the BTS3812E (Initial).

–


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)


5-9


Scenario



Mandatory/ Optional. This function is customized. Therefore, it is not applied to all scenarios. Optional NOTE

l


l


l



Prerequisite l


l


l


l


l


Preparation

5-10


Issue 01 (2008-06-25)

NodeB NodeB Initial Configuration Guide l



Procedure






Description


Issue 01 (2008-06-25)


5-11





Description

1


2



5-12


Issue 01 (2008-06-25)




NOTE

l


l





Issue 01 (2008-06-25)


5-13


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


l


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)


6-1



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


Issue 01 (2008-06-25)



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




Preparation Table 6-1 Negotiation and planned data of the NodeB

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Exampl e

NodeB ID

NodeB_Id


1

Name of the NodeB

NodeB_Na me


NodeB_ 1

Bearer type

IubBearerT ype


ATM_T RANS

l

ATM_TRANS

l

IP_TRANS

l

ATMANDIP_TRANS


Source

Network planning


6-3



Input Data

Field Name

Description

Exampl e

Sharing support

SharingSup port

Whether to share NodeB information Optional parameters:

NON_S HARED


CnOpIndex

l


l



Source

0


ATM Address

RscMngM ode

NSAP


SHARE

l

EXCLUSIVE

The NodeB relevant ATM address in hexadecimal format. This parameter is invalid when IubBearerType is set to IP_TRANS. You need to set the first byte of the ATM address to H'45 (indicating an E.164 address), H'39 (indicating a DCC address) or H'47 (indicating an ICD address).

SHARE

H'39010 1010101 01 0101010 1010101 01 0101010 101

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


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Exampl e

Hybrid transport flag

IPTransAp artInd

Identifies whether hybrid transport is supported over the Iub interface. This parameter is valid only when IubBearerType is set to IP_TRANS or ATMANDIP_TRANS. Optional parameters:

-


TransDelay


IPApartTra nsDelay


SatelliteInd

NodeB type

Protocol Version

Issue 01 (2008-06-25)


l

SUPPORT

l

NOT_SUPPORT


Source

10


-


NodeBTyp e

ProtocolVe r

Identifies the satellite transmission on the Iub interface. Optional parameters: l

TRUE

l

FALSE

Identifies the type of the logical NodeB. Optional parameters: l

NORMAL

l

PICO_TYPE1

l

PICO_TYPE2


R99

l

R4

l

R5

l

R6


FALSE

NORMA L

R6

6-5



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



l





Step 5 Repeat Step 3 through Step 4 to add more NodeB records. ----End 6-6


Issue 01 (2008-06-25)



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)


6-7



Table 6-2 Module information Sequen ce Number

Module/ Board Type

Description

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.

l

NPSU: Power supply module

l

NPMU: Power monitoring module

5

6

Power module

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


Issue 01 (2008-06-25)



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



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

Issue 01 (2008-06-25)


6-9



Preparation Table 6-3 Negotiation and planned data of the physical NodeB Input Data

Field Name

Description

Example


E1T1WorkMod e


E1

Clock source

ClockSource


LINE



GPS feeder delay

6-10

ClockWorkMod e

IPClockMode

GPSCableDelay

l


l


l


l


Working mode of the system clock Optional parameters: l


l




l


Delay of the GPS feeder Value range: 0 through 1000


Source


MANUA L

Network planning

-

0

Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Source

SNTP switch

SNTPSwitch

Synchronization switch Optional parameters:

ON

Network planning

10.11.1.1



SNTPServerIP

l


l


The SNTP server is used to synchronize the time of multiple SNTP clients, which is important for centralized maintenance, especially for alarm management. 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.

Issue 01 (2008-06-25)


SyncPeriod

Demodula tion mode

DemMode

l


l



10

Value range: 1 through 525600 Demodulation mode of the NodeB Optional parameters: l


l


l



DEM_2_ CHAN Network planning

6-11



Input Data

Field Name

Description

Example


HighThreshold


1E-5

Smooth power switch

SMTHPWRSwi tch

LowerLimit Lower and upper limits of timer setting

l

1E-3

l

1E-4

l

1E-5

l

1E-6


OPEN

l

CLOSE


Source

CLOSE

0



0


ResAllocateRul e

NodeB IP address

LocalIP


17.21.2.1 5

Subnet mask

LocalIPMask


255.255. 0.0

NMPT backup mode

NMPTBackup Mode


ENABLE



-

STM-1 frame mode

Managem ent unit

6-12




l


l


l



AU3

l

AU4


PERFFI RST

FRAME MODE_ SDH AU3

Internal planning


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Bypass unit

Tu

This parameter is valid only for the channelized optical interface. Optional parameters:

TU12



PowerType

l


l


Configuring the power type for the NodeB. This parameter is available only for the macro NodeB. Optional parameters: l

-48 V DC

l

24 V DC

l

220 V AC


OFF

IUBGroup1


SHARIN G


l



Issue 01 (2008-06-25)

-48 V DC

CHRSwitch

l


Source

Internal planning

6-13



Input Data

Field Name

Description

Example

IUBGroup2

Group backup mode of the Iub interface board, namely the NUTI, in slots 14 and 15 Optional parameters:

SHARIN G

l


l


Source

Procedure



Step 3 Select a logical NodeB on the left of the window, and then click NodeB dialog box is displayed, as shown in Figure 6-3.

. The Create Physical


6-14


Issue 01 (2008-06-25)



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

. The NodeB Equipment Layer window is

Figure 6-4 NodeB Equipment Layer window

Step 7 Click the Basic Info tab. Set the basic information of the NodeB. l

Click the Basic tab. Set or modify the related parameters such as IP Attribute and FTPS Policy based on the prepared data.

l

Click the More tab. Set or modify the related parameters such as Frame Mode and CHR Switch based on the prepared data.

l

Click the DST tab. Set the time zone and DST-related parameters.

Step 8 Click


----End Issue 01 (2008-06-25)


6-15



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



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

6-16

Input Data

Field Name

Description

NMPT

NMPT

l


l


Example If backup is not required, configure the NMPT in slot 10.


NMON



Baseboard

-




Source

Internal planning

Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example

Transport boards

-



Bearer mode

IP clock switch

Line impedance

Issue 01 (2008-06-25)


BearMod e

IPClock Switch

LineImp edance

l


l


This parameter is valid only when the transport board is the NUTI. Optional parameters: l

ATM

l

IPV4

You need to set the IP clock switch on 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



l


l



Source

IPV4

ENABLE

75

6-17



Input Data

Field Name

Description

Example

HSDPA switch

HsdpaS witch



l


l

Source



Procedure



Step 3 Select a physical NodeB, and then click displayed. 6-18



Issue 01 (2008-06-25)



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:

Issue 01 (2008-06-25)

l

IMA links in the IMA group

l

UNI link

l

TreeLink PVC


6-19



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


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



6-20


Issue 01 (2008-06-25)



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

Issue 01 (2008-06-25)

Input Data

Field Name

Description


ULResou rceGroup Id

l


l


l



Example

Source

1

Internal planning

6-21



Input Data

Field Name

Description

Example


DLResou rceGroup Id

l


l


l


Source

0

Procedure l

6-22

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

3.

Select a physical NodeB, and then click is displayed.

4.

Click the Other Info tab. The tab page is displayed, as shown in Figure 6-6.

. The Physical NodeB Basic Information window is displayed. . The NodeB Equipment Layer window


Issue 01 (2008-06-25)



Figure 6-6 Adding an uplink baseband resource group


Description

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

to add

5.

Click ULGroup, and in area 1, select ULResourceGroupId. Then, click one or multiple baseband resource groups.

6.

Click

7.

Select an uplink resource group in area 1, and select an uplink resource item in area


, the selected item is added to the selected uplink resource group 2. Click and is shown in area 3. 8. l

(Optional) Configure the CMB. 1.

Issue 01 (2008-06-25)

Click DLGroup. Repeat Step 5 through Step 7 to add one or multiple downlink resource groups. Click CMB in Figure 6-6, and configure SrcCellId, SrcFachId, DestCellId, and DestFachId. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

6-23


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



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


Issue 01 (2008-06-25)



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

Field Name

Description

Example

Chain type

Chain Type


CHAIN


Head Subrack No.


Head Board No.

Head port number

Head Port No.

l


l



0


0


0 Internal planning


Source

End Subrack No


-


End Board No


-


End Port No


-


Issue 01 (2008-06-25)


6-25



Input Data

Field Name

Description

Example

Break position 1

Break Position 1


OFF

Source


6-26

l


l



Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Break position 2

Break Position 2


-

Source



l


l



Issue 01 (2008-06-25)


6-27




Field Name

Description

RF Module

-

l


l


l


l


Example

Source


RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0


RRUNo


2

Internal planning



6-28

BoardStatus

ToPoPosition


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example




0

RRU IF offset

Floor

IFOffset

Floor

l


l


l




l


l


l


l


l


l



Source

MIDDLE

0


Issue 01 (2008-06-25)


6-29



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0



Field Name

Description

Example

RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0

Source


RRUNo


2

Internal planning



Floor

BoardStatus

ToPoPosition

Floor


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

0


6-30


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0


Procedure



Step 3 Select a physical NodeB, and then click 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)


6-31



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



l

Subracks 2 and 3 are configured with RF modules.

l

MTRUs in subrack 2 and MAFUs in subrack 3 are configured in pairs.


Prerequisite The HBBI or NBBI is configured. For details, refer to Adding Boards in the Baseband Subrack (Initial).

Preparation None.

Procedure

in the configuration object pane, and then click Step 1 On the main interface of the CME, click NodeB CM Express in the configuration task pane. The NodeB CM Express window is displayed. Step 2 Click




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

6-32


Issue 01 (2008-06-25)



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




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)


6-33



Step 2 Click




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


Issue 01 (2008-06-25)




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


Preparation None.

Procedure






Issue 01 (2008-06-25)


6-35



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




Preparation None. 6-36


Issue 01 (2008-06-25)



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.

in the configuration object pane, 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.

2.

Click

3.


4.

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


Figure 6-11 Adding an NPMU

5.

l

Issue 01 (2008-06-25)

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.

Modify the NPMU attributes in the BTS3812E.

1.


2.

Click

3.


4.

in the PowerType editing box, the NPMU Click the Basic Info tab. Click Attribute is displayed, as shown in Figure 6-12.



6-37



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



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.


Preparation None.

6-38


Issue 01 (2008-06-25)



Procedure





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



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)


6-39



Preparation None.

Procedure





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



6-40


Issue 01 (2008-06-25)



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

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example

Source


AntennaNo


N0A

Network planning

Device Name

DeviceName

RET 1

Internal planning



6-41



Input Data

Field Name

Description

Example

Scenario

UseCase


REGULA R

l


l


l


l


Vendor code

RETType

VendorCode

Network planning




l



6-42

Source


DUAL

Internal planning

Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example


SerialNo


-


SubUnit


0

Antenna tilt angle

AntTilt


BypassMode

SASU gain

l

GSMGain

l

UMTSGa in

l


l


l


l



0

Source

Network planning



l

Bypass mode



l



NORMA L

0

6-43



Input Data

Field Name

Description

Example


DCSwitch


UMTS

l


l


l

OFF


DCload


20

STMA gain

Gain


0

Source

Procedure





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


Issue 01 (2008-06-25)



Figure 6-15 Adding the ALD

Step 5 Click the tab SINGLE_RET or MULTI_RET, and click based on prepared data, and then click Step 6 Click the STMA tab, and click

. Configure related parameters

to add an RET.

. Set related parameters based on the prepared data, and click

to add an STMA. Step 7 Click the STMA tab, and click


to add an SASU. Step 8 Click the RET_2G tab, and click click

. Set related parameters based on the prepared data, and

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)


6-45



Figure 6-16 BTS3812E panel

Table 6-11 Module information Sequen ce Number

Module/ Board Type

Description

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

6-46

Fan

Provides the function of a fan, and is configured in subrack 1.


Issue 01 (2008-06-25)



Sequen ce Number

Module/ Board Type

Description

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)


6-47



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.





Preparation Table 6-12 Negotiation and planned data of the physical NodeB

6-48

Input Data

Field Name

Description

Example


E1T1WorkMod e


E1

Clock source

ClockSource


LINE

l


l


l


l



Source


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example


ClockWorkMod e


MANUA L


Issue 01 (2008-06-25)


IPClockMode

GPS feeder delay

GPSCableDelay

SNTP switch

SNTPSwitch

l


l




l



Network planning

-

0

Internal planning

ON

Network planning



l



Source

6-49



Input Data

Field Name

Description

Example

Source


SNTPServerIP


10.11.1.1




SyncPeriod

Demodula tion mode

DemMode


Smooth power switch

6-50

l


l



10


HighThreshold

SMTHPWRSwi tch



l


l



1E-3

l

1E-4

l

1E-5

l

1E-6


OPEN

l

CLOSE


DEM_2_ CHAN


CLOSE

Issue 01 (2008-06-25)




Field Name

Description

Example

LowerLimit


0

Source



0


ResAllocateRul e

NodeB IP address

LocalIP


17.21.2.1 5

Subnet mask

LocalIPMask


255.255. 0.0

NMPT backup mode

NMPTBackup Mode


ENABLE



-

STM-1 frame mode

Managem ent unit

Bypass unit

Issue 01 (2008-06-25)


Tu



l


l


l



AU3

l

AU4



l



PERFFI RST

Internal planning

FRAME MODE_ SDH AU3


TU12

6-51



Input Data

Field Name

Description

Example


PowerType


-48 V DC


l

-48 V DC

l

24 V DC

l

220 V AC

CHRSwitch


OFF

IUBGroup1


SHARIN G

l

l


6-52

IUBGroup2


Source

Internal planning




l



SHARIN G

Issue 01 (2008-06-25)



Procedure







Issue 01 (2008-06-25)



6-53






l


l


Step 8 Click


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



6-54


Issue 01 (2008-06-25)



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.


Preparation Table 6-13 Negotiation and planned data of the BBU

Issue 01 (2008-06-25)

Input Data

Field Name

Description

NMPT

NMPT

l


l


Example If backup is not required, configure the NMPT in slot 10.


NMON



Baseboard

-



Transport boards

-



l


l



Source

Internal planning

6-55



Input Data

Field Name

Description

Example

Bearer mode

BearMod e

This parameter is valid only when the transport board is the NUTI. Optional parameters:

IPV4

IP clock switch

Line impedance

6-56

IPClock Switch

LineImp edance

l

ATM

l

IPV4

You need to set the IP clock switch on 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



l


l



Source

ENABLE

75

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

HSDPA switch

HsdpaS witch



l


l

Source



Procedure



Step 3 Select a physical NodeB, and then click displayed. Issue 01 (2008-06-25)



6-57



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:

6-58

l


l

UNI link

l

TreeLink PVC


Issue 01 (2008-06-25)



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


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



Issue 01 (2008-06-25)


6-59



l


l


l



l


l


NOTE


Prerequisite One of the following boards is added: l

the HULP/EULP and the HDLP/NDLP

l

the NBBI, HBBI, EBBI, or EBOI

For the configuration method, refer to 6.3.2 Adding the Boards in the Baseband Subrack (Initial).


6-60

Input Data

Field Name

Description


ULResou rceGroup Id

l


l


l



Example

Source

1

Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


DLResou rceGroup Id

l


l


l


Source

0

Procedure l

Issue 01 (2008-06-25)


1.


2.

Click

3.


4.




6-61





Description

1


2


3


to add

5.


6.

Click

7.





6-62

Click DLGroup. Repeat Step 5 through Step 7 to add one or multiple downlink resource groups. Click CMB in Figure 6-20, and configure SrcCellId, SrcFachId, DestCellId, and DestFachId. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)



l


l


l


l


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



l


l


l



Prerequisite The EBOI is configured. For details, refer to Adding Boards in the Baseband Subrack (Initial).

Issue 01 (2008-06-25)


6-63




Field Name

Description

Example

Chain type

Chain Type


CHAIN


Head Subrack No.


Head Board No.

Head port number

Head Port No.

l


l



0


0


0 Internal planning


Source

End Subrack No


-


End Board No


-


End Port No


-


6-64


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Break position 1

Break Position 1


OFF

Source


Issue 01 (2008-06-25)

l


l



6-65



Input Data

Field Name

Description

Example

Break position 2

Break Position 2


-

Source



l


l



6-66


Issue 01 (2008-06-25)




Field Name

Description

RF Module

-

l


l


l


l


Example

Source


RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0


RRUNo


2

Internal planning



Issue 01 (2008-06-25)

BoardStatus

ToPoPosition


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

6-67



Input Data

Field Name

Description

Example




0

RRU IF offset

Floor

IFOffset

Floor

l


l


l




l


l


l


l


l


l



Source

MIDDLE

0


6-68


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0



Field Name

Description

Example

RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0

Source


RRUNo


2

Internal planning



Floor

BoardStatus

ToPoPosition

Floor


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

0


Issue 01 (2008-06-25)


6-69



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0


Procedure





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


Issue 01 (2008-06-25)




6.3.5 Adding RF Modules (Initial) This describes how to add RF modules, that is, the MAFU and MTRU modules. Scenario



l

Subracks 2 and 3 are configured with RF modules.

l

MTRUs in subrack 2 and MAFUs in subrack 3 are configured in pairs.


Prerequisite The HBBI or NBBI is configured. For details, refer to Adding Boards in the Baseband Subrack (Initial).

Preparation None.

Procedure






Issue 01 (2008-06-25)


6-71



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




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


Issue 01 (2008-06-25)


Step 2 Click





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 Issue 01 (2008-06-25)


6-73




The NEMU is applicable only to the BTS3812E.


Preparation None.

Procedure






6-74


Issue 01 (2008-06-25)



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




Preparation None. Issue 01 (2008-06-25)


6-75



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.


2.

Click

3.


4.

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


Figure 6-25 Adding an NPMU

5.

l

6-76

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.

Modify the NPMU attributes in the BTS3812E.

1.


2.

Click

3.


4.

in the PowerType editing box, the NPMU Click the Basic Info tab. Click Attribute is displayed, as shown in Figure 6-26.



Issue 01 (2008-06-25)



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



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)


6-77



Procedure





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


Issue 01 (2008-06-25)



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



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


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






Issue 01 (2008-06-25)


6-79



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



6-80


Issue 01 (2008-06-25)



NOTE

l


l


l


Prerequisite l


l



Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example

Source


AntennaNo


N0A

Network planning

Device Name

DeviceName

RET 1

Internal planning



6-81



Input Data

Field Name

Description

Example

Scenario

UseCase


REGULA R

l


l


l


l


Vendor code

RETType

VendorCode

Network planning




l



6-82

Source


DUAL

Internal planning

Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example


SerialNo


-


SubUnit


0

Antenna tilt angle

AntTilt


BypassMode

SASU gain

l

GSMGain

l

UMTSGa in

l


l


l


l



0

Source

Network planning



l

Bypass mode



l



NORMA L

0

6-83



Input Data

Field Name

Description

Example


DCSwitch


UMTS

l


l


l

OFF


DCload


20

STMA gain

Gain


0

Source

Procedure






6-84


Issue 01 (2008-06-25)






to add an RET.






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)


6-85



Figure 6-30 DBS3800 panel

Table 6-20 Module information Module/Board Type

Description

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

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


Issue 01 (2008-06-25)



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.





Preparation Table 6-21 Negotiation and planned data of the physical NodeB

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example


E1T1WorkMod e


E1

Clock source

ClockSource


LINE

l


l


l


l



Source


6-87



Input Data

Field Name

Description

Example


ClockWorkMod e


MANUA L


6-88

IPClockMode

GPS feeder delay

GPSCableDelay

SNTP switch

SNTPSwitch

l


l




l



Network planning

-

0

Internal planning

ON

Network planning



l



Source

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Source


SNTPServerIP


10.11.1.1




SyncPeriod

Demodula tion mode

DemMode


Smooth power switch

Issue 01 (2008-06-25)

l


l



10


HighThreshold

SMTHPWRSwi tch



l


l



1E-3

l

1E-4

l

1E-5

l

1E-6


OPEN

l

CLOSE


DEM_2_ CHAN


CLOSE

6-89




Field Name

Description

Example

LowerLimit


0

Source



0


ResAllocateRul e

NodeB IP address

LocalIP


17.21.2.1 5

Subnet mask

LocalIPMask


255.255. 0.0

NMPT backup mode

NMPTBackup Mode


ENABLE



-

STM-1 frame mode

Managem ent unit

Bypass unit

6-90


Tu



l


l


l



AU3

l

AU4



l



PERFFI RST

Internal planning

FRAME MODE_ SDH AU3


TU12

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


PowerType


-48 V DC


l

-48 V DC

l

24 V DC

l

220 V AC

CHRSwitch


OFF

IUBGroup1


SHARIN G

l

l


Issue 01 (2008-06-25)

IUBGroup2


Source

Internal planning




l



SHARIN G

6-91



Procedure







6-92



Issue 01 (2008-06-25)






l


l


Step 8 Click


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



Issue 01 (2008-06-25)


6-93



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.


Preparation Table 6-22 Negotiation and planned data of the BBU Input Data

Field Name

Description

Example

Board status

BoardStatus

Blocking status of the board Optional parameters:

UnBlock

Clock source

Bearer mode

HSUPA switch

6-94

ClockSource 8K

BearMode

HSUPA

l

Block

l

Unblock

E1/T1 ports for extracting the Iub interface clock signals. Optional parameters: l

None

l

Port 0 to port 7


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, the ATM transport layer cannot use the E1/T1 ports, that is, you cannot configure the physical links.


ENABLE (The HSUPA is supported)

l

DISABLE (The HSUPA is not supported)


Port 0

Source

Internal planning

ATM

Negotiati on with the destinatio n DISABL E

Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example

Source

Clock Mode

ClockMode

For the cascaded NodeBs, the clock of the upper-level NodeB is set to 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:

SLAVE

Network planning

Line Code

Frame Structure

Issue 01 (2008-06-25)


LineCode

FrameStru

l


l



HDB3 (for E1 mode)

l

AMI (for E1 or T1 mode)

l

B8ZS (for T1 mode)


E1_DOUBLE_FRAME (double frame, for E1 mode)

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)


HDB3

E1_CRC 4_MULT I_FRAM E


6-95



Input Data

Field Name

Description

Example

HSDPA switch

HsdpaSwitch


AUTO_A DJUST_ FLOW_C TRL


HsdpaTD

l


l


l



Source

4

Value range:0 to 20 Discard rate threshold

HsdpaDR


1

Value range:0 to 1000

6-96


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Working Mode

WorkMode


OFF

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

l

CUSTOM (customized mode): 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.

Internal planning

Alarm ID

AlarmId

This parameter is valid only when WorkMode is set to CUSTOM.

-

Alarm voltage

ALarmVolta ge

This parameter is valid only when WorkMode is set to CUSTOM. Optional parameters:

-

l

HIGH (alarms related to high impedance)

l

LOW (alarms related to low impedance)

Source

Procedure


Issue 01 (2008-06-25)



6-97





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


Issue 01 (2008-06-25)



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



l


l


l



l


l


NOTE


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


Issue 01 (2008-06-25)

Input Data

Field Name

Description


ULResou rceGroup Id

l


l


l



Example

Source

1

Internal planning

6-99



Input Data

Field Name

Description

Example


DLResou rceGroup Id

l


l


l


Source

0

Procedure l

6-100


1.


2.

Click

3.


4.




Issue 01 (2008-06-25)





Description

1


2


3


5.


to add

6.

Click

7.





Issue 01 (2008-06-25)

Click DLGroup. Repeat Step 5 through Step 7 to add one or multiple downlink resource groups. Click CMB in Figure 6-34, and configure SrcCellId, SrcFachId, DestCellId, and DestFachId.


6-101



l


l


l


l


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


Mandatory/ Mandatory Optional l


l


l




Field Name

Description

Example

Chain type

Chain Type


CHAIN

Chain/ Ring head subrack number 6-102

Head Subrack No.

l


l



0

Source

Internal planning



Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


Head Board No.

Number of the slot that holds the head BBU in the chain or ring

0

Head port number

Head Port No.

Source


0


End Subrack No


-


End Board No


-


End Port No


-


Issue 01 (2008-06-25)


6-103



Input Data

Field Name

Description

Example

Break position 1

Break Position 1


OFF

Source


6-104

l


l



Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Break position 2

Break Position 2


-

Source



l


l



Issue 01 (2008-06-25)


6-105




Field Name

Description

RF Module

-

l


l


l


l


Example

Source


RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0


RRUNo


2

Internal planning



6-106

BoardStatus

ToPoPosition


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


RTWPofCarrier Carrier numberonRxRX channel number


0

RRU IF offset

Floor

IFOffset

Floor

l


l

RX channel number: 0 through 1

l




l


l


l


l


l


l



Source

MIDDLE

0


Issue 01 (2008-06-25)


6-107



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0



Field Name

Description

Example

RRU name

RRUName

Name of the MRRU

Name

RRU chain number

RRUChainNo


0

Source


RRUNo


2

Internal planning



Floor

BoardStatus

ToPoPosition

Floor


Block

l

Unblock



l



UnBlock

TRUNK

Network planning

0


6-108


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Vertical

Vertical


0

Source


Horizontal


0


Procedure





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)


6-109




6.4.5 Adding an NEMU (Initial, Distributed NodeB) This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for the DBS3800. Scenario



The NEMU can be configured only in slot 00 of subrack 0.


Preparation None.

Procedure






6-110


Issue 01 (2008-06-25)



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



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

in the configuration object pane, and then click Step 1 On the main interface of the CME, click NodeB CM Express in the configuration task pane. The NodeB CM Express window is displayed. Issue 01 (2008-06-25)


6-111



Step 2 Click




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


Issue 01 (2008-06-25)


Scenario




l


l


l


Prerequisite l


l



Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example

Source


AntennaNo


N0A

Network planning

Device Name

DeviceName

RET 1

Internal planning



6-113



Input Data

Field Name

Description

Example

Scenario

UseCase


REGULA R

l


l


l


l


Vendor code

RETType

VendorCode

Network planning




l



6-114

Source


DUAL

Internal planning

Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example


SerialNo


-


SubUnit


0

Antenna tilt angle

AntTilt


BypassMode

SASU gain

l

GSMGain

l

UMTSGa in

l


l


l


l



0

Source

Network planning



l

Bypass mode



l



NORMA L

0

6-115



Input Data

Field Name

Description

Example


DCSwitch


UMTS

l


l


l

OFF


DCload


20

STMA gain

Gain


0

Source

Procedure






6-116


Issue 01 (2008-06-25)






to add an RET.






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)


6-117



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


Issue 01 (2008-06-25)



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



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


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)


6-119


6 Manually Adding a NodeB (Initial) 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 Data

Field Name

Description

Example

Slot No.

SlotNo


14

Source


IMA group ID

Transmit frame length

6-120

SubBdType

IMAId

IMATxFram eLength

Type of the sub-board where the E1/ T1 port used by the IMA link is located Optional parameters: l

Baseboard

l


l


l


l


l


Longer transmit frame can enhance transmission efficiency but reduces error sensitivity. Therefore, the default value is recommended. Optional parameters: l

D32

l

D64

l

D128

l

D256



0 Internal planning

D128

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Minimum active links

IMAMinAct iveLinks

Threshold for identifying the 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.

1

Differentia l maximum delay

IMADiffMa xDelay

l


l


l


Different transmission links in an IMA group may result in different 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.

Source

25

Value range: 4 through 100 Scramble mode

Timeslot 16 support

ScrambleMo de

TimeSlot16



l


The channelized optical sub-board does not support this function. Optional parameters: l

ENABLE

l

DISABLE

ENABLE

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)


6-121



Input Data

Field Name

Description

Example

Source

Link number

LinkNo

Number of the E1/T1 ports for the links in an IMA group.

0, 1, 2


HSDPA switch

HsdpaSwitc h

l


l


l




l


l


HsdpaTD


Internal planning



4


6-122


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


HsdpaDR


1

Source


Procedure l

Add the IMA group and the IMA link individually.

1.


2.

Click

3.

Select a physical NodeB, and then click window is displayed.

4.

Click ATMPort, and then click the IMA tab. The tab page is displayed, as shown in Figure 6-40.

. The Physical NodeB Basic Information window is displayed. . The NodeB ATM Transport Layer

Figure 6-40 Configuring the IMA group and the IMA link individually

5.

Issue 01 (2008-06-25)

Select SubrackNo, and click shown in Figure 6-41.

. The Search Iub Board window is displayed, as


6-123



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

l

Add UNI groups and links in bulk. 1.

6-124

to add an IMA link.

. The NodeB In the NodeB ATM Transport Layer window, click ATM Bulk Link CM window is displayed, as shown in Figure 6-42.


Issue 01 (2008-06-25)



Figure 6-42 Configuring the IMA links in batches


2.


Description

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

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



Issue 01 (2008-06-25)


6-125



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


l


l


Preparation Table 6-31 Negotiation and planned data of the UNI links Input Data

Field Name

Description

Example

Slot No.

SlotNo


12

Source


6-126

SubBdType

Type of the sub-board where the E1/T1 port is located by the UNI link Optional parameters: l

Baseboard

l


l



BaseBoard Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Source

Link number

LinkNo

Number of the E1/T1 ports for UNI links

3

Negotiation with the destination

Scramble mode

Timeslot 16 support

ScrambleMo de

TimeSlot16

l


l


l




l


The channelized optical subboard does not support this function. Optional parameters: l

ENABLE

l

DISABLE

ENABLE

DISABLE

Internal planning

After this parameter is enabled, the bandwidth of the UNI link is added by 64 kbit/s.

Issue 01 (2008-06-25)


6-127



Input Data

Field Name

Description

Example

HSDPA switch

HsdpaSwitc h


AUTO_AD JUST_FLO W_CTRL


HsdpaTD

l


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



Source

4


HsdpaDR


1


6-128


Issue 01 (2008-06-25)



Procedure l

Add the IMA group and the IMA link individually.

1.


2.

Click

3.


4.

Click ATMPort, and then click the UNI tab. The tab page is displayed, as shown in Figure 6-43.


Figure 6-43 Configure the UNI links individually.

5.

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

l

Add UNI groups and links in bulk. 1.

Issue 01 (2008-06-25)

to add an UNI link.

. The NodeB In the NodeB ATM Transport Layer window, click ATM Bulk Link CM window is displayed, as shown in Figure 6-44.


6-129



Figure 6-44 Configure the UNI links in batches.


2.


Description

1

Available E1/T1 port for the UNI link on the configured Iub interface board

2

E1/T1 port assigned to the UNI link

In area 1, select an E1/T1 port, and then click

to add one UNI link.

----End

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



6-130


Issue 01 (2008-06-25)



NOTE

l

The Fractional ATM link can be configured on only the E1/T1 port 0 through 1 on the baseboards in slots 12 through 15.

l

One E1/T1 port can be configured with multiple Fractional ATM links if the timeslots occupied by the links do not conflict.

l

The total number of IMA groups, UNI links and Fractional ATM links on the same baseboard does not exceed eight.

l

The total number of IMA links, UNI links and Fractional ATM links on the same baseboard does not exceed eight.

Prerequisite l


l


l


Preparation Table 6-33 Negotiation and planned data of the fractional ATM links Input Data

Field Name

Description

Example

Slot No.

SlotNo


13


Source

Internal planning

Sub-board type

SubBdType

Type of the sub-board with the E1/ T1 port available for the fractional ATM link Optional parameters: Baseboard

BaseBoar d

Port No.

E1T1No

Number of the E1/T1 port available for the fractional ATM link

0

Negotiatio n with the destinatio n Internal planning


LinkNo


1

Timeslots

TSBitMap

The fractional ATM link provides timeslots for the 3G equipment. If port 0 is configured, the timeslots must be reserved for timeslot cross connection.

TS24 to TS31



Issue 01 (2008-06-25)


6-131



Input Data

Field Name

Description

Example

Scramble mode

ScrambleMo de


ENABLE

HSDPA switch

HsdpaSwitch

l


l




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


HsdpaTD

Source


Internal planning



4


HsdpaDR


1


6-132


Issue 01 (2008-06-25)



Procedure




. The NodeB ATM Transport Layer window is

Step 4 Click ATMPort, and then click the Fractional ATM tab. The tab page is displayed, as shown in Figure 6-45. Figure 6-45 Adding a fractional ATM link

Step 5 Select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select an E1/ T1 port, and click OK to return to the NodeB ATM Transport Layer window. Step 6 Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the timeslot to be used, and then click OK to return to the NodeB ATM Transport Layer window. NOTE

The CME automatically filters the timeslot that is already occupied or reserved on the same E1/T1 port. The available timeslots appear yellow. The used timeslots appear dark green.

Step 7 Configure other parameters based on the prepared data, and then click ATM links.

to add fractional

----End Issue 01 (2008-06-25)


6-133



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. NodeB initial configuration

Scenario


l

The SDT CES and UDT CES can be configured only on E1/T1 0 through 1 of the NDTI baseboard.

l

The SDT CES and the UDT CES exclusively occupy an E1/T1 port.

l

The bandwidth of the SDT or UDT CES link must be lower than that of the physical bearer link. The UDT CES link occupies relatively high bandwidth. Only the IMA link can be used as the physical bearer link.

l

The formula (unit: kbit/s, each cell has 53 bytes) to calculate the CES links is as follows: l

UDT CES: 64 x 32 x bytes of a cell/partial fill rate

l

SDT CES: 64 x selected timeslots except for slot 0 x bytes of a cell/partial fill rate

Prerequisite l


l

The NUTI of the macro NodeB is configured, as described in 6.2.2 Adding the Boards in the Baseband Subrack (Initial).

Preparation Table 6-34 Negotiation and planned data of the SDT CES Input Data

Field Name

Description

Example

Port type

Type

Type of the interface that carries the SDT CES channels Optional parameters:

FRAATM

Source slot No.

6-134

PortNo

l

FRAATM

l

IMA

l

UNI

l

STM1


Source

Internal planning

12

Value range: 12 through 13 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


SubBdTyp e

Type of the sub-board where the source E1/T1 port is located by the SDT CES channel Optional parameters: Baseboard

BaseBoar d

Source port No.

PortNo

Number of the source E1/T1 ports for the SDT CES channel

0

Source

Value range: 0 through 1 Partial fill level

PFL

ATM cell has 48-byte payloads. 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.

47

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. Value range: TS1 to TS31


SlotNo


TS1 to TS7 13


Issue 01 (2008-06-25)

SubBdTyp e

Type of the sub-board where the destination E1/T1 port is located by the SDT CES channel Optional parameters: l

Baseboard

l


l


l



BaseBoar d

6-135



Input Data

Field Name

Description

Example

Destinatio n port No.

E1T1No

Number of the destination E1/T1 port for the SDT CES channel (This parameter is valid only when Type is set to FRAATM or UNI).

0

Link No./ IMA ID

6-136

LinkNo/ IMAId

l


l


l


Number of the fractional ATM or UNI link, of the IMA group, or of the STM1 optical port that carries the SDT CES channel. l


l


l


l


l


l



Source

0

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


VPI

Identifier of the virtual channel for the SDT CES channel.

1


VCI

Source

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


l


32

Table 6-35 Negotiation and planned data of the UDT CES Input Data

Field Name

Description

Example

Port type

Type

Type of the interface that carries the UDT CES channel Optional parameters:

IMA

l

IMA

l

STM1

Source slot No.

PortNo



SubBdTyp e

Type of the sub-board where the source E1/T1 port is located by the UDT CES channel Optional parameters: Baseboard

BaseBoar d

Source port No.

PortNo

Number of the source E1/T1 ports for the UDT CES channel

1

Source

12


Internal planning


Issue 01 (2008-06-25)


6-137



Input Data

Field Name

Description

Example

Partial fill level

PFL

The value of the partial fill 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.

47

Source

Value range: 4 through 47 Tx Clock Mode


TxClockM ode

SlotNo


NOACM (non-adaptive clock mode)

l

NOACM (adaptive clock mode)


ACM

14


6-138

SubBdTyp e

Type of the sub-board where the destination E1/T1 port is located by the UDT CES channel Optional parameters: l

Baseboard

l


l


l




Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Optical port No./ IMA ID

LinkNo/ IMAId

Number of the IMA group or STM1 optical port that carries the UDT CES channel.

0


VPI


VCI

l


l


l


Identifier of the virtual channel for the UDT CES channel.

Source

1

Value range: 0 through 31 (six successive values from 0 to 31) Identifier of the virtual channel for the UDT CES channel. l


l


32

Procedure l

Issue 01 (2008-06-25)

Configure the SDT CES links.

1.


2.

Click

3.


4.

Click Network, and then click the SDT tab. The tab page is displayed, as shown in Figure 6-46.



6-139



Figure 6-46 Configuring the SDT CES links


5.


Description

1

Physical bearer link

2

SDT CES configuration area

In area 1, select a physical bearer link; In area 2, select SubrackNo and then click , the Search E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB ATM Transport Layer window. NOTE

The SDT and UDT CES each inclusively occupies an E1/T1 port, and thus the CME automatically filters the E1/T1 port that is already used by the UDT CES link.

6.

Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the timeslot to be used, and then click OK to return to the NodeB ATM Transport Layer window. NOTE


7. l

to add an

Configure the UDT CES links. 1.

6-140

Configure other parameters based on the prepared data, and then click SDT CES link.

In the NodeB ATM Transport Layer window, click the UDT tab, as shown in Figure 6-47. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)



Figure 6-47 Configuring the UDT CES links


2.


Description

1

Physical bearer link (The system automatically filters the IMA link.)

2

UDT CES configuration area

In area 1, select an IMA link as the physical bearer link providing bandwidth for the UDT link. In area 2, select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB ATM Transport Layer window. NOTE

The SDT and UDT CES each inclusively occupies an E1/T1 port, and thus the CME automatically filters the E1/T1 port that is already used by the SDT CES link.

3.

Configure other parameters based on the prepared data, and then click SDT CES link.

to add an

----End

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

Issue 01 (2008-06-25)



6-141




l

The timeslot cross channel can be configured on only the E1/T1 port 2 through 3 on the baseboards in slots 12 through 15.

l

No IMA or UNI links can be added to the source E1/T1 link where the timeslots cross channel is configured.

l

The source and destination ports of the timeslot cross channel must be different, and the same E1/T1 port cannot be repeatedly used.

l

When both E1/T1 2 and 3 use the timeslot cross channel, the timeslots of both links do not conflict. That is, the fractional ATM link timeslot that is configured to E1/T1 0 cannot conflict with the fractional ATM link timeslot that is configured to either E1/T1 2 or 3.

Prerequisite The negotiation and planned data is ready.

Preparation Table 6-38 Negotiation and planned data of the timeslot cross links Input Data

Field Name

Description

Example

Source slot No.

SlotNo


13

Source


PortNo


3


TSBitMap


TS16 to TS23


DestSlotN o

Number of the slot that holds the NDTI or NUTI (The number must be identical with that of the SlotNo)

13

Internal planning


DestPortN o


0

Value range: 0

6-142


Issue 01 (2008-06-25)



Procedure





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


Description

1

Area for the destination port

2

Configuration area of the timeslot cross channel

Step 5 In area 1, select a destination port; In area 2, select TScrossNo, and then click , the Search E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB ATM Transport Layer window. Step 6 Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the timeslot to be used, and then click OK to return to the NodeB ATM Transport Layer window. Issue 01 (2008-06-25)


6-143




Step 7 Configure other parameters based on the prepared data, and then click cross channel.

to add a timeslot

----End

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


Mandatory/ Optional. The configuration is required only when the SAAL links, the AAL2 Optional PATH or the OMCH links join the transmission resource group. NOTE

l

Each physical link can be configured with a maximum of four transmission groups, that is, the total number of transmission groups over ATM and IP.

l

Each Iub interface board or BBU supports a maximum of 16 transmission resource groups over ATM or 8 transmission resource groups over IP.

l

The transmit bandwidth of the transmission resource group should be not greater than the idle bandwidth at the physical links.

Prerequisite The physical layer data is configured, refer to 6.5.1 Adding Links at the Physical Layer (Initial).

Preparation Table 6-40 Negotiation and planned data of the transmission resource group (over ATM)

6-144

Input Data

Field Name

Description

Exampl e

Port type

Type

Type of the interface that carries the transmission resource group Optional parameters:

IMA

l

FRAATM

l

IMA

l

UNI

l

STM1


Source

Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e


RscgrpNo


1

Transmit bandwidth

TxBandwidt h


5000

Source

Value range: 32 through 15800 Receive bandwidth

RxBandwid th


5000


Procedure





Step 4 Click RSCGroup, as shown in Figure 6-49.

Issue 01 (2008-06-25)


6-145



Figure 6-49 Configuring the transmission resource group


Description

1

Configured physical link list

2

Configuration area for the transmission resource group

Step 5 In area 1, select a physical bearer link; In area 2, select RscgrpNo and then click Step 6 Configure other parameters based on the prepared data, and then click resource group over ATM.

.

to add a transmission

----End

6.5.3 Adding SAAL Links (Initial) This describes how to add SAAL links. The SAAL links are used to carry the NBAP and ALCAP when the Iub interface is over ATM. Scenario



6-146


Issue 01 (2008-06-25)



NOTE

l

The PCR value should be greater than the SCR value for the SAAL.

l

The PCR value of the SAAL link should be less than or equal to the available bandwidth of the physical link that carries this SAAL link.

l

If the SAAL is added to the transmission resource group, the PCR of the SAAL should be less than or equal to the bandwidth of the transmission resource group.

Prerequisite l

The physical layer link is configured, refer to 6.5.1 Adding Links at the Physical Layer (Initial).

l

The transmission resource group is configured, refer to 6.5.2 Adding Transmission Resource Group (Initial, over ATM).

Preparation Table 6-42 Negotiation and planned data of the SAAL links Input Data

Field Name

Description

Exampl e

Port type

Type

Type of the interface that carries the SAAL links Optional parameters:

IMA



Issue 01 (2008-06-25)

VPI

l

FRAATM

l

IMA

l

UNI

l

STM1


1

Value range:

VCI

l


l



Source


34

Value range: l


l



6-147



Input Data

Field Name

Description

Exampl e

Service type

ServiceTyp e

When this parameter is set to CBR or 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.

RTVBR

Source


Peak cell rate

Minimum cell rate

PCR

MCR

l


l


l


l


l


Peak cell rate of the ATM channel 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


l


The value of the MCR of the ATM channel should be smaller than that of the PCR. This parameter is valid only when the service type is UBR+.

200

-

Value range: 30 through 6759 Sustainable cell rate

SCR


180


6-148


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e


JoinRscgrp

Specify whether this link should be added to the resource group. Optional parameters:

ENABL E


RscgrpNo

l

DISABLE

l

ENABLE

Source

Internal planning


1


Procedure





Step 4 Click SAAL, as shown in Figure 6-50. Figure 6-50 Configuring the SAAL

Issue 01 (2008-06-25)


6-149




Description

1


2

Transmission resource group carried on the corresponding physical link

3

Configuration area for the SAAL links

Step 5 In area 1, select the physical bearer link. Then the transmission resource group carried on this physical link is displayed in area 2. In area 3, click SAALNo, and click

.

Step 6 (Optional) Set JoinRscgrp to ENABLE. Select RscgrpNo, and click , the Search Resource Group window is displayed. Select a transmission resource group, and click OK to return to the NodeB ATM Transport Layer window. NOTE

The physical bearer type of the transmission resource group is identical with that of the SAAL link. Figure 6-50 and Table 6-43 show the matching relation.

Step 7 Configure other parameters based on the prepared data, and then click link.

to add an SAAL

----End

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



l

One NodeB can be configured with the active and the standby NCPs or CCPs.

l

Each SAAL link can be configured with only one NCP or CCP.

l

The active and the standby NCPs or CCPs should be configured on different links. For example, if the active one is configured on the SAAL, the standby one should be configured on the SCTP. Otherwise the configuration is invalid.

Prerequisite The SAAL links are configured, as described in 6.5.3 Adding SAAL Links (Initial).

6-150


Issue 01 (2008-06-25)



Preparation Table 6-44 Negotiation and planned data of the NBAP Input Data Port type

SAAL number

Field Name

Description

Exampl e

PortType


NCP

SAALNo

l

NCP

l

CCP

SAAL number that carries the NCP

1


NCP Flag

Flag

Port type

Port No.

PortType

PortNo


SLAVE

l

MASTER


NCP

l

CCP


MASTE R

CCP

SAAL number

SAALNo

SAAL number that carries the CCP

Internal planning Negotiati on with the destinati on

Internal planning

Internal planning

0

Value range: 0 through 65535 CCP

Source

2



Issue 01 (2008-06-25)

Flag


SLAVE

l

MASTER


MASTE R

Internal planning

6-151



Procedure





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


Description

1

Configured SAAL link list

2

Configuration area of the NBAP

Step 5 In area 1, select an SAAL link; in area 2, select PortType and then click parameters based on prepared data, and then click

6-152

. Configure related

to add an NCP link.


Issue 01 (2008-06-25)



Step 6 In area 1, select an SAAL link; in area 2, select PortType and then click parameters based on prepared data, and then click

. Configure related

to add an CCP link.

----End

6.5.5 Adding an ALCAP (Initial) This describes how to configure an AAL2 node to the NodeB so that the ALCAP is added at the NodeB. The ALCAP allocates the micro channels of the AAL2 path. Scenario



l

One NodeB can be configured with multiple adjacent nodes.

l

One NodeB can be configured with either one end node or one exchange node.

l

The ATM address must begin with 39/45/47 and end with that in accordance with the protocol.

l

The distributed NodeB can be configured with only the nodes of type.

Prerequisite l

The SAAL links are configured, as described in 6.5.3 Adding SAAL Links (Initial).

l

An exchange node cannot be configured on the SAAL over the NDTI. Therefore, you need to configure the SAAL over the NUTI before you configure the exchange node if required.

Preparation Table 6-46 Negotiation and planned data of the ALCAP Input Data

Field Name

Description

Example

Node type

NodeType

The exchange node must be configured before configuring the adjacent node.

LOCAL

The exchange node cannot be carried on the SAAL link on the NDTI. Optional parameters:

Issue 01 (2008-06-25)

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)


Source

Internal planning

6-153



Input Data

Field Name

Description

Example

Adjacent node identifier

ANI

Identify an adjacent node. This parameter is valid only when the parameter NodeType is set to ADJNODE.

-

Source

Value range: 0 through 31 Network service access point

NSAP

SAAL number

SAALNo

The full name is: Net service access point. When the NodeB uses ATM transmission, the NSAP is the address of the NodeB that is connected to the AAL2 path. The address is a hexadecimal with a length of 20 bytes (excluding the prefix H'). SAAL number that carries the ALCAP

H'390101 01010101 01010101 01010101 01010101 01

3


Procedure





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

6-154


Issue 01 (2008-06-25)



Figure 6-52 Adding the AAL2 node


Description

1

Configured SAAL link list

2

Configuration area of the ALCAP

Step 5 In area 1, select an SAAL link; in area 2, select NodeType and then click

.

Step 6 In the drop-down list, select the node type of the AAL2 link, and configure other parameters based on prepared data. Click

to add an AAL2 node.

NOTE

l

The NodeType is set to :NSAP must be the same as the NSAP of the logical NodeB created at the RNC side.

l

The NodeType is set to :NSAP can be configured only at the NodeB side.

l

The NodeType is set to :NSAP needs no configuration.

----End

6.5.6 Adding AAL2 Path Data (Initial) This describes how to add AAL2 PATH data over ATM. The AAL2 path carries the user plane data between the RNC and other equipment. Scenario



Issue 01 (2008-06-25)


6-155



l

Each NDTI board can be configured with a maximum of 16 AAL2 PATH; Each NUTI board can be configured with a maximum of 32 AAL2 PATH.

l

The sum of the IP paths and AAL2 paths configured on one NodeB should be less than or equal to 16.

l

For an AAL2 path, the PCR value should be greater than the SCR value.

l

The PCR value of the AAL2 path should be less than or equal to the available bandwidth of the physical link that carries the AAL2 path.

l

If a physical port is configured with the transmission resource groups, all the AAL2 paths should be added to a certain transmission resource group, and the PCR of the AAL2 path should be less than the bandwidth of the transmission resource group.

l

If a physical port is configured with AAL2 path links or IP path links, and the links are not in a resource group. No transmission resource group can be added to this physical port.

Prerequisite l

The AAL2 nodes are configured. For details, refer to 6.5.5 Adding an ALCAP (Initial).

l


Preparation Table 6-48 Negotiation and planned data of the AAL2 PATH

6-156

Input Data

Field Name

Description

Example

Port type

Type

Type of the interface that carries the AAL2 PATH Optional parameters:

IMA

l

FRAATM

l

IMA

l

UNI

l

STM1

PATH type PathType

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

RT



1

VPI

Source

Negotiat ion with the destinati on

Value range: l


l



Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example


VCI


37

Service type

Peak cell rate

Issue 01 (2008-06-25)


Source

Value range:

ServiceTyp e

PCR

l


l




l


l


l


l


Peak cell rate of the ATM channel 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.


RTVBR

1920

6-157



Input Data

Field Name

Description

Example


SCR

The value of the SCR of the ATM 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.

960

Received cell rate

RCR

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.

This parameter must be consistent with 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.

Source

2048

Value range: 64 through 20000 Join the resource group


JoinRscgrp

RscgrpNo

Specify whether AAL2 path should be added to the resource group. Optional parameters: l

DISABLE

l

ENABLE


ENABLE

Internal planning 1


Procedure


6-158



Issue 01 (2008-06-25)





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


Description

1

Configured AAL2 node list

2


3


4

Configuration area for the AAL2 path

Step 5 In area 1, select an AAL2 node; in area 2, select the physical bearer link. Then the transmission resource group carried on this physical link is displayed in area 3. In area 4, click AAL2PathId, and click

.

NOTE

The physical bearer type of the resource group is the same as that of the AAL2 PATH. Figure 6-53 and Table 6-49 show the matching relation.

Step 6 (Optional) Set JoinRscgrp to ENABLE. Select RscgrpNo, and click , the Search Resource Group window is displayed. Select a transmission resource group, and click OK to return to the NodeB ATM Transport Layer window. Issue 01 (2008-06-25)


6-159



Step 7 Configure other parameters based on the prepared data, and then click path link.

to add an AAL2

NOTE

l

If the service type is either RTVBR or NRTVBR, the value of the parameter should meet the following condition: 0 < SCR < PCR ≤ RSCGRP configuration bandwidth.

l

If the service type is UBR+, the value of the parameter should meet the following condition: MCR
----End

6.5.7 Adding an OMCH of the NodeB (Initial, over ATM) This describes how to add an Operation and Maintenance Channel (OMCH) of the NodeB. Scenario



l

In ATM transport mode, only one OMCH can be configured. It can be either active or standby. If the configured OMCH is active, it takes effect as the active channel; if the configured OMCH is standby, the configuration does not take effect.

l

Local IP addresses of two OMCH channels cannot be on the same network segment.

l

The local IP address and the destination IP address of the OMCH must be in the same network segment.

l

For an OMCH, the PCR value should be greater than the SCR value.

l

The PCR value of the OMCH should be less than or equal to the available bandwidth of the physical link that carries the OMCH.

l

If the OMCH is added to the transmission resource group, the PCR of the OMCH should be less than or equal to the bandwidth of the transmission resource group.

Prerequisite

6-160

l

The physical layer link is configured, refer to 6.5.1 Adding Links at the Physical Layer (Initial).

l



Issue 01 (2008-06-25)



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

Field Name

Description

Example

Port type

Type

Type of the interface that carries the OMCH Optional parameters:

UNI



Service type

Peak cell rate

Issue 01 (2008-06-25)

VPI

l

FRAATM

l

IMA

l

UNI

l

STM1


Source

1

Value range:

VCI

l

Macro NodeB: 1 or within the VPI range of the actual board configuration

l



33

Value range:

ServiceTy pe

PCR

l


l




l


l


l


l


Peak cell rate of the ATM channel When the service type is RTVBR, NRTVBR or UBR+, the value of this parameter should be greater than that of the SCR. l


l



CBR


512

6-161



Input Data

Field Name

Description

Example

Sustainable cell rate

SCR


-

Source

Value range: 30 through 6759 Local IP address of the OMCH

LocalIP

IP address for NodeB remote maintenance

10.1.2.10

Destination IP address of the OMCH

DestIP

Destination IP address for NodeB remote maintenance, that is, the IP address configured on the ATM interface board at the RNC.

10.1.2.1

Destination subnet mask of the OMCH

DestIPMas k

Subnet mask of the destination IP address for NodeB remote maintenance

255.255. 255.0


JoinRscgrp

Specify whether AAL2 path should be added to the resource group. Optional parameters:

ENABLE


RscgrpNo

Flag

Flag

l

DISABLE

l

ENABLE


2

Internal planning

Value range: 0 through 3 Master/slave flag for the remote OM channels Optional parameters: l

SLAVE

l

MASTER

MASTE R

Procedure


6-162



Issue 01 (2008-06-25)





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


Description

1


2


3

OMCH configuration area

Step 5 In area 1, select the physical bearer link. Then the transmission resource group carried on this physical link is displayed in area 2. Step 6 In area 3, select LocalIP, and click , the LocalIP & Mask dialog box is displayed. Set the peer IP address and the mask of the OMCH, and then click OK to return to the NodeB ATM Transport Layer window. Step 7 Select DestIP, and click . The IP and IP Mask dialog box is displayed. Set the peer IP address and the mask of the OMCH, and then click OK to return to the NodeB ATM Transport Layer window. Step 8 (Optional) Set JoinRscgrp to ENABLE. Select RscgrpNo, and click , the Search Resource Group window is displayed. Select a transmission resource group, and click OK to return to the NodeB ATM Transport Layer window. Issue 01 (2008-06-25)


6-163



The physical bearer type of the resource group is identical with that of the OMCH. Figure 6-54 and Table 6-51 show the matching relation.


to add an OMCH

----End

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



l

The source port and the destination port must be different.

l

For the treelink PVC, the PCR value should be greater than the SCR value.

l

The bandwidth of the treelink PVC should be less than or equal to the bandwidth of the physical port (such as the types of IMA group and UNI link) that bears the treelink PVC.

Prerequisite The physical layer link is configured, refer to 6.5.1 Adding Links at the Physical Layer (Initial).

Preparation Table 6-52 Negotiation and planned data of the treelink PVC

6-164

Input Data

Field Name

Description

Exampl e

Source port type

SourceType

Type of the interface that carries the source port of the treelink PVC Optional parameters:

FRAAT M

l

FRAATM

l

IMA

l

UNI

l

STM1


Source

Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e

Destinatio n port type

DestinationT ype

Type of the interface that carries the destination port of the treelink PVC Optional parameters:

UNI

ByPassMo de

Source VPI

ByPassMode

SourVPI

l

FRAATM

l

IMA

l

UNI

l

STM1

When the NodeB is powered off or exceptions occur to the NodeB, the 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)

Virtual channel used by the upper 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.

l

For the VC switching, the source port VPI must be within the VPI configured to the board, and the value can be 1.

l

Source VCI

Issue 01 (2008-06-25)

SourVCI

DISABL E

1



Identifier of the virtual channel for the upper-level links. This parameter is valid for VC switching. l


l



Source

33

6-165



Input Data

Field Name

Description

Exampl e

Destinatio n VPI

DestVPI

Virtual channel used by the lowerlevel network link

1

Destinatio n VCI

Service type

Peak cell rate

6-166

DestVCI

ServiceType

PCR

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


Identifier of the virtual channel for the lower-level links. This parameter is valid for VC switching. l


l



RTVBR

l

NRTVBR

l


l


Peak cell rate of the ATM channel 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



Source

32

RTVBR

400

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e


SCR


380

Source


Procedure





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

Issue 01 (2008-06-25)


6-167




Description

1

Source port list: shows all configured physical links

2

Destination port list: shows all configured physical links

3

Treelink PVC configuration area

Step 5 Select a source port in area 1; select a destination port in area 2. Step 6 In area 3, select VCXNo, and then click to add a TreeLink PVC. The CME automatically allocates parameters SourVPI, SourVCI, DestVPI, and DestVCI. Set the other parameters such as VCXType, ServiceType, PCR, and SCR. Click

to add a treelink PVC.

NOTE

l

For the VP switching, the source port VPI must be out of the VPI range configured to the board, and the value cannot be 1; The destination port VPI must be out of the VPI range configured to the board, and the value cannot be 1.

l

For the VC switching, the source port VPI must be within the VPI range configured to the board, and the value can be 1; the destination port VPI must be within the VPI range configured to the board, and the value can be 1.

----End

6.6 Manually Adding Transport Layer Data of the NodeB (over IP) This describes how to configure the transport layer data of the NodeB in IP transport mode.

Prerequisite NOTE

In the TCP/IP protocol, the reserved IP addresses are as follows: l

10.0.0.0 to 10.255.255.255

l

172.16.0.0 to 172.31.255.255

l

192.168.0.0 to 192.168.255.255

l

127.*.*.*: local loop address

To configure the distributed NodeB, the CME reserves the following IP addresses: l

10.22.1.*/24: reserved for inter-BBU communication

l

17.21.2.15/16: reserved for DBS3800 or iDBS3800 local maintenance.

To configure the macro NodeB, the CME reserves the following IP addresses: l

10.22.1.*/24: reserved for communications between the NMPT and the standby NMPT, between baseband boards, and between the NMPT and the NodeB Iub interface board.

l

17.21.2.15/16: reserved for BTS3812A/BTS3812E/BTS3812AE local maintenance.

The data of the equipment layer of the NodeB is configured. For details, refer to: 6-168


Issue 01 (2008-06-25)



l

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

l

6.4 Adding Equipment Layer Data of the DBS3800 (Initial)

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

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


6-169



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



l

Local IP addresses of various PPP links cannot be on the same network segment.

l

Local IP addresses of the PPP link, the MLPPP group, and the PPPoE link cannot be on the same network segment.

l

One E1/T1 port can be configured with multiple PPP links and MLPPP links if the timeslots occupied by the links do not conflict.

Prerequisite l

The macro NodeB is configured with the NUTI board, and the bearer type of the NUTI is set to IPV4. For details, refer to 6.2.2 Adding the Boards in the Baseband Subrack (Initial)

l

The distributed NodeB is configured with the BBU, and the bearer type of the BBU is set to IPV4. For details, refer to 6.4.2 Adding a BBU (Initial).

Preparation Table 6-54 Negotiation and planned data of the ppp links Input Data

Field Name

Description

Example

Slot No.

SlotNo


13

Value range: 12 through 15 6-170


Source

Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Port No.

PortNo

Number of the E1/T1 ports for PPP links

0

Source


LinkNo

Each PPP link and each MLPPP link must have a unique number.

0


User name

AuthType

UserName



l


l



NONAU TH

-

Value range: not greater than 64 characters Timeslot map

TSBitMap

A map of the timeslots for PPP links. The map is presented in binary format or the chart. If a timeslot is selected, it is in use. Otherwise, it is not in use.

TS1 to TS15

Local IP address

LocalIP

Local IP address of the PPP link. When the value is 0.0.0.0, it indicates that the parameter needs to be negotiated with the RNC.

17.17.17. 111


PeerIP

Destination IP address of the PPP link

17.17.17. 17


Issue 01 (2008-06-25)

IPHC

l

In cascading mode, this parameter specifies the IP address of a lowerlevel 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.



l





6-171



6-172

Input Data

Field Name

Description

Example


PPPMux


DISABL E


MRU


RestartTimer


3000


PFC


ENABLE


ACFC

l

ENABLE

l

DISABLE


Source

1500


l

ENABLE

l

DISABLE


ENABLE

l

DISABLE


ENABLE

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

HSDPA switch

HsdpaSwitch




HsdpaTD

l


l


l



Source

4


HsdpaDR


1


Issue 01 (2008-06-25)


6-173



Procedure




. The NodeB IP Transport Layer window is

Step 4 Click IPPort, and then click the PPP tab. The tab page is displayed, as shown in Figure 6-56. Figure 6-56 Adding a PPP link

Step 5 Select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select an E1/ T1 port, and click OK to return to the NodeB IP Transport Layer window. Step 6 Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the timeslot to be used, and then click OK to return to the NodeB IP Transport Layer window. NOTE


Step 7 Select LocalIP , and click , the LocalIP & LocalMask dialog box is displayed. Set the local IP address and mask for the PPP link, and then click OK to return to the NodeB IP Transport Layer window. Step 8 Select PeerIP, and click , the PeerIP dialog box is displayed. Set the local IP address and mask for the PPP link, and then click OK to return to the NodeB IP Transport Layer window.

6-174


Issue 01 (2008-06-25)



Step 9 Configure other parameters based on the prepared data, and then click

to add a PPP link.

----End

Adding MLPPP Data (Initial) This describes how to add PPP data. This task is optional when the NodeB uses the E1/T1 cables. The MLPPP group combines multiple PPP links into a logical link. Scenario



l

Local IP addresses of various MLPPP groups cannot be on the same network segment.

l


l

One E1/T1 port can be configured with multiple PPP links and MLPPP links if the timeslots occupied by the links do not conflict.

l

Each Iub interface board or BBU can be configured with a maximum of four MLPPP groups, and each MLPPP group can be configured with a maximum of 16 MLPPP links.

Prerequisite l

The macro NodeB is configured with the NUTI board, and the bearer type of the NUTI is set to IPV4. For details, refer to 6.2.2 Adding the Boards in the Baseband Subrack (Initial)

l

The distributed NodeB is configured with the BBU, and the bearer type of the BBU is set to IPV4. For details, refer to 6.4.2 Adding a BBU (Initial).

Preparation Table 6-55 Negotiation and planned data of the MLPPP group and MLPPP links Input Data

Field Name

Description

Exampl e

Slot No.

SlotNo


13

Source


Issue 01 (2008-06-25)

MLPPP group number

GroupNo


AuthType

MLPPP group number

0

Value range: 0 through 3 Optional parameters: l


l


l



NONAU TH

Internal planning

6-175



Input Data

Field Name

Description

Exampl e

User name

UserName


-

Source

Value range: not greater than 64 characters Local IP address

LocalIP

Local IP address of the MLPPP group

16.16.16. 111

Local subnet mask

LocalMask

Subnet mask of the local IP address for the MLPPP group

255.255. 255.0


PeerIP

Peer IP address of the MLPPP group

16.16.16. 16

Port No.

PortNo

Number of the E1/T1 ports for MLPPP links

0



LinkNo

Number of the MLPPP link that joins the MLPPP group. Each MLPPP and each PPP link must have a unique number.

1

Internal planning



6-176

Timeslot map

TSBitMap

A map of the timeslots for MLPPP links. The map is presented in binary format or the chart. If a timeslot is selected, it is in use. Otherwise, it is not in use.

TS24 to TS31


IPHC


ENABL E


PPPMux

Multi-class PPP

MCPPP

l


l



ENABLE

l

DISABLE


ENABLE (using the MCPPP)

l

DISABLE (not using the MCPPP)


DISABL E

Internal planning

ENABL E

Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Exampl e


MRU


1500


RestartTimer


3000


PFC


ENABL E


ACFC

HSDPA switch

HsdpaSwitch

Source


l

ENABLE

l

DISABLE


ENABLE

l

DISABLE



l


l



ENABL E

AUTO_ ADJUST _FLOW _CTRL

6-177



Input Data

Field Name

Description

Exampl e


HsdpaTD


4

Source


HsdpaDR


1


Procedure





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

6-178


Issue 01 (2008-06-25)




Description

1

Configuration area of the MLPPP group

2

Configuration area of the MLPPP links

Step 5 In area 1, select SubrackNo, and click . The Search Iub Board window is displayed, as shown in Figure 6-58. Select an interface board, and click OK to return to the NodeB IP Transport Layer window. Figure 6-58 Search Iub Board window

NOTE

In the Search Iub Board window, the NUTIs configured to slots 12 and 13 are displayed.

Step 6 Select LocalIP , and click , the LocalIP & LocalMask dialog box is displayed. Set the local IP address and mask for the MLPPP group, and then click OK to return to the NodeB IP Transport Layer window. Step 7 Select PeerIP, and click , the PeerIP dialog box is displayed. Set the local IP address and mask for the MLPPP group, and then click OK to return to the NodeB IP Transport Layer window. Step 8 Configure other parameters based on the prepared data, and then click group.

to add an MLPPP

Step 9 In area 2, select SubrackNo, and click . The Search E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB IP Transport Layer window. Step 10 Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the timeslot to be used, and then click OK to return to the NodeB IP Transport Layer window. Issue 01 (2008-06-25)


6-179





to add an MLPPP

----End

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



l

Local IP addresses of various PPPoE links cannot be on the same network segment.

l


l

The PPPoE links are configured to FE port 0 or 1 on the NUTI boards of slots 12 through 15.

l

The PPPoE link and the ETH link can use the same FE port.

Prerequisite l

The NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the Boards in the Baseband Subrack (Initial).

l


Preparation Table 6-57 Negotiation and planned data of the PPPoE links Input Data

Field Name

Description

Exampl e

Slot No.

SlotNo


13


PortNo

Number of the FE port for the PPPoE link

0

Source

Internal planning


6-180


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e


AuthType


NONAU TH

User name

UserName

l


l


l


This parameter is valid only when AuthType is set to PAP or CHAP.

Source

-

Value range: not greater than 64 characters

Issue 01 (2008-06-25)

Local IP address

LocalIP

Local IP address of the PPPoE link

12.3.0.1

Local subnet mask

LocalMask


255.255. 255.0

IP header compressio n

IPHC


ENABL E

l


l



MRU



RestartTim er


3000


PPPMux


DISABL E


1450


l

ENABLE

l

DISABLE


Internal planning

6-181



Input Data

Field Name

Description

Exampl e

HSDPA switch

HsdpaSwit ch


AUTO_ ADJUST _FLOW_ CTRL


HsdpaTD

l


l


l



Source

4


HsdpaDR


1


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


Issue 01 (2008-06-25)


Step 2 Click





Step 4 Click IPPort, and then click the PPPoE tab. The tab page is displayed, as shown in Figure 6-59. Figure 6-59 Adding a PPPoE link

Step 5 Select SubrackNo, and click . The Search Ethernet Port window is displayed. Select an FE port, and click OK to return to the NodeB IP Transport Layer window. Step 6 Select LocalIP , and click , the LocalIP & LocalMask dialog box is displayed. Set the local IP address and mask for the PPPoE link, and then click OK to return to the NodeB IP Transport Layer window. Step 7 Configure other parameters based on the prepared data, and then click

to add a PPPoE link.

----End

Adding DEVIP Data (Initial) This describes how to add the device IP address to the IP port. The IP ports can be any of the following types: PPP, MLPPP, or Ethernet. Scenario



Issue 01 (2008-06-25)


6-183



l

The four IP port types are: ETH, PPP, MLPPP, and PPPoE.

l

A maximum of four IP addresses can be added to one IP port.

l

IP addresses for different ports cannot be on the same network segment; IP addresses for the same port can be on the same network segment.

Prerequisite l

The NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the Boards in the Baseband Subrack (Initial).

l


l

The PPP link, MLPPP group, and the PPPoE link are configured. For details, refer to 6.6.1 Adding a Link at the Data Link Layer (Initial).

Preparation Table 6-58 Negotiation and planned data of the DEVIP Input Data

Field Name

Description

Exampl e

Slot No.

SlotNo


13

Source


Port type

Local IP address

6-184

PortNo

PortType

LocalIP

l

For the PPP link, the MLPPP group, 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.

The port types consist of the following 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 address of the device IP


0

ETH

12.11.12. 12

Internal planning


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Exampl e


LocalMask

If the network is not divided into subnets, use the default mask.

255.255. 255.0

Source

Procedure





Step 4 Click IPPort, and then click the DEVIP tab. The tab page is displayed, as shown in Figure 6-60. Figure 6-60 Configuring the DEVIP


Issue 01 (2008-06-25)


Description

1

Configuration area for the device IP address Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

6-185




Description

2

Configuration area for the VLAN service priority

Step 5 In area 1, select SubrackNo, and click . The Search Ethernet Port window is displayed. Select an IP port, and click OK to return to the NodeB IP Transport Layer window. Step 6 Select LocalIP , and click , the LocalIP & LocalMask dialog box is displayed. Set the local IP address and mask for the device, and then click OK to return to the NodeB IP Transport Layer window. Step 7 Click

to add the device IP address.

Step 8 (Optional) In area 2, select TrafficType, and click

. Then, Set VLAN service priority

mapping according to the actual network planning. Click


----End

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



l

The timeslot cross channel can be configured on only the E1/T1 port 2 through 3 on the baseboards in slots 12 through 15.

l

No IMA or UNI links can be added to the source E1/T1 link where the timeslots cross channel is configured.

l

The source and destination ports of the timeslot cross channel must be different, and the same E1/T1 port cannot be repeatedly used.

l

When both E1/T1 2 and 3 use the timeslot cross channel, the timeslots of both links do not conflict. That is, the fractional ATM link timeslot that is configured to E1/T1 0 cannot conflict with the fractional ATM link timeslot that is configured to either E1/T1 2 or 3.

Prerequisite The negotiation and planned data is ready.

6-186


Issue 01 (2008-06-25)



Preparation Table 6-60 Negotiation and planned data of the timeslot cross links Input Data

Field Name

Description

Example

Source slot No.

SlotNo


13

Source


PortNo


3


TSBitMap


DestSlotN o

Value range: TS1 to TS31 Number of the slot that holds the NDTI or NUTI (The number must be identical with that of the SlotNo)

TS16 to TS23 13

Internal planning


DestPortN o


0

Value range: 0

Procedure





Step 4 Click Network, and then click the TSCross tab. The tab page is displayed, as shown in Figure 6-61.

Issue 01 (2008-06-25)


6-187



Figure 6-61 Configuring the timeslot cross channel


Description

1

Area for the destination port

2

Configuration area of the timeslot cross channel

Step 5 In area 1, select a destination port; In area 2, select TScrossNo, and then click , the Search E1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeB ATM Transport Layer window. Step 6 Select TSBitMap, and then click . The TimeSlot Select dialog box is displayed. Select the timeslot to be used, and then click OK to return to the NodeB ATM Transport Layer window. NOTE


Step 7 Configure other parameters based on the prepared data, and then click cross channel.

to add a timeslot

----End

6.6.2 Adding an IP Route (Initial) This describes how to add an IP route for transmitting the NodeB IP data of the transmission control plane, the user plane, and the management plane. Scenario

6-188



Issue 01 (2008-06-25)




Prerequisite The physical links at the IP transport layer are configured. For details, refer to 6.6.1 Adding a Link at the Data Link Layer (Initial).

Preparation Table 6-62 Negotiation and planned data of the IP route

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Exampl e

Port type

ItfType

Interface type of the route Optional parameters:

ETH

l

ETH

l

MLPPP

l

PPP

l

PPPoE

Destinatio n network

DestNet

This parameter must meet all the following requirements: Valid network address, except the default route 0.0.0.0 IP AND mask must be equal to the IP address.

17.18.17. 0

Destinatio n mask

DestMask

This parameter must meet all the following requirements: IP AND mask must be equal to the IP address. If the mask is converted into binary value, 0 is not allowed to precede 1.

255.255. 255.0

Next hop IP address

NextHop

This parameter is valid only when the parameter InsertFlag is set to ETH. This parameter meets the following requirements:

12.11.12. 1

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.


Source

Network planning

6-189



Procedure





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


Description

1

Physical link list of the configured IP transport layer

2

Configuration area of the IP route on the control plane, the user plane, and the management plane

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

6-190


Issue 01 (2008-06-25)



NOTE

l

DestNet is the IP address of the destination network. Destination IP address AND subnet mask is the IP address of the destination network, that is DestIP & DestMask = DestNet.

l

In area 1, select the physical link, that is, the out port of the route is determined.

Step 6 Select NextHop, and click , the NextHop dialog box is displayed. Set the IP address of the next hop, and return to the NodeB IP Transport Layer window. NOTE

If the Iub interface is in layer 3 networking, the next hop IP address is the IP address of the router connecting to the NodeB, or the IP address of the port on the layer 3 switch connecting to the NodeB.

----End

6.6.3 Adding SCTP Links (Initial) This describes how to add SCTP links. The SCTP links are used to carry the IPCP, that is, the NBAP at the IP transport layer. Scenario



A complete piece of information of an SCTP link contains the local IP address, the peer IP address, the local IP address of the second SCTP link, the peer IP address of the second SCTP link, the port number of the local SCTP link, and the port number of the peer SCTP link. The two SCTP links must be different in content.

Prerequisite l

The physical links at the IP transport layer are configured. For details, refer to 6.6.1 Adding a Link at the Data Link Layer (Initial).

l

The route to the destination IP address is configured. For details, refer to 6.6.2 Adding an IP Route (Initial).

Preparation Table 6-64 Negotiation and planned data of the SCTP links

Issue 01 (2008-06-25)

Input Data

Field Name

Description

Example

Source

Port type

ItfType

Type of the interface that carries the SCTP links Optional parameters:

PPP

Internal planning

l

ETH

l

MLPPP

l

PPP

l

PPPoE


6-191



Input Data

Field Name

Description

Example

Local IP address

LocalIP

At the NodeB, the IP address of the primary physical link that carries the SCTP link.

17.17.17. 111

Destination IP address

DestIP

At the RNC, the IP address of the primary physical link that carries the SCTP link.

14.1.1.4

The second local IP address

SecLocalIP

At the NodeB, the IP address of the standby physical link that carries the SCTP link.

0.0.0.0

The IP address 0.0.0.0 indicates that this address is not in use. The second destination IP address

SecDestIP

At the RNC, the IP address of the standby physical link that carries the SCTP link.

0.0.0.0

Source


The IP address 0.0.0.0 indicates that this address is not in use. Local port number and destination port number

LocalPort

Destination port number

DestPort

Automatical ly switches back to the master IP address

IPAutoCha nge

Local port number of the SCTP

1024


Destination port number of the SCTP

8021

Value range: 1024 through 65535 After the fault of the master IP address is rectified, the services can be automatically switched back to the master IP address. Optional parameters: l

ENABLE

l

DISABLE

ENABLE

Internal planning

Procedure


6-192



Issue 01 (2008-06-25)





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


Description

1

Configuration area for the SCTP links

2


3

Configured SCTP route list

Step 5 In area 1, click SCTPNo, and click

.

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

Issue 01 (2008-06-25)


6-193



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


Description

1

Configuration area for the destination IP address of the SCTP

2

Physical link list at the IP transport layer

NOTE

l

The local IP address of the SCTP link is the local IP address in area 1 of Figure 6-64. The peer IP address of the SCTP link is on the same network segment with DestNet.

l

After the data link layer is configured, the CME automatically adds the network segment route that is on the same network segment as the local IP address of the data link. That is, the IP address of the destination network and the local IP address of the data link are on the same network segment. For details, refer to area 1 in Figure 6-64. (DestNet and LocalIP use the route of the same network segment.)

l

After the route is determined, the CME automatically traces route related physical link. As shown in area 2 of Figure 6-64, this physical link cannot be changed.


to add an SCTP link.

NOTE

Select the configured SCTP link, and the CME automatically traces the SCTP physical link and its related SCTP route, as shown in area 2 and 3 of Figure 6-63.

----End

6-194


Issue 01 (2008-06-25)



6.6.4 Adding an IPCP (Initial) This describes how to configure the NodeB Control Port (NCP) and Communication Control Port (CCP). These two ports are carried on the SCTP links. Scenario



l

One NodeB can be configured with the active and the standby NCPs or CCPs.

l

Each SCTP link can be configured with only one NCP or CCP.

l

The active and the standby NCPs or CCPs should be configured on different links. For example, if the active one is configured on the SAAL, the standby one should be configured on the SCTP. Otherwise the configuration is invalid.

Prerequisite The SCTP links are configured, as described in 6.6.3 Adding SCTP Links (Initial).

Preparation Table 6-67 Negotiation and planned data of the IPCP Input Data Port type

SCTP number

Field Name

Description

Exampl e

Source

PortType


NCP

Internal planning

1


MASTE R

Internal planning

CCP

Internal planning

SCTPNo

Flag

Flag

Port type

Issue 01 (2008-06-25)

NCP

l

CCP

SCTP number that carries the NCP Value range: 0 through 19

NCP

CCP

l

PortType


SLAVE

l

MASTER


NCP

l

CCP


6-195



Input Data Port No.

Field Name

Description

Exampl e

PortNo


0 Negotiati on with the destinati on

Value range: 0 through 65535 SCTP number

SCTPNo

SCTP number that carries the CCP

Source

2


Flag


SLAVE

l

MASTER

MASTE R

Internal planning

Procedure





Step 4 Click IPCP, as shown in Figure 6-65.

6-196


Issue 01 (2008-06-25)



Figure 6-65 Configuring the NCP and the CCP


Description

1

Configured SCTP link list

2

Configuration area for the IPCP links (NCP, CCP)

Step 5 In area 1, select an SCTP link; in area 2, select PortType and then click parameters based on prepared data, and then click

to add an NCP link.

Step 6 In area 1, select an SCTP link; in area 2, select PortType and then click parameters based on prepared data, and then click

. Configure related

. Configure related

to add an CCP link.

----End

6.6.5 Adding Transmission Resource Group (Initial, over IP) 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 UE data. Each resource group has its separate access control, congestion control, and HSPA flow control. Scenario

NodeB Initial Configuration Guide

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

Issue 01 (2008-06-25)


6-197



l

Each physical link can be configured with a maximum of four transmission groups, that is, the total number of transmission groups over ATM and IP.

l

Each Iub interface board or BBU supports a maximum of 16 transmission resource groups over ATM or 8 transmission resource groups over IP.

l

The transmit bandwidth of the transmission resource group should be not greater than the idle bandwidth at the physical links.

Prerequisite The physical links at the IP transport layer are configured. For details, refer to 6.6.1 Adding a Link at the Data Link Layer (Initial).

Preparation Table 6-69 Negotiation and planned data of the transmission resource group (over IP)

6-198

Input Data

Field Name

Description

Example

Port type

ItfType

Type of the interface that carries the IP transmission resource group Optional parameters:

ETH

l

ETH

l

MLPPP

l

PPP

l

PPPoE


RscgrpNo


0

Transmit bandwidth

TxBandwi dth


10000

l


l


l


l



Source

Internal planning

Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Receive bandwidth

RxBandwi dth


10000

l


l


l


l


Source

Procedure





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

Issue 01 (2008-06-25)


6-199




Description

1


2

Configuration area for the transmission resource group

Step 5 In area 1, select a physical bearer link; In area 2, select RscgrpNo and then click Step 6 Configure other parameters based on the prepared data, and then click resource group over IP.

.

to add a transmission

----End

6.6.6 Adding IP Path Data (Initial) This describes how to add an IP PATH for transmitting the user plane data. Scenario



l

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

l

Each NodeB can be configured with a maximum of 32 IP paths. The total number the configured IP paths and AAL2 paths of the HSPA type cannot exceed 16.

l

The destination IP addresses for the IP PATH configured at the same transport layer link must be the same.

l

The values of the parameters DSCP and TrafficType configured for the IP path in the same transport layer link must differ.

l

If an IP link is configured with a transmission resource group, all IP path links configured at this IP link must join the transmission resource group of the IP link.

l

If a physical port is configured with AAL2 paths or IP paths, and the links are not in a resource group. No transmission resource group can be added to this physical port.

Prerequisite

6-200

l

The IP routes to destination addresses are configured, as described in 6.6.2 Adding an IP Route (Initial).

l

The transmission resource group is configured, refer to 6.6.5 Adding Transmission Resource Group (Initial, over IP).


Issue 01 (2008-06-25)



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

Field Name

Description

Example

Source

Port type

ItfType

Type of the interface that carries the IP PATH Optional parameters:

ETH

Internal planning

ETH

l

MLPPP

l

PPP

l

PPPoE


DestIP

Destination IP address of the IP path

17.18.17. 121


DSCP priority

DSCP


60

Network planning

Service type

TrafficType


RT

Receive bandwidth

Issue 01 (2008-06-25)

l

RxBandwith

l

RT

l

NRT

l

HSPA_RT

l

HSPA_NRT

When PATH joins the resource 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


l


l


l



1000 Negotiati on with the destinatio n

6-201



Input Data

Field Name

Description

Example

Transmit bandwidth

TxBandwith

When PATH joins the resource 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.

1000

Transmit committed burst size

TxCBS

l


l


l


l


Value range: 15000 to 155000000. The recommended value is 1/2 of the transmit bandwidth.

Source

500000

Unit: bit Transmit excessive burst size

TxEBS

Path check

PathCheck



6-202


1000000

Unit: bit

JoinRscgrp

RscgrpNo


ENABLE: Path check is enabled.

l

DISABLE: Path check is disabled.

Specify whether the IP PATH should be added to the resource group. Optional parameters: l

DISABLE

l

ENABLE

Number of the IP transmission resource group

DISABL E

Internal planning

ENABLE

0



Issue 01 (2008-06-25)



Procedure





Step 4 Click IPPath, as shown in Figure 6-67. Figure 6-67 Configuring the IP PATH


Issue 01 (2008-06-25)


Description

1

Configuration area for the IP path

2


3


4

Configured IP path route list


6-203



Step 5 In area 1, click PathId, and click

.

Step 6 Select DestIP, and click . The Destination IP window is displayed, as shown in Figure 6-68. In area 1, select the network segment route, and set the peer IP address of the IP path in the upper middle part of the window. Click OK to return to the NodeB IP Transport Layer window. Figure 6-68 Configuring the destination IP address of the IP PATH


Description

1

Configuration area for the destination IP address of the IP PATH

2


NOTE

6-204

l

The local IP address of the IP PATH is the local IP address in area 1 of Figure 6-68. The peer IP address of the IP PATH is on the same network segment with DestNet.

l


l

After the route is determined, the CME automatically traces route related IP transmission resource group. As shown in area 2 of Figure 6-68, this IP transmission resource group cannot be changed.


Issue 01 (2008-06-25)



Step 7 (Optional) Set JoinRscgrp to ENABLE. Select RscgrpNo, and click , the Search Resource Group window is displayed. Select a transmission resource group, and click OK to return to the NodeB IP Transport Layer window. NOTE

The physical bearer type of the resource group is identical with that of the IP path. Figure 6-67 and Table 6-72 show the matching relation.


to add an IP path.

NOTE

Select the configured IP path, and then the CME automatically traces the related IP transmission resource group and the IP path route, as shown in areas 3 and 4 of Figure 6-67.

----End

6.6.7 Adding an OMCH of the NodeB (Initial, over IP) This describes how to configure an OMCH of the NodeB in IP transport mode. Scenario



l

A maximum of two OMCH channels are added, that is, the master and the slave channels. You can also configure only one OMCH channel. If it acts as the master channel, the data takes effect; if it acts as the slave channel, the data will not take effect.

l

Local IP addresses of two OMCH channels cannot be on the same network segment.

Prerequisite l


l

The IP routes to destination addresses are configured, as described in 6.6.2 Adding an IP Route (Initial).

Issue 01 (2008-06-25)


6-205



Preparation Table 6-74 Negotiation and planned data of the OMCH (IP) Input Data

Field Name

Description

Example

Bind the route

BindRoute Valid

Determine whether to bind the route. 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:

YES

Port type

6-206

ItfType

l

NO

l

YES

Type of the interface that carries the bound routes Optional parameters: l

ETH

l

MLPPP

l

PPP

l

PPPoE

ETH

Bound IP address on the destination network

BindDestIP


11.11.10. 0


BindDestIP Mask


255.255. 255.0

Bound next hop IP address

NextHop

This parameter is valid only when the port type is ETH.

12.11.12. 1

Local IP address

LocalIP

IP address at the NodeB for the OMCH

11.11.12. 12

Local subnet mask

Mask

Mask of the IP address at the NodeB for the OMCH

255.255. 0.0


DestIP

Destination IP address of the OMCH, that is, the IP address of the LMT or the M2000.

11.11.11. 12

Flag

Flag


MASTE R

l


l



Source


Internal planning

Issue 01 (2008-06-25)



Procedure





Step 4 Click OMCH, as shown in Figure 6-69. Figure 6-69 Adding an OMCH


Description

1

OMCH configuration area

2

Type of the interface that carries the bound routes

3

Configured OMCH route list

Step 5 (Optional) Set the parameter BandRouteValid to YES. Then, select the parameter BandDestIP and click Issue 01 (2008-06-25)

, the BandDestIP & BandDestIPMask dialog box is displayed. Set


6-207



the IP address and the mask for the binding destination network of the OMCH, and then click OK to return to the NodeB IP Transport Layer window. NOTE

l

The destination network segment of the binding route must differ from the network segment of the DestNet in 6.6.2 Adding an IP Route (Initial).

l

The destination IP address of the OMCH can use the network segment where the binding route is located.

Step 6 In area 1, select LocalIP, and click , the LocalIP & Mask dialog box is displayed. Set the local IP address and the mask for the OMCH, and then click OK to return to the NodeB IP Transport Layer window. Step 7 Select DestIP, and click . The Destination IP Address window is displayed, as shown in Figure 6-70. Select the network segment route, and set the peer IP address of the IP OMCH in the upper middle part of the window. Click OK to return to the NodeB IP Transport Layer window. Figure 6-70 Adding a destination IP address of the OMCH

NOTE

l

If the BandRouteValid is set to YES(the route is bound), the CME system automatically generates the route to the bound destination network. For instance, the network IP address of Figure 6-70 is 11.11.10.0, and the interface type is ETH.

l

The destination IP address of the OMCH can be either on the same network segment as the DestNet in 6.6.2 Adding an IP Route (Initial), or on the same network segment as the BandDestIP.


6-208


to add an OMCH

Issue 01 (2008-06-25)



NOTE

Select the configured OMCH, the CME automatically traces the related OMCH route, as shown in area 3 of Figure 6-69.

----End

6.6.8 Adding A Bound Destination Network Segment to the Transmission Resource Group (Initial, IP) This describes how to add a bound destination network segment to the transmission resource group. All data to the subnet from the port of the transmission resource group will be calculated in the transmission resource group. Scenario


Mandatory/ Optional. This configuration is required when the SCTP link or the OMCH link Optional joins the transmission resource group. NOTE

l

Two transmission resource groups of the same physical port cannot be bound to the same destination network segment.

l

The transmission resource group (IP as the bearer mode) to which the bound destination network segment is added is already configured. Otherwise, the binding fails to proceed.

Prerequisite The IP transmission resource group is configured, refer to 6.6.5 Adding Transmission Resource Group (Initial, over IP).

Preparation Table 6-76 Negotiation and planned data of the transmission resource group whose destination IP network segment is bound Input Data

Field Name

Description

Example

Port type

ItfType

Type of the interface that carries the resource group Optional parameters:

ETH


RscgrpNo

l

ETH

l

MLPPP

l

PPP

l

PPPoE

Number of the IP transmission resource group that corresponds to the physical bearer port

Source

Internal planning 0


Issue 01 (2008-06-25)


6-209



Input Data

Field Name

Description

Example


DestIP

Bound destination IP address, that is, the IP address on the same network 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).

11.11.10.1 0

Destinatio n mask

IPMask


255.255.2 55.255

Source

Procedure





Step 4 Click IP2RSCGroup, as shown in Figure 6-71. Figure 6-71 Adding a bound destination network segment to the transmission resource group (initial, over IP)

6-210


Issue 01 (2008-06-25)




Description

1

Configured IP transmission resource group

2

Configured route mapping the IP transmission resource group

3

Configuration area for adding a bound destination network segment to the transmission resource group

Step 5 In area 1, select an IP transmission resource group; in area 2, select the IP address of the bound destination network. . Select DestIP, and click . The DestIP & Step 6 In area 3, click SubrackNo, and click Mask dialog box is displayed. To add a destination IP address, click OK to return to the NodeB IP Transport Layer window. NOTE

l

DestIP & DestMask = DestNet & DestMask; DestIP & IPMask = DestIP.

l

If the SCTP link joins the resource group, the DestIP is the destination IP address of the SCTP link.

l

If the OMCH link joins the resource group, the DestIP is the bound destination IP address of the OMCH link. (The bound destination IP address and BindDestIP are on the same network segment).

Step 7 Configure other parameters based on the prepared data. Click network segment to the transmission resource group.

to add a bound destination

----End

6.6.9 Adding IP Clock Links (Initial) This describe how to add IP clock links. The NodeB can obtain the clock signals from the clock server through the IP link. Scenario



CAUTION l

The timeslot cross channel over IP cannot be configured to the NUTI that uses the parameter IPClockSwitch.

l

When the IP clock link is added, you need to set the current ClockSource (clock resource type) to the IP (IP clock resource) mode before the NodeB is used by the IP clock. For details, refer to 6.2.1 Manually Creating a Physical NodeB (Initial).

Issue 01 (2008-06-25)


6-211



Prerequisite l

The parameter IPClockSwitch on the NUTI is enabled. For details, refer to 6.2.2 Adding the Boards in the Baseband Subrack (Initial).

l


l

The IP routes to the server are configured, as described in 6.6.2 Adding an IP Route (Initial).

Preparation Table 6-78 Negotiation and planned data of the IP clock links Input Data

Field Name

Description

Example

Source

Port type

ItfType

Type of the interface that carries the IP clock links Optional parameters:

PPPoE

Internal planning

l

ETH

l

MLPPP

l

PPP

l

PPPoE

IP address at the client

ClientIP

Obtain the NodeB IP address of the IP clock

12.3.0.1

IP address at the server

ServerIP

IP address at the IP clock server

12.3.0.10

Priority

Priority

The clock links that has the highest priority is used first. The number is in a negative relation with the priority level.

Network planning

0


Procedure


6-212



Issue 01 (2008-06-25)





Step 4 Click IPCLKLNK, as shown in Figure 6-72. Figure 6-72 Adding an IPCLKLNK link


Description

1

Configuration area for the IP clock link

2


3

Configured IP clock link route list

. Select ServerIP, and click . The Destination IP Step 5 In area 1, click SubrackNo, and click Address & Local IP Interface window is displayed, as shown in Figure 6-73. In area 1, select the network segment route, and set the server IP address of the IP clock link in the upper middle part of the window. Click OK to return to the NodeB IP Transport Layer window.

Issue 01 (2008-06-25)


6-213



Figure 6-73 Configuring the IP address at the IP clock link server


Description

1

Configuration area for the destination IP address of the IP clock link

2


NOTE

l

The client IP address of the IP clock link is the local IP address in area 1 of Figure 6-73. The server IP address of the IP clock link is on the same network segment with DestNet.

l


l

After the route is determined, the CME automatically traces route related physical link. As shown in area 2 of Figure 6-73, this physical link cannot be changed.


to add a clock link.

NOTE

Select the configured IP clock link, and the CME automatically traces the IP clock link and its related IP clock route, as shown in areas 2 and 3 of Figure 6-72.

----End

6-214


Issue 01 (2008-06-25)



6.6.10 Modifying IP QoS Data (Initial) This describes how to modify the signaling and Operation and Maintenance (OM) priorities. Scenario



l

IP QoS is an IP network capability to provide specific services over the IP network that uses multiple bottom-layer network technologies such as MP, FR, ATM, Ethernet, SDH, and MPLS.

l

IP QoS supports the switching between the IP precedence and DSCP. The IP QoS configuration is flexible depending on actual requirements.

Prerequisite None.

Preparation Table 6-81 Negotiation and planned data of the IPQoS Input Data

Field Name

Description

Example

Priority rule

PriRule


IPPRECE DENCE

Signaling priority

Operation and Maintenanc e (OM) priority

SigPri

OMPri

l

IPPRECEDENCE

l

DSCP

l


l


l


l


Source

7 Network planning 7

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)


6-215



Step 2 Click




Step 4 Click IPQos, as shown in Figure 6-74. Figure 6-74 Configuring the Diffserv priority on the transport layer

Step 5 Select PriRule, and select a priority rule from the drop-down list. Step 6 Select SigPri and OMPri, and then set the signaling and OM priorities. Step 7 Click


----End

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


Mandatory/ Optional. This function is customized. Therefore, it is not applied to all scenarios. Optional

6-216


Issue 01 (2008-06-25)



NOTE

l


l


l



Prerequisite l


l


l


l


l


l


Preparation

Issue 01 (2008-06-25)


6-217



Procedure






Description


6-218


Issue 01 (2008-06-25)





Description

1


2



Issue 01 (2008-06-25)


6-219




NOTE

l


l





6.8 Adding Radio Layer Data This describes how to configure radio network layer data for the NodeB. The related activities involve adding sites, adding sectors, and adding local cells. 6.8.1 Adding Sites This describes how to add a NodeB site. The NodeB modules that are in the charge of the same main module are called a NodeB. They can be located in different places and connected to each other through optical fibers and standard interfaces. Each module at a specific place can be planned as a site. 6.8.2 Adding Sectors and Cells (Macro NodeB) This describes how to configure cells in local sectors, remote sectors, and distributed sectors in a macro NodeB. From the hardware perspective, the local sector needs the support from the MTRU and MAFU, and the remote and the distributed sector needs the support from the MRRU 6-220


Issue 01 (2008-06-25)



or the PicoRRU (PRRU). The cells can be configured in the local sectors, remote sectors, or distributed sectors. 6.8.3 Adding Sectors and Cells (Distributed NodeB) This describes how to add the remote sectors and distributed sectors for a distributed NodeB. The distributed NodeB supports only remote and distributed sectors. In terms of hardware support, the remote sector and the distributed sector need the MRRU or PRRU (PicoRRU) RF unit. The cells can be configured only in remote sectors or distributed sectors.

6.8.1 Adding Sites This describes how to add a NodeB site. The NodeB modules that are in the charge of the same main module are called a NodeB. They can be located in different places and connected to each other through optical fibers and standard interfaces. Each module at a specific place can be planned as a site. Scenario





Field Name

Description

Example

Source

Site name

Site Name

The site is usually named after the geographical location.

Shanghai

Network planning

Procedure



Step 3 Select a physical NodeB, and then click as shown in Figure 6-78. Issue 01 (2008-06-25)

. The NodeB Radio Layer window is displayed,


6-221



Figure 6-78 Adding Sites


Description

1

Configuration area for sites

Step 4 In area 1, select SiteId, and click to the prepared data.

. Configure parameters SiteId and Site Name according

NOTE

SiteId is unique in one NodeB.

Step 5 Click

to add a site.

----End

6.8.2 Adding Sectors and Cells (Macro NodeB) This describes how to configure cells in local sectors, remote sectors, and distributed sectors in a macro NodeB. From the hardware perspective, the local sector needs the support from the MTRU and MAFU, and the remote and the distributed sector needs the support from the MRRU or the PicoRRU (PRRU). The cells can be configured in the local sectors, remote sectors, or distributed sectors. Scenario 6-222


Issue 01 (2008-06-25)




l

The MAFU or MRRU supports four carrier frequencies and the PRRU supports two carrier frequencies.

l

The uplink and downlink frequencies of the cell configured in the same MAFU, MRRU, or PRRU must be at the same frequency band, and the difference of frequency between cells should meet certain conditions. l

If the PA supports two carriers, the carriers are on the same PA. The frequency difference between two local cells should not be smaller than 4.2 MHz (21 x 0.2 MHz), and not greater than 5 MHz (25 x 0.2 MHz).

l

If the PA supports four carriers, the carriers are on the same PA. The frequency difference between two local cells should not be smaller than 4.2 MHz (21 x 0.2 MHz), and not greater than 15 MHz (75 x 0.2 MHz).

l

A represents TX/RX antenna.

l

B represents RX antenna.

Prerequisite l

The physical NodeB,that is the BTS3812AE, BTS3812A, or BTS3812E is configured. For details, refer to 6.2.1 Manually Creating a Physical NodeB (Initial).

l

The remote and distributed sectors can be configured only when the BTS3812AE, BTS3812A, or BTS3812E is configured with the MRRU or PRRU (PicoRRU). For details, refer to 6.2.4 Adding an RRU (Initial, Macro NodeB).

l

The local sectors can use only the antenna channel on the MAFU module. For details, refer to 6.2.5 Adding RF Modules (Initial).

l

The sites are configured. For details, refer to 6.8.1 Adding Sites.

Issue 01 (2008-06-25)


6-223



Preparation Table 6-84 Negotiation and planned data of the sector Input Data

Field Name

Description

Example


RxAntennaN um


2

Source



TxDiversity Mode

l


l




l


l


TX_DIVE RSITY

Network planning

When the number of configured RX antennas is one, the sector can work only in no transmit diversity mode.

6-224


Issue 01 (2008-06-25)


Issue 01 (2008-06-25)


Input Data

Field Name

Description

Example

Coverage type

Cover Type


-

l


l



Source

6-225



Table 6-85 Negotiation and planned data of the cell Input Data

Field Name

Description

Example

Uplink frequency

UARFCNUp Link


9612

Source



l


l


Network planning



l


l

6-226



Issue 01 (2008-06-25)


Input Data


Field Name

Description

Example

Source

Special frequencies: {812,837}. Offset:670.1 l


l


l


Issue 01 (2008-06-25)


6-227



Input Data

Field Name

Description

Example

Downlink frequency

UARFCNDo wnLink


10562

Source



l


l


l


l


l


6-228


Issue 01 (2008-06-25)


Input Data


Field Name

Description l

Example

Source


l


l


Issue 01 (2008-06-25)


ULResource GroupId


0


DLResource GroupId


0


BbPoolType


GEN_POO L


6-229



Input Data

Field Name

Description

Example


MaxTxPower


430

l


l


Source


CellRadius


29000




0


6-230


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


Desensy


Source




Hispm

Spr

DefPowerLvl



l

TRUE (high speed)


250

l

400

l

500


FALSE

-

100


Procedure l

Configure local sectors and cells. NOTE

The local sector uses only the RF board, that is, MAFU.

1.

Issue 01 (2008-06-25)

In the NodeB Radio Layer window, click the Local Sector tab, and the tab page is displayed, as shown in Figure 6-79.


6-231



Figure 6-79 Configuring local sectors and cells


2.


Description

1

Configuration area for the local sectors

2

Antenna channel list for the local sectors

3

Used antenna channel list

4

Cell configuration areas for the local sectors

5

List of available RF channels for cells

6

Used RF channel list

click 3.

. Set parameters based on prepared data. Then,

In area 1, click SectorNo, and click to add a local sector.

In area 2, the available antenna channels that can be used by the local sectors are filtered out. Select the antenna channel, and then click the antenna channel used by the local sector.

6-232

to configure

.

4.

In area 4, click LoCell, and click

5.

Set parameters UARFCNUpLink and UARFCNDownLink for the cell.


Issue 01 (2008-06-25)



6.

Select ULResourceGroupId or DLResourceGroupId, and click . The ULGroup or DLGroup window is displayed. Select an uplink or a downlink resource group, and click Close to return to the NodeB Radio Layer window.

7.

Select INHBOARD, and click . The Mac Params Confige Form window is displayed, as shown in Figure 6-80. Modify Mac-hs and Mac-e related parameters, and click

. Then, click Close to return to the NodeB Radio Layer window.

Figure 6-80 Modifying Mac-hs and Mac-e related parameters


Issue 01 (2008-06-25)


Description

1

Modify Mac-hs scheduling parameters.

2

Modify Mac-hs resource limit parameters.

3

Modify Mac-hs SPI scheduling parameters.


6-233



l

For the BTS3812AE, BTS3812A, or BTS3812E, if the previously mentioned parameters for the specified local cells are modified, you must select the HSDPA Capability check box, and the INHBOARD is INHBOARD; if you deselect the HSDPA Capability check box, the INHBOARD is UNLIMITED.

l

For the DBS3800, the status of the HSDPA Capability check box is unchangeable, that is, the check box can only be selected. The INHBOARD can only be INHBOARD.

8.

Configure other parameters based on the prepared data, and then click cell.

9.

In area 5, the available RF channels that can be used by the cell are filtered out. Select the RF channel, and then click the cell.

l

to add a

to configure the RF channel used by

Configure remote sectors and cells. NOTE

1.

l

When the number of receive antennas is 2 or 4, only the RX/TX antenna channels on the MRRU configured on the main line of the RRU chain/ring can be used.

l

When the number of receive antennas is 1, only the RX/TX antenna channels on the MRRU/ PRRU configured on the main line of the RRU chain/ring can be used.

In the NodeB Radio Layer window, click the Remote Sector tab, the tab page is displayed, as shown in Figure 6-81.

Figure 6-81 Configuring remote sectors and cells

6-234


Issue 01 (2008-06-25)




l


Description

1

Configuration area for the remote sectors

2

Available antenna channel list for remote sectors

3


4

Configuration area for the cells of the remote sectors

5


6


2.

Perform Step 2 through Step 3 to configure remote sectors.

3.

Perform Step 4 through Step 9 to configure cells of the remote sectors.

Configure distributed sectors and cells NOTE

1.

l

The TX/RX mode of distributed sectors is always unidirectional (TX/RX).

l

The distributed sector uses only the RX/TX antenna channels on the MRRU or PRRU (including the PRRU configured on the RHUB) configured on the RRU chain/ring.

In the NodeB Radio Layer window, click the Distribute Sector tab, the tab page is displayed, as shown in Figure 6-82.

Figure 6-82 Configure distributed sectors and cells

Issue 01 (2008-06-25)


6-235




Description

1

Configuration area for the distributed sectors

2

Available antenna channel list for distributed sectors

3


4

Configuration area for the cells of the distributed sectors

5


6


2.

Perform Step 2 through Step 3 to configure the distributed sectors.

3.

Perform Step 4 through Step 9 to configure cells of the distributed sectors.

----End

6.8.3 Adding Sectors and Cells (Distributed NodeB) This describes how to add the remote sectors and distributed sectors for a distributed NodeB. The distributed NodeB supports only remote and distributed sectors. In terms of hardware support, the remote sector and the distributed sector need the MRRU or PRRU (PicoRRU) RF unit. The cells can be configured only in remote sectors or distributed sectors. Scenario



l

The MRRU supports four carrier frequencies and the PRRU supports two carrier frequencies.

l

The uplink and downlink frequencies of the cell configured in the same MRFU, MRRU, or PRRU must be at the same frequency band, the uplink frequencies must be smaller than the downlink frequencies, and the difference of frequency between cells should meet certain conditions. l

If the PA supports two carriers, the carriers are on the same PA. The frequency difference between two local cells should not be smaller than 4.2 MHz (21 x 0.2 MHz), and not greater than 5 MHz (25 x 0.2 MHz).

l

If the PA supports four carriers, the carriers are on the same PA. The frequency difference between two local cells should not be smaller than 4.2 MHz (21 x 0.2 MHz), and not greater than 15 MHz (75 x 0.2 MHz).

l

A represents TX/RX antenna.

l

B represents RX antenna.

Prerequisite l

6-236

The DBS3800 related physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a Physical NodeB (Initial). Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)



l


l

The sites are configured. For details, refer to 6.8.1 Adding Sites.

Preparation Table 6-90 Negotiation and planned data of the sector Input Data

Field Name

Description

Example


RxAntennaN um


2

Source



TxDiversity Mode

l


l




l


l


TX_DIVE RSITY

Network planning

When the number of configured RX antennas is one, the sector can work only in no transmit diversity mode. Issue 01 (2008-06-25)


6-237



6-238

Input Data

Field Name

Description

Example

Coverage type

Cover Type


-

l


l



Source

Issue 01 (2008-06-25)



Table 6-91 Negotiation and planned data of the cell Input Data

Field Name

Description

Example

Uplink frequency

UARFCNUp Link


9612

Source



l


l


Network planning



l


l

Issue 01 (2008-06-25)



6-239



Input Data

Field Name

Description

Example

Source

Special frequencies: {812,837}. Offset:670.1 l


l


l


6-240


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example

Downlink frequency

UARFCNDo wnLink


10562

Source



l


l


l


l


l


Issue 01 (2008-06-25)


6-241



Input Data

Field Name

Description l

Example

Source


l


l


6-242


ULResource GroupId


0


DLResource GroupId


0


BbPoolType


GEN_POO L


Issue 01 (2008-06-25)



Input Data

Field Name

Description

Example


MaxTxPower


430

l


l


Source


CellRadius


29000




0


Issue 01 (2008-06-25)


6-243



Input Data

Field Name

Description

Example


Desensy


Source


Hispm



Spr

DefPowerLvl



l

TRUE (high speed)


250

l

400

l

500


FALSE

-

100


Procedure l

Configure remote sectors and cells. NOTE

1.

6-244

l

When the number of receive antennas is 2 or 4, only the RX/TX antenna channels on the MRRU configured on the main line of the RRU chain/ring can be used.

l

When the number of receive antennas is 1, only the RX/TX antenna channels on the MRRU/ PRRU configured on the main line of the RRU chain/ring can be used.

In the NodeB Radio Layer window, click the Remote Sector tab, the tab page is displayed, as shown in Figure 6-83.


Issue 01 (2008-06-25)



Figure 6-83 Configuring remote sectors and cells


l


Description

1

Configuration area for the remote sectors

2

Available antenna channel list for remote sectors

3


4

Configuration area for the cells of the remote sectors

5


6


2.

Perform Step 2 through Step 3 in the 6.8.2 Adding Sectors and Cells (Macro NodeB) to add remote sectors.

3.

Perform Step 4 through Step 9 in the 6.8.2 Adding Sectors and Cells (Macro NodeB) to add cells of the remote sectors.

Configure distributed sectors and cells NOTE

1.

Issue 01 (2008-06-25)

l

The TX/RX mode of distributed sectors is always unidirectional (TX/RX).

l

The distributed sector uses only the RX/TX antenna channels on the MRRU or PRRU (including the PRRU configured on the RHUB) configured on the RRU chain/ring.

In the NodeB Radio Layer window, click the Distribute Sector tab, the tab page is displayed, as shown in Figure 6-84. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

6-245



Figure 6-84 Configure distributed sectors and cells


Description

1

Configuration area for the distributed sectors

2

Available antenna channel list for distributed sectors

3


4

Configuration area for the cells of the distributed sectors

5


6


2.

Perform Step 2 through Step 3 in the 6.8.2 Adding Sectors and Cells (Macro NodeB) to add distributed sectors.

3.

Perform Step 4 through Step 9 in the 6.8.2 Adding Sectors and Cells (Macro NodeB) to add cells of the distributed sectors.

----End

6-246


Issue 01 (2008-06-25)


7

7 Related Concepts of NodeB Initial Configuration

Related Concepts of NodeB Initial Configuration

About This Chapter This provides the related concepts to be referenced during the process of the NodeB initial configuration. 7.1 Cell Related Concepts This provides the cell related concepts, including those of the sectors, carriers, cells, physical resources of cells, local cells, and logical cells. 7.2 ATM Protocol-Related Terms This describes the terms related to the ATM protocol. The reference model of the ATM protocol consists of three planes and three function layers. The three planes are control plane, user plane, and management plane. The three function layers are physical layer, ATM layer, and ATM adaptation layer (AAL). 7.3 IP Protocol-Related Terms This describes the terms related to the protocols of the data link layer, network layer, and transport network layer when the Iub interface uses the IP transport. 7.4 NodeB Treelink PVC The function of a NodeB treelink PVC is similar to that of the ATM switching. This describes how to add a treelink PVC to the NodeB, that is, to add an ATM switching route to the NodeB (over ATM), so as to switch the PVC from one physical bearer to another. 7.5 NodeBs in Direct/Cascading Connections This defines the NodeBs in direct and cascading connections. In addition, it describes the configuration differences between these two connections.

Issue 01 (2008-06-25)


7-1



7.1 Cell Related Concepts This provides the cell related concepts, including those of the sectors, carriers, cells, physical resources of cells, local cells, and logical cells. 7.1.1 Sector, Carrier, and Cell This describes the sector, carrier, and cell. A sector is the smallest radio coverage area unit, which is covered by one or more radio carriers. Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallest serving unit for UE access. 7.1.2 Physical Resources of Cells This describes the physical resources of cells from the perspectives of RF resources of sectors and resource pools of cells. 7.1.3 Local Cell and Logical Cell This describes local and logical cells. In the 3GPP protocols, a serving cell is called local cell and logical cell at the implementation layer of physical layer and the management layer of logical resources respectively.

7.1.1 Sector, Carrier, and Cell This describes the sector, carrier, and cell. A sector is the smallest radio coverage area unit, which is covered by one or more radio carriers. Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallest serving unit for UE access. Sectors are classified into omnidirectional sectors and directional sectors. An omnidirectional sector is used in small traffic areas. Centered around the omnidirectional RX/TX antenna, the omnidirectional sector covers 360o circular areas. When the traffic increases, the omnidirectional sector is split into three or six directional sectors. The directional sectors are covered by directional antennas. For example, when there are three directional sectors, each set of directional antenna covers a 120o area. When there are six directional sectors, each set of directional antenna covers a 60o area. In fact, the azimuth of the antenna is greater than the theoretical value, and therefore there is overlap between the sectors. Number of cells supported by a NodeB = number of sectors x number of carriers in each sector. Figure 7-1 shows the typical 3 x 2 configuration. The area is split into sectors 0, 1, and 2. Each sector has two carriers, and each carrier forms a cell. There are six cells in total. Frequency multiplexing is allowed in a WCDMA system if different downlink primary scrambling codes are used in neighboring cells of different sectors that use the same frequency. In this way, the inter-cell interference is reduced.

7-2


Issue 01 (2008-06-25)



Figure 7-1 Relations among a sector, carrier, and cell

7.1.2 Physical Resources of Cells This describes the physical resources of cells from the perspectives of RF resources of sectors and resource pools of cells.

RF Resources of Sectors The NodeB provides RF resources of cells. Figure 7-2 shows the physical RF resources mapped to a NodeB from sectors. Each sector uses one directional antenna. Each directional antenna provides 2-way receive channels to enhance the receiving sensitivity, and the two channels work in mutual receive diversity mode. l

RF modules of a distributed NodeB are the RRU and PicoRRU (PRRU).

l

RF modules of a macro NodeB are the MAFU and MTRU. The MAFU and MTRU work in pairs.

Issue 01 (2008-06-25)


7-3



Figure 7-2 Physical RF resources mapped from sectors onto NodeB

Figure 7-2 shows the mapping between the sectors and the RF module for a 2-carrier NodeB in 2-way receive diversity mode. The mapping may vary with the NodeB configuration. Figure 7-3 shows the rules of the mapping between BTS3812E sectors and MAFUs and MTRUs.

7-4

l

1MAFU+1MTRU for one sector: The NodeB supports 6 sectors. This mode supports 1carrier or 2-carrier 1T2R configuration.

l

2MAFUs+2MTRUs for one sector: The NodeB supports three sectors. This mode supports 1-carrier or 2-carrier 1T2R or 2T2R configuration, and 3-carrier or 4-carrier 1T2R Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)



configuration. You may change the external interface connections of the MTRUs and MAFUs so that this sector mode can support 1-carrier or 2-carrier 2T4R configuration. l

4MAFUs+4MTRUs for one sector: The NodeB supports one to three sectors. A combined cabinet is required when there are more than one sector. This mode supports 3-carrier or 4-carrier 2T4R configuration.

Figure 7-3 Rules of the mapping between NodeB sectors and MAFUs or MTRUs

Resource Pools of Cells The macro NodeB sends the uplink or downlink signal processing resources to the resource pool. Cells in the resource pool can share the resources. When you configure the cell, specify the type of resource pool that the cell belongs to. Two types of resource pools are as follows: l

GEN_POOL: indicates the uplink and downlink baseband resource pool that consists of the HBBI, HULP, and HDLP. This type of resource pool is commonly used. When the resource pool is used, you must specify uplink baseband resource groups.

l

GRP_POOL: indicates the uplink and downlink baseband resource pool that consists of the HBOI in slot 15. When the resource pool is used, you do not need to specify uplink baseband resource groups.

The NodeB divides the uplink baseband resources into different groups, which are called uplink baseband resource groups. The uplink baseband resource groups have the following features and requirements: l

One uplink baseband resource group consists of one or more uplink processing units. One uplink processing unit corresponds to one HBBI/HBOI/HULP board or one BBU module.

l

The cells in one uplink baseband resource group share the uplink resources. Each uplink baseband resource group supports a maximum of 6 cells in 2-way and enhanced 2-way modes. Each uplink baseband resource group supports a maximum of three cells in 4-way and economic 4-way modes.

l

The softer handover can be performed between the cells in the same uplink baseband resource group. You need to add the intra-frequency cells to the same group.

l

Keep the number of resource groups as small as possible. For example, for a 3 x 4 NodeB, divide the resource pool into two groups, each of which supports 6 cells.

Issue 01 (2008-06-25)


7-5



7.1.3 Local Cell and Logical Cell This describes local and logical cells. In the 3GPP protocols, a serving cell is called local cell and logical cell at the implementation layer of physical layer and the management layer of logical resources respectively.

Local Cell A local cell is a combination of physical resources, such as hardware and software resources, in a cell of a NodeB. A local cell is related to the physical implementation of a device. NodeBs from different vendors have different ways of providing physical resources for cells. Therefore, the concept of logical cell is proposed in the 3GPP to ensure that the RNC can control the radio resources in certain cells through the standard Iub interface. These cells are carried on NodeBs from different vendors.

Logical Cell A logical cell is a standard logical model that helps the RNC control the radio resources in a cell. The model is independent of the implementation of local cells in the NodeB, and ensures that the Iub interface is an open interface. The parameters of a local cell are configured at and managed by the NodeB. The parameters of a logical cell are configured at and managed by the RNC. A logical cell and a local cell have the one-to-one correspondence.

7.2 ATM Protocol-Related Terms This describes the terms related to the ATM protocol. The reference model of the ATM protocol consists of three planes and three function layers. The three planes are control plane, user plane, and management plane. The three function layers are physical layer, ATM layer, and ATM adaptation layer (AAL). Figure 7-4 shows the reference model of the ATM protocol. Figure 7-4 Reference model of the ATM protocol

7.2.1 ATM User Plane, ATM Control Plane, and ATM Management Plane 7-6


Issue 01 (2008-06-25)



This describes the functions of the ATM user plane, ATM control plane, and ATM management plane. 7.2.2 ATM Physical Layer, ATM Layer, and AAL This describes the functions of the physical layer, ATM layer, and AAL.

7.2.1 ATM User Plane, ATM Control Plane, and ATM Management Plane This describes the functions of the ATM user plane, ATM control plane, and ATM management plane. Table 7-1 describes the functions of the ATM user plane, ATM control plane, and ATM management plane. Table 7-1 Functions of the ATM user plane, ATM control plane, and ATM management plane Plane

Function

User plane

The user plane transfers user data, such as protocol data and voice data.

Control plane

The control plane transfers signaling messages, such as connection setup and connection release.

Management Plane

The management plane transfers network OM data. This plane is classified into the layer management part and the plane management part. The former is responsible for intra-layer management, and the latter for inter-layer management.

NOTE

As stated in the ATM protocols, the AAL and higher layers process the data on the control plane and the user plane in different ways. The ATM layer and the physical layer, however, process the data on the two planes in the same way.

7.2.2 ATM Physical Layer, ATM Layer, and AAL This describes the functions of the physical layer, ATM layer, and AAL. Table 7-2 describes the layers and functions of the reference model of the ATM protocol. Table 7-2 Layers and functions of the reference model of the ATM protocol Protocol Layer CS AAL

Issue 01 (2008-06-25)

Function The AAL is a higher layer of the ATM layer and performs the adaptation from the upper layer applications to the ATM layer. For various types of services, the AAL performs the adaptation in different ways. It segments data from the upper layer into SDUs. Each SDU has 48 bytes. The AAL reassembles and


7-7



Protocol Layer

ATM layer

Function

SAR

restores the SDUs from the ATM layer, and then transfers them to the upper layer. The CS layer performs the convergence. The SAR layer performs the segmentation and reassembly.

-

ATM switching is a fast packet switching technology. In ATM switching, each 53-byte packet is called a cell. At the physical layer, the ATM layer communicates with the peer layer through ATM cells.

TC (UNI, IMA, Fractional ATM, Fractional IMA, or STM-1 mode) PM (PDH over E1/T1, SDH)

Physical layer

l

Generic traffic control

l

Cell header generation and extraction

l

VPI and VCI translation

l

Cell multiplexing and demultiplexing

The physical layer provides channels for bit streams of ATM cells. During data transmission, the physical layer adds the overhead to the ATM cells sent by the ATM layer to form a consecutive bit stream. Then, the physical layer puts the stream on a transport channel. During data reception, the physical layer selects valid ATM cells from the bit stream on the transport channel and then transfers these cells to the ATM layer. The physical layer consists of the PM sublayer and the TC sublayer. The TC sublayer performs the following functions: l Generation and recovery of transmission frames l

Adaptation of transmission frames

l

Cell delimitation

l

Generation and verification of HEC header sequence Decoupling of cell rate

l

The PM sublayer performs the following functions: l Bit timing l

Physical medium

7.3 IP Protocol-Related Terms This describes the terms related to the protocols of the data link layer, network layer, and transport network layer when the Iub interface uses the IP transport. 7.3.1 Data Link Layer Protocols 7-8


Issue 01 (2008-06-25)



This describes the data link layer protocols related to IP transport. 7.3.2 IP This describes the Internet Protocol (IP). It provides a connectionless service between networks and defines the rules and details for data communication. It is used along with the Transmission Control Protocol (TCP) to provide guaranteed data transfer. 7.3.3 SCTP This describes the Stream Control Transmission Protocol (SCTP). It is mainly used for transmitting reliable datagrams through an unreliable network.

7.3.1 Data Link Layer Protocols This describes the data link layer protocols related to IP transport. 7.3.1.1 PPP This describes the Point-to-Point Protocol (PPP). The PPP is used at the data link layer. The PPP provides standard methods for encapsulating the multi-protocol datagrams on point-to-point links. These datagrams include IP, IPX, and Apple Talk. 7.3.1.2 MP This describes the Multilink PPP (MP). With the wide application of the PPP, the MP emerges as an extended protocol of the PPP. The MP provides a large bandwidth to enable quick data transfer. In addition, the MP dynamically allocates the link resources to effectively save the valuable resources. 7.3.1.3 PPPoE This describes the PPPoE protocol. It is a standard that defines how multiple hosts are connected to a remote Access Concentration (AC) in a broadcasting-type network (for example Ethernet). When the PPPoE is used in the RAN system, multiple NodeBs are connected to the RNC through the access equipment. 7.3.1.4 EtherIP This describes the EtherIP link. It is connected to the Ethernet, and the relay boards use the FE ports.

PPP This describes the Point-to-Point Protocol (PPP). The PPP is used at the data link layer. The PPP provides standard methods for encapsulating the multi-protocol datagrams on point-to-point links. These datagrams include IP, IPX, and Apple Talk. Figure 7-5 shows the hierarchy of the PPP.

Issue 01 (2008-06-25)


7-9



Figure 7-5 Hierarchy of the PPP

The PPP consists of the link control protocol (LCP), network control protocol (NCP), and extended protocols. They are described as follows: l

LCP: used to configure, test, or remove a data link.

l

NCP: used to configure parameters at the network layer for communications between the equipment.

l

Extended protocols, such as the multilink protocol (MP): The PPP combines multiple physical links into a logical link through the MP, thus providing a large bandwidth and enabling fast data transfer. Huawei RNC implements the MP by adding MLPPP data.

MP This describes the Multilink PPP (MP). With the wide application of the PPP, the MP emerges as an extended protocol of the PPP. The MP provides a large bandwidth to enable quick data transfer. In addition, the MP dynamically allocates the link resources to effectively save the valuable resources. The MP can flexibly arrange multiple independent physical links between point-to-point systems. It provides a virtual link for the whole system, and the bandwidth of the virtual link is the sum of bandwidths of the N (N ≥ 1) physical links. With the development of network technologies, bandwidth is no longer a bottleneck. Therefore, the extended protocols of the PPP are not required.

PPPoE This describes the PPPoE protocol. It is a standard that defines how multiple hosts are connected to a remote Access Concentration (AC) in a broadcasting-type network (for example Ethernet). When the PPPoE is used in the RAN system, multiple NodeBs are connected to the RNC through the access equipment. In this network topology, all hosts can independently initialize PPP protocol stacks, and perform charging and management for the subscribers on this network. To set up and maintain the pointto-point relations between hosts and the AC in a broadcasting-type network, each host should be able to set up a unique point-to-point session with the AC. 7-10


Issue 01 (2008-06-25)



The procedure for setting up a PPPoE session is as follows: 1.

When a host wants to start a PPPoE session, it searches for an AC in the network.

2.

If multiple ACs exist on the network, the host selects an AC based on the services provided by the AC or the settings predefined by the subscribers.

3.

After an AC is selected, the host starts to set up a PPPoE session with the AC and assigns a unique process ID.

4.

PPPoE session phase starts after the session is set up. During this phase, the two sides with point-to-point connection exchange the datagrams by using the PPP to complete a series of PPP processes, and then transfer the network layer datagrams over this point-to-point logical channel.

EtherIP This describes the EtherIP link. It is connected to the Ethernet, and the relay boards use the FE ports. When IP_RAN is selected as the transmission mode of the NodeB, the NodeB can be configured with the following four links: l

PPP

l

MP

l

PPPoE

l

EtherIP

PPP and MP links are connected to the dedicated line network, and the relay boards use the E1/ T1 ports. PPPoE and EtherIP links are connected to the Ethernet, and the relay boards use the FE ports.

7.3.2 IP This describes the Internet Protocol (IP). It provides a connectionless service between networks and defines the rules and details for data communication. It is used along with the Transmission Control Protocol (TCP) to provide guaranteed data transfer.

IPv4 and IPv6 The current and most popular network layer protocol of the TCP/IP is IPv4, which was launched in 1981. IPv6, which was launched in 1995, is gradually going to replace IPv4. Compared with IPv4, IPv6 has much more address space to meet more requirements for IP addresses.

Principles for IP Address Planning When using the TCP/IP protocol for communication, each communication entity needs an IP address. In the application of the RAN, comply with the following principles when planning the IP addresses: l

IP addresses and subnet masks must be valid. The network number is not all-zero and that the host number is not all-zero or all-one.

l

The IP addresses of classes A, B, and C are valid, but those of classes D and E are invalid.

l

Do not set the IP address to a loopback address of 127.X.X.X.

Issue 01 (2008-06-25)


7-11



IP Address Structure In an IP network, IP addresses should be assigned to hosts. If you connect a computer to the Internet, you need to apply for an IP address from the Internet Service Provider (ISP). The length of the IP address is 32 bits. The IP address consists of the following parts: l

Network number (net-id): The first bits are called class segments (class bits) that are used to identify the class of an IP address.

l

Host number (host-id): indicates different hosts in the same network.

IP Address Classification IP addresses are categorized into five classes, as shown in Figure 7-6. You can identify an IP address class by its first few bits. Figure 7-6 Five classes of IP addresses

The IP addresses of classes A, B, and C are most commonly used. IP addresses of class D are used for multicasting. IP addresses of class E are reserved. For details, refer to the RFC1166 Internet Numbers released by IETF.

IP Address Range Some IP addresses are reserved for special purposes. Table 7-3 describes the ranges of IP addresses.

7-12


Issue 01 (2008-06-25)



Table 7-3 Classification and range of IP addresses Net wor k Typ e

Address Range

A

0.0.0.0 to

1.0.0.0 to

127.255.255.255

126.0.0.0

B

C

D

128.0.0.0 to

128.0.0.0 to

191.255.255.255

191.254.0.0

192.0.0.0 to

192.0.0.0 to

223.255.255.255

223.255.254.0

224.0.0.0 to 239.255.255.255

Issue 01 (2008-06-25)

Available Range

None.

Description

l

An all-zero host number means that the IP address is the network address for network routing.

l

An all-one host number means that the IP address is used to broadcast messages to all the hosts on the network.

l

When the DHCP is used, the local host can take 0.0.0.0 as the temporary IP address but never as the valid destination address.

l

The IP address with network number of 0 represents the current network that can be referenced by other computers without knowing its network number.

l

All the IP addresses in the 127.X.X.X format are reserved for loopback testing. The packets sent to this address are not sent to lines. The packets are handled internally as input packets.

l


l


l


l


IP addresses of class D are used for multicasting.


7-13



Net wor k Typ e

Address Range

E

240.0.0.0 to

Available Range

None.

255.255.255.255

Description

Reserved. The IP address of 255.255.255.255 is used for broadcasting in the LAN.

7.3.3 SCTP This describes the Stream Control Transmission Protocol (SCTP). It is mainly used for transmitting reliable datagrams through an unreliable network.

Advantages of the SCTP Compared with the TCP Compared with the TCP, the SCTP has the following advantages: l

Supports the transmission of datagrams that are not delimitated by the upper layer.

l

Provides better real-time performance.

l

Provides higher security.

l

Avoids the blocking of line headers.

l

Supports the multi-homing function.

Provides the signaling transmission of higher requirements for real-time performance, security, and reliability.

SCTP Endpoint The SCTP endpoint is the logical transmitter or receiver of SCTP packets. The SCTP endpoint on a multi-homing host can be either a group of valid destination transport addresses for data transmission to the peer host, or a group of valid originating transport addresses for transmitting SCTP packets. All the transport addresses used by an SCTP endpoint must use the same port number but can use multiple IP addresses. The transport address used by an SCTP endpoint at a time must be unique. A transport address is defined by the network layer address, transport layer protocols, and port number. When the SCTP protocol works on the IP transport layer, the transport address is defined by the IP address and SCTP port number. Then, the SCTP protocol acts as the transport layer protocol.

SCTP Association SCTP association is the mapping between two SCTP endpoints. It involves two SCTP endpoints and protocol status data. The protocol status data includes verification tag and transport sequence number. 7-14


Issue 01 (2008-06-25)



SCTP association is uniquely identified by the transport address of the SCTP endpoint that uses the SCTP association. There is a maximum of one SCTP association between two SCTP endpoints.

SCTP Message Structure The SCTP message consists of the common header and the chunks. Figure 7-7 shows the SCTP message structure. Figure 7-7 SCTP Message Structure

Multiple chunks can be bundled and transmitted in one datagram, thus saving the bandwidth.

7.4 NodeB Treelink PVC The function of a NodeB treelink PVC is similar to that of the ATM switching. This describes how to add a treelink PVC to the NodeB, that is, to add an ATM switching route to the NodeB (over ATM), so as to switch the PVC from one physical bearer to another.

Networking Principles If a NodeB is connected to a lower-level NodeB, this parent NodeB must be configured with a treelink PVC for transferring ATM cells to the lower-level node. The red dashed line in Figure 7-8 represents the treelink PVC.

Issue 01 (2008-06-25)


7-15



Figure 7-8 Treelink PVC

The purpose of a treelink PVC is to switch the data of the lower-level NodeB to the upper-level one through a hub NodeB. The treelink PVCs configured on a hub NodeB should be able to switch all the data of the Iub interface to the upper-level node. Figure 7-9 Treelink PVC principles

Relations Between Iub PVCs of Lower-Level NodeB and Treelink PVCs The NCP, CCP, ALCAP, AAL2 PATH, IPoA, CES, and treelink PVC of the lower-level NodeB correspond to different PVCs. The method of adding a treelink PVC is the same as that of adding a PVC switching route. You need to add switching routes for all PVCs of the lower-level NodeB. To add a PVC switching route, you can select either of the following methods: l

Through VCI switching: A treelink PVC corresponds to a PVC switching route. You need to specify the source (VPI, VCI) and the destination (VPI, VCI).

l

Through VPI switching: A treelink PVC corresponds to multiple PVC switching routes. You need to specify only the source VPI and the destination VPI. The VCI is unchanged.

The amount of treelink PVCs depends on the amount of physical bearers, switching methods (VP or VC), and the amount of the upper-level applications.

7-16

l

For VC switching, the amount of treelink PVCs depends on that of the PVCs of the upperlevel node.

l

For VP switching, the amount of treelink PVCs depends on that of the PVCs of the upperlevel node and the VPI values of all PVCs. Assume that all the PVCs on the Iub interface Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)



of a lower-level NodeB are carried on one ATM physical bearer, that is, the slot number, link type, link (group) number, and VPI of each PVC are the same as those of other PVCs. In this case, only one treelink PVC needs to be configured. NOTE

By adjusting the interface board of a lower-level NodeB or hub NodeB, you can meet the requirements for the VPIs and VCIs of treelink PVCs.

Comparison Between VP Switching and VC Switching l

The planning and configuration based on VP switching is easier.

l

The configuration based on VC switching is more flexible.

7.5 NodeBs in Direct/Cascading Connections This defines the NodeBs in direct and cascading connections. In addition, it describes the configuration differences between these two connections. 7.5.1 Definitions of NodeBs in Direct/Cascading Connections The physical connections between an RNC and a NodeB are of two types: direct and cascading connections. 7.5.2 Configuration Differences Between NodeBs in Direct/Cascading Connections NodeBy in cascading connection is connected to NodeBx through E1, in which case NodeBx works as the transmission equipment between NodeBy and the RNC. In this sense, it is similar to configure NodeBs in direct or cascading connection. This, however, describes the configuration differences between direct and cascading connections.

7.5.1 Definitions of NodeBs in Direct/Cascading Connections The physical connections between an RNC and a NodeB are of two types: direct and cascading connections.

Direct Connection In direct connection, the NodeB is connected to the RNC directly or through transport equipment. Figure 7-10 shows an example of direct connection between NodeBx and the RNC.

Cascading Connection In cascading mode, the NodeB is connected to the RNC through another NodeB. Figure 7-10shows an example of cascading connection between NodeBy and the RNC. In this case, NodeBx is called the NodeB that provides cascading connection for NodeBy.

Issue 01 (2008-06-25)


7-17



Figure 7-10 Direct and cascading connections

NOTE

Multi-level cascading is allowed. In multi-level cascading mode, NodeBy is connected to the RNC through multiple NodeBs that provide cascading connections. Each cascaded NodeB occupies a portion of the bandwidth between the RNC and the upper-level NodeB (that is, the NodeB that provides cascading connection). The bandwidth is also required by the upper-level NodeB. Therefore, multi-level cascading is not recommended.

7.5.2 Configuration Differences Between NodeBs in Direct/ Cascading Connections NodeBy in cascading connection is connected to NodeBx through E1, in which case NodeBx works as the transmission equipment between NodeBy and the RNC. In this sense, it is similar to configure NodeBs in direct or cascading connection. This, however, describes the configuration differences between direct and cascading connections. NodeBx provides the cascading path for NodeBy in either of the following ways: l

NodeBx provides the E1/T1 timeslot cross function.

l

NodeBx works as the ATM switching equipment, providing the VP/VC switching function, which is also called the treelink PVC function.

Table 7-4 lists the configuration differences between NodeBs in direct/cascading connections. Table 7-4 Configuration differences between NodeBs in direct/cascading connections

7-18

NodeBx Cascading Path

Prerequisites for NodeBy Configuration

Timeslot cross. The NodeBx works as the equipment that provides the timeslot cross function.

l

NodeBx is connected to the RNC through E1/T1, including E1 over SDH.

l

By default, NodeBx must be connected to the RNC over fractional ATM. Besides, there are redundant timeslots between NodeBx and the RNC.


Configuration differences between NodeBy and the NodeB in direct connection l

NodeBy must be connected to NodeBx over fractional ATM and occupies only the redundant timeslots of NodeBx.

l

You need to configure the timeslot cross connection on NodeBx.

Issue 01 (2008-06-25)



NodeBx Cascading Path

Prerequisites for NodeBy Configuration

ATM switching

Redundant portions of the bandwidth are available between NodeBx and the RNC.

Configuration differences between NodeBy and the NodeB in direct connection You need to add a treelink PVC to NodeBx.

As the ATM switching equipment, NodeBx is connected to the RNC by E1/T1 or SDH with the application as UNI, IMA, or STM-1. NodeBy may also be connected to NodeBx by E1/T1 with the applications as UNI or IMA. This type of cascading path for the NodeB is recommended.

Issue 01 (2008-06-25)


7-19

NodeB Initial Configuration Guide-(V100R010_01)

Recommend Documents