nodeb initial configuration guide-(v100r010_01)

NodeB

V100R010

NodeB Initial Configuration Guide

Issue 01

Date 2008-06-25

Part Number

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

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

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People'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 writtenconsent 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. NoticeThe information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but the statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

http://www.huawei.com

mailto:[email protected]

Contents

About This Document.....................................................................................................................1

1 Introduction to NodeB Initial Configuration.......................................................................1-11.1 Definition of NodeB Initial Configuration......................................................................................................1-21.2 NodeB Initial Configuration Scenarios...........................................................................................................1-21.3 NodeB Initial Configuration Tool...................................................................................................................1-21.4 NodeB Initial Configuration Methods.............................................................................................................1-2

2 Data Planning and Negotiation of NodeB Initial Configuration.....................................2-12.1 NodeB Basic Data...........................................................................................................................................2-22.2 NodeB Equipment Layer Data........................................................................................................................2-42.3 NodeB Transport Layer Data........................................................................................................................2-322.4 NodeB Radio Layer Data..............................................................................................................................2-72

3 NodeB Initial Configuration....................................................................................................3-1

4 Adding a NodeB Through the Template File (Initial)........................................................4-14.1 NodeB Template File......................................................................................................................................4-24.2 Creating a Logical NodeB (Initial)..................................................................................................................4-24.3 Creating a Physical NodeB by Importing the Template File (Initial).............................................................4-64.4 Reconfiguring NodeB Data (Initial)................................................................................................................4-84.5 Refreshing the Transport Layer Data of the NodeB (Initial)..........................................................................4-9

5 Adding a NodeB Through the Configuration File (Initial)...............................................5-15.1 NodeB Configuration File...............................................................................................................................5-25.2 Creating a Logical NodeB (Initial)..................................................................................................................5-25.3 Creating a Physical NodeB by Importing a Configuration File (Initial).........................................................5-65.4 Reconfiguring NodeB Data (Initial)................................................................................................................5-85.5 Refreshing the Transport Layer Data of the NodeB (Initial)..........................................................................5-9

6 Manually Adding a NodeB (Initial).......................................................................................6-16.1 Creating a Logical NodeB (Initial)..................................................................................................................6-36.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial).......................................................6-7

6.2.1 Manually Creating a Physical NodeB (Initial).......................................................................................6-96.2.2 Adding the Boards in the Baseband Subrack (Initial)..........................................................................6-166.2.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Macro NodeB)........6-206.2.4 Adding an RRU (Initial, Macro NodeB)..............................................................................................6-24

NodeBNodeB Initial Configuration Guide Contents

Issue 01 (2008-06-25) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

6.2.5 Adding RF Modules (Initial)................................................................................................................6-326.2.6 Adding an NGRU (Initial)....................................................................................................................6-336.2.7 Adding an NCMU (Initial, BTS3812AE)............................................................................................6-346.2.8 Adding an NPMU (Initial, Macro NodeB)...........................................................................................6-366.2.9 Adding NPSUs (Initial, BTS3812AE/BTS3812A)..............................................................................6-386.2.10 Adding Batteries (Initial, BTS3812AE/BTS3812A).........................................................................6-396.2.11 Adding an ALD (Initial).....................................................................................................................6-40

6.3 Adding Equipment Layer Data of the BTS3812E (Initial)...........................................................................6-456.3.1 Manually Creating a Physical NodeB (Initial).....................................................................................6-486.3.2 Adding the Boards in the Baseband Subrack (Initial)..........................................................................6-546.3.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Macro NodeB)........6-596.3.4 Adding an RRU (Initial, Macro NodeB)..............................................................................................6-636.3.5 Adding RF Modules (Initial)................................................................................................................6-716.3.6 Adding an NGRU (Initial)....................................................................................................................6-726.3.7 Adding an NEMU (Initial, BTS3812E)...............................................................................................6-736.3.8 Adding an NPMU (Initial, Macro NodeB)...........................................................................................6-756.3.9 Adding NPSUs (Initial, BTS3812E)....................................................................................................6-776.3.10 Adding Batteries (Initial, BTS3812E)................................................................................................6-796.3.11 Adding an ALD (Initial).....................................................................................................................6-80

6.4 Adding Equipment Layer Data of the DBS3800 (Initial).............................................................................6-856.4.1 Manually Creating a Physical NodeB (Initial).....................................................................................6-876.4.2 Adding a BBU (Initial).........................................................................................................................6-936.4.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, Distributed NodeB).......................................................................................................................................................................6-986.4.4 Adding an RRU (Initial, Distributed NodeB)....................................................................................6-1026.4.5 Adding an NEMU (Initial, Distributed NodeB).................................................................................6-1106.4.6 Adding an NPMU (Initial, Distributed NodeB).................................................................................6-1116.4.7 Adding an ALD (Initial).....................................................................................................................6-112

6.5 Manually Adding the Transport Layer Data of the NodeB (over ATM)....................................................6-1176.5.1 Adding Links at the Physical Layer (Initial)......................................................................................6-1186.5.2 Adding Transmission Resource Group (Initial, over ATM)..............................................................6-1446.5.3 Adding SAAL Links (Initial).............................................................................................................6-1466.5.4 Adding an NBAP (Initial)..................................................................................................................6-1506.5.5 Adding an ALCAP (Initial)................................................................................................................6-1536.5.6 Adding AAL2 Path Data (Initial).......................................................................................................6-1556.5.7 Adding an OMCH of the NodeB (Initial, over ATM).......................................................................6-1606.5.8 Adding a Treelink PVC (Initial).........................................................................................................6-164

6.6 Manually Adding Transport Layer Data of the NodeB (over IP)...............................................................6-1686.6.1 Adding a Link at the Data Link Layer (Initial)..................................................................................6-1696.6.2 Adding an IP Route (Initial)...............................................................................................................6-1886.6.3 Adding SCTP Links (Initial)..............................................................................................................6-1916.6.4 Adding an IPCP (Initial)....................................................................................................................6-1956.6.5 Adding Transmission Resource Group (Initial, over IP)...................................................................6-197

ContentsNodeB


ii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

6.6.6 Adding IP Path Data (Initial).............................................................................................................6-2006.6.7 Adding an OMCH of the NodeB (Initial, over IP).............................................................................6-2056.6.8 Adding A Bound Destination Network Segment to the Transmission Resource Group (Initial, IP).....................................................................................................................................................................6-2096.6.9 Adding IP Clock Links (Initial).........................................................................................................6-2116.6.10 Modifying IP QoS Data (Initial)......................................................................................................6-215

6.7 Refreshing the Transport Layer Data of the NodeB (Initial)......................................................................6-2166.8 Adding Radio Layer Data...........................................................................................................................6-220

6.8.1 Adding Sites.......................................................................................................................................6-2216.8.2 Adding Sectors and Cells (Macro NodeB).........................................................................................6-2226.8.3 Adding Sectors and Cells (Distributed NodeB).................................................................................6-236

7 Related Concepts of NodeB Initial Configuration..............................................................7-17.1 Cell Related Concepts.....................................................................................................................................7-2

7.1.1 Sector, Carrier, and Cell.........................................................................................................................7-27.1.2 Physical Resources of Cells...................................................................................................................7-37.1.3 Local Cell and Logical Cell...................................................................................................................7-6

7.2 ATM Protocol-Related Terms.........................................................................................................................7-67.2.1 ATM User Plane, ATM Control Plane, and ATM Management Plane.................................................7-77.2.2 ATM Physical Layer, ATM Layer, and AAL........................................................................................7-7

7.3 IP Protocol-Related Terms..............................................................................................................................7-87.3.1 Data Link Layer Protocols.....................................................................................................................7-97.3.2 IP..........................................................................................................................................................7-117.3.3 SCTP....................................................................................................................................................7-14

7.4 NodeB Treelink PVC....................................................................................................................................7-157.5 NodeBs in Direct/Cascading Connections....................................................................................................7-17

7.5.1 Definitions of NodeBs in Direct/Cascading Connections....................................................................7-177.5.2 Configuration Differences Between NodeBs in Direct/Cascading Connections.................................7-18

NodeBNodeB Initial Configuration Guide Contents


iii

Figures

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

NodeBNodeB Initial Configuration Guide Figures


v

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

FiguresNodeB


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

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

NodeBNodeB Initial Configuration Guide Figures


vii

Tables

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

NodeBNodeB Initial Configuration Guide Tables


ix

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

TablesNodeB


x Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

Table 6-26 Negotiation and planned data of the RRU.....................................................................................6-106Table 6-27 Negotiation and planned data of the RHUB..................................................................................6-108Table 6-28 Negotiation and planned data of the ALD.....................................................................................6-113Table 6-29 Negotiation and planned data of the IMA group and IMA links...................................................6-120Table 6-30 Description of the configuration pane............................................................................................6-125Table 6-31 Negotiation and planned data of the UNI links..............................................................................6-126Table 6-32 Description of the configuration pane............................................................................................6-130Table 6-33 Negotiation and planned data of the fractional ATM links............................................................6-131Table 6-34 Negotiation and planned data of the SDT CES..............................................................................6-134Table 6-35 Negotiation and planned data of the UDT CES.............................................................................6-137Table 6-36 Description of the configuration pane............................................................................................6-140Table 6-37 Description of the configuration pane............................................................................................6-141Table 6-38 Negotiation and planned data of the timeslot cross links...............................................................6-142Table 6-39 Description of the configuration pane............................................................................................6-143Table 6-40 Negotiation and planned data of the transmission resource group (over ATM)............................6-144Table 6-41 Description of the configuration pane............................................................................................6-146Table 6-42 Negotiation and planned data of the SAAL links..........................................................................6-147Table 6-43 Description of the configuration pane............................................................................................6-150Table 6-44 Negotiation and planned data of the NBAP...................................................................................6-151Table 6-45 Description of the configuration pane............................................................................................6-152Table 6-46 Negotiation and planned data of the ALCAP................................................................................6-153Table 6-47 Description of the configuration pane............................................................................................6-155Table 6-48 Negotiation and planned data of the AAL2 PATH........................................................................6-156Table 6-49 Description of the configuration pane............................................................................................6-159Table 6-50 Negotiation and planned data of the OMCH (ATM).....................................................................6-161Table 6-51 Description of the configuration pane............................................................................................6-163Table 6-52 Negotiation and planned data of the treelink PVC.........................................................................6-164Table 6-53 Description of the configuration pane............................................................................................6-168Table 6-54 Negotiation and planned data of the ppp links...............................................................................6-170Table 6-55 Negotiation and planned data of the MLPPP group and MLPPP links.........................................6-175Table 6-56 Description of the configuration pane............................................................................................6-179Table 6-57 Negotiation and planned data of the PPPoE links..........................................................................6-180Table 6-58 Negotiation and planned data of the DEVIP..................................................................................6-184Table 6-59 Description of the configuration pane............................................................................................6-185Table 6-60 Negotiation and planned data of the timeslot cross links...............................................................6-187Table 6-61 Description of the configuration pane............................................................................................6-188Table 6-62 Negotiation and planned data of the IP route.................................................................................6-189Table 6-63 Description of the configuration pane............................................................................................6-190Table 6-64 Negotiation and planned data of the SCTP links...........................................................................6-191Table 6-65 Description of the configuration pane............................................................................................6-193Table 6-66 Description of the configuration pane............................................................................................6-194Table 6-67 Negotiation and planned data of the IPCP.....................................................................................6-195

NodeBNodeB Initial Configuration Guide Tables


xi

Table 6-68 Description of the configuration pane............................................................................................6-197Table 6-69 Negotiation and planned data of the transmission resource group (over IP).................................6-198Table 6-70 Description of the configuration pane............................................................................................6-200Table 6-71 Negotiation and planned data of the IP PATH...............................................................................6-201Table 6-72 Description of the configuration pane............................................................................................6-203Table 6-73 Description of the configuration pane............................................................................................6-204Table 6-74 Negotiation and planned data of the OMCH (IP)..........................................................................6-206Table 6-75 Description of the configuration pane............................................................................................6-207Table 6-76 Negotiation and planned data of the transmission resource group whose destination IP network segmentis bound.............................................................................................................................................................6-209Table 6-77 Description of the configuration pane............................................................................................6-211Table 6-78 Negotiation and planned data of the IP clock links........................................................................6-212Table 6-79 Description of the configuration pane............................................................................................6-213Table 6-80 Description of the configuration pane............................................................................................6-214Table 6-81 Negotiation and planned data of the IPQoS...................................................................................6-215Table 6-82 Description of the configuration pane............................................................................................6-219Table 6-83 Negotiation and planned data of the NodeB..................................................................................6-221Table 6-84 Negotiation and planned data of the sector....................................................................................6-224Table 6-85 Negotiation and planned data of the cell........................................................................................6-226Table 6-86 Description of the configuration pane............................................................................................6-232Table 6-87 Description of the configuration pane............................................................................................6-233Table 6-88 Description of the configuration pane............................................................................................6-235Table 6-89 Description of the configuration pane............................................................................................6-236Table 6-90 Negotiation and planned data of the sector....................................................................................6-237Table 6-91 Negotiation and planned data of the cell........................................................................................6-239Table 6-92 Description of the configuration pane............................................................................................6-245Table 6-93 Description of the configuration pane............................................................................................6-246Table 7-1 Functions of the ATM user plane, ATM control plane, and ATM management plane.......................7-7Table 7-2 Layers and functions of the reference model of the ATM protocol.....................................................7-7Table 7-3 Classification and range of IP addresses............................................................................................7-13Table 7-4 Configuration differences between NodeBs in direct/cascading connections...................................7-18

TablesNodeB


xii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

About This Document

This describes how to use the CME to configure a new site, that is, the NodeB, during networkconstruction or network optimization.

PurposeNOTE

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 filefor each NodeB and load the file to the NodeB in commissioning so as to ensure that the NodeBworks as designed.

This document serves as a guideline on how to configure the initial data for the NodeB. Thecontent involves two parts. That is, how to prepare data for NodeB initial configuration and howto add data to the NodeB through manual operations, template files, and configuration files. Inaddition, this document also provides the reference information for the configuration.

VersionsProduct Names Versions

WRAN CME V100R005

NodeB VersionsProduct Names Versions

BTS3812A V100R010

BTS3812AE V100R010

BTS3812E V100R010

DBS3800 V100R010

iDBS3800 V100R010

NodeBNodeB Initial Configuration Guide About This Document


1

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

2 Data Planning and Negotiation of NodeB Initial Configuration

This describes the preparations you must make before configuring initial data to the NodeB. Thepreparations must be based on the network planning, connections with other devices, bandwidthresources, 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 typeof 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 isapplicable 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 atemplate 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 initialconfiguration.

Conventions

1. Symbol Conventions

The following symbols may be found in this document. They are defined as follows

About This DocumentNodeB


2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

Symbol Description

DANGERIndicates a hazard with a high level of risk that, if not avoided,will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk which, ifnot avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if not avoided,could cause equipment damage, data loss, and performancedegradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save yourtime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

2. General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files,directories,folders,and users are in boldface. Forexample,log in as user root .

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

3. Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{x | y | ...} Alternative items are grouped in braces and separated by verticalbars.One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets andseparated by vertical bars.One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by verticalbars.A minimum of one or a maximum of all can be selected.

NodeBNodeB Initial Configuration Guide About This Document


3


[ x | y | ... ] * Alternative items are grouped in braces and separated by verticalbars.A minimum of zero or a maximum of all can be selected.

4. GUI Conventions


Boldface Buttons,menus,parameters,tabs,window,and dialog titles are inboldface. For example,click OK.

> Multi-level menus are in boldface and separated by the ">" signs.For example,choose File > Create > Folder .

5. Keyboard Operation


Key Press the key.For example,press Enter and press Tab.

Key1+Key2 Press the keys concurrently.For example,pressing Ctrl+Alt+Ameans the three keys should be pressed concurrently.

Key1,Key2 Press the keys in turn.For example,pressing Alt,A means the twokeys should be pressed in turn.

6. Mouse Operation

Action Description

Click Select and release the primary mouse button without moving thepointer.

Double-click Press the primary mouse button twice continuously and quicklywithout moving the pointer.

Drag Press and hold the primary mouse button and move the pointerto a certain position.

About This DocumentNodeB


4 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

1 Introduction to NodeB Initial Configuration

About This Chapter

This provides the definition and describes the scenarios, tools, and methods of NodeB initialconfiguration.

1.1 Definition of NodeB Initial ConfigurationNodeB initial configuration is the process of preparing and configuring the data after the NodeBhardware components are installed. The configuration is based on the NodeB hardwarecomponents, 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 ScenariosThis describes the scenarios of the NodeB initial configuration.

1.3 NodeB Initial Configuration ToolWRAN CME, a tool for NodeB initial configuration, provides an integrated solution to RANdata configuration. In addition, this tool can be used for initial configuration and datareconfiguration for the NodeB and the RNC.

1.4 NodeB Initial Configuration MethodsThis describes three methods of the NodeB initial configuration. You can perform the NodeBinitial configuration through any of the following methods: Adding a NodeB through a templatefile, adding a NodeB through a configuration file, and manually adding a NodeB. Select anappropriate configuration method depending on the scenario.

NodeBNodeB Initial Configuration Guide 1 Introduction to NodeB Initial Configuration


1-1

1.1 Definition of NodeB Initial ConfigurationNodeB initial configuration is the process of preparing and configuring the data after the NodeBhardware components are installed. The configuration is based on the NodeB hardwarecomponents, 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 ensuresnormal data exchange between the NodeB and the RNC.

1.2 NodeB Initial Configuration ScenariosThis 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 ofexisting NodeBs. For details about data reconfiguration, refer to RAN Reconfiguration Guide (CME-Based).

1.3 NodeB Initial Configuration ToolWRAN CME, a tool for NodeB initial configuration, provides an integrated solution to RANdata configuration. In addition, this tool can be used for initial configuration and datareconfiguration for the NodeB and the RNC.

The GUI-based CME provides the operating platform for RAN data configuration. For detailson how to use the WRAN CME, refer to the CME User Guide.

1.4 NodeB Initial Configuration MethodsThis describes three methods of the NodeB initial configuration. You can perform the NodeBinitial configuration through any of the following methods: Adding a NodeB through a templatefile, adding a NodeB through a configuration file, and manually adding a NodeB. Select anappropriate configuration method depending on the scenario.

Table 1-1 lists the methods and scenarios of the NodeB initial configuration.

1 Introduction to NodeB Initial ConfigurationNodeB


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

Issue 01 (2008-06-25)

Table 1-1 DBS3800 initial configuration methods and scenarios

Method Scenario

4 Adding a NodeBThrough theTemplate File(Initial)

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

5 Adding a NodeBThrough theConfiguration File(Initial)

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

6 Manually Addinga NodeB (Initial)

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

NodeBNodeB Initial Configuration Guide 1 Introduction to NodeB Initial Configuration


1-3

2 Data Planning and Negotiation of NodeBInitial Configuration

About This Chapter

This describes the preparations you must make before configuring initial data to the NodeB. Thepreparations must be based on the network planning, connections with other devices, bandwidthresources, and the NodeB hardware resources.

2.1 NodeB Basic DataThis lists the basic data for configuring logical NodeBs.

2.2 NodeB Equipment Layer DataThis describes the data to be prepared for configuring the NodeB equipment layer.

2.3 NodeB Transport Layer DataThis describes the data to be prepared for configuring the NodeB transport layer in the ATMand the IP mode.

2.4 NodeB Radio Layer DataThis describes the data to be prepared for configuring the NodeB radio layer.

NodeBNodeB Initial Configuration Guide

2 Data Planning and Negotiation of NodeB InitialConfiguration


2-1

2.1 NodeB Basic DataThis lists the basic data for configuring logical NodeBs.

Table 2-1 Negotiation and planned data of the NodeB

InputData

FieldName

Description Example

Source

NodeB ID NodeB_Id The NodeB ID is automaticallyallocated. You can define the logicalNodeB before configuring it as aphysical NodeB.

1

NetworkplanningName of

the NodeBNodeB_Name

This parameter indicates the name of theNodeB. You are recommended to namethe NodeB according to its geographicallocation.

NodeB_1

Bearer type IubBearerType

Identify the transmission type of the Iubinterface for the RNC. The type mustmatch the type of the interface board atthe RNC. Optional parameters:l ATM_TRANS

l IP_TRANS

l ATMANDIP_TRANS

ATM_TRANS

Negotiation withthedestination

Sharingsupport

SharingSupport

Whether to share NodeB informationOptional parameters:l SHARED: indicates that all network

operators can browse the informationof this logical NodeB and that of thecorresponding physical NodeB.

l NON_SHARED: indicates that onlythe network operator specified by theCnOpIndex parameter can browsethe information of this logical NodeBand the that of the correspondingphysical NodeB

NON_SHARED

Telecomoperatorindex

CnOpIndex This parameter is valid only when theSharingSupport parameter is set toNON_SHARED.Value range: 0 through 3

0

Resourcemanagement mode

RscMngMode

Defines the resource management modewhen the bandwidth is allocatedOptional parameters:l SHARE

l EXCLUSIVE

SHARE




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

ATMAddress

NSAP The NodeB relevant ATM address inhexadecimal format. This parameter isinvalid when IubBearerType is set toIP_TRANS.You need to set the first byte of the ATMaddress to H'45 (indicating an E.164address), H'39 (indicating a DCCaddress) or H'47 (indicating an ICDaddress).If the first byte is H'45, the followingseven and a half bytes (that is, 15 digits)must be a BCD code. If the followingpart, called DSP, are all 0s, this addressis called E.164e. If the DSP are not all0s, this address is called E.164A. TheATM addresses are allocated in theATM network and cannot be repeated.Value range: 42 bytes (including theprefix H')

H'3901010101010101010101010101010101010101

Hybridtransportflag

IPTransApartInd

Identifies whether hybrid transport issupported over the Iub interface. Thisparameter is valid only whenIubBearerType is set to IP_TRANS orATMANDIP_TRANS. Optionalparameters:l SUPPORT

l NOT_SUPPORT

-

Transmission delay onthe Iubinterface

TransDelay Initial round-trip transmission delay onthe Iub interface in ATM circuittransport or IP dedicated transportValue range: 0 through 65535

10

Transmission delay onthe Iubinterface inhybrid IPtransport

IPApartTransDelay

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

-

Satellitetransmission indication

SatelliteInd Identifies the satellite transmission onthe Iub interface. Optional parameters:l TRUE

l FALSE

FALSE




2-3

InputData

FieldName

Description Example

Source

NodeBtype

NodeBType

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

l PICO_TYPE1

l PICO_TYPE2

NORMAL

ProtocolVersion

ProtocolVer

Protocol version of the NodeB.Optional parameters:l R99

l R4

l R5

l R6

R6

2.2 NodeB Equipment Layer DataThis 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

InputData

Field Name Description Example Source

Workingmode ofE1/T1links

E1T1WorkMode

The working mode of E1/T1 linksdepends on the state of DIPswitches on the BBU or NUTI andthe configuration file.

E1


Clocksource

ClockSource This parameter is valid only whenClockWorkMode is set toMANUAL. Optional parameters:l GPSCARD (GPS card clock

source)l BITS (BITS clock source): The

outdoor BBU (HBBUC) cannotuse this clock source.

l LINE (clock source extractedfrom the Iub interface line)

l IP (IP clock source)

LINE




Issue 01 (2008-06-25)

InputData


Workingmode ofthe clock

ClockWorkMode

Working mode of the system clockOptional parameters:l MANUAL (manual mode): In

this mode, the user specifies theclock source, and automaticallyswitching the system clock toother clock sources is notallowed. Even if the specifiedclock source is faulty, suchswitching is not allowed.

l FREE (free-run mode): Thefree-run mode is the workingmode for the clock source at aninitial phase.

MANUAL

Networkplanning

Workingmode ofthe IPclock

IPClockMode This parameter is valid only whenClockSource is set to IP. Optionalparameters:l AUTO (default value)

l MANUAL (This parameter isconfigured when the IP clock isalready configured.)

-

GPSfeederdelay

GPSCableDelay Delay of the GPS feederValue range: 0 through 1000

0 Internalplanning

SNTPswitch

SNTPSwitch Synchronization switch Optionalparameters:l ON (SNTP client requires time

synchronization)l OFF (SNTP client does not

require time synchronization)

ON Networkplanning




2-5

InputData


IP addressof theSNTPserver

SNTPServerIP The SNTP server is used tosynchronize the time of multipleSNTP clients, which is importantfor centralized maintenance,especially for alarm management.For example, when an E1 link isdisconnected, the NodeB and theRNC report the alarm at the sametime based on SNTP. This helpsfault locating.The SNTP server of the NodeB canbe either the M2000 or the RNC.l The SNTP server of the NodeB

is the RNC (recommended): setSNTPServerIP to the BAMinternal IP address.

l The SNTP server of the NodeBis the M2000: setSNTPServerIP to the M2000host external IP address.

10.11.1.1 Negotiation withthedestination

Synchronizationperiod

SyncPeriod The period in which nodes aresynchronized.Value range: 1 through 525600

10

Networkplanning

Demodulation mode

DemMode Demodulation mode of the NodeBOptional parameters:l DEM_2_CHAN (two-way

demodulation mode)l DEM_4_CHAN (four-way

demodulation mode)l DEM_ECON_4_CHAN (four-

way economical demodulationmode)

DEM_2_CHAN

High BERthresholdsof E1/T1

HighThreshold Optional parameters:l 1E-3

l 1E-4

l 1E-5

l 1E-6

1E-5

Smoothpowerswitch

SMTHPWRSwitch

Optional parameters:l OPEN

l CLOSE

CLOSE




Issue 01 (2008-06-25)

InputData


Lower andupperlimits oftimersetting

LowerLimit Disabling the lower limit of thetime range for the transmitterValue range: 0 through 255

0

UpperLimit Disabling the upper limit of thetime range for the transmitterValue range: 0 through 255

0

NodeBresourcedistribution mode

ResAllocateRule

Optional parameters:l PERFFIRST (handover

performance priority mode)l CAPAFIRST (capacity priority

mode)

PERFFIRST

NodeB IPaddress

LocalIP IP address of the NodeB for localmaintenance

17.21.2.15

Subnetmask

LocalIPMask Subnet mask of the NodeB IPaddress for local maintenance

255.255.0.0

NMPTbackupmode

NMPTBackupMode

This parameter is available onlyfor the macro NodeB.

ENABLE Internalplanning

STM-1framemode

NAOIFrameMode (macroNodeB)

Frame structure of the optical portchip Optional parameters:l FRAMEMODE_SONET (in

SONET mode)l FRAMEMODE_SDH (in SDH

mode)

-


STM1FrameMode (distributedNodeB)

FRAMEMODE_SDH

Management unit

Au This parameter is valid only for thechannelized optical interface.Optional parameters:l AU3

l AU4

AU3

Bypassunit

Tu This parameter is valid only for thechannelized optical interface.Optional parameters:l TU11 (the E1/T1 mode is T1)

l TU12 (the E1/T1 mode is E1)

TU12




2-7

InputData


Power typeof themacroNodeB

PowerType Configuring the power type for theNodeB. This parameter isavailable only for the macroNodeB. Optional parameters:l -48 V DC

l 24 V DC

l 220 V AC

-48 V DC

Internalplanning

Reportswitch forcall historyrecord

CHRSwitch When the NodeB CHR reportswitch is on, the NodeB uploadsthe CHR log to the FTP server thatis at the NodeB side.

OFF

Iubinterfaceboardgroupbackupmode

IUBGroup1 Group backup mode of the Iubinterface board, namely the NDTIor the NUTI, in slots 12 and 13Optional parameters:l REDUNDANCY (active and

standby backup): The boardmust be the NUTI. No sub-board can be added. Only thebaseboard held in slot 12 can beused. The attributes of the boardheld in slot 13 remainunchanged.

l SHARING (load sharing): TheNDTI and NUTI can be insertedin either slot 12 or 13. Both theboard of the baseband subrackand the sub-board can be used.

SHARING

IUBGroup2 Group backup mode of the Iubinterface board, namely the NUTI,in slots 14 and 15 Optionalparameters:l REDUNDANCY (active and

standby backup): No sub-boardcan be added. Only thebaseboard held in slot 14 can beused. The attributes of the boardheld in slot 15 remainunchanged.

l SHARING (load sharing): Onlythe sub-board added to theNUTI held in slots 14 and 15can be used.

SHARING




Issue 01 (2008-06-25)

Macro NodeB Equipment Layer Data

Table 2-3 Negotiation and planned data of the BBU

InputData

FieldName

Description Example Source

NMPT NMPT l When the NMPT needs a backup,configure two NMPTs. The activeNMPT is configured in slot 10, andthe standby NMPT is configured inslot 11.

l When the NMPT does not need abackup, configure one NMPT. TheNMPT is configured in slot 10.

If backup isnotrequired,configurethe NMPTin slot 10.

Internalplanning

NodeBmonitoringunit

NMON The NMON controls the RETcontroller and provides Boolean valuemonitoring interfaces such as the 32-line Boolean input interface and 7-lineBoolean output interface.

TheNMON isconfiguredin slot 16.

Baseboard - According to the capacity of the HBBI/NBBI, EBBI/EBOI, HULP/EULP, andHDLP/NDLP and the expected NodeBconfiguration, select applicablebaseband boards.

The HBOIand theEBOI areconfiguredin slots 0and 1.

Transportboards

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

The NUTIisconfiguredin slot 13.

Bearermode

BearMode

This parameter is valid only when thetransport board is the NUTI. Optionalparameters:l ATM

l IPV4

IPV4




2-9

InputData

FieldName


IP clockswitch

IPClockSwitch

You need to set the IP clock switch onthe NUTI baseboard to ENABLE if youplan to use the FE ports on the NUTIboard to receive the IP clock signals.(This parameter is valid only whenBearMode is set to IPV4.) Optionalparameters:l ENABLE

l DISABLE

ENABLE

Lineimpedance

LineImpedance

Line impedance of the E1 line Optionalparameters:l 75 (E1 working mode)

l 100 (T1 working mode)

l 120 (E1 working mode)

75

HSDPAswitch

HsdpaSwitch

This parameter is available when theNUTI is configured or theunchannelized optical sub-board isconfigured on the NUTI. Optionalparameters:l SIMPLE_FLOW_CTRL: Based on

the configured Iub bandwidth andthe bandwidth occupied by R99users, traffic is allocated to HSDPAusers when the physical bandwidthrestriction is taken into account.

l AUTO_ADJUST_FLOW_CTRL:According to the flow control ofSIMPLE_FLOW_CTRL, traffic isallocated to HSDPA users when thedelay and packet loss on the Iubinterface are taken into account. TheRNC uses the R6 switch to performthis function. It is recommended thatthe RNC be used in compliance withthe R6 protocol.

l NO_FLOW_CTRL: The NodeBdoes not allocate bandwidthaccording to the configuration ordelay on the Iub interface. The RNCallocates the bandwidth according tothe bandwidth on the Uu interfacereported by the NodeB. To performthis function, the reverse flowcontrol switch must be enabled bythe RNC.

AUTO_ADJUST_FLOW_CTRL




Issue 01 (2008-06-25)

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

InputData

FieldName


ID of theULbasebandresourcegroup

ULResourceGroupId

l A board that is not added to theUL baseband resource group, thatis, the HBBI/NBBI, EBBI/EBOI,and HULP/EULP, cannot processbaseband services.

l An uplink baseband resourcegroup can process a maximum ofsix cells.

l Insufficient uplink basebandresources may result in a cellsetup failure.

1

Internalplanning

ID of theDLbasebandresourcegroup

DLResourceGroupId

l A board that is not added to theDL baseband resource group, thatis, the HBBI/NBBI, EBBI/EBOI,and HDLP/NDLP, cannot processbaseband services.

l The downlink processing unitswithin the downlink resourcegroup should belong to an uplinkresource group.

l The amount of local cellssupported by the resource groupis determined by the amount andthe specifications of the boardswithin the resource group.

0

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

InputData


Chaintype

Chain Type RRU topology structure Optionalparameters:l CHAIN (chain topology)

l RING (ring topology)

CHAIN

Internalplanning

Chain/Ring headsubracknumber

Head SubrackNo.

Number of the subrack that holdsthe head BBU in the chain or ringValue range: 0 through 1

0




2-11

InputData


Chain/Ring headboardnumber

Head Board No. Number of the slot that holds thehead BBU in the chain or ringOptional parameters:0

0

Head portnumber

Head Port No. Number of the port on the headBBU that is connected to the RRUin the chain or ringValue range: 0 through 2

0

Endsubracknumber

End SubrackNo

Number of the subrack that holdsthe end BBU in the ring. Thisparameter is applicable only to thering topology.Value range: 0 through 1

-

End boardnumber

End Board No Number of the slot that holds theend BBU in the ring. Thisparameter is valid for only the ringtopology.Optional parameters:0

-

End portnumber

End Port No Number of the port on the endBBU that is connected to the RRUin the chain or ring. This parameteris valid for only the ring topology.Value range: 0 through 2

-




Issue 01 (2008-06-25)

InputData


Breakposition 1

Break Position1

This parameter indicates theposition of the first break point.When you add and delete an RRUat a particular position in thecurrent RRU topology (ring orchain), set a break point at thisposition. After the RRU is addedor deleted, delete the break point toresume the data.For RRU chain, only one breakpoint can be set. After the settingof break point, the RRU chain isdivided into two parts:l The first part refers to the

section between the head ofRRU chain and the break point.This part of RRU service is notaffected.

l The second part refers to thepost-break point section of theRRU chain. This part of RRUservice is disrupted because it isin separate status.

OFF




2-13

InputData


Breakposition 2

Break Position2

Second position of the break pointonly for the ring topologyWhen you add and delete an RRUat a particular position in thecurrent RRU topology (ring orchain), set a break point at thisposition. After the RRU is addedor deleted, delete the break point toresume the data.For the RRU ring, two break pointscan be set. After the setting ofbreak point, the RRU chain isdivided into three parts:l The first part refers to the

section between the head the ofRRU ring and the first breakpoint. This part of RRU servicecan be affected.

l The second part refers to thesection between two breakpoints of the RRU ring. Thispart of RRU service is disruptedbecause it is in separate status.

l The third part refers to thesection between the secondbreak point and the end of theRRU ring. This part of RRUservice can be affected.

For the RRU ring, when only onebreak point is set, the actual case isthat two break points are set in thesame position, that is, two breakpoints overlap.

-




Issue 01 (2008-06-25)

Table 2-6 Negotiation and planned data of the RRU

InputData


RFModule

- l In 1 x 1 configuration,configure one RF module.

l In 3 x 1 configuration,configure three RFmodules.

l In 3 x 2 configuration,configure three or six RFmodules.

l In 6 x 1 configuration,configure six RF modules.

Configureeither theRRU or theWRFU

Networkplanning

RRU name RRUName Name of the MRRU Name

Internalplanning

RRU chainnumber

RRUChainNo This parameter indicates thenumber of the chain to whichthe RRU is connected.Value range: 0 through 249

0

RRUnumber

RRUNo The TRUNK positionindicates that the RRU is atthe cascaded position of themain chain or ring. TheBRANCH position indicatesthat the RRU is at thecascaded position where theparent node is located. Theparent node refers to theRHUB.Value range: 0 through 7

2

Boardstatus

BoardStatus Blocking status of the RRUOptional parameters:l Block

l Unblock

UnBlock

Topologyposition ofthe RRU

ToPoPosition Optional parameters:l TRUNK (in the main ring)

l BRANCH (under theRHUB node)

TRUNK Networkplanning




2-15

InputData


Initialcorrectionvalue forthe RTWP

RTWPofCarrierCarriernumberonRxRX channelnumber

Set the initial correctionvalue for the RTWP of thecarrier and TX channelspecified by the RRU. Valuerange:l Number of Carrier: 0 to 3

(MRRU/WRFU), 0 to 1(PRRU)

l RX channel number:0 to 1

l Initial correction value forthe RTWP: -130 to +130,unit: 0.1 dB

0

RRU IFoffset

IFOffset Offset direction of theIntermediate Frequency (IF)filter Optional parameters:l BOTTOM: Offset to

bottom, that is, to theminimum value (Theinterference signalfrequency is greater thanor equal to the currentreceive frequency.)

l MIDDLE: Offset tomiddle, that is, no offset(no interference)

l TOP: Offset to top, that is,to the maximum value(The interference signalfrequency is smaller thanthe current receivefrequency.)

l MINUS_50M (only fourcarrier RRU support)

l PLUS_50M (only fourcarrier RRU support)



MIDDLE

Floor Floor Floor for installing the RRUValue range: -100 through+1000

0




Issue 01 (2008-06-25)

InputData


Vertical Vertical Vertical position of the RRUValue range: 0 through 1000

0

Horizontal Horizontal Horizontal position of theRRUValue range: 0 through 1000

0

Table 2-7 Negotiation and planned data of the RHUB

InputData



Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock


ToPoPosition Optional parameters:l TRUNK (in the main

ring)l BRANCH (under the

RHUB node)



0




2-17

InputData



0


0

Equipment Layer Data of the Distributed NodeB


InputData

FieldName



ULResourceGroupId

l A board such as the HBBU or theHBBUC that is not added to theUL baseband resource groupcannot process baseband services.



1

Internalplanning


DLResourceGroupId




0




Issue 01 (2008-06-25)


InputData


Boardstatus

BoardStatus Blocking status of the board Optionalparameters:l Block

l Unblock

UnBlock

InternalplanningClock

sourceClockSource8K

E1/T1 ports for extracting the Iubinterface clock signals. Optionalparameters:l None

l Port 0 to port 7

Port 0

Bearermode

BearMode Optional parameters:l ATM: If the bearer mode is ATM,

the IP transport layer cannot usethe E1/T1 ports, that is, you cannotconfigure the PPP or MP links.

l IPv4: If the bearer mode is IPv4,the ATM transport layer cannotuse the E1/T1 ports, that is, youcannot configure the physicallinks.

ATM


HSUPAswitch

HSUPA Optional parameters:l ENABLE (The HSUPA is

supported)l DISABLE (The HSUPA is not

supported)

DISABLE

ClockMode

ClockMode For the cascaded NodeBs, the clockof the upper-level NodeB is set toMASTER and that of the lower-levelNodeB is set to SLAVE. If the valueis not specified, the original clockmode is retained. Optionalparameters:l MASTER (primary mode)

l SLAVE (secondary mode)

SLAVE Networkplanning

Line Code LineCode Optional parameters:l HDB3 (for E1 mode)

l AMI (for E1 or T1 mode)

l B8ZS (for T1 mode)

HDB3 Negotiation withthedestination




2-19

InputData


FrameStructure

FrameStru Optional parameters: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 T1mode)

E1_CRC4_MULTI_FRAME

HSDPAswitch

HsdpaSwitch Optional parameters:l SIMPLE_FLOW_CTRL: Based

on the configured Iub bandwidthand the bandwidth occupied byR99 users, traffic is allocated toHSDPA users when the physicalbandwidth restriction is taken intoaccount.

l AUTO_ADJUST_FLOW_CTRL: According to the flow control ofSIMPLE_FLOW_CTRL, trafficis allocated to HSDPA users whenthe delay and packet loss on theIub interface are taken intoaccount. The RNC uses the R6switch to perform this function. Itis recommended that the RNC beused in compliance with the R6protocol.

l NO_FLOW_CTRL: The NodeBdoes not allocate bandwidthaccording to the configuration ordelay on the Iub interface. TheRNC allocates the bandwidthaccording to the bandwidth on theUu interface reported by theNodeB. To perform this function,the reverse flow control switchmust be enabled by the RNC.


Time delaythreshold

HsdpaTD When the time delay is lower thanthis threshold, you can infer that thelink is not congested.Value range:0 to 20

4




Issue 01 (2008-06-25)

InputData


Discardratethreshold

HsdpaDR The link is not congested when frameloss ratio is not higher than thisthreshold.Value range:0 to 1000

1

WorkingMode

WorkMode Optional parameters:l OFF (inhibited mode): indicates

that the port works in inhibitedmode, that is, the port does notdetect the alarms. All ports workin such mode by default.

l Default (default mode): indicatesthat the system detects and reportsthe alarms in default mode. In suchmode, the UE cannot set the alarmID of this port or other parametersrelated to this port. The systemreports alarms based on its ownfixed setting rather than the user-defined setting.

l CUSTOM (customized mode):indicates that the UE can changethe binding relation, that is, thesystem reports the alarm and setthe alarm Bool based on thecustomer specified ID.

OFF

Internalplanning

Alarm ID AlarmId This parameter is valid only whenWorkMode is set to CUSTOM.

-

Alarmvoltage

ALarmVoltage

This parameter is valid only whenWorkMode is set to CUSTOM.Optional parameters:l HIGH (alarms related to high

impedance)l LOW (alarms related to low

impedance)

-




2-21


InputData


Chaintype



CHAIN

Internalplanning


Head SubrackNo.


0



0

Head portnumber


0

Endsubracknumber

End SubrackNo


-

End boardnumber


-

End portnumber


-




Issue 01 (2008-06-25)

InputData


Breakposition 1

Break Position1




OFF




2-23

InputData


Breakposition 2

Break Position2






-




Issue 01 (2008-06-25)


InputData


RFModule




l In 6 x 1 configuration,configure six RFmodules.


Networkplanning


Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock




RHUB node)





2-25

InputData



RTWPofCarrierCarriernumberonRxRXchannel number



l RX channel number: 0through 1


0

RRU IFoffset









MIDDLE


0




Issue 01 (2008-06-25)

InputData



0


0


InputData



Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock




RHUB node)



0




2-27

InputData



0


0

ALD Data

Table 2-13 Negotiation and planned data of the ALD

InputData


Antennaconnectornumber

AntennaNo In the 2G extended scenario, thisparameter is unavailable.When dual-polarized RET isconfigured and the value is NOA;when single-polarized RET or STMAis configured, the value is NOA orNOB.

N0A Networkplanning

DeviceName

DeviceName Name of the ALD. The maximumlength is a string of 31 characters.

RET 1 Internalplanning




Issue 01 (2008-06-25)

InputData


Scenario UseCase Scenario of the antenna Optionalparameters:l REGULAR: Regular installation,

that is, only one dual polarizationRET can be installed to anANT_Tx/RxA port, and this RETis controlled through this port.

l SECTOR_SPLITTING: Sectorsplitting, that is, a maximum of sixRETs can be installed to anANT_Tx/RxA port through asplitter, and these RETs arecontrolled through this port.

l DAISY_CHAIN: Antennacascading, that is, a maximum ofsix RETs installed to differentports can be cascaded to anANT_Tx/RxA port throughcontrol signal cables, and theseRETs are controlled through thisport.

l 2G_EXTENSION: 2G extension.The 2G RET is controlled throughthe NodeB. It is an extended modeof cascaded NodeBs.

REGULAR

Networkplanning

Antennapolarization type

RETType When the device type is eitherSINGLE_RET or MULTI_RETsupported by the AISG protocol, thisparameter is valid. Optionalparameters:l In the scenario of antenna

cascaded application, theparameter value can be set to eitherDUAL (dual polarization antenna)or SINGLE (single polarizationantenna).

l In other scenarios other thanantenna cascading, the value ofthis parameter can only be DUAL.

DUAL

Vendorcode

VendorCode Vendor code of the ALD. The lengthis a 2-byte letter or number.For details about the relation betweenthe vendor code and vendor name ofthe ALD, refer to the AISG protocol.

-

Internalplanning




2-29

InputData


Equipment serialnumber

SerialNo Serial number of the ALD. Themaximum length is a 17-byte letter ornumber.

-

Antennasubunitnumber

SubUnit Select different subunit numbersaccording to different antenna devicetypes: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 numberranges from 1 to 6. When multipleantennas do not support 6 subunits,the subunit number ranges from 1to 2.

l The subunit number for a singleantenna is not displayed, and is 0by default.

0

NetworkplanningAntenna

tilt angleAntTilt Downtilt of the RET antenna

Value range: -100 through +3000

Workingmode ofthe STMA

BypassMode Optional parameters:l NORMAL (normal mode)

l Bypass mode

NORMAL

SASUgain

l GSMGain

l UMTSGain

According to different types ofchannels, the SASU gain can bedivided into the following two types:l GSMGain indicates the SASU

gain in the GSM channel. Valuerange: 0 through 255.

l UMTSGain indicates the SASUgain in the UMTS channel. Valuerange: 0 through 255.

0




Issue 01 (2008-06-25)

InputData


DC switchon theSASUantennaconnector

DCSwitch DC switch (on the SASU antennaconnector) status When the status isset to GSM, the DC power load of theSASU GSM cannot be started.Optional parameters:l GSM (The GSM feeder supplies

the power)l UMTS (The UMTS feeder

supplies the power)l OFF

UMTS

SASUGSM DCpower load

DCload The DC power load is applied to theTMA that simulates the GSM system.The SASU needs to inform the GSMthat a TMA is connected to the BTSantenna when the UE sets a relativelyhigh gain for the GSM Rx channelthrough the WCDMA NodeB. Theeasiest method is that you add a DCload to the GSM BTS. In thissituation, the GSM BTS is informedof the TMA connected to the antennaby checking the DC power of theantenna.

20

STMAgain

Gain Value range: 0 through 255 0

Data of the Iub Transmission Sharing Function

Table 2-14 Data of the Iub transmission sharing function

Input Data FieldName

Description Source

Source logicalcell ID

SrcCellId Value range: 0through 65535

Network planning

Source FACHID

SrcFachId Value range: 0through 255

Destinationlogical cell ID

DestCellId Value range: 0through 65535

DestinationFACH ID

DestFachId Value range: 0through 255




2-31

2.3 NodeB Transport Layer DataThis describes the data to be prepared for configuring the NodeB transport layer in the ATMand the IP mode.

Transport Layer Data (over ATM)

Table 2-15 Negotiation and planned data of the IMA group and IMA links

InputData


Slot No. SlotNo Number of slot where the NDTI orNUTI is held (Slots 14 and 15 holdonly the NUTI)Value range: 12 through 15

14

Internalplanning

Sub-boardtype

SubBdType Type of the sub-board where the E1/T1 port used by the IMA link islocated Optional parameters:l Baseboard

l E1 CoverBoard: E1 coverboard

l Channelled CoverBoard:channelized optical sub-board

ChannelledCoverBoard

IMA groupID

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

l When SubBdType is E1CoverBoard, the value range is 0through 3.

l When SubBdType is ChannelledCoverBoard, the value range is 0through 1.

0

Transmitframelength

IMATxFrameLength

Longer transmit frame can enhancetransmission efficiency but reduceserror sensitivity. Therefore, thedefault value is recommended.Optional parameters:l D32

l D64

l D128

l D256

D128




Issue 01 (2008-06-25)

InputData


Minimumactive links

IMAMinActiveLinks

Threshold for identifying theavailability of the IMA group Forexample, if the value is 3, there are atleast three active IMA links in anIMA group and thus this group isavailable. If there are less than threeactive links, the IMA group isunavailable.l When SubBdType is BaseBoard,

the value range is 1 through 8.l When SubBdType is E1

CoverBoard, the value range is 1through 8.


1

Differential maximumdelay

IMADiffMaxDelay

Different transmission links in anIMA group may result in differenttransmission delays. Thus, there is achange in the relative delay betweenlinks, which is called link differentialdelay. The LODS alarms are reportedwhen the link differential delayoccurs.Value range: 4 through 100

25

Scramblemode

ScrambleMode

Optional parameters:l DISABLE (unavailable, the

scramble mode is disabled)l ENABLE (The scramble mode

must be enabled if the E1/T1transmission uses AMI linecodes.)

ENABLE

Timeslot16 support

TimeSlot16 The channelized optical sub-boarddoes not support this function.Optional parameters:l ENABLE

l DISABLE

After this parameter is enabled, thebandwidth of each IMA link in theIMA group is added by 64 kbit/s.

DISABLE




2-33

InputData


Linknumber

LinkNo Number of the E1/T1 ports for thelinks in an IMA group.l When SubBdType is BaseBoard,




0, 1, 2 Negotiation withthedestination

HSDPAswitch

HsdpaSwitch

Optional parameters:l SIMPLE_FLOW_CTRL: Based





Internalplanning

Time delaythreshold

HsdpaTD When the time delay is lower thanthis threshold, you can infer that thelink is not congested.Value range: 0 through 20

4




Issue 01 (2008-06-25)

InputData



HsdpaDR The link is not congested when frameloss ratio is not higher than thisthreshold.Value range: 0 through 1000

1

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

InputData


Slot No. SlotNo Number of slot where the NDTIor NUTI is held (Slots 14 and 15hold only the NUTI)Value range: 12 through 15

12

Internalplanning

Sub-boardtype

SubBdType Type of the sub-board where theE1/T1 port is located by the UNIlink Optional parameters:l Baseboard

l E1 CoverBoard: E1coverboard


BaseBoard

Linknumber

LinkNo Number of the E1/T1 ports forUNI linksl When SubBdType is

BaseBoard, the value range is0 through 7.

l When SubBdType is E1CoverBoard, the value range is0 through 7.

l When SubBdType isChannelled CoverBoard, thevalue range is 0 through 62.

3 Negotiationwith thedestination

Scramblemode

ScrambleMode




ENABLE

Internalplanning




2-35

InputData


Timeslot16 support

TimeSlot16 The channelized optical sub-board does not support thisfunction. Optional parameters:l ENABLE

l DISABLE

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

DISABLE

HSDPAswitch

HsdpaSwitch

Optional parameters:l SIMPLE_FLOW_CTRL:

Based on the configured Iubbandwidth and the bandwidthoccupied by R99 users, trafficis allocated to HSDPA userswhen the physical bandwidthrestriction is taken intoaccount.

l AUTO_ADJUST_FLOW_CTRL: According to the flowcontrol ofSIMPLE_FLOW_CTRL,traffic is allocated to HSDPAusers when the delay andpacket loss on the Iub interfaceare taken into account. TheRNC uses the R6 switch toperform this function. It isrecommended that the RNC beused in compliance with the R6protocol.

l NO_FLOW_CTRL: TheNodeB does not allocatebandwidth according to theconfiguration or delay on theIub interface. The RNCallocates the bandwidthaccording to the bandwidth onthe Uu interface reported bythe NodeB. To perform thisfunction, the reverse flowcontrol switch must be enabledby the RNC.


Time delaythreshold

HsdpaTD When the time delay is lower thanthis threshold, you can infer thatthe link is not congested.Value range: 0 through 20

4




Issue 01 (2008-06-25)

InputData



HsdpaDR The link is not congested whenframe loss ratio is not higher thanthis threshold.Value range: 0 through 1000

1

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

InputData



13

InternalplanningSub-board

typeSubBdType Type of the sub-board with the E1/

T1 port available for the fractionalATM link Optional parameters:Baseboard

BaseBoard

Port No. E1T1No Number of the E1/T1 port availablefor the fractional ATM linkValue range: 0 through 1

0 Negotiation with thedestination

Linknumber

LinkNo Value range: 0 through 7 1 Internalplanning

Timeslots TSBitMap The fractional ATM link providestimeslots for the 3G equipment. Ifport 0 is configured, the timeslotsmust be reserved for timeslot crossconnection.Value range: TS1 to TS31

TS24 toTS31 Negotiatio

n with thedestination

Scramblemode

ScrambleMode




ENABLE

Internalplanning




2-37

InputData


HSDPAswitch


on the configured Iub bandwidthand the bandwidth occupied byR99 users, traffic is allocated toHSDPA users when the physicalbandwidth restriction is takeninto account.

l AUTO_ADJUST_FLOW_CTRL: According to the flow controlof SIMPLE_FLOW_CTRL,traffic is allocated to HSDPAusers when the delay and packetloss on the Iub interface are takeninto account. The RNC uses theR6 switch to perform thisfunction. It is recommended thatthe RNC be used in compliancewith the R6 protocol.

l NO_FLOW_CTRL: The NodeBdoes not allocate bandwidthaccording to the configuration ordelay on the Iub interface. TheRNC allocates the bandwidthaccording to the bandwidth onthe Uu interface reported by theNodeB. To perform thisfunction, the reverse flow controlswitch must be enabled by theRNC.


Time delaythreshold


4



1




Issue 01 (2008-06-25)

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

InputData

FieldName


Source slotNo.

SlotNo Number of the slot that holdsthe NDTI or NUTIValue range: 12 through 15

13

Internalplanning

Sourceport No.

PortNo Number of the source E1/T1ports for timeslot cross linksValue range: 2 through 3

3

Sourcetimeslots

TSBitMap Value range: TS1 to TS31 TS16 to TS23

Destination slot No.

DestSlotNo

Number of the slot that holdsthe NDTI or NUTI (Thenumber must be identicalwith that of the SlotNo)Value range: 12 through 15

13

Destination port No.

DestPortNo

Number of the destinationE1/T1 ports for timeslotcross linksValue range: 0

0

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

InputData

FieldName


Port type Type Type of the interface that carries theSDT CES channels Optionalparameters:l FRAATM

l IMA

l UNI

l STM1

FRAATM

Internalplanning

Source slotNo.

PortNo Number of the slot that holds the NDTIValue range: 12 through 13

12

Sourcesub-boardtype

SubBdType

Type of the sub-board where thesource E1/T1 port is located by theSDT CES channel Optionalparameters: Baseboard

BaseBoard




2-39

InputData

FieldName


Source portNo.

PortNo Number of the source E1/T1 ports forthe SDT CES channelValue range: 0 through 1

0

Partial filllevel

PFL ATM cell has 48-byte payloads.Except for the first byte, the other 47bytes can be used to transmit timeslotsignals. Each timeslot occupies onebyte. The number of filling bytes isthat of valid bytes filled in each ATMcell.Value range: 4 through 47, and thevalue should be greater than thenumber of selected timeslots exceptfor slot 0.

47

Timeslots TSBitMap Timeslot 0 is unavailable.Value range: TS1 to TS31

TS1 toTS7


SlotNo Number of slot where the NDTI orNUTI is held (Slots 14 and 15 holdonly the NUTI)Value range: 12 through 15

13

Destination sub-board type

SubBdType

Type of the sub-board where thedestination E1/T1 port is located bythe SDT CES channel Optionalparameters:l Baseboard



l Unchannelled CoverBoard:unchannelized optical sub-board

BaseBoard




Issue 01 (2008-06-25)

InputData

FieldName



E1T1No Number of the destination E1/T1 portfor the SDT CES channel (Thisparameter is valid only when Type isset to FRAATM or UNI).l When Type is set to FRAATM and

SubBdType(destination sub-boardtype) is BaseBoard, the value rangeis 0 through 7.

l When Type is set to UNI andSubBdType(destination sub-boardtype) is BaseBoard or E1CoverBoard, the value range is 0through 7.

l When Type is set to UNI andSubBdType(destination sub-boardtype) is Channelled CoverBoard,the value range is 0 through 62.

0

Link No./IMA ID

LinkNo/IMAId

Number of the fractional ATM or UNIlink, of the IMA group, or of the STM1optical port that carries the SDT CESchannel.l When Type is set to FRAATM and




l When Type is set to IMA andSubBdType(destination sub-boardtype) is BaseBoard or E1CoverBoard, the value range is 0through 3.

l When Type is set to IMA andSubBdType(destination sub-boardtype) is Channelled CoverBoard,the value range is 0 through 1.

l When Type is STM1, the valuerange is 0 through 1.

0




2-41

InputData

FieldName


Virtualchannelidentifier

VPI Identifier of the virtual channel for theSDT CES channel.Value range: 0 through 31 (sixsuccessive values from 0 to 31)

1


VCI Identifier of the virtual channel for theSDT CES channel.l When the interface board is the

NDTI, the value range is 32 through255.

l When the interface board is theNUTI, the value range is 32 through127.

32

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

InputData

FieldName


Port type Type Type of the interface that carries theUDT CES channel Optionalparameters:l IMA

l STM1

IMA

Internalplanning

Source slotNo.


12

Sourcesub-boardtype

SubBdType

Type of the sub-board where thesource E1/T1 port is located by theUDT CES channel Optionalparameters: Baseboard

BaseBoard

Source portNo.

PortNo Number of the source E1/T1 ports forthe UDT CES channelValue range: 0 through 1

1




Issue 01 (2008-06-25)

InputData

FieldName


Partial filllevel

PFL The value of the partial fill levelaffects both the transmissionbandwidth and the transmission delay.When the value reaches the maximumof 47, the transmission bandwidth isnot affected, and the transmissiondelay reaches the maximum value;when the value is smaller than 47, thetransmission bandwidth equals to theoriginal transmission bandwidth x (53/PFL), and the transmission delay isreduced. In order not to affect thetransmission bandwidth, set thedefault value to 47.Value range: 4 through 47

47

Tx ClockMode

TxClockMode

Optional parameters:l NOACM (non-adaptive clock

mode)l NOACM (adaptive clock mode)

ACM



14


SubBdType

Type of the sub-board where thedestination E1/T1 port is located bythe UDT CES channel Optionalparameters:l Baseboard








2-43

InputData

FieldName


Opticalport No./IMA ID

LinkNo/IMAId

Number of the IMA group or STM1optical port that carries the UDT CESchannel.l When Type is set to IMA and

SubBdType(destination sub-boardtype) is BaseBoard or E1CoverBoard, the value range is 0through 3.



0


VPI Identifier of the virtual channel for theUDT CES channel.Value range: 0 through 31 (sixsuccessive values from 0 to 31)

1


VCI Identifier of the virtual channel for theUDT CES channel.l When the interface board is the



32

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

InputData

FieldName

Description Example

Source

Port type Type Type of the interface that carries thetransmission resource group Optionalparameters:l FRAATM

l IMA

l UNI

l STM1

IMA

Internalplanning

Resourcegroupnumber

RscgrpNo Value range: 0 through 3 1




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Transmitbandwidth

TxBandwidth

The transmit bandwidth of the resourcegroup cannot exceed the bandwidth ofthe port to which the resource groupbelong.Value range: 32 through 15800

5000

Receivebandwidth

RxBandwidth

Receive bandwidth of the resourcegroup.Value range: 30 through 20000

5000

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

InputData

FieldName

Description Example

Source

Port type Type Type of the interface that carries theSAAL links Optional parameters:l FRAATM

l IMA

l UNI

l STM1

IMA



VPI Identifier of the virtual channel for theSAAL links.Value range:l Macro NodeB: 0 through 31 (six

successive values from 0 to 31)l Distributed NodeB: 0 through 29

1


VCI Identifier of the virtual channel for theSAAL links.Value range:l Macro NodeB: 32 through 255

(NDTI) or 32 through 127 (NUTI)l Distributed NodeB: 32 through 127

34




2-45

InputData

FieldName

Description Example

Source

Servicetype

ServiceType

When this parameter is set to CBR orUBR, you need to set only theparameter PCR; when this parameteris set to RTVBR or NRTVBR, youneed to set parameters SCR and PCR;when this parameter is set to UBR+,you need to set parameters PCR andMCR.Optional parameters:l CBR (applicable to the CES

channel)l RTVBR (applicable to services

carried on the AAL2 path)l NRTVBR (applicable to services

carried on the AAL5 path)l UBR+ (unspecified bit rate,

provides cell rate guarantee)l UBR (unspecified bit rate)

RTVBR

Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than thatof 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 rangeis 31 to 6760.

200

Minimumcell rate

MCR The value of the MCR of the ATMchannel should be smaller than that ofthe PCR. This parameter is valid onlywhen the service type is UBR+.Value range: 30 through 6759

-

Sustainablecell rate

SCR The value of the SCR of the ATMchannel should be smaller than that ofthe PCR. This parameter is valid onlywhen the service type is RTVBR orNRTVBRValue range: 30 through 6759

180




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Join theresourcegroup

JoinRscgrp Specify whether this link should beadded to the resource group. Optionalparameters:l DISABLE

l ENABLE

ENABLE

Internalplanning

Resourcegroupnumber

RscgrpNo Number of the ATM transmissionresource groupValue range: 0 through 3

1

Table 2-23 Negotiation and planned data of the NBAP


Description Example

Source

NCP

Port type PortType Optional parameters:l NCP

l CCP

NCPInternalplanning

SAALnumber

SAALNo SAAL number that carries theNCPValue range: 0 through 63

1 Negotiation withthedestination

Flag Flag Master/slave flag for thetransmission channels Optionalparameters:l SLAVE

l MASTER

MASTER

Internalplanning

CCP


l CCP

CCPInternalplanning

Port No. PortNo Number of the CCP port. Thisparameter is valid only whenPortType is set to CCP.Value range: 0 through 65535

0


SAALnumber

SAALNo SAAL number that carries theCCPValue range: 0 through 63

2




2-47


Description Example

Source


l MASTER

MASTER

Internalplanning

Table 2-24 Negotiation and planned data of the ALCAP

InputData

FieldName


Node type NodeType The exchange node must be configuredbefore configuring the adjacent node.The exchange node cannot be carried onthe SAAL link on the NDTI. Optionalparameters:l LOCAL (peer node)

l HUB (switch node, indicating thatthe NodeB has a lower-level NodeB)

l ADJNODE (adjacent node,indicating the lower-level NodeB)

LOCAL

Internalplanning

Adjacentnodeidentifier

ANI Identify an adjacent node. Thisparameter is valid only when theparameter NodeType is set toADJNODE.Value range: 0 through 31

-

Networkserviceaccesspoint

NSAP The full name is: Net service accesspoint.When the NodeB uses ATMtransmission, the NSAP is the addressof the NodeB that is connected to theAAL2 path. The address is ahexadecimal with a length of 20 bytes(excluding the prefix H').

H'3901010101010101010101010101010101010101

SAALnumber

SAALNo SAAL number that carries the ALCAPValue range: 0 through 63

3




Issue 01 (2008-06-25)

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

InputData

FieldName


Port type Type Type of the interface that carries theAAL2 PATH Optional parameters:l FRAATM

l IMA

l UNI

l STM1

IMA


PATH type PathType Type of the AAL2 path, whichindicates the desired service typecarried on the path. Optionalparameters: RT, NRT, HSPA_RT,HSPA_NRT

RT


VPI Identifier of the virtual channel for theAAL2 path.Value range:l Macro NodeB: 0 through 31 (six


1


VCI Identifier of the virtual channel for theAAL2 path.Value range:l Macro NodeB: 32 through 255


37

Servicetype

ServiceType

Optional parameters:l CBR (applicable to the CES





RTVBR




2-49

InputData

FieldName


Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than that ofthe SCR. This parameter should be oneof the bandwidth parameters for thetransmission direction.l When the sub-board type is

BaseBoard, and the service type isCBR or UBR, the value range is 30through 15800.

l When the sub-board type isChannelled CoverBoard orUnchannelled CoverBoard, and theservice type is RTVBR,NRTVBR,or UBR+, the value rangeis 31 through 15800.

1920

Sustainable cell rate

SCR The value of the SCR of the ATMchannel should be smaller than that ofthe PCR. This parameter is valid onlywhen the service type is RTVBR orNRTVBRThis parameter should beone of the bandwidth parameters for thetransmission direction.l When sub-board type is BaseBoard,

the value range is 30 through 15799.l When the sub-board type is

Channelled CoverBoard orUnchannelled CoverBoard, thevalue range is 30 through 6759.

960

Receivedcell rate

RCR This parameter must be consistent withthe downlink bandwidth configured bythe RNC. This parameter acts as animportant factor in flow control by theNodeB receive bandwidth. Whether ornot this parameter is correctlyconfigured will affect the effect of flowcontrol.Value range: 64 through 20000

2048


JoinRscgrp Specify whether AAL2 path should beadded to the resource group. Optionalparameters:l DISABLE

l ENABLE

ENABLE

Internalplanning




Issue 01 (2008-06-25)

InputData

FieldName


Resourcegroupnumber


1

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



Port type Type Type of the interface that carries theOMCH Optional parameters:l FRAATM

l IMA

l UNI

l STM1

UNI



VPI Virtual channel for the OMCHValue range:l Macro NodeB: 1 or within the VPI

range of the actual boardconfiguration

l Distributed NodeB: 0 through 29

1


VCI Virtual channel for the OMCHValue range:l Macro NodeB: 32 through 255


33

Service type ServiceType






CBR




2-51



Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than that ofthe SCR.l When the service type is CBR or



512



-

Local IPaddress ofthe OMCH

LocalIP IP address for NodeB remotemaintenance

10.1.2.10

DestinationIP addressof theOMCH

DestIP Destination IP address for NodeBremote maintenance, that is, the IPaddress configured on the ATMinterface board at the RNC.

10.1.2.1

Destinationsubnet maskof theOMCH

DestIPMask

Subnet mask of the destination IPaddress for NodeB remote maintenance

255.255.255.0



l ENABLE

ENABLE

Internalplanning

Resourcegroupnumber


2

Flag Flag Master/slave flag for the remote OMchannels Optional parameters:l SLAVE

l MASTER

MASTER




Issue 01 (2008-06-25)

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

InputData

Field Name Description Example

Source

Source porttype

SourceType Type of the interface that carries thesource port of the treelink PVCOptional parameters:l FRAATM

l IMA

l UNI

l STM1

FRAATM

Internalplanning

Destination port type

DestinationType

Type of the interface that carries thedestination port of the treelink PVCOptional parameters:l FRAATM

l IMA

l UNI

l STM1

UNI

ByPassMode

ByPassMode When the NodeB is powered off orexceptions occur to the NodeB, theE1/T1 can be connected to the lowernode by switching to theByPassMode. The treelink PVC is setusing the ByPassMode that thusguarantees the connection betweenthe lower node and the RNC. Optionalparameters:l DISABLE (disable the

ByPassMode)l ENABLE (enable the

ByPassMode)

DISABLE

Source VPI SourVPI Virtual channel used by the upperlevel network linkl For the VP switching, the source

port VPI must be beyond the VPIconfigured to the board, and thevalue cannot be 1.

l For the VC switching, the sourceport VPI must be within the VPIconfigured to the board, and thevalue can be 1.

l For the VC switching, the SourVPIand the DestVPI must meet theconditions of the source board andthe destination board respectively.

1





2-53

InputData


Source

SourceVCI

SourVCI Identifier of the virtual channel for theupper-level links. This parameter isvalid for VC switching.l For the macro NodeB, the value

range is 32 through 255 (NDTI) or32 through 127 (NUTI)

l For the distributed NodeB, thevalue range is 32 through 127

33

Destination VPI

DestVPI Virtual channel used by the lower-level network linkl For the VP switching, the

destination port VPI must bebeyond the VPI configured to theboard, and the value cannot be 1.

l For the VC switching, thedestination port VPI must be withinthe VPI configured to the board,and the value can be 1.


1

Destination VCI

DestVCI Identifier of the virtual channel for thelower-level links. This parameter isvalid for VC switching.l For the macro NodeB, the value



32

Servicetype

ServiceType Optional parameters:l RTVBR

l NRTVBR

l UBR (unspecified bit rate)

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

RTVBR




Issue 01 (2008-06-25)

InputData


Source

Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than thatof the SCR.l When the service type is UBR, the

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

NRTVBR or UBR+, the valuerange is 31 to 6760.

400



380

Transport Layer Data (over IP)

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

InputData


Slot No. SlotNo Number of the slot that holds theNUTIValue range: 12 through 15

13

Internalplanning

Port No. PortNo Number of the E1/T1 ports for PPPlinksValue range: 0 through 7

0

Linknumber

LinkNo Each PPP link and each MLPPP linkmust have a unique number.Value range: 0 through 15

0

Authentication type

AuthType Optional parameters:l NONAUTH (without

authentication)l PAP (with PAP authentication)

l CHAP (with CHAPauthentication)

NONAUTH




2-55

InputData


User name UserName When AuthType is not set toNONAUTH, this field is mandatory,otherwise, the authentication fails.Value range: not greater than 64characters

-

Timeslotmap

TSBitMap A map of the timeslots for PPP links.The map is presented in binaryformat or the chart. If a timeslot isselected, it is in use. Otherwise, it isnot in use.

TS1 toTS15


Local IPaddress

LocalIP Local IP address of the PPP link.When the value is 0.0.0.0, it indicatesthat the parameter needs to benegotiated with the RNC.

17.17.17.111

Destination IPaddress

PeerIP Destination IP address of the PPPlinkl In cascading mode, this parameter

specifies the IP address of a lower-level cascaded node.

l In non-cascading mode, when thevalue is 0, it indicates that theparameter needs to be negotiatedwith an upper-level node.

17.17.17.17

IP headercompression

IPHC Optional parameters:l DISABLE: The IP header of the

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

the peer end is compressed.

ENABLE

Internalplanning

PPPmultiframemultiplexing

PPPMux Optional parameters:

l ENABLE

l DISABLE

DISABLE

Maximumreceivedunit

MRU Expected value sent from the peerendValue range: 128 through 1500

1500

Restarttimer ofpacketrequestresponse

RestartTimer Value range: 1 through 65535 3000




Issue 01 (2008-06-25)

InputData


Protocolfieldcompress

PFC Optional parameters:l ENABLE

l DISABLE

ENABLE

Address &controlfieldcompress

ACFC Optional parameters:

l ENABLE

l DISABLE

ENABLE

HSDPAswitch






Time delaythreshold


4



1




2-57

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

InputData


Source


13

Internalplanning

MLPPPgroupnumber

GroupNo MLPPP group numberValue range: 0 through 3

0

Authentication type



l CHAP (with CHAP authentication)

NONAUTH


-

Local IPaddress

LocalIP Local IP address of the MLPPP group 16.16.16.111


Localsubnetmask

LocalMask Subnet mask of the local IP address forthe 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 forMLPPP linksValue range: 0 through 7

0

Internalplanning

Linknumber

LinkNo Number of the MLPPP link that joinsthe MLPPP group. Each MLPPP andeach PPP link must have a uniquenumber.Value range: 0 through 15

1

Timeslotmap

TSBitMap A map of the timeslots for MLPPPlinks. The map is presented in binaryformat or the chart. If a timeslot isselected, it is in use. Otherwise, it isnot in use.

TS24 toTS31





Issue 01 (2008-06-25)

InputData


Source





ENABLE

Internalplanning



l ENABLE

l DISABLE

DISABLE

Multi-classPPP

MCPPP Optional parameters:l ENABLE (using the MCPPP)

l DISABLE (not using the MCPPP)

ENABLE

Maximumreceivedunit

MRU Expected value sent from the peer endValue range: 128 through 1500

1500





l DISABLE

ENABLE



l ENABLE

l DISABLE

ENABLE




2-59

InputData


Source

HSDPAswitch

HsdpaSwitch Optional parameters:l SIMPLE_FLOW_CTRL: Based on


l AUTO_ADJUST_FLOW_CTRL:According to the flow control ofSIMPLE_FLOW_CTRL, traffic isallocated to HSDPA users when thedelay and packet loss on the Iubinterface are taken into account.The RNC uses the R6 switch toperform this function. It isrecommended that the RNC be usedin compliance with the R6 protocol.



Time delaythreshold

HsdpaTD When the time delay is lower than thisthreshold, you can infer that the link isnot congested.Value range: 0 through 20

4



1

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

InputData

FieldName

Description Example

Source

Slot No. SlotNo Number of the slot that holds the NUTIValue range: 12 through 15

13 Internalplanning




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Port No. PortNo Number of the FE port for the PPPoElinkValue range: 0 through 1

0

Authentication type

AuthType Optional parameters:l NONAUTH (without authentication)

l PAP (with PAP authentication)


NONAUTH

User name UserName This parameter is valid only whenAuthType is set to PAP or CHAP.Value range: not greater than 64characters

-

Local IPaddress

LocalIP Local IP address of the PPPoE link 12.3.0.1 Negotiation withthedestination

Localsubnetmask

LocalMask Subnet mask of the local IP address 255.255.255.0


IPHC Optional parameters:l DISABLE: The IP header of the peer

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

peer end is compressed.

ENABLE

Internalplanning

Maximumreceivedunit


1450


RestartTimer

Value range: 1 through 65535 3000



l ENABLE

l DISABLE

DISABLE




2-61

InputData

FieldName

Description Example

Source

HSDPAswitch

HsdpaSwitch

Optional parameters:l SIMPLE_FLOW_CTRL: Based on

the configured Iub bandwidth and thebandwidth occupied by R99 users,traffic is allocated to HSDPA userswhen the physical bandwidthrestriction is taken into account.


l NO_FLOW_CTRL: The NodeBdoes not allocate bandwidthaccording to the configuration ordelay on the Iub interface. The RNCallocates the bandwidth according tothe bandwidth on the Uu interfacereported by the NodeB. To performthis function, the reverse flow controlswitch must be enabled by the RNC.


Time delaythreshold


4



1

Table 2-31 Negotiation and planned data of the DEVIP

InputData

FieldName

Description Example

Source


13 Internalplanning




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Port No. PortNo l For the PPP link, the MLPPP group,and the PPPoE link, PortNorepresents the port number for theconfigured PPP link, the MLPPPgroup, and the PPPoE link.

l For the ETH link, the port valueranges from 0 to 1.

0

Port type PortType The port types consist of the followingitems: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.

ETH

Local IPaddress

LocalIP Local IP address of the device IP 12.11.12.12 Negotiati

on withthedestination

Subnetmask of thelocal IPaddress

LocalMask If the network is not divided intosubnets, use the default mask.

255.255.255.0


InputData

FieldName


Source slotNo.

SlotNo Number of the slot that holdsthe NUTIValue range: 12 through 15

13

Internalplanning

Sourceport No.


2

Sourcetimeslots





2-63

InputData

FieldName



DestSlotNo

Number of the slot that holdsthe NUTI (The number mustbe identical with that of theSlotNo)Value range: 12 through 15

13


DestPortNo


0

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

InputData


Source

Port type ItfType Interface type of the route Optionalparameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Networkplanning

Destination network

DestNet This parameter must meet all thefollowing requirements: Validnetwork address, except the defaultroute 0.0.0.0 IP AND mask must beequal to the IP address.

17.18.17.0

Destination mask

DestMask This parameter must meet all thefollowing requirements: IP ANDmask must be equal to the IP address.If the mask is converted into binaryvalue, 0 is not allowed to precede 1.

255.255.255.0

Next hopIP address

NextHop This parameter is valid only when theparameter InsertFlag is set to ETH.This parameter meets the followingrequirements: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.

12.11.12.1




Issue 01 (2008-06-25)

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



Port type ItfType Type of the interface that carries theSCTP links Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

PPP Internalplanning

Local IPaddress

LocalIP At the NodeB, the IP address of theprimary physical link that carries theSCTP link.

17.17.17.111

Negotiation with thedestination

DestinationIP address

DestIP At the RNC, the IP address of theprimary physical link that carries theSCTP link.

14.1.1.4

The secondlocal IPaddress

SecLocalIP At the NodeB, the IP address of thestandby physical link that carries theSCTP link.The IP address 0.0.0.0 indicates thatthis address is not in use.

0.0.0.0

The seconddestinationIP address

SecDestIP At the RNC, the IP address of thestandby physical link that carries theSCTP link.The IP address 0.0.0.0 indicates thatthis address is not in use.

0.0.0.0

Local portnumber anddestinationport number

LocalPort Local port number of the SCTPValue range: 1024 through 65535

1024

Destinationport number

DestPort Destination port number of the SCTPValue range: 1024 through 65535

8021

Automatically switchesback to themaster IPaddress

IPAutoChange

After the fault of the master IPaddress is rectified, the services canbe automatically switched back tothe master IP address. Optionalparameters:l ENABLE

l DISABLE





2-65

Table 2-35 Negotiation and planned data of the IPCP


Description Example

Source

NCP


l CCP

NCP Internalplanning

SCTPnumber

SCTPNo SCTP number that carries theNCPValue range: 0 through 19



l MASTER

MASTER

Internalplanning

CCP


l CCP

CCP Internalplanning


0


SCTPnumber

SCTPNo SCTP number that carries theCCPValue range: 0 through 19

2


l MASTER

MASTER

Internalplanning




Issue 01 (2008-06-25)

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

InputData

FieldName


Port type ItfType Type of the interface that carries the IPtransmission resource group Optionalparameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Internalplanning

Resourcegroupnumber


Transmitbandwidth

TxBandwidth

The transmit bandwidth of theresource group cannot exceed thebandwidth of the port to which theresource group belong.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.

10000

Receivebandwidth

RxBandwidth

Receive bandwidth of the resourcegroup.l When the port type is ETH, the





10000




2-67

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

InputData


Port type ItfType Type of the interface that carries theIP PATH Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH Internalplanning


DestIP Destination IP address of the IP path 17.18.17.121


DSCPpriority

DSCP Value range: 0 through 63 60 Networkplanning

Servicetype

TrafficType Optional parameters:l RT

l NRT

l HSPA_RT

l HSPA_NRT

RT


Receivebandwidth

RxBandwith When PATH joins the resourcegroup, the receive bandwidth doesnot exceed the bandwidth of theresource group; when PATH doesnot join the resource group, thereceive bandwidth doe not exceed thebandwidth of the physical port.l When the port type is PPP, the

value range is 8 through 1984.l When the port type is PPPoE, the


value range is 8 through 31744.l When the port type is ETH, the


1000




Issue 01 (2008-06-25)

InputData


Transmitbandwidth

TxBandwith When PATH joins the resourcegroup, the receive bandwidth doesnot exceed the bandwidth of theresource group; when PATH doesnot join the resource group, thereceive bandwidth doe not exceed thebandwidth of the physical port.l When the port type is PPP, the





1000

Transmitcommittedburst size

TxCBS Value range: 15000 to 155000000.The recommended value is 1/2 of thetransmit bandwidth.Unit: bit

500000

Internalplanning

Transmitexcessiveburst size

TxEBS Value range: 0 through 155000000Unit: bit

1000000

Path check PathCheck Optional parameters:l ENABLE: Path check is enabled.

l DISABLE: Path check is disabled.

DISABLE


JoinRscgrp Specify whether the IP PATH shouldbe added to the resource group.Optional parameters:l DISABLE

l ENABLE

ENABLE

Resourcegroupnumber

RscgrpNo Number of the IP transmissionresource groupValue range: 0 through 3

0




2-69

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

InputData

FieldName


Bind theroute

BindRouteValid

Determine whether to bind the route.Route binding is necessary when thepeer IP address of the OMCH is ondifferent network segments from theDestNet in the 6.6.2 Adding an IPRoute (Initial). Optional parameters:l NO

l YES

YES


Port type ItfType Type of the interface that carries thebound routes Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Bound IPaddress onthedestinationnetwork

BindDestIP This parameter is valid only when theparameter BindRouteValid is set toYES.

11.11.10.0

Bounddestinationmask

BindDestIPMask

This parameter is valid only when theparameter BindRouteValid is set toYES.

255.255.255.0

Bound nexthop IPaddress

NextHop This parameter is valid only when theport type is ETH.

12.11.12.1

Local IPaddress

LocalIP IP address at the NodeB for the OMCH 11.11.12.12

Localsubnetmask

Mask Mask of the IP address at the NodeBfor the OMCH

255.255.0.0


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

11.11.11.12

Flag Flag Optional parameters:l MASTER (primary mode)


MASTER Internal

planning




Issue 01 (2008-06-25)

Table 2-39 Negotiation and planned data of the transmission resource group whose destinationIP network segment is bound

InputData

FieldName


Port type ItfType Type of the interface that carries theresource group Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Internalplanning

Resourcegroupnumber

RscgrpNo Number of the IP transmission resourcegroup that corresponds to the physicalbearer portValue range: 0 through 3

0


DestIP Bound destination IP address, that is,the IP address on the same networksegment with BindDestIP in 6.6.7Adding an OMCH of the NodeB(Initial, over IP) or the destination IPaddress of the SCTP link of 6.6.3Adding SCTP Links (Initial).

11.11.10.10

Destination mask

IPMask Bound destination mask 255.255.255.255

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

InputData

FieldName


Port type ItfType Type of the interface that carries the IPclock links Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

PPPoE Internalplanning

IP addressat the client

ClientIP Obtain the NodeB IP address of the IPclock

12.3.0.1

NetworkplanningIP address

at theserver

ServerIP IP address at the IP clock server 12.3.0.10




2-71

InputData

FieldName


Priority Priority The clock links that has the highestpriority is used first. The number is ina negative relation with the prioritylevel.Value range: 0 through 1

0

Table 2-41 Negotiation and planned data of the IPQoS

InputData

FieldName


Priority rule PriRule Optional parameters:l IPPRECEDENCE

l DSCP

IPPRECEDENCE

Networkplanning

Signalingpriority

SigPri l In IPPRECEDENCE rule, the valuerange is 0 through 7.

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

7

OperationandMaintenance (OM)priority

OMPri l In IPPRECEDENCE rule, the valuerange is 0 through 7.


7

2.4 NodeB Radio Layer DataThis describes the data to be prepared for configuring the NodeB radio layer.

Site Data


InputData


Site name Site Name The site is usually named afterthe geographical location.

Shanghai Networkplanning




Issue 01 (2008-06-25)

Sector Data

Table 2-43 Negotiation and planned data of the sector

Input Data Field Name Description Example Source

Number ofRX antennas

RxAntennaNum

The number of RX antennas ina sector is associated with theparameter DemMode set atthe NodeB equipment layer..You can define the number ofRX antennas beforeconfiguring antenna channelsfor the sectors. You need to,however, adhere to thefollowing principles:l If DemMode is set to four-

way demodulation mode orfour-way economicaldemodulation mode, onlyone or four RX antennas canbe configured.

l If DemMode is set to two-way demodulation mode,only one or two RXantennas can be configured.

2

Networkplanning

Transmitdiversitymode

TxDiversityMode

Diversity mode of the sector,which can be configuredbefore the antenna channel isconfigured. Optionalparameters:l NO_TX_DIVERSITY (no

transmit diversity): onesector uses one TX channel.

l TX_DIVERSITY (transmitdiversity): one sector usestwo TX channels.

l HALFFREQ (0.5/0.5frequency mode, which canbe configured only inremote sectors)

When the number ofconfigured RX antennas isone, the sector can work onlyin no transmit diversity mode.

TX_DIVERSITY




2-73


Coveragetype

Cover Type This parameter is required forthe remote sector. It is validonly when the transmitdiversity mode isHALFFREQ. Optionalparameters:l SAMEZONE (same

coverage type)l DIFFZONE (different

coverage type)

-




Issue 01 (2008-06-25)

Cell Data

Table 2-44 Negotiation and planned data of the cell


Uplinkfrequency

UARFCNUpLink

The UL and DL frequencies ofa cell must be at the samefrequency band.

Frequency (MHz) =(Frequency / 5) + offset

Value range: 0 through 65535

l Band 1Common frequencies: 9612through 9888 inclusive.Offset:0

Special frequencies: None.Offset: 0

l Band 2Common frequencies: 9262through 9538 inclusive.Offset: 0

Special frequencies: {12,37, 62, 87, 112, 137, 162,187, 212, 237, 262, 287}.Offset:1850.1


Special frequencies: None.Offset:0


Special frequencies: {1662,1687, 1712, 1737, 1762,1787, 1812, 1837, 1862}.Offset:1380.1


Special frequencies: {782,787, 807, 812, 837, 862}.Offset:670.1

l Band 6

9612

Networkplanning




2-75


Common frequencies: 4162through 4188 inclusive.Offset:0Special frequencies:{812,837}. Offset:670.1

l Band 7Common frequencies: 2012through 2338 inclusive.Offset:2100Special frequencies: {2362,2387, 2412, 2437, 2462,2487, 2512, 2537, 2562,2587, 2612, 2637, 2662,2687}. Offset:2030.1

l Band 8Common frequencies: 2712through 2863 inclusive.Offset:340Special frequencies: None.Offset:0





Issue 01 (2008-06-25)


Downlinkfrequency

UARFCNDownLink

The UL and DL frequencies ofa cell must be at the samefrequency band.Frequency (MHz) =(Frequency / 5) + offsetValue range: 0 through 65535l Band 1

Common frequencies:10562 through 10838inclusive. Offset:0Special frequencies: None.Offset:0

l Band 2Common frequencies: 9662through 9938 inclusive.Offset:0Special frequencies: {412,437, 462, 487, 512, 537,562, 587, 612, 637, 662,687}. Offset:1850.1


l Band 4Common frequencies: 1537through 1738 inclusive.Offset:1805Special frequencies: {1887,1912, 1937, 1962, 1987,2012, 2037, 2062, 2087}.Offset:1735.1

l Band 5Common frequencies: 4357through 4458 inclusive.Offset:0Special frequencies: {1007,1012, 1032, 1037, 1062,1087}. Offset:670.1

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

10562




2-77





Uplinkresourcegroup ID

ULResourceGroupId

The cells within an uplinkresource group share theuplink resources. One ULresource group has amaximum of six cells. If theUL resource group has high-speed movement cells, itsupports a maximum of threecells.

0

Downlinkresourcegroup ID

DLResourceGroupId

When adding local cells, youneed to select the downlinkresource group. One local cellis only carried on a board of itsdownlink resource group.

0

Basebandresource pooltype

BbPoolType Optional parameters:GEN_POOL: general resourcepool, which consists of theboards located at slot 0 throughslot 9.

GEN_POOL




Issue 01 (2008-06-25)


Maximumtransmitpower

MaxTxPower The maximum transmit powerof a local or remote cell refersto that on the TOC. Thetransmit power must be withinthe range that is supported bythe power amplifier lest thecell is unavailable.l When the sector works in

NO_TX_DIVERSITYmode, the maximumtransmit power range of thecell is:[TOC maximum outputpower of the poweramplifier - 10 dB, TOCmaximum output power ofthe power amplifier]

l When the sector works intransmit diversity mode or0.5/0.5 frequency mode, themaximum transmit powerrange of the cell is:An intersection of [TOC1maximum output power - 7dB, TOC1 maximum outputpower + 3 dB] and [TOC2maximum output power -7dB, TOC2 maximumoutput power + 3 dB].


430

Cell radius CellRadius The coverage is affected by thecell radius, which isrecommended to be set asdesigned according to thenetwork planning.Value range: 150 through180000

29000

Innerhandoverradius

CellInnerHandoverRadidus

The inner handover radius ofthe cell should not be greaterthan the cell radius. It isrecommended to be set asdesigned according to thenetwork planning.Value range: 0 through 180000

0




2-79


Desensitization intensity

Desensy This parameter needs to be setonly in cells of local andremote sectors. It is the ratio ofuplink noise intensity tobackground noise of thereceiver. This value is not usedwhen the sector is a distributedone. The data is determined inthe network planning, and it isconsistent with that at theRNC.Value range: 0 through 30

0

High-speedmovementmode

Hispm The data is determined in thenetwork planning, and it isconsistent with that at theRNC. Optional parameters:l FALSE (not high speed)

l TRUE (high speed)

FALSE

Rate in high-speedmovementmode

Spr This parameter is valid whenthe Hispm is set to TRUE. Thedata is determined in thenetwork planning, and it isconsistent with that at theRNC. Optional parameters:l 250

l 400

l 500

-

Ratio of thedefaulttransmitpower to theRRU

DefPowerLvl Cells in distributed sectorsneed the configuration.Value range: 10 through 100

100




Issue 01 (2008-06-25)

3 NodeB Initial Configuration

This describes how to add a NodeB on the CME.

Procedure

Step 1 Start the CME applications.

Step 2 Create an RNS.

Step 3 Open the RNS.

Step 4 Add a NodeB.

Option Description

4 Adding a NodeB Through the TemplateFile (Initial)

If the configuration type of the NodeB is oneof the typical configuration types defined intemplate files, this configuration mode ispreferred.

5 Adding a NodeB Through theConfiguration File (Initial)

If a configuration file that is applicable to theNodeB is available, this configuration modeis preferred.

6 Manually Adding a NodeB (Initial) Manually reconfigure the data after thetemplate file or the configuration file isimported. If you are familiar with the RANconfiguration, this configuration mode ispreferred.

----End

NodeBNodeB Initial Configuration Guide 3 NodeB Initial Configuration


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 typeof the NodeB is one of the typical configuration types of the template file.

4.1 NodeB Template FileThis defines the NodeB template file and describes the scenarios for using the file, the methodof 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 theNodeB.

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 physicalNodeB 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 theradio layer data of the physical NodeB based on the negotiated and planned data after you createthe 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 simultaneouslyupdate the Iub data at the RNC and the NodeB sides. If the Iub interface data is configured atthe RNC side, the data at the NodeB side is updated at the same time. Thus, the Iub data at boththe RNC and the NodeB sides can be consistent.

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


4-1

4.1 NodeB Template FileThis defines the NodeB template file and describes the scenarios for using the file, the methodof obtaining the file, and the role of the file in the CME.

DefinitionA NodeB template file contains a set of recommended data that is predefined with commonconfiguration types, demodulation modes, and Iub transmission modes to simplify NodeB dataconfiguration.

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 dataconfiguration as a template, which serves as a data source for future data configuration.

WARNINGThe default NodeB template provided by the CME cannot be modified.

Application ScenarioDuring NodeB initial configuration on the CME, import a NodeB template file according to theNodeB type. The NodeB template file facilitates NodeB data configuration.

Obtaining MethodThe NodeB template file is provided with the CME software. The file is available at CMEinstallation directory\WRANCMEV100R005\template\NodeB.

The NodeB template file is named in the form of transport protocol type_demodulationmode_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 NodeBTemplate File.

Role in the CMEThe NodeB template file can be a data source for NodeB data configuration on the CME.


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



Issue 01 (2008-06-25)

Scenario NodeB initial configuration

Mandatory/Optional

Mandatory

PrerequisiteThe RSS or the RBS is already configured.

Preparation


InputData

FieldName

Description Example

Source


1


the NodeBNodeB_Name


NodeB_1



l IP_TRANS

l ATMANDIP_TRANS

ATM_TRANS


Sharingsupport

SharingSupport




NON_SHARED



0



4-3

InputData

FieldName

Description Example

Source


RscMngMode


l EXCLUSIVE

SHARE

ATMAddress


H'3901010101010101010101010101010101010101

Hybridtransportflag

IPTransApartInd


l NOT_SUPPORT

-



10


IPApartTransDelay


-




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source



l FALSE

FALSE

NodeBtype

NodeBType


l PICO_TYPE1

l PICO_TYPE2

NORMAL

ProtocolVersion

ProtocolVer


l R4

l R5

l R6

R6

Procedure

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



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, parametersSharingSupport and CnOpIndex are configured according to scenarios. (Parameter CnOpIndex isvalid 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, parametersSharingSupport 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 theinformation 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 TemplateFile (Initial)

This describes how to create a physical NodeB by importing a NodeB template file. The physicalNodeB corresponds to an actual NodeB.





Issue 01 (2008-06-25)

Mandatory/Optional

Mandatory

Prerequisitel The logical NodeB is configured. For details, refer to 4.2 Creating a Logical NodeB

(Initial).l The NodeB template file with the same or similar configuration type acts as the data source.

Procedure


Step 2 Click . The Physical NodeB Basic Information window is displayed, as shown in Figure4-2.


Table 4-2 Description of the configuration pane

Sequence of dataconfiguration

Description

1 Logical NodeB list

2 "Create a physical NodeB" button

3 "Delete a physical NodeB" button



4-7


Description

4 Physical NodeB list

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

Figure 4-3 Create Physical NodeB dialog box

Step 4 Select the values in the Series and Version drop-down lists based on the prepared data, and thenselect 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 inthe NodeB Creating dialog box.

Step 6 After the template file is imported, the Information dialog box is displayed. Click OK, andinformation related to the configured physical NodeB is displayed in area 4.

----End



Mandatory/Optional

Optional

NOTE

After the physical NodeB is created through the template or the configuration file, you need to manuallyreconfigure the equipment layer data according to the actual network planning. The reconfigurationinvolves physical NodeB basic information, interface board addition or deletion, and RF modules or RRUaddition or deletion.After the physical NodeB is created through the template or the configuration file, you need to manuallyreconfigure the radio layer data according to the actual network planning. The reconfiguration involvescell frequencies, uplink/downlink resource groups, and power.




Issue 01 (2008-06-25)

PrerequisiteThe NodeB is created by importing a template file or a configuration file. For details, refer tothe 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).

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

Procedurel Reconfigure the equipment layer data.

The equipment layer data is reconfigured according to the NodeB type. For details, referto:– 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 (overATM) 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 simultaneouslyupdate the Iub data at the RNC and the NodeB sides. If the Iub interface data is configured atthe RNC side, the data at the NodeB side is updated at the same time. Thus, the Iub data at boththe RNC and the NodeB sides can be consistent.

Scenario NodeB initial configuration (The RNC and the NodeB is directly connectedwithout ATM switch inbetween.)

Mandatory/Optional

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



4-9

NOTE

l Whether to connect the RNC and the NodeB directly depends on actual scenarios. The Iub refreshingfunction 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 transportmode and the RNC is connected to the NodeB through an ATM switch. The Iub refreshing functiondetermines that the NodeB and the RNC are directly connected. The Iub refreshing function issupported. 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 theversion of the RNC matches that of the NodeB. If the versions on both the NodeB and the RNC sidesmatch, the data over the Iub interface on the RNC side can be synchronized to the NodeB side. For thematching relations, refer to Figure 4-4.

Figure 4-4 Matching relations

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

Preparationl 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 BasebandSubrack (Initial).

l For the distributed NodeB, the equipment layer is configured with the BBU with bearertype of ATM or IPv4. For details, refer to 6.4.2 Adding a BBU (Initial).




Issue 01 (2008-06-25)

Procedure

Step 1 On the main interface of the CME, click in the configuration object pane, and then clickNodeB CM Express in the configuration task pane. The NodeB CM Express window isdisplayed.

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 refreshedat a time.

Go to Step 5.

More than one target NodeB needs to berefreshed at a time.

1. In the NodeB Selection dialog box, clickFilter. The Select NodeB window isdisplayed, as shown in Figure 4-5.

2. In area 2, select multiple physical NodeBs,

and click . The physical NodeBsare added to area 1.

3. Click Close to return to the NodeBSelection window.



4-11

Figure 4-5 NodeB Selection window



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.




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

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



4-13

5 Adding a NodeB Through the ConfigurationFile (Initial)

About This Chapter

This describes how to add a NodeB through a configuration file if the configuration file isapplicable to the NodeB.

5.1 NodeB Configuration FileThis defines the NodeB configuration file and describes the scenarios for using the file, themethod of obtaining the file, and the role of the file in the CME.


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 physicalNodeB corresponds to an installed NodeB.



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


5-1

5.1 NodeB Configuration FileThis defines the NodeB configuration file and describes the scenarios for using the file, themethod of obtaining the file, and the role of the file in the CME.

DefinitionA NodeB configuration file contains a complete set of NodeB configuration data for properoperation of the NodeB.

The NodeB configuration file, also called NodeB XML file, is saved in .xml format.

Application ScenarioThe NodeB configuration file is used in the following scenarios:

l Export the NodeB configuration file to the NodeB LMT after the RAN configuration iscomplete 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 theCME server to synchronize the NodeB data in the CME with that on the existing network.

Obtaining MethodYou can obtain the NodeB configuration file by exporting all the NodeB data from the CME orobtain the file from the NodeB LMT.

Role in the CMEThe NodeB configuration file can be loaded to the NodeB. The file can be a data source forNodeB configuration on the CME.



Mandatory/Optional

Mandatory


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



Issue 01 (2008-06-25)

Preparation


InputData

FieldName

Description Example

Source


1


the NodeBNodeB_Name


NodeB_1



l IP_TRANS

l ATMANDIP_TRANS

ATM_TRANS


Sharingsupport

SharingSupport




NON_SHARED



0


RscMngMode


l EXCLUSIVE

SHARE



5-3

InputData

FieldName

Description Example

Source

ATMAddress


H'3901010101010101010101010101010101010101

Hybridtransportflag

IPTransApartInd


l NOT_SUPPORT

-



10


IPApartTransDelay


-



l FALSE

FALSE




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

NodeBtype

NodeBType


l PICO_TYPE1

l PICO_TYPE2

NORMAL

ProtocolVersion

ProtocolVer


l R4

l R5

l R6

R6

Procedure





5-5


NOTE








----End

5.3 Creating a Physical NodeB by Importing a ConfigurationFile (Initial)

This describes how to create a physical NodeB by importing a configuration file. The physicalNodeB corresponds to an installed NodeB.





Issue 01 (2008-06-25)

Mandatory/Optional

Mandatory

NOTE

l To import a NodeB configuration file, you have to conform to the following principle: A logical NodeBis available for each matching NodeB name in the configuration file to be imported. If the logicalNodeB that corresponds to the NodeB name in the importing NodeB configuration is unavailable, theCME 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 importedconfiguration data will overwrite the data of the existing physical NodeB.

Prerequisitel 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 . The Import NodeB window isdisplayed, as shown in Figure 5-2.



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, andthen click Search. The valid configuration file is displayed in the upper right pane, and theinvalid 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, adialog box is displayed to ask whether to create the logical NodeB. Click OK, and then enter the subracknumber 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, theInformation 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 Informationwindow.

----End



Mandatory/Optional

Optional




Issue 01 (2008-06-25)

NOTE

After the physical NodeB is created through the template or the configuration file, you need to manuallyreconfigure the equipment layer data according to the actual network planning. The reconfigurationinvolves physical NodeB basic information, interface board addition or deletion, and RF modules or RRUaddition or deletion.

After the physical NodeB is created through the template or the configuration file, you need to manuallyreconfigure the radio layer data according to the actual network planning. The reconfiguration involvescell frequencies, uplink/downlink resource groups, and power.

Prerequisite

The NodeB is created by importing a template file or a configuration file. For details, refer tothe 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).

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

Procedurel Reconfigure the equipment layer data.

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

– 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 (overATM) 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-9


Mandatory/Optional


NOTE








baseband interface board at the NodeB side.

l If the optical interface board is adopted, ensure that the NUTI is configured with thecorresponding sub-board.






Issue 01 (2008-06-25)


Procedure





Option Description


Go to Step 5.








5-11




Description







Issue 01 (2008-06-25)


NOTE






----End



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 atemplate file or a configuration file is imported.

Procedure

Step 1 6.1 Creating a Logical NodeB (Initial).

Step 2 NodeB Equipment Layer Datal 6.2 Adding Equipment Layer Data of the BTS3812AE/BTS3812A (Initial).

l 6.4 Adding Equipment Layer Data of the DBS3800 (Initial).

Step 3 NodeB Transport Layer Datal 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.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)

NodeBNodeB Initial Configuration Guide 6 Manually Adding a NodeB (Initial)


6-1

This describes how to configure the transport layer data of the NodeB in IP transport mode.


6.8 Adding Radio Layer DataThis describes how to configure radio network layer data for the NodeB. The related activitiesinvolve adding sites, adding sectors, and adding local cells.

6 Manually Adding a NodeB (Initial)NodeB



Issue 01 (2008-06-25)



Mandatory/Optional

Mandatory


Preparation


InputData

FieldName

Description Example

Source


1


the NodeBNodeB_Name


NodeB_1



l IP_TRANS

l ATMANDIP_TRANS

ATM_TRANS




6-3

InputData

FieldName

Description Example

Source

Sharingsupport

SharingSupport




NON_SHARED



0


RscMngMode


l EXCLUSIVE

SHARE

ATMAddress


H'3901010101010101010101010101010101010101




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Hybridtransportflag

IPTransApartInd


l NOT_SUPPORT

-



10


IPApartTransDelay


-



l FALSE

FALSE

NodeBtype

NodeBType


l PICO_TYPE1

l PICO_TYPE2

NORMAL

ProtocolVersion

ProtocolVer


l R4

l R5

l R6

R6



6-5

Procedure




NOTE








----End




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.

ContextOn the CME client, Figure 6-2 shows the panel of the BTS3812AE/BTS3812A.

Figure 6-2 BTS3812AE/BTS3812A panel



6-7

Table 6-2 Module information

SequenceNumber

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 isconfigured in subrack 3. The MAFU and MTRU must existin 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 isinstalled in slots 10 and 11 of the baseband subrack.

l NMON: NodeB Monitoring Unit, and is installed in slot 16of the baseband subrack.

l NBBI\HBBI\EBBI\EBOI: NodeB HSDPA supportedbaseband processing interface unit, and is inserted in slots 0and 1 in the baseband subrack.

l HULP/EULP: NodeB HSDPA supported uplink basebandprocessing interface unit, and is inserted in slots 2 and 7 inthe baseband subrack.

l HDLP/NDLP: NodeB HSDPA supported downlinkbaseband processing interface unit, and is inserted in slots 8and 9 in the baseband subrack.

l NDTI: NodeB Digital Trunk Interface Unit, and is installedin slots 12 and 13 of the baseband subrack.

l NUTI: NodeB Universal Transport Interface Unit, and isinstalled in slots from 12 to 15 of the baseband subrack.

5 Power module l NPSU: Power supply module

l NPMU: Power monitoring module

6 Battery The battery is configured in subrack 9.

6.2.1 Manually Creating a Physical NodeB (Initial)This describes how to manually configure the basic information for the NodeB.

6.2.2 Adding the Boards in the Baseband Subrack (Initial)This describes how to configure the boards in the baseband subrack of the macro NodeB. Theboards 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, MacroNodeB)This describes how to add an uplink or an downlink baseband resource group so as to reasonablyallocate the uplink or downlink baseband resources of the NodeB.

6.2.4 Adding an RRU (Initial, Macro NodeB)




Issue 01 (2008-06-25)

This describes how to add an RRU. The RRU is the outdoor RF remote unit. It is used to performfunctions 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 RFchannels for receiving and transmitting signals. Adding an RRU includes two parts: adding theRRU 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 andprovide 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. Thisdescribes 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). Thebatteries 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.



Mandatory/Optional

Mandatory

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



6-9

Preparation


InputData



E1T1WorkMode


E1


Clocksource






LINE


ClockWorkMode




MANUAL

Networkplanning




-

GPSfeederdelay


0 Internalplanning




Issue 01 (2008-06-25)

InputData


SNTPswitch




ON Networkplanning








10

Networkplanning

Demodulation mode





DEM_2_CHAN



6-11

InputData




l 1E-4

l 1E-5

l 1E-6

1E-5

Smoothpowerswitch

SMTHPWRSwitch


l CLOSE

CLOSE



0


0


ResAllocateRule



mode)

PERFFIRST

NodeB IPaddress


17.21.2.15

Subnetmask


255.255.0.0

NMPTbackupmode

NMPTBackupMode



STM-1framemode




mode)

-



FRAMEMODE_SDH

Management unit


l AU4

AU3




Issue 01 (2008-06-25)

InputData


Bypassunit



TU12



l 24 V DC

l 220 V AC

-48 V DC

Internalplanning



OFF





SHARING



6-13

InputData





SHARING

Procedure



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





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 dialogbox shows the importing progress.

Step 5 After the NodeB configuration file is imported, the Information dialog box is displayed. ClickOK to return to the Physical NodeB Basic Information window. The information of theconfigured physical NodeB is displayed on the right of the window.

Step 6 Select a physical NodeB, and then click . The NodeB Equipment Layer window isdisplayed, as shown in Figure 6-4.

Figure 6-4 NodeB Equipment Layer window

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

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

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

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


----End



6-15



Mandatory/Optional

Mandatory

NOTE

l Subrack 0 is for the baseband subrack.

l When configuring the NDTI/NUTI, ensure that the difference between MaxVPI and MinVPI is lessthan 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 PhysicalNodeB (Initial).

Preparation


InputData

FieldName





Internalplanning

NodeBmonitoringunit








Issue 01 (2008-06-25)

InputData

FieldName


Transportboards





Bearermode

BearMode


l IPV4

IPV4

IP clockswitch

IPClockSwitch


l DISABLE

ENABLE

Lineimpedance

LineImpedance




75



6-17

InputData

FieldName


HSDPAswitch

HsdpaSwitch






Procedure



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




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.

CAUTIONThe 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 E1Coverboard... from the shortcut menu.

The eight E1 ports on the E1 sub-board can be usedfor only the following elements:

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 ChannelledCoverboard... from the shortcut menu.

The 63 optical E1 ports on the channelized opticalsub-board are used for the following elements:


l UNI link

l TreeLink PVC

Add unchannelized optical sub-board. Right-click the NUTI and choose AddUnChannelled Coverboard... from the shortcutmenu.

The two optical ports on the channelized opticalsub-board are used for the following elements:

l Upper-level bandwidth for the SDT link or theUDT 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 onthe 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 andthe CMB (Initial, Macro NodeB)

This describes how to add an uplink or an downlink baseband resource group so as to reasonablyallocate the uplink or downlink baseband resources of the NodeB.


Mandatory/Optional

Mandatory




Issue 01 (2008-06-25)

NOTE

l When configuring the downlink resource group, check that local cells pertaining to this resource groupshould 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 uplinkresource group. Otherwise, the alarm, informing that the downlink resource group is not a subset ofthe 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 groupsby 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-frequencycells 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 thiscase, 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 isthe same. If all data sources are transferred over the Iub interface, it is a waste for the Iub resource. Withthe duplication function of the CME FACH, identical data sources are overlapped and will be transferredover the Iub interface as one data source. The NodeB fulfills the duplication of the CMB data betweencells. 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


InputData

FieldName



ULResourceGroupId




1

Internalplanning



6-21

InputData

FieldName



DLResourceGroupId




0

Procedurel 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 CMExpress window is displayed.

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

3. Select a physical NodeB, and then click . The NodeB Equipment Layer windowis displayed.

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




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

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

6. Click to save the settings.7. Select an uplink resource group in area 1, and select an uplink resource item in area

2. Click , the selected item is added to the selected uplink resource groupand is shown in area 3.

8. Click DLGroup. Repeat Step 5 through Step 7 to add one or multiple downlinkresource groups.

l (Optional) Configure the CMB.1. Click CMB in Figure 6-6, and configure SrcCellId, SrcFachId, DestCellId, and

DestFachId.



6-23

NOTE

l If the Iub transmission sharing function of the CMB service is required, the NodeB isrequired to support this function.

l One source FACH and several corresponding destination FACHs form a CMB FACHgroup.

l Before configuring the Iub transmission sharing function at the NodeB, ensure that thecorresponding CMB FACH group data is configured at the RNC. Otherwise, the normalservice may be affected.

l In one CMB FACH group, the source logical cell ID must be different from the destinationlogical 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 performfunctions 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 RFchannels for receiving and transmitting signals. Adding an RRU includes two parts: adding theRRU chain and adding the RRU module.


Mandatory/Optional

Optional

NOTE

l The RRUs are of the following types: MRRU, RHUB, and PRRU.

l If an RRU is required to be added to the branch, it must be the PRRU (PicoRRU) and the PRRU mustbe 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 Aantenna and supports two carriers.

The RRU is similar to the RF module in function. When RF modules such as the MTRU andMAFU are configured, at least one HBBI or NBBI is required; when the RRU is configured, atleast one EBOI is required. Based on the configured HBBI/NBBI/EBOI in slots 00 through 01of the baseband subrack, the NodeB can be configured with RF modules or RRUs, or both RFmodules and RRUs.

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




Issue 01 (2008-06-25)

Preparation


InputData


Chaintype



CHAIN

Internalplanning


Head SubrackNo.


0



0

Head portnumber


0

Endsubracknumber

End SubrackNo


-

End boardnumber


-

End portnumber


-



6-25

InputData


Breakposition 1

Break Position1




OFF




Issue 01 (2008-06-25)

InputData


Breakposition 2

Break Position2






-



6-27


InputData


RFModule






Networkplanning


Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock








Issue 01 (2008-06-25)

InputData








0

RRU IFoffset









MIDDLE


0



6-29

InputData



0


0


InputData



Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock




RHUB node)



0




Issue 01 (2008-06-25)

InputData



0


0

Procedure





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

Step 6 Right-click the added RRU Chain. Based on the actual network, choose Add MRRU..., AddRHUB... or Add PRRU... from the shortcut menu. Configure related parameters based onprepared data, and click OK to display the added MRRU, PRRU or RHUB.



6-31

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

----End



Mandatory/Optional

Optional

NOTE

l Subracks 2 and 3 are configured with RF modules.

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


Prerequisite

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

PreparationNone.

Procedure








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

----End



Mandatory/Optional

Optional

Prerequisite


PreparationNone.

Procedure




6-33




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. Thisdescribes how to add an NCMU for the BTS3812AE.





Issue 01 (2008-06-25)

Mandatory/Optional

Mandatory

NOTE

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

PrerequisiteThe physical NodeB is configured. For details, refer to 6.2.1 Manually Creating a PhysicalNodeB (Initial).

PreparationNone.

Procedure







6-35

Figure 6-10 Adding an NCMU.

Step 5 Right-click subrack 8, and choose Add Board... from the shortcut menu. Configure relatedparameters based on prepared data, and click OK to add the NCMU.

----End



Mandatory/Optional

Optional

Prerequisite


PreparationNone.




Issue 01 (2008-06-25)

Procedurel Add the NPMU to the BTS3812AE/BTS3812A.

NOTE

For the BTS3812A/BTS3812AE, the value of PowerType cannot be changed. You can use only thedefault value -48V DC.




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

Figure 6-11 Adding an NPMU

5. Right-click the lower left part of subrack 7, and choose Add Board... from the shortcutmenu. Configure related parameters based on prepared data, and click OK to add theNPMU.

l Modify the NPMU attributes in the BTS3812E.




4. Click the Basic Info tab. Click in the PowerType editing box, the NPMUAttribute 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. ClickOK 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 BTS3812Ecabinet. In these two cases, the BTS3812E has no NPMU, and the parameters in the NPMUAttribute 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.


Mandatory/Optional

Optional

NOTE

The NPSU is configured in any of the seven slots except the one that holds the NPMU of subrack 7. TheNPMU controls the status of the NPSU.

Prerequisite


PreparationNone.




Issue 01 (2008-06-25)

Procedure





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 thenchoose 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). Thebatteries are backup power facilities of the NodeB.


Mandatory/Optional

Optional

CAUTIONCapacity is the battery capacity parameter. The value of this parameter must be set as that ofthe actual capacity of the batteries. Otherwise, the batteries can be damaged. For details aboutthe actual capacity of the batteries, refer to the related instructions of the batteries.




6-39

PreparationNone.

Procedure





Figure 6-14 Adding Batteries

Step 5 Right-click subrack 9, and choose Add Board... from the shortcut menu. Configure relatedparameters based on prepared data, and click OK to add batteries.

----End



Mandatory/Optional

Optional




Issue 01 (2008-06-25)

NOTE

l Only the ALD that supports protocols such as AISG or 3GPP IUANT needs to be configured. TheALD can be configured on only the MAFU of subrack 3 for the macro NodeB or on the MRRU for thedistributed NodeB.

l In typical installation scenarios, you can add the ALD without manually entering the vendor codes orSNs, which can be obtained by scanning. In other installation scenarios, you are required to manuallyenter the vendor codes and SNs when adding the ALD. Otherwise, the system cannot communicatewith the ALD. The vendor codes and SNs must be entered at the same time. If only one of them isentered, the system provides a parameter illegality message.

l In 2G extended application scenarios, you are not required to configure the subrack number, the cabinetnumber, or the antenna connector number. In other scenarios, ensure that the configured subracknumber, the cabinet number, or the antenna connector number are consistent with the number of theequipment that the ALD is connected to. Otherwise, the mapping between the ALD and sector cannotbe determined.

Prerequisitel 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


InputData




N0A Networkplanning

DeviceName





6-41

InputData







REGULAR

Networkplanning





DUAL

Vendorcode


-

Internalplanning




Issue 01 (2008-06-25)

InputData




-







0






l Bypass mode

NORMAL

SASUgain

l GSMGain

l UMTSGain




0



6-43

InputData






UMTS



20

STMAgain


Procedure




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




Issue 01 (2008-06-25)

Figure 6-15 Adding the ALD

Step 5 Click the tab SINGLE_RET or MULTI_RET, and click . Configure related parameters

based on prepared data, and then click to add an RET.

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

to add an STMA.


to add an SASU.

Step 8 Click the RET_2G tab, and click . Set related parameters based on the prepared data, and

click to add an RET_2G.

----End

6.3 Adding Equipment Layer Data of the BTS3812E (Initial)This describes how to configure the equipment layer data of the BTS3812E.

ContextOn the CME client, Figure 6-16 shows the panel of the BTS3812E.



6-45

Figure 6-16 BTS3812E panel


SequenceNumber

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 isconfigured in subrack 3. The MAFU and MTRU must existin pairs.

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




Issue 01 (2008-06-25)

SequenceNumber

Module/Board Type

Description

3 Baseboard l NMPT: NodeB Main Processing and Timing Unit, and isinstalled in slots 10 and 11 of the baseband subrack.

l NMON: NodeB Monitoring Unit, and is installed in slot 16of the baseband subrack.

l NBBI\HBBI\EBBI\EBOI: NodeB HSDPA supportedbaseband processing interface unit, and is inserted in slots 0and 1 in the baseband subrack.

l HULP/EULP: NodeB HSDPA supported uplink basebandprocessing interface unit, and is inserted in slots 2 and 7 inthe baseband subrack.

l HDLP/NDLP: NodeB HSDPA supported downlinkbaseband processing interface unit, and is inserted in slots 8and 9 in the baseband subrack.

l NDTI: NodeB Digital Trunk Interface Unit, and is installedin slots 12 and 13 of the baseband subrack.

l NUTI: NodeB Universal Transport Interface Unit, and isinstalled in slots from 12 to 15 of the baseband subrack.



6.3.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, MacroNodeB)This describes how to add an uplink or an downlink baseband resource group so as to reasonablyallocate the uplink or downlink baseband resources of the NodeB.




6.3.7 Adding an NEMU (Initial, BTS3812E)This describes how to configure a NodeB Environment Monitoring Unit (NEMU) for theBTS3812E.



6-47


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 powerfacilities of the NodeB.




Mandatory/Optional

Mandatory

Prerequisite

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

Preparation


InputData



E1T1WorkMode


E1


Clocksource






LINE




Issue 01 (2008-06-25)

InputData



ClockWorkMode




MANUAL

Networkplanning




-

GPSfeederdelay


0 Internalplanning

SNTPswitch




ON Networkplanning



6-49

InputData









10

Networkplanning

Demodulation mode





DEM_2_CHAN



l 1E-4

l 1E-5

l 1E-6

1E-5

Smoothpowerswitch

SMTHPWRSwitch


l CLOSE

CLOSE




Issue 01 (2008-06-25)

InputData




0


0


ResAllocateRule



mode)

PERFFIRST

NodeB IPaddress


17.21.2.15

Subnetmask


255.255.0.0

NMPTbackupmode

NMPTBackupMode



STM-1framemode




mode)

-



FRAMEMODE_SDH

Management unit


l AU4

AU3

Bypassunit



TU12



6-51

InputData




l 24 V DC

l 220 V AC

-48 V DC

Internalplanning



OFF





SHARING




SHARING




Issue 01 (2008-06-25)

Procedure










6-53


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 FTPSPolicy based on the prepared data.

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

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


----End



Mandatory/Optional

Mandatory




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 lessthan or equal to 5.

l The bearer mode for the NUTIs in slots 14 and 15 cannot be set to IPV4.


Preparation


InputData

FieldName





Internalplanning

NodeBmonitoringunit





Transportboards







6-55

InputData

FieldName


Bearermode

BearMode


l IPV4

IPV4

IP clockswitch

IPClockSwitch


l DISABLE

ENABLE

Lineimpedance

LineImpedance




75




Issue 01 (2008-06-25)

InputData

FieldName


HSDPAswitch

HsdpaSwitch






Procedure






6-57


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.

CAUTIONThe 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 E1Coverboard... from the shortcut menu.

The eight E1 ports on the E1 sub-board can be usedfor only the following elements:


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 ChannelledCoverboard... from the shortcut menu.

The 63 optical E1 ports on the channelized opticalsub-board are used for the following elements:


l UNI link

l TreeLink PVC

Add unchannelized optical sub-board. Right-click the NUTI and choose AddUnChannelled Coverboard... from the shortcutmenu.

The two optical ports on the channelized opticalsub-board are used for the following elements:

l Upper-level bandwidth for the SDT link or theUDT 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 onthe 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 andthe CMB (Initial, Macro NodeB)

This describes how to add an uplink or an downlink baseband resource group so as to reasonablyallocate the uplink or downlink baseband resources of the NodeB.


Mandatory/Optional

Mandatory



6-59

NOTE







NOTE


Prerequisite

One of the following boards is added:

l the HULP/EULP and the HDLP/NDLP

l the NBBI, HBBI, EBBI, or EBOI

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

Preparation


InputData

FieldName



ULResourceGroupId




1

Internalplanning




Issue 01 (2008-06-25)

InputData

FieldName



DLResourceGroupId




0








6-61




Description









DestFachId.




Issue 01 (2008-06-25)

NOTE





----End



Mandatory/Optional

Optional

NOTE


l If an RRU is required to be added to the branch, it must be the PRRU (PicoRRU) and the PRRU mustbe 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 Aantenna and supports two carriers.


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



6-63

Preparation


InputData


Chaintype



CHAIN

Internalplanning


Head SubrackNo.


0



0

Head portnumber


0

Endsubracknumber

End SubrackNo


-

End boardnumber


-

End portnumber


-




Issue 01 (2008-06-25)

InputData


Breakposition 1

Break Position1




OFF



6-65

InputData


Breakposition 2

Break Position2






-




Issue 01 (2008-06-25)


InputData


RFModule






Networkplanning


Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock







6-67

InputData








0

RRU IFoffset









MIDDLE


0




Issue 01 (2008-06-25)

InputData



0


0


InputData



Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock




RHUB node)



0



6-69

InputData



0


0

Procedure





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





Issue 01 (2008-06-25)


----End



Mandatory/Optional

Optional

NOTE

l Subracks 2 and 3 are configured with RF modules.

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


Prerequisite

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

PreparationNone.

Procedure







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

----End



Mandatory/Optional

Optional

Prerequisite


PreparationNone.

Procedure





Issue 01 (2008-06-25)




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




6-73

Mandatory/Optional

Optional

NOTE

The NEMU is applicable only to the BTS3812E.


PreparationNone.

Procedure








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



Mandatory/Optional

Optional


PreparationNone.



6-75

Procedurel Add the NPMU to the BTS3812AE/BTS3812A.

NOTE

For the BTS3812A/BTS3812AE, the value of PowerType cannot be changed. You can use only thedefault value -48V DC.




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

Figure 6-25 Adding an NPMU

5. Right-click the lower left part of subrack 7, and choose Add Board... from the shortcutmenu. Configure related parameters based on prepared data, and click OK to add theNPMU.

l Modify the NPMU attributes in the BTS3812E.




4. Click the Basic Info tab. Click in the PowerType editing box, the NPMUAttribute 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. ClickOK 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 BTS3812Ecabinet. In these two cases, the BTS3812E has no NPMU, and the parameters in the NPMUAttribute 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.


Mandatory/Optional

Optional

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

PreparationNone.



6-77

Procedure





Figure 6-27 Adding an NPSU.

Step 5 Right-click in the blank area beyond the subrack area, and choose NPSU... from the shortcutmenu. The Board window is displayed. Configure related parameters based on prepared data,and then click OK to add an NPSU.

----End




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 powerfacilities of the NodeB.


Mandatory/Optional

Optional

CAUTIONCapacity is the battery capacity parameter. The value of this parameter must be set as that ofthe actual capacity of the batteries. Otherwise, the batteries can be damaged. For details aboutthe actual capacity of the batteries, refer to the related instructions of the batteries.


Physical NodeB (Initial).l Before adding the batteries for the BTS3812E, change the NPMU attributes. For details,

refer to Change the NPMU attributes for the BTS3812E.

PreparationNone.

Procedure







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. TheBoard window is displayed. Configure related parameters based on prepared data, and then clickOK to add batteries.

----End



Mandatory/Optional

Optional




Issue 01 (2008-06-25)

NOTE






Preparation


InputData




N0A Networkplanning

DeviceName





6-81

InputData







REGULAR

Networkplanning





DUAL

Vendorcode


-

Internalplanning




Issue 01 (2008-06-25)

InputData




-







0






l Bypass mode

NORMAL

SASUgain

l GSMGain

l UMTSGain




0



6-83

InputData






UMTS



20

STMAgain


Procedure








Issue 01 (2008-06-25)





to add an STMA.


to add an SASU.



----End

6.4 Adding Equipment Layer Data of the DBS3800 (Initial)This describes how to configure the equipment layer data of the distributed NodeB.

ContextOn the CME client, Figure 6-30 shows the DBS3800 panel.



6-85

Figure 6-30 DBS3800 panel


Module/BoardType

Description

BBU module l HBBU: indicates that the BBU type is BBU3806, which supportsUBTI and EBBC.

l HBBUC: indicates that the BBU type is BBU3806C, which does notsupport UBTI or EBBC.

l UBTI: Universal BBU Transport Interface board, which supports thechannelized optical sub-board and the unchannelized optical sub-board.

l EBBC: indicates the enhanced baseband card of the HBBU.


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

6.4.3 Adding an Uplink/Downlink Baseband Resource Group and the CMB (Initial, DistributedNodeB)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 areconfigured, and by specifying the ID of the DL resource group, the downlink baseband resourcesof the cell are configured. This describes how to add an uplink or an downlink baseband resourcegroup 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 performfunctions 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 RFchannels for receiving and transmitting signals. Adding an RRU includes two parts: adding theRRU chain and adding the RRU module.

6.4.5 Adding an NEMU (Initial, Distributed NodeB)




Issue 01 (2008-06-25)

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

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




Mandatory/Optional

Mandatory

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

Preparation


InputData



E1T1WorkMode


E1


Clocksource






LINE



6-87

InputData



ClockWorkMode




MANUAL

Networkplanning




-

GPSfeederdelay


0 Internalplanning

SNTPswitch




ON Networkplanning




Issue 01 (2008-06-25)

InputData









10

Networkplanning

Demodulation mode





DEM_2_CHAN



l 1E-4

l 1E-5

l 1E-6

1E-5

Smoothpowerswitch

SMTHPWRSwitch


l CLOSE

CLOSE



6-89

InputData




0


0


ResAllocateRule



mode)

PERFFIRST

NodeB IPaddress


17.21.2.15

Subnetmask


255.255.0.0

NMPTbackupmode

NMPTBackupMode



STM-1framemode




mode)

-



FRAMEMODE_SDH

Management unit


l AU4

AU3

Bypassunit



TU12




Issue 01 (2008-06-25)

InputData




l 24 V DC

l 220 V AC

-48 V DC

Internalplanning



OFF





SHARING




SHARING



6-91

Procedure











Issue 01 (2008-06-25)


Step 7 Click the Basic Info tab. Set the basic information of the NodeB.l Click the Basic tab. Set or modify the related parameters such as IP Attribute and FTPS

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

Switch based on the prepared data.l Click the DST tab. Set the time zone and DST-related parameters.


----End

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


Mandatory/Optional

Mandatory



6-93

NOTE

l On the Basic Info tab page of the NodeB Equipment Layer window, set the parameterClockSource to BITS, and the HBBUC cannot be added.

l The HBBU and the HBBUC should be inserted into their own slots as specified.


Preparation


InputData


Boardstatus

BoardStatus Blocking status of the board Optionalparameters:l Block

l Unblock

UnBlock

InternalplanningClock

sourceClockSource8K

E1/T1 ports for extracting the Iubinterface clock signals. Optionalparameters:l None

l Port 0 to port 7

Port 0

Bearermode

BearMode Optional parameters:l ATM: If the bearer mode is ATM,

the IP transport layer cannot usethe E1/T1 ports, that is, you cannotconfigure the PPP or MP links.

l IPv4: If the bearer mode is IPv4,the ATM transport layer cannotuse the E1/T1 ports, that is, youcannot configure the physicallinks.

ATM


HSUPAswitch

HSUPA Optional parameters:l ENABLE (The HSUPA is

supported)l DISABLE (The HSUPA is not

supported)

DISABLE




Issue 01 (2008-06-25)

InputData


ClockMode

ClockMode For the cascaded NodeBs, the clockof the upper-level NodeB is set toMASTER and that of the lower-levelNodeB is set to SLAVE. If the valueis not specified, the original clockmode is retained. Optionalparameters:l MASTER (primary mode)


SLAVE Networkplanning

Line Code LineCode Optional parameters:l HDB3 (for E1 mode)

l AMI (for E1 or T1 mode)

l B8ZS (for T1 mode)

HDB3


FrameStructure

FrameStru Optional parameters: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 T1mode)

E1_CRC4_MULTI_FRAME



6-95

InputData


HSDPAswitch






Time delaythreshold

HsdpaTD When the time delay is lower thanthis threshold, you can infer that thelink is not congested.Value range:0 to 20

4


HsdpaDR The link is not congested when frameloss ratio is not higher than thisthreshold.Value range:0 to 1000

1




Issue 01 (2008-06-25)

InputData


WorkingMode

WorkMode Optional parameters:l OFF (inhibited mode): indicates

that the port works in inhibitedmode, that is, the port does notdetect the alarms. All ports workin such mode by default.

l Default (default mode): indicatesthat the system detects and reportsthe alarms in default mode. In suchmode, the UE cannot set the alarmID of this port or other parametersrelated to this port. The systemreports alarms based on its ownfixed setting rather than the user-defined setting.

l CUSTOM (customized mode):indicates that the UE can changethe binding relation, that is, thesystem reports the alarm and setthe alarm Bool based on thecustomer specified ID.

OFF

Internalplanning

Alarm ID AlarmId This parameter is valid only whenWorkMode is set to CUSTOM.

-

Alarmvoltage

ALarmVoltage

This parameter is valid only whenWorkMode is set to CUSTOM.Optional parameters:l HIGH (alarms related to high

impedance)l LOW (alarms related to low

impedance)

-

Procedure





6-97



Figure 6-33 Adding the BBU

NOTE

l The DBS3800 supports only 2 cascaded BBUs. The BBUs can be configured in subrack 0 and subrack1.

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

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

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 theshortcut menu. Configure related parameters based on prepared data, and then click OK to adda channelized optical sub-board or an unchannelized optical sub-board.

----End

6.4.3 Adding an Uplink/Downlink Baseband Resource Group andthe 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 areconfigured, and by specifying the ID of the DL resource group, the downlink baseband resources




Issue 01 (2008-06-25)

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


Mandatory/Optional

Mandatory

NOTE







NOTE


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

Preparation


InputData

FieldName



ULResourceGroupId




1

Internalplanning



6-99

InputData

FieldName



DLResourceGroupId




0









Issue 01 (2008-06-25)




Description









DestFachId.



6-101

NOTE





----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 performfunctions 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 RFchannels for receiving and transmitting signals. Adding an RRU includes two parts: adding theRRU chain and adding the RRU module.


Mandatory/Optional

Mandatory


l If an RRU is required to be added to the branch, it must be the PRRU (PicoRRU) and thePRRU 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 onlyone A antenna and supports two carriers.


Preparation


InputData


Chaintype



CHAIN

Internalplanning


Head SubrackNo.


0




Issue 01 (2008-06-25)

InputData




0

Head portnumber


0

Endsubracknumber

End SubrackNo


-

End boardnumber


-

End portnumber


-



6-103

InputData


Breakposition 1

Break Position1




OFF




Issue 01 (2008-06-25)

InputData


Breakposition 2

Break Position2






-



6-105


InputData


RFModule




l In 6 x 1 configuration,configure six RFmodules.


Networkplanning


Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock




RHUB node)





Issue 01 (2008-06-25)

InputData



RTWPofCarrierCarriernumberonRxRXchannel number



l RX channel number: 0through 1


0

RRU IFoffset









MIDDLE


0



6-107

InputData



0


0


InputData



Internalplanning

RRU chainnumber


0

RRUnumber


2

Boardstatus


l Unblock

UnBlock




RHUB node)



0




Issue 01 (2008-06-25)

InputData



0


0

Procedure





Figure 6-35 Adding an RRU (DBS3800)

Step 5 Right-click the configured HBBU or HBBUC, and then choose Add RRUChain... from theshortcut menu. Configure related parameters based on prepared data, and then click OK todisplay the added RRU Chain.




6-109


----End

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


Mandatory/Optional

Optional

NOTE

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


PreparationNone.

Procedure








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 theshortcut menu. Configure related parameters based on prepared data, and then click OK to addan NEMU.

----End

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


Mandatory/Optional

Optional

NOTE

l You may add the NPMU only in slot 00 of subrack 0 of the DBS3800 cabinet.

l You may the NPMU for the RRU (MRRU). One MRRU, however, can be configured with only oneNPMU.

Prerequisitel 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, DistributedNodeB).

PreparationNone.

Procedure




6-111



Step 4 Click the tab Device Panel, and add an NPMU in the DBS3800 cabinet, as shown in Figure6-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 parametersbased 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 AddNPMU... from the shortcut menu. Configure related parameters based on prepared data, andthen click OK to add an NPMU for the RRU.

----End





Issue 01 (2008-06-25)


Mandatory/Optional

Optional

NOTE






Preparation


InputData




N0A Networkplanning

DeviceName





6-113

InputData







REGULAR

Networkplanning





DUAL

Vendorcode


-

Internalplanning




Issue 01 (2008-06-25)

InputData




-







0






l Bypass mode

NORMAL

SASUgain

l GSMGain

l UMTSGain




0



6-115

InputData






UMTS



20

STMAgain


Procedure








Issue 01 (2008-06-25)





to add an STMA.


to add an SASU.



----End

6.5 Manually Adding the Transport Layer Data of the NodeB(over ATM)

This describes how to configure the transport layer data of the NodeB in ATM transport mode.

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



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 toconfigure at least one type from among the IMA group, IMA link, UNI link, and Fractional ATMlink. 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 thebandwidth of the physical link to the transmission resource group for carrying the data on thecontrol plane, the user plane, and the OM channel. Each group occupies one portion of thebandwidth 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 ALCAPwhen 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 ControlPort (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 theNodeB. 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 planedata 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 betweenthe 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 toconfigure at least one type from among the IMA group, IMA link, UNI link, and Fractional ATMlink. 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 modeover the TC sub-layer of the ATM physical layer. The IMA technology multiplexes multiplelow-speed links for transmitting high-speed ATM cell flows, so as to achieve wideband ATMtransmission.

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 linkuses all the timeslots of an E1/T1 port. This describes how to add UNI links.

6.5.1.3 Adding Fractional ATM Links (Initial)




Issue 01 (2008-06-25)

The fractional ATM is a transmission mode over the TC sub-layer of the ATM physical layerand 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 betransmitted over the 3G network. The CES links use either Structured Data Transfer (SDT) modeor Unstructured Data Transfer (UDT) mode. This describes how to configure the SDT CES orUDT CES link. The Circuit Emulation Service (CES) provides the transmission channel forGSM services to be transmitted over the 3G network. The CES links use either Structured DataTransfer (SDT) mode or Unstructured Data Transfer (UDT) mode. This describes how toconfigure the SDT CES or the UDT CES link. The SDT CES and the UDT CES are onlyconfigured 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 thedata 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 modeover the TC sub-layer of the ATM physical layer. The IMA technology multiplexes multiplelow-speed links for transmitting high-speed ATM cell flows, so as to achieve wideband ATMtransmission.


Mandatory/Optional

Optional

NOTE

l After the IMA group is created, you can add the IMA links in the IMA group.

l The IMA links and the matching IMA group should be configured on the same baseboard or subboard.

l The E1/T1 ports used by the ATM link, UNI link, fractional ATM link, timeslot cross and CES linkshould not conflict.

l A maximum of four IMA groups can be configured on the same baseboard or E1 coverboard. Eachchannelized 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 IMAgroup 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 E1coverboard does not exceed eight.

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

l The total number of IMA groups and UNI links on the same channelized optical subboard does notexceed two.


Physical NodeB (Initial).

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



6-119

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

InputData



14

Internalplanning

Sub-boardtype

SubBdType Type of the sub-board where the E1/T1 port used by the IMA link islocated Optional parameters:l Baseboard




IMA groupID

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

l When SubBdType is E1CoverBoard, the value range is 0through 3.


0

Transmitframelength

IMATxFrameLength

Longer transmit frame can enhancetransmission efficiency but reduceserror sensitivity. Therefore, thedefault value is recommended.Optional parameters:l D32

l D64

l D128

l D256

D128




Issue 01 (2008-06-25)

InputData


Minimumactive links

IMAMinActiveLinks

Threshold for identifying theavailability of the IMA group Forexample, if the value is 3, there are atleast three active IMA links in anIMA group and thus this group isavailable. If there are less than threeactive links, the IMA group isunavailable.l When SubBdType is BaseBoard,




1

Differential maximumdelay

IMADiffMaxDelay

Different transmission links in anIMA group may result in differenttransmission delays. Thus, there is achange in the relative delay betweenlinks, which is called link differentialdelay. The LODS alarms are reportedwhen the link differential delayoccurs.Value range: 4 through 100

25

Scramblemode

ScrambleMode




ENABLE

Timeslot16 support

TimeSlot16 The channelized optical sub-boarddoes not support this function.Optional parameters:l ENABLE

l DISABLE

After this parameter is enabled, thebandwidth of each IMA link in theIMA group is added by 64 kbit/s.

DISABLE



6-121

InputData


Linknumber

LinkNo Number of the E1/T1 ports for thelinks in an IMA group.l When SubBdType is BaseBoard,




0, 1, 2 Negotiation withthedestination

HSDPAswitch

HsdpaSwitch

Optional parameters:l SIMPLE_FLOW_CTRL: Based





Internalplanning

Time delaythreshold


4




Issue 01 (2008-06-25)

InputData




1

Procedurel Add the IMA group and the IMA link individually.



3. Select a physical NodeB, and then click . The NodeB ATM Transport Layerwindow is displayed.

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

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

5. Select SubrackNo, and click . The Search Iub Board window is displayed, asshown in Figure 6-41.



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. Selectan E1/T1 port, and then click OK to return to the NodeB ATM Transport Layer

window. Click to add an IMA link.l Add UNI groups and links in bulk.

1. In the NodeB ATM Transport Layer window, click . The NodeBATM 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



Description

1 IMA group list

2 Available E1/T1 port on the interface board where the IMAgroup is configured

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

2. In area 1, select an IMA group; in area 2, select an E1/T1 port, and then click

to add an IMA link.

----End

Adding UNI Links (Initial)The UNI is a transmission mode over the TC sub-layer of the ATM physical layer. A UNI linkuses all the timeslots of an E1/T1 port. This describes how to add UNI links.


Mandatory/Optional

Optional



6-125

NOTE

l The E1/T1 ports used by the ATM link, UNI link, fractional ATM link, timeslot cross and CES linkshould not conflict.

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

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

l The total number of IMA groups and UNI links on the same channelized optical subboard does notexceed two.


Physical NodeB (Initial).l The NDTI/NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the

Boards in the Baseband Subrack (Initial).l The BBU of the distributed NodeB is configured, as described in 6.4.2 Adding a BBU

(Initial).

Preparation

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

InputData


Slot No. SlotNo Number of slot where the NDTIor NUTI is held (Slots 14 and 15hold only the NUTI)Value range: 12 through 15

12

Internalplanning

Sub-boardtype

SubBdType Type of the sub-board where theE1/T1 port is located by the UNIlink Optional parameters:l Baseboard

l E1 CoverBoard: E1coverboard


BaseBoard




Issue 01 (2008-06-25)

InputData


Linknumber

LinkNo Number of the E1/T1 ports forUNI linksl When SubBdType is

BaseBoard, the value range is0 through 7.

l When SubBdType is E1CoverBoard, the value range is0 through 7.

l When SubBdType isChannelled CoverBoard, thevalue range is 0 through 62.

3 Negotiationwith thedestination

Scramblemode

ScrambleMode




ENABLE

InternalplanningTimeslot

16 supportTimeSlot16 The channelized optical sub-

board does not support thisfunction. Optional parameters:l ENABLE

l DISABLE

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

DISABLE



6-127

InputData


HSDPAswitch

HsdpaSwitch

Optional parameters:l SIMPLE_FLOW_CTRL:

Based on the configured Iubbandwidth and the bandwidthoccupied by R99 users, trafficis allocated to HSDPA userswhen the physical bandwidthrestriction is taken intoaccount.

l AUTO_ADJUST_FLOW_CTRL: According to the flowcontrol ofSIMPLE_FLOW_CTRL,traffic is allocated to HSDPAusers when the delay andpacket loss on the Iub interfaceare taken into account. TheRNC uses the R6 switch toperform this function. It isrecommended that the RNC beused in compliance with the R6protocol.

l NO_FLOW_CTRL: TheNodeB does not allocatebandwidth according to theconfiguration or delay on theIub interface. The RNCallocates the bandwidthaccording to the bandwidth onthe Uu interface reported bythe NodeB. To perform thisfunction, the reverse flowcontrol switch must be enabledby the RNC.


Time delaythreshold

HsdpaTD When the time delay is lower thanthis threshold, you can infer thatthe link is not congested.Value range: 0 through 20

4



1




Issue 01 (2008-06-25)

Procedurel Add the IMA group and the IMA link individually.




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

Figure 6-43 Configure the UNI links individually.

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

window. Click to add an UNI link.l Add UNI groups and links in bulk.

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



6-129

Figure 6-44 Configure the UNI links in batches.



Description

1 Available E1/T1 port for the UNI link on the configured Iubinterface board

2 E1/T1 port assigned to the UNI link

2. In area 1, select an E1/T1 port, and then click to add one UNI link.

----End

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


Mandatory/Optional

Optional




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 inslots 12 through 15.

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

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

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


Physical NodeB (Initial).

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


Preparation

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

InputData



13

InternalplanningSub-board

typeSubBdType Type of the sub-board with the E1/

T1 port available for the fractionalATM link Optional parameters:Baseboard

BaseBoard

Port No. E1T1No Number of the E1/T1 port availablefor the fractional ATM linkValue range: 0 through 1

0 Negotiation with thedestination

Linknumber

LinkNo Value range: 0 through 7 1 Internalplanning

Timeslots TSBitMap The fractional ATM link providestimeslots for the 3G equipment. Ifport 0 is configured, the timeslotsmust be reserved for timeslot crossconnection.Value range: TS1 to TS31

TS24 toTS31 Negotiatio

n with thedestination



6-131

InputData


Scramblemode

ScrambleMode




ENABLE

Internalplanning

HSDPAswitch


on the configured Iub bandwidthand the bandwidth occupied byR99 users, traffic is allocated toHSDPA users when the physicalbandwidth restriction is takeninto account.

l AUTO_ADJUST_FLOW_CTRL: According to the flow controlof SIMPLE_FLOW_CTRL,traffic is allocated to HSDPAusers when the delay and packetloss on the Iub interface are takeninto account. The RNC uses theR6 switch to perform thisfunction. It is recommended thatthe RNC be used in compliancewith the R6 protocol.

l NO_FLOW_CTRL: The NodeBdoes not allocate bandwidthaccording to the configuration ordelay on the Iub interface. TheRNC allocates the bandwidthaccording to the bandwidth onthe Uu interface reported by theNodeB. To perform thisfunction, the reverse flow controlswitch must be enabled by theRNC.


Time delaythreshold


4



1




Issue 01 (2008-06-25)

Procedure



Step 3 Select a physical NodeB, and then click . The NodeB ATM Transport Layer window isdisplayed.

Step 4 Click ATMPort, and then click the Fractional ATM tab. The tab page is displayed, as shownin 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 thetimeslot to be used, and then click OK to return to the NodeB ATM Transport Layer window.

NOTE

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

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

----End



6-133

Adding SDT CES or UDT CES Link (Initial)The Circuit Emulation Service (CES) provides the transmission channel for GSM services to betransmitted over the 3G network. The CES links use either Structured Data Transfer (SDT) modeor Unstructured Data Transfer (UDT) mode. This describes how to configure the SDT CES orUDT CES link. The Circuit Emulation Service (CES) provides the transmission channel forGSM services to be transmitted over the 3G network. The CES links use either Structured DataTransfer (SDT) mode or Unstructured Data Transfer (UDT) mode. This describes how toconfigure the SDT CES or the UDT CES link. The SDT CES and the UDT CES are onlyconfigured in the macro NodeB.


Mandatory/Optional

Optional

NOTE

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

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

l The bandwidth of the SDT or UDT CES link must be lower than that of the physical bearer link. TheUDT CES link occupies relatively high bandwidth. Only the IMA link can be used as the physicalbearer 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


Physical NodeB (Initial).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

InputData

FieldName


Port type Type Type of the interface that carries theSDT CES channels Optionalparameters:l FRAATM

l IMA

l UNI

l STM1

FRAATM

Internalplanning

Source slotNo.


12




Issue 01 (2008-06-25)

InputData

FieldName


Sourcesub-boardtype

SubBdType

Type of the sub-board where thesource E1/T1 port is located by theSDT CES channel Optionalparameters: Baseboard

BaseBoard

Source portNo.

PortNo Number of the source E1/T1 ports forthe SDT CES channelValue range: 0 through 1

0

Partial filllevel

PFL ATM cell has 48-byte payloads.Except for the first byte, the other 47bytes can be used to transmit timeslotsignals. Each timeslot occupies onebyte. The number of filling bytes isthat of valid bytes filled in each ATMcell.Value range: 4 through 47, and thevalue should be greater than thenumber of selected timeslots exceptfor slot 0.

47

Timeslots TSBitMap Timeslot 0 is unavailable.Value range: TS1 to TS31

TS1 toTS7



13


SubBdType

Type of the sub-board where thedestination E1/T1 port is located bythe SDT CES channel Optionalparameters:l Baseboard




BaseBoard



6-135

InputData

FieldName



E1T1No Number of the destination E1/T1 portfor the SDT CES channel (Thisparameter is valid only when Type isset to FRAATM or UNI).l When Type is set to FRAATM and




0

Link No./IMA ID

LinkNo/IMAId

Number of the fractional ATM or UNIlink, of the IMA group, or of the STM1optical port that carries the SDT CESchannel.l When Type is set to FRAATM and




l When Type is set to IMA andSubBdType(destination sub-boardtype) is BaseBoard or E1CoverBoard, the value range is 0through 3.



0




Issue 01 (2008-06-25)

InputData

FieldName



VPI Identifier of the virtual channel for theSDT CES channel.Value range: 0 through 31 (sixsuccessive values from 0 to 31)

1


VCI Identifier of the virtual channel for theSDT CES channel.l When the interface board is the



32

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

InputData

FieldName


Port type Type Type of the interface that carries theUDT CES channel Optionalparameters:l IMA

l STM1

IMA

Internalplanning

Source slotNo.


12

Sourcesub-boardtype

SubBdType

Type of the sub-board where thesource E1/T1 port is located by theUDT CES channel Optionalparameters: Baseboard

BaseBoard

Source portNo.

PortNo Number of the source E1/T1 ports forthe UDT CES channelValue range: 0 through 1

1



6-137

InputData

FieldName


Partial filllevel

PFL The value of the partial fill levelaffects both the transmissionbandwidth and the transmission delay.When the value reaches the maximumof 47, the transmission bandwidth isnot affected, and the transmissiondelay reaches the maximum value;when the value is smaller than 47, thetransmission bandwidth equals to theoriginal transmission bandwidth x (53/PFL), and the transmission delay isreduced. In order not to affect thetransmission bandwidth, set thedefault value to 47.Value range: 4 through 47

47

Tx ClockMode

TxClockMode

Optional parameters:l NOACM (non-adaptive clock

mode)l NOACM (adaptive clock mode)

ACM



14


SubBdType

Type of the sub-board where thedestination E1/T1 port is located bythe UDT CES channel Optionalparameters:l Baseboard








Issue 01 (2008-06-25)

InputData

FieldName


Opticalport No./IMA ID

LinkNo/IMAId

Number of the IMA group or STM1optical port that carries the UDT CESchannel.l When Type is set to IMA and

SubBdType(destination sub-boardtype) is BaseBoard or E1CoverBoard, the value range is 0through 3.



0


VPI Identifier of the virtual channel for theUDT CES channel.Value range: 0 through 31 (sixsuccessive values from 0 to 31)

1


VCI Identifier of the virtual channel for theUDT CES channel.l When the interface board is the



32

Procedurel Configure the SDT CES links.




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



6-139

Figure 6-46 Configuring the SDT CES links



Description

1 Physical bearer link

2 SDT CES configuration area

5. In area 1, select a physical bearer link; In area 2, select SubrackNo and then click, the Search E1/T1 Port window is displayed. Select an E1/T1 port, and click

OK to return to the NodeB ATM Transport Layer window.

NOTE

The SDT and UDT CES each inclusively occupies an E1/T1 port, and thus the CMEautomatically 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 ATMTransport Layer window.

NOTE

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

7. Configure other parameters based on the prepared data, and then click to add anSDT CES link.

l Configure the UDT CES links.

1. In the NodeB ATM Transport Layer window, click the UDT tab, as shown in Figure6-47.




Issue 01 (2008-06-25)

Figure 6-47 Configuring the UDT CES links



Description

1 Physical bearer link (The system automatically filters theIMA link.)

2 UDT CES configuration area

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

NOTE

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

3. Configure other parameters based on the prepared data, and then click to add anSDT CES link.

----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 thedata of services on the 3G network.




6-141

Mandatory/Optional

Optional

NOTE

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

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

l The source and destination ports of the timeslot cross channel must be different, and the same E1/T1port 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 fractionalATM link timeslot that is configured to either E1/T1 2 or 3.

PrerequisiteThe negotiation and planned data is ready.

Preparation


InputData

FieldName


Source slotNo.


13

Internalplanning

Sourceport No.


3

Sourcetimeslots



DestSlotNo


13


DestPortNo


0




Issue 01 (2008-06-25)

Procedure




Step 4 Click Network, and then click the TSCross tab. The tab page is displayed, as shown in Figure6-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 SearchE1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeBATM Transport Layer window.




6-143

NOTE


Step 7 Configure other parameters based on the prepared data, and then click to add a timeslotcross channel.

----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 thebandwidth of the physical link to the transmission resource group for carrying the data on thecontrol plane, the user plane, and the OM channel. Each group occupies one portion of thebandwidth and has separate access control, congestion control and HSPA flow control.


Mandatory/Optional

Optional. The configuration is required only when the SAAL links, the AAL2PATH 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 totalnumber of transmission groups over ATM and IP.

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

l The transmit bandwidth of the transmission resource group should be not greater than the idlebandwidth 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)

InputData

FieldName

Description Example

Source

Port type Type Type of the interface that carries thetransmission resource group Optionalparameters:l FRAATM

l IMA

l UNI

l STM1

IMA

Internalplanning




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Resourcegroupnumber


Transmitbandwidth

TxBandwidth

The transmit bandwidth of the resourcegroup cannot exceed the bandwidth ofthe port to which the resource groupbelong.Value range: 32 through 15800

5000

Receivebandwidth

RxBandwidth

Receive bandwidth of the resourcegroup.Value range: 30 through 20000

5000

Procedure




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



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 to add a transmissionresource group over ATM.

----End

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


Mandatory/Optional

Mandatory




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 physicallink 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 orequal to the bandwidth of the transmission resource group.

Prerequisitel 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

InputData

FieldName

Description Example

Source

Port type Type Type of the interface that carries theSAAL links Optional parameters:l FRAATM

l IMA

l UNI

l STM1

IMA



VPI Identifier of the virtual channel for theSAAL links.Value range:l Macro NodeB: 0 through 31 (six


1


VCI Identifier of the virtual channel for theSAAL links.Value range:l Macro NodeB: 32 through 255


34



6-147

InputData

FieldName

Description Example

Source

Servicetype

ServiceType

When this parameter is set to CBR orUBR, you need to set only theparameter PCR; when this parameteris set to RTVBR or NRTVBR, youneed to set parameters SCR and PCR;when this parameter is set to UBR+,you need to set parameters PCR andMCR.Optional parameters:l CBR (applicable to the CES





RTVBR

Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than thatof the SCR or MCR.l When the service type is CBR or



200

Minimumcell rate

MCR The value of the MCR of the ATMchannel should be smaller than that ofthe PCR. This parameter is valid onlywhen the service type is UBR+.Value range: 30 through 6759

-



180




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source


JoinRscgrp Specify whether this link should beadded to the resource group. Optionalparameters:l DISABLE

l ENABLE

ENABLE

Internalplanning

Resourcegroupnumber


1

Procedure




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

Figure 6-50 Configuring the SAAL



6-149



Description


2 Transmission resource group carried on the corresponding physicallink

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 ResourceGroup window is displayed. Select a transmission resource group, and click OK to return tothe NodeB ATM Transport Layer window.

NOTE

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

Step 7 Configure other parameters based on the prepared data, and then click to add an SAALlink.

----End

6.5.4 Adding an NBAP (Initial)This describes how to configure the NodeB Control Port (NCP) and Communication ControlPort (CCP). These two ports are carried on the SAAL links.


Mandatory/Optional

Mandatory

NOTE

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

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

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

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




Issue 01 (2008-06-25)

Preparation

Table 6-44 Negotiation and planned data of the NBAP


Description Example

Source

NCP


l CCP

NCPInternalplanning

SAALnumber

SAALNo SAAL number that carries theNCPValue range: 0 through 63



l MASTER

MASTER

Internalplanning

CCP


l CCP

CCPInternalplanning


0


SAALnumber

SAALNo SAAL number that carries theCCPValue range: 0 through 63

2


l MASTER

MASTER

Internalplanning



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

parameters based on prepared data, and then click 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 . Configure related

parameters based on prepared data, and then click to add an CCP link.

----End

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


Mandatory/Optional

Mandatory

NOTE

l One NodeB can be configured with multiple adjacent nodes.

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

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

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

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

InputData

FieldName


Node type NodeType The exchange node must be configuredbefore configuring the adjacent node.The exchange node cannot be carried onthe SAAL link on the NDTI. Optionalparameters:l LOCAL (peer node)

l HUB (switch node, indicating thatthe NodeB has a lower-level NodeB)

l ADJNODE (adjacent node,indicating the lower-level NodeB)

LOCAL

Internalplanning



6-153

InputData

FieldName


Adjacentnodeidentifier

ANI Identify an adjacent node. Thisparameter is valid only when theparameter NodeType is set toADJNODE.Value range: 0 through 31

-

Networkserviceaccesspoint

NSAP The full name is: Net service accesspoint.When the NodeB uses ATMtransmission, the NSAP is the addressof the NodeB that is connected to theAAL2 path. The address is ahexadecimal with a length of 20 bytes(excluding the prefix H').

H'3901010101010101010101010101010101010101

SAALnumber

SAALNo SAAL number that carries the ALCAPValue range: 0 through 63

3

Procedure




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




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 theRNC 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 planedata between the RNC and other equipment.


Mandatory/Optional

Mandatory



6-155

NOTE

l Each NDTI board can be configured with a maximum of 16 AAL2 PATH; Each NUTI board can beconfigured 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 physicallink that carries the AAL2 path.

l If a physical port is configured with the transmission resource groups, all the AAL2 paths should beadded to a certain transmission resource group, and the PCR of the AAL2 path should be less than thebandwidth 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 resourcegroup. No transmission resource group can be added to this physical port.

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

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

Preparation

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

InputData

FieldName


Port type Type Type of the interface that carries theAAL2 PATH Optional parameters:l FRAATM

l IMA

l UNI

l STM1

IMA


PATH type PathType Type of the AAL2 path, whichindicates the desired service typecarried on the path. Optionalparameters: RT, NRT, HSPA_RT,HSPA_NRT

RT


VPI Identifier of the virtual channel for theAAL2 path.Value range:l Macro NodeB: 0 through 31 (six


1




Issue 01 (2008-06-25)

InputData

FieldName



VCI Identifier of the virtual channel for theAAL2 path.Value range:l Macro NodeB: 32 through 255


37

Servicetype

ServiceType






RTVBR

Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than that ofthe SCR. This parameter should be oneof the bandwidth parameters for thetransmission direction.l When the sub-board type is

BaseBoard, and the service type isCBR or UBR, the value range is 30through 15800.

l When the sub-board type isChannelled CoverBoard orUnchannelled CoverBoard, and theservice type is RTVBR,NRTVBR,or UBR+, the value rangeis 31 through 15800.

1920



6-157

InputData

FieldName



SCR The value of the SCR of the ATMchannel should be smaller than that ofthe PCR. This parameter is valid onlywhen the service type is RTVBR orNRTVBRThis parameter should beone of the bandwidth parameters for thetransmission direction.l When sub-board type is BaseBoard,

the value range is 30 through 15799.l When the sub-board type is

Channelled CoverBoard orUnchannelled CoverBoard, thevalue range is 30 through 6759.

960

Receivedcell rate

RCR This parameter must be consistent withthe downlink bandwidth configured bythe RNC. This parameter acts as animportant factor in flow control by theNodeB receive bandwidth. Whether ornot this parameter is correctlyconfigured will affect the effect of flowcontrol.Value range: 64 through 20000

2048



l ENABLE

ENABLE

Internalplanning

Resourcegroupnumber


1

Procedure






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



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 transmissionresource 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 andTable 6-49 show the matching relation.




6-159

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

NOTE

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

l If the service type is UBR+, the value of the parameter should meet the following condition: MCR<PCRand 0<MCR<PCR<=bandwidth configured for the RSCGRP

----End

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


Mandatory/Optional

Optional

NOTE

l In ATM transport mode, only one OMCH can be configured. It can be either active or standby. If theconfigured 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 physicallink that carries the OMCH.

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

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




Issue 01 (2008-06-25)

Preparation

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



Port type Type Type of the interface that carries theOMCH Optional parameters:l FRAATM

l IMA

l UNI

l STM1

UNI



VPI Virtual channel for the OMCHValue range:l Macro NodeB: 1 or within the VPI

range of the actual boardconfiguration

l Distributed NodeB: 0 through 29

1


VCI Virtual channel for the OMCHValue range:l Macro NodeB: 32 through 255


33

Service type ServiceType






CBR

Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than that ofthe SCR.l When the service type is CBR or



512



6-161





-

Local IPaddress ofthe OMCH

LocalIP IP address for NodeB remotemaintenance

10.1.2.10

DestinationIP addressof theOMCH

DestIP Destination IP address for NodeBremote maintenance, that is, the IPaddress configured on the ATMinterface board at the RNC.

10.1.2.1

Destinationsubnet maskof theOMCH

DestIPMask

Subnet mask of the destination IPaddress for NodeB remote maintenance

255.255.255.0



l ENABLE

ENABLE

Internalplanning

Resourcegroupnumber


2

Flag Flag Master/slave flag for the remote OMchannels Optional parameters:l SLAVE

l MASTER

MASTER

Procedure






Issue 01 (2008-06-25)


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

Figure 6-54 Adding an OMCH



Description



3 OMCH configuration area

Step 5 In area 1, select the physical bearer link. Then the transmission resource group carried on thisphysical link is displayed in area 2.

Step 6 In area 3, select LocalIP, and click , the LocalIP & Mask dialog box is displayed. Set thepeer IP address and the mask of the OMCH, and then click OK to return to the NodeB ATMTransport Layer window.

Step 7 Select DestIP, and click . The IP and IP Mask dialog box is displayed. Set the peer IP addressand the mask of the OMCH, and then click OK to return to the NodeB ATM TransportLayer window.




6-163

NOTE

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

Step 9 Configure other parameters based on the prepared data, and then click to add an OMCHlink.

----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 betweenthe upper-level NE and the lower-level NE.


Mandatory/Optional

Optional

NOTE

l The source port and the destination port must be different.

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

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

PrerequisiteThe 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

InputData


Source

Source porttype

SourceType Type of the interface that carries thesource port of the treelink PVCOptional parameters:l FRAATM

l IMA

l UNI

l STM1

FRAATM

Internalplanning




Issue 01 (2008-06-25)

InputData


Source

Destination port type

DestinationType

Type of the interface that carries thedestination port of the treelink PVCOptional parameters:l FRAATM

l IMA

l UNI

l STM1

UNI

ByPassMode

ByPassMode When the NodeB is powered off orexceptions occur to the NodeB, theE1/T1 can be connected to the lowernode by switching to theByPassMode. The treelink PVC is setusing the ByPassMode that thusguarantees the connection betweenthe lower node and the RNC. Optionalparameters:l DISABLE (disable the

ByPassMode)l ENABLE (enable the

ByPassMode)

DISABLE

Source VPI SourVPI Virtual channel used by the upperlevel network linkl For the VP switching, the source

port VPI must be beyond the VPIconfigured to the board, and thevalue cannot be 1.

l For the VC switching, the sourceport VPI must be within the VPIconfigured to the board, and thevalue can be 1.


1


SourceVCI

SourVCI Identifier of the virtual channel for theupper-level links. This parameter isvalid for VC switching.l For the macro NodeB, the value



33



6-165

InputData


Source

Destination VPI

DestVPI Virtual channel used by the lower-level network linkl For the VP switching, the

destination port VPI must bebeyond the VPI configured to theboard, and the value cannot be 1.

l For the VC switching, thedestination port VPI must be withinthe VPI configured to the board,and the value can be 1.


1

Destination VCI

DestVCI Identifier of the virtual channel for thelower-level links. This parameter isvalid for VC switching.l For the macro NodeB, the value



32

Servicetype

ServiceType Optional parameters:l RTVBR

l NRTVBR

l UBR (unspecified bit rate)

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

RTVBR

Peak cellrate

PCR Peak cell rate of the ATM channelWhen the service type is RTVBR,NRTVBR or UBR+, the value of thisparameter should be greater than thatof the SCR.l When the service type is UBR, the

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

NRTVBR or UBR+, the valuerange is 31 to 6760.

400




Issue 01 (2008-06-25)

InputData


Source



380

Procedure




Step 4 Click Network, and then click the TreeLink PVC tab. The tab page is displayed, as shown inFigure 6-55.

Figure 6-55 NodeB ATM Transport Layer (Treelink PVC) window



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 automaticallyallocates 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, andthe 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, andthe value can be 1; the destination port VPI must be within the VPI range configured to the board, andthe 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.

PrerequisiteNOTE

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, betweenbaseband 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:




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 layerconsists of the PPP link, MLPPP link, PPPoE link, IP address of the FE port, and the timeslotcross channel. You need to configure at least one type from the PPP link, MLPPP link, PPPoElink, and IP address of the FE port. And you can configure only one type or configure all thetypes.

6.6.2 Adding an IP Route (Initial)This describes how to add an IP route for transmitting the NodeB IP data of the transmissioncontrol 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, theNBAP at the IP transport layer.

6.6.4 Adding an IPCP (Initial)This describes how to configure the NodeB Control Port (NCP) and Communication ControlPort (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 thebandwidth of the physical link to the transmission resource group for carrying the UE data. Eachresource 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 resourcegroup. All data to the subnet from the port of the transmission resource group will be calculatedin 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 clockserver 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 layerconsists of the PPP link, MLPPP link, PPPoE link, IP address of the FE port, and the timeslotcross channel. You need to configure at least one type from the PPP link, MLPPP link, PPPoElink, and IP address of the FE port. And you can configure only one type or configure all thetypes.

6.6.1.1 Adding PPP Link Data (Initial)



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 theAccess 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 thefollowing 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 thedata 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.


Mandatory/Optional

Optional

NOTE

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

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

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

Prerequisitel 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 setto IPV4. For details, refer to 6.4.2 Adding a BBU (Initial).

Preparation

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

InputData



13Internalplanning




Issue 01 (2008-06-25)

InputData


Port No. PortNo Number of the E1/T1 ports for PPPlinksValue range: 0 through 7

0

Linknumber

LinkNo Each PPP link and each MLPPP linkmust have a unique number.Value range: 0 through 15

0

Authentication type



l CHAP (with CHAPauthentication)

NONAUTH


-

Timeslotmap

TSBitMap A map of the timeslots for PPP links.The map is presented in binaryformat or the chart. If a timeslot isselected, it is in use. Otherwise, it isnot in use.

TS1 toTS15


Local IPaddress

LocalIP Local IP address of the PPP link.When the value is 0.0.0.0, it indicatesthat the parameter needs to benegotiated with the RNC.

17.17.17.111


PeerIP Destination IP address of the PPPlinkl In cascading mode, this parameter

specifies the IP address of a lower-level cascaded node.

l In non-cascading mode, when thevalue is 0, it indicates that theparameter needs to be negotiatedwith an upper-level node.

17.17.17.17





ENABLE

Internalplanning



6-171

InputData




l ENABLE

l DISABLE

DISABLE

Maximumreceivedunit

MRU Expected value sent from the peerendValue range: 128 through 1500

1500





l DISABLE

ENABLE



l ENABLE

l DISABLE

ENABLE




Issue 01 (2008-06-25)

InputData


HSDPAswitch






Time delaythreshold


4



1



6-173

Procedure



Step 3 Select a physical NodeB, and then click . The NodeB IP Transport Layer window isdisplayed.

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 thetimeslot 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 localIP address and mask for the PPP link, and then click OK to return to the NodeB IP TransportLayer window.

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




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.


Mandatory/Optional

Optional

NOTE

l Local IP addresses of various MLPPP groups 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 occupiedby the links do not conflict.

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

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

InputData


Source


13

Internalplanning

MLPPPgroupnumber

GroupNo MLPPP group numberValue range: 0 through 3

0

Authentication type




NONAUTH



6-175

InputData


Source


-

Local IPaddress

LocalIP Local IP address of the MLPPP group 16.16.16.111


Localsubnetmask

LocalMask Subnet mask of the local IP address forthe 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 forMLPPP linksValue range: 0 through 7

0

Internalplanning

Linknumber

LinkNo Number of the MLPPP link that joinsthe MLPPP group. Each MLPPP andeach PPP link must have a uniquenumber.Value range: 0 through 15

1

Timeslotmap

TSBitMap A map of the timeslots for MLPPPlinks. The map is presented in binaryformat or the chart. If a timeslot isselected, it is in use. Otherwise, it isnot in use.

TS24 toTS31






ENABLE

Internalplanning



l ENABLE

l DISABLE

DISABLE

Multi-classPPP

MCPPP Optional parameters:l ENABLE (using the MCPPP)

l DISABLE (not using the MCPPP)

ENABLE




Issue 01 (2008-06-25)

InputData


Source

Maximumreceivedunit


1500





l DISABLE

ENABLE



l ENABLE

l DISABLE

ENABLE

HSDPAswitch

HsdpaSwitch Optional parameters:l SIMPLE_FLOW_CTRL: Based on


l AUTO_ADJUST_FLOW_CTRL:According to the flow control ofSIMPLE_FLOW_CTRL, traffic isallocated to HSDPA users when thedelay and packet loss on the Iubinterface are taken into account.The RNC uses the R6 switch toperform this function. It isrecommended that the RNC be usedin compliance with the R6 protocol.





6-177

InputData


Source

Time delaythreshold


4



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




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, asshown in Figure 6-58. Select an interface board, and click OK to return to the NodeB IPTransport 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 localIP address and mask for the MLPPP group, and then click OK to return to the NodeB IPTransport Layer window.

Step 7 Select PeerIP, and click , the PeerIP dialog box is displayed. Set the local IP address andmask for the MLPPP group, and then click OK to return to the NodeB IP Transport Layerwindow.

Step 8 Configure other parameters based on the prepared data, and then click to add an MLPPPgroup.

Step 9 In area 2, select SubrackNo, and click . The Search E1/T1 Port window is displayed. Selectan 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 thetimeslot to be used, and then click OK to return to the NodeB IP Transport Layer window.



6-179

NOTE


Step 11 Configure other parameters based on the prepared data, and then click to add an MLPPPlink.

----End

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


Mandatory/Optional

Optional

NOTE

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


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.

Prerequisitel The NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the Boards in

the Baseband Subrack (Initial).l The BBU of the distributed NodeB is configured, as described in 6.4.2 Adding a BBU

(Initial).

Preparation

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

InputData

FieldName

Description Example

Source


13

InternalplanningPort No. PortNo Number of the FE port for the PPPoE

linkValue range: 0 through 1

0




Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Authentication type

AuthType Optional parameters:l NONAUTH (without authentication)

l PAP (with PAP authentication)


NONAUTH

User name UserName This parameter is valid only whenAuthType is set to PAP or CHAP.Value range: not greater than 64characters

-

Local IPaddress

LocalIP Local IP address of the PPPoE link 12.3.0.1 Negotiation withthedestination

Localsubnetmask

LocalMask Subnet mask of the local IP address 255.255.255.0


IPHC Optional parameters:l DISABLE: The IP header of the peer

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

peer end is compressed.

ENABLE

Internalplanning

Maximumreceivedunit


1450


RestartTimer

Value range: 1 through 65535 3000



l ENABLE

l DISABLE

DISABLE



6-181

InputData

FieldName

Description Example

Source

HSDPAswitch

HsdpaSwitch

Optional parameters:l SIMPLE_FLOW_CTRL: Based on

the configured Iub bandwidth and thebandwidth occupied by R99 users,traffic is allocated to HSDPA userswhen the physical bandwidthrestriction is taken into account.


l NO_FLOW_CTRL: The NodeBdoes not allocate bandwidthaccording to the configuration ordelay on the Iub interface. The RNCallocates the bandwidth according tothe bandwidth on the Uu interfacereported by the NodeB. To performthis function, the reverse flow controlswitch must be enabled by the RNC.


Time delaythreshold


4



1

Procedure





Issue 01 (2008-06-25)



Step 4 Click IPPort, and then click the PPPoE tab. The tab page is displayed, as shown in Figure6-59.

Figure 6-59 Adding a PPPoE link

Step 5 Select SubrackNo, and click . The Search Ethernet Port window is displayed. Select anFE 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 localIP address and mask for the PPPoE link, and then click OK to return to the NodeB IP TransportLayer 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 thefollowing types: PPP, MLPPP, or Ethernet.


Mandatory/Optional

Optional



6-183

NOTE

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

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

l IP addresses for different ports cannot be on the same network segment; IP addresses for the same portcan be on the same network segment.

Prerequisitel The NUTI of the Macro NodeB is configured, as described in 6.2.2 Adding the Boards in

the Baseband Subrack (Initial).


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

Preparation

Table 6-58 Negotiation and planned data of the DEVIP

InputData

FieldName

Description Example

Source


13

Internalplanning

Port No. PortNo l For the PPP link, the MLPPP group,and the PPPoE link, PortNorepresents the port number for theconfigured PPP link, the MLPPPgroup, and the PPPoE link.

l For the ETH link, the port valueranges from 0 to 1.

0

Port type PortType The port types consist of the followingitems: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.

ETH

Local IPaddress

LocalIP Local IP address of the device IP 12.11.12.12





Issue 01 (2008-06-25)

InputData

FieldName

Description Example

Source

Subnetmask of thelocal IPaddress

LocalMask If the network is not divided intosubnets, use the default mask.

255.255.255.0

Procedure




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

Figure 6-60 Configuring the DEVIP



Description

1 Configuration area for the device IP address



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 localIP address and mask for the device, and then click OK to return to the NodeB IP TransportLayer window.

Step 7 Click to add the device IP address.

Step 8 (Optional) In area 2, select TrafficType, and click . Then, Set VLAN service priority

mapping according to the actual network planning. Click to save the settings.

----End

Adding a Timeslot Cross Channel (Initial, over ATM)This describes how to add a timeslot cross channel for the 2G equipment so as to transmit thedata of services on the 3G network.


Mandatory/Optional

Optional

NOTE

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

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

l The source and destination ports of the timeslot cross channel must be different, and the same E1/T1port 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 fractionalATM link timeslot that is configured to either E1/T1 2 or 3.

PrerequisiteThe negotiation and planned data is ready.




Issue 01 (2008-06-25)

Preparation


InputData

FieldName


Source slotNo.


13

Internalplanning

Sourceport No.


3

Sourcetimeslots



DestSlotNo


13


DestPortNo


0

Procedure




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



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 SearchE1/T1 Port window is displayed. Select an E1/T1 port, and click OK to return to the NodeBATM Transport Layer window.


NOTE


Step 7 Configure other parameters based on the prepared data, and then click to add a timeslotcross channel.

----End

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





Issue 01 (2008-06-25)

Mandatory/Optional

Mandatory

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

Preparation

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

InputData


Source

Port type ItfType Interface type of the route Optionalparameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Networkplanning

Destination network

DestNet This parameter must meet all thefollowing requirements: Validnetwork address, except the defaultroute 0.0.0.0 IP AND mask must beequal to the IP address.

17.18.17.0

Destination mask

DestMask This parameter must meet all thefollowing requirements: IP ANDmask must be equal to the IP address.If the mask is converted into binaryvalue, 0 is not allowed to precede 1.

255.255.255.0

Next hopIP address

NextHop This parameter is valid only when theparameter InsertFlag is set to ETH.This parameter meets the followingrequirements: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.

12.11.12.1



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




Issue 01 (2008-06-25)

NOTE

l DestNet is the IP address of the destination network. Destination IP address AND subnet mask is theIP 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 thenext 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 connectingto 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, theNBAP at the IP transport layer.


Mandatory/Optional

Mandatory

NOTE

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

Prerequisitel 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



Port type ItfType Type of the interface that carries theSCTP links Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

PPP Internalplanning



6-191



Local IPaddress

LocalIP At the NodeB, the IP address of theprimary physical link that carries theSCTP link.

17.17.17.111

Negotiation with thedestination

DestinationIP address

DestIP At the RNC, the IP address of theprimary physical link that carries theSCTP link.

14.1.1.4

The secondlocal IPaddress

SecLocalIP At the NodeB, the IP address of thestandby physical link that carries theSCTP link.The IP address 0.0.0.0 indicates thatthis address is not in use.

0.0.0.0

The seconddestinationIP address

SecDestIP At the RNC, the IP address of thestandby physical link that carries theSCTP link.The IP address 0.0.0.0 indicates thatthis address is not in use.

0.0.0.0

Local portnumber anddestinationport number

LocalPort Local port number of the SCTPValue range: 1024 through 65535

1024

Destinationport number

DestPort Destination port number of the SCTPValue range: 1024 through 65535

8021

Automatically switchesback to themaster IPaddress

IPAutoChange

After the fault of the master IPaddress is rectified, the services canbe automatically switched back tothe master IP address. Optionalparameters:l ENABLE

l DISABLE


Procedure






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


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 isdisplayed, as shown in Figure 6-64. In area 1, select the network segment route, and set the peerIP address of the SCTP link in the upper middle part of the window. Click OK to return to theNodeB IP Transport Layer window.



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 IPaddress 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 ison the same network segment as the local IP address of the data link. That is, the IP address of thedestination network and the local IP address of the data link are on the same network segment. Fordetails, refer to area 1 in Figure 6-64. (DestNet and LocalIP use the route of the same networksegment.)

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

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

NOTE

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

----End




Issue 01 (2008-06-25)

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


Mandatory/Optional

Mandatory

NOTE

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

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

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

PrerequisiteThe 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


Description Example

Source

NCP


l CCP

NCP Internalplanning

SCTPnumber

SCTPNo SCTP number that carries theNCPValue range: 0 through 19



l MASTER

MASTER

Internalplanning

CCP


l CCP

CCP Internalplanning



6-195


Description Example

Source


0


SCTPnumber

SCTPNo SCTP number that carries theCCPValue range: 0 through 19

2


l MASTER

MASTER

Internalplanning

Procedure




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




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

parameters based on prepared data, and then click to add an NCP link.

Step 6 In area 1, select an SCTP link; in area 2, select PortType and then click . Configure related

parameters based on prepared data, and then click to add an CCP link.

----End

6.6.5 Adding Transmission Resource Group (Initial, over IP)This describes how to add the transmission resource group, which is used to allocates thebandwidth of the physical link to the transmission resource group for carrying the UE data. Eachresource group has its separate access control, congestion control, and HSPA flow control.

Scenario NodeB Initial Configuration Guide

Mandatory/Optional

Optional. This configuration is required when the IP path joins the transmissionresource group.



6-197

NOTE

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

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

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

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

Preparation

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

InputData

FieldName


Port type ItfType Type of the interface that carries the IPtransmission resource group Optionalparameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Internalplanning

Resourcegroupnumber


Transmitbandwidth

TxBandwidth

The transmit bandwidth of theresource group cannot exceed thebandwidth of the port to which theresource group belong.l When the port type is ETH, the





10000




Issue 01 (2008-06-25)

InputData

FieldName


Receivebandwidth

RxBandwidth

Receive bandwidth of the resourcegroup.l When the port type is ETH, the





10000

Procedure




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

Figure 6-66 Adding the IP transmission resource group



6-199



Description


2 Configuration area for the transmission resource group

Step 5 In area 1, select a physical bearer link; In area 2, select RscgrpNo and then click .

Step 6 Configure other parameters based on the prepared data, and then click to add a transmissionresource group over IP.

----End

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


Mandatory/Optional

Mandatory

NOTE

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

l Each NodeB can be configured with a maximum of 32 IP paths. The total number the configured IPpaths 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 thesame.

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

l If an IP link is configured with a transmission resource group, all IP path links configured at this IPlink 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.

Prerequisitel 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

InputData


Port type ItfType Type of the interface that carries theIP PATH Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH Internalplanning


DestIP Destination IP address of the IP path 17.18.17.121


DSCPpriority

DSCP Value range: 0 through 63 60 Networkplanning

Servicetype

TrafficType Optional parameters:l RT

l NRT

l HSPA_RT

l HSPA_NRT

RT


Receivebandwidth

RxBandwith When PATH joins the resourcegroup, the receive bandwidth doesnot exceed the bandwidth of theresource group; when PATH doesnot join the resource group, thereceive bandwidth doe not exceed thebandwidth of the physical port.l When the port type is PPP, the





1000



6-201

InputData


Transmitbandwidth

TxBandwith When PATH joins the resourcegroup, the receive bandwidth doesnot exceed the bandwidth of theresource group; when PATH doesnot join the resource group, thereceive bandwidth doe not exceed thebandwidth of the physical port.l When the port type is PPP, the





1000

Transmitcommittedburst size

TxCBS Value range: 15000 to 155000000.The recommended value is 1/2 of thetransmit bandwidth.Unit: bit

500000

Internalplanning

Transmitexcessiveburst size

TxEBS Value range: 0 through 155000000Unit: bit

1000000

Path check PathCheck Optional parameters:l ENABLE: Path check is enabled.

l DISABLE: Path check is disabled.

DISABLE


JoinRscgrp Specify whether the IP PATH shouldbe added to the resource group.Optional parameters:l DISABLE

l ENABLE

ENABLE

Resourcegroupnumber

RscgrpNo Number of the IP transmissionresource groupValue range: 0 through 3

0




Issue 01 (2008-06-25)

Procedure




Step 4 Click IPPath, as shown in Figure 6-67.

Figure 6-67 Configuring the IP PATH



Description

1 Configuration area for the IP path



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 Figure6-68. In area 1, select the network segment route, and set the peer IP address of the IP path inthe upper middle part of the window. Click OK to return to the NodeB IP Transport Layerwindow.

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


NOTE

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


l After the route is determined, the CME automatically traces route related IP transmission resourcegroup. 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 ResourceGroup window is displayed. Select a transmission resource group, and click OK to return tothe 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 Table6-72 show the matching relation.

Step 8 Configure other parameters based on the prepared data, and then click to add an IP path.

NOTE

Select the configured IP path, and then the CME automatically traces the related IP transmission resourcegroup 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.


Mandatory/Optional

Mandatory

NOTE

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

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

Prerequisitel 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 IP routes to destination addresses are configured, as described in 6.6.2 Adding an IP

Route (Initial).



6-205

Preparation

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

InputData

FieldName


Bind theroute

BindRouteValid

Determine whether to bind the route.Route binding is necessary when thepeer IP address of the OMCH is ondifferent network segments from theDestNet in the 6.6.2 Adding an IPRoute (Initial). Optional parameters:l NO

l YES

YES


Port type ItfType Type of the interface that carries thebound routes Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Bound IPaddress onthedestinationnetwork

BindDestIP This parameter is valid only when theparameter BindRouteValid is set toYES.

11.11.10.0

Bounddestinationmask

BindDestIPMask

This parameter is valid only when theparameter BindRouteValid is set toYES.

255.255.255.0

Bound nexthop IPaddress

NextHop This parameter is valid only when theport type is ETH.

12.11.12.1

Local IPaddress

LocalIP IP address at the NodeB for the OMCH 11.11.12.12

Localsubnetmask

Mask Mask of the IP address at the NodeBfor the OMCH

255.255.0.0


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

11.11.11.12

Flag Flag Optional parameters:l MASTER (primary mode)


MASTER 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 parameterBandDestIP and click , 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 clickOK 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 theDestNet 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 islocated.

Step 6 In area 1, select LocalIP, and click , the LocalIP & Mask dialog box is displayed. Set thelocal IP address and the mask for the OMCH, and then click OK to return to the NodeB IPTransport Layer window.

Step 7 Select DestIP, and click . The Destination IP Address window is displayed, as shown inFigure 6-70. Select the network segment route, and set the peer IP address of the IP OMCH inthe upper middle part of the window. Click OK to return to the NodeB IP Transport Layerwindow.

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 generatesthe route to the bound destination network. For instance, the network IP address of Figure 6-70 is11.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 DestNetin 6.6.2 Adding an IP Route (Initial), or on the same network segment as the BandDestIP.

Step 8 Configure other parameters based on the prepared data, and then click to add an OMCHlink.




Issue 01 (2008-06-25)

NOTE

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

----End

6.6.8 Adding A Bound Destination Network Segment to theTransmission Resource Group (Initial, IP)

This describes how to add a bound destination network segment to the transmission resourcegroup. All data to the subnet from the port of the transmission resource group will be calculatedin the transmission resource group.


Mandatory/Optional

Optional. This configuration is required when the SCTP link or the OMCH linkjoins the transmission resource group.

NOTE

l Two transmission resource groups of the same physical port cannot be bound to the same destinationnetwork segment.

l The transmission resource group (IP as the bearer mode) to which the bound destination networksegment 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 TransmissionResource Group (Initial, over IP).

Preparation

Table 6-76 Negotiation and planned data of the transmission resource group whose destinationIP network segment is bound

InputData

FieldName


Port type ItfType Type of the interface that carries theresource group Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

ETH

Internalplanning

Resourcegroupnumber

RscgrpNo Number of the IP transmission resourcegroup that corresponds to the physicalbearer portValue range: 0 through 3

0



6-209

InputData

FieldName



DestIP Bound destination IP address, that is,the IP address on the same networksegment with BindDestIP in 6.6.7Adding an OMCH of the NodeB(Initial, over IP) or the destination IPaddress of the SCTP link of 6.6.3Adding SCTP Links (Initial).

11.11.10.10

Destination mask

IPMask Bound destination mask 255.255.255.255

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)




Issue 01 (2008-06-25)


Sequence ofdataconfiguration

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 thetransmission resource group

Step 5 In area 1, select an IP transmission resource group; in area 2, select the IP address of the bounddestination network.

Step 6 In area 3, click SubrackNo, and click . Select DestIP, and click . The DestIP &Mask dialog box is displayed. To add a destination IP address, click OK to return to the NodeBIP 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 OMCHlink. (The bound destination IP address and BindDestIP are on the same network segment).

Step 7 Configure other parameters based on the prepared data. Click to add a bound destinationnetwork segment to the transmission resource group.

----End

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


Mandatory/Optional

Optional

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



6-211

Prerequisitel The parameter IPClockSwitch on the NUTI is enabled. For details, refer to 6.2.2 Adding

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

InputData

FieldName


Port type ItfType Type of the interface that carries the IPclock links Optional parameters:l ETH

l MLPPP

l PPP

l PPPoE

PPPoE Internalplanning

IP addressat the client

ClientIP Obtain the NodeB IP address of the IPclock

12.3.0.1

Networkplanning

IP addressat theserver

ServerIP IP address at the IP clock server 12.3.0.10

Priority Priority The clock links that has the highestpriority is used first. The number is ina negative relation with the prioritylevel.Value range: 0 through 1

0

Procedure






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


3 Configured IP clock link route list

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



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


NOTE

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


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

Step 6 Configure other parameters based on the prepared data, and then click to add a clock link.

NOTE

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

----End




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.


Mandatory/Optional

Optional

NOTE

l IP QoS is an IP network capability to provide specific services over the IP network thatuses 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 QoSconfiguration is flexible depending on actual requirements.

PrerequisiteNone.

Preparation

Table 6-81 Negotiation and planned data of the IPQoS

InputData

FieldName


Priority rule PriRule Optional parameters:l IPPRECEDENCE

l DSCP

IPPRECEDENCE

Networkplanning

Signalingpriority

SigPri l In IPPRECEDENCE rule, the valuerange is 0 through 7.


7

OperationandMaintenance (OM)priority

OMPri l In IPPRECEDENCE rule, the valuerange is 0 through 7.


7

Procedure




6-215



Step 4 Click IPQos, as shown in Figure 6-74.

Figure 6-74 Configuring the Diffserv priority on the transport layer

Step 5 Select PriRule, and select a priority rule from the drop-down list.

Step 6 Select SigPri and OMPri, and then set the signaling and OM priorities.


----End




Mandatory/Optional





Issue 01 (2008-06-25)

NOTE








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.






6-217

Procedure





Option Description


Go to Step 5.









Issue 01 (2008-06-25)




Description






6-219


NOTE






----End

6.8 Adding Radio Layer DataThis describes how to configure radio network layer data for the NodeB. The related activitiesinvolve adding sites, adding sectors, and adding local cells.

6.8.1 Adding SitesThis describes how to add a NodeB site. The NodeB modules that are in the charge of the samemain module are called a NodeB. They can be located in different places and connected to eachother through optical fibers and standard interfaces. Each module at a specific place can beplanned 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 ina macro NodeB. From the hardware perspective, the local sector needs the support from theMTRU and MAFU, and the remote and the distributed sector needs the support from the MRRU




Issue 01 (2008-06-25)

or the PicoRRU (PRRU). The cells can be configured in the local sectors, remote sectors, ordistributed 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 hardwaresupport, the remote sector and the distributed sector need the MRRU or PRRU (PicoRRU) RFunit. The cells can be configured only in remote sectors or distributed sectors.

6.8.1 Adding SitesThis describes how to add a NodeB site. The NodeB modules that are in the charge of the samemain module are called a NodeB. They can be located in different places and connected to eachother through optical fibers and standard interfaces. Each module at a specific place can beplanned as a site.


Mandatory/Optional

Mandatory

Prerequisite


Preparation


InputData


Site name Site Name The site is usually named afterthe geographical location.

Shanghai Networkplanning

Procedure



Step 3 Select a physical NodeB, and then click . The NodeB Radio Layer window is displayed,as shown in Figure 6-78.



6-221

Figure 6-78 Adding Sites

Sequence of data configuration Description

1 Configuration area for sites

Step 4 In area 1, select SiteId, and click . Configure parameters SiteId and Site Name accordingto the prepared data.

NOTE

SiteId is unique in one NodeB.

Step 5 Click to add a site.

----End

6.8.2 Adding Sectors and Cells (Macro NodeB)This describes how to configure cells in local sectors, remote sectors, and distributed sectors ina macro NodeB. From the hardware perspective, the local sector needs the support from theMTRU and MAFU, and the remote and the distributed sector needs the support from the MRRUor the PicoRRU (PRRU). The cells can be configured in the local sectors, remote sectors, ordistributed sectors.





Issue 01 (2008-06-25)

Mandatory/Optional

Mandatory

NOTE

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

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

l If the PA supports two carriers, the carriers are on the same PA. The frequency difference betweentwo 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 betweentwo 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.

Prerequisitel 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, referto 6.2.5 Adding RF Modules (Initial).

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



6-223

Preparation




RxAntennaNum




2

Networkplanning


TxDiversityMode






TX_DIVERSITY




Issue 01 (2008-06-25)


Coveragetype



coverage type)

-



6-225



Uplinkfrequency

UARFCNUpLink


Common frequencies: 9612through 9888 inclusive.Offset:0Special frequencies: None.Offset: 0

l Band 2Common frequencies: 9262through 9538 inclusive.Offset: 0Special frequencies: {12,37, 62, 87, 112, 137, 162,187, 212, 237, 262, 287}.Offset:1850.1



l Band 5Common frequencies: 4132through 4233 inclusive.Offset:0Special frequencies: {782,787, 807, 812, 837, 862}.Offset:670.1


9612

Networkplanning




Issue 01 (2008-06-25)


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






6-227


Downlinkfrequency

UARFCNDownLink








10562




Issue 01 (2008-06-25)






ULResourceGroupId


0


DLResourceGroupId


0



GEN_POOL



6-229







430


29000

Innerhandoverradius



0




Issue 01 (2008-06-25)




0



l TRUE (high speed)

FALSE



l 400

l 500

-



100

Procedurel Configure local sectors and cells.

NOTE

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

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



6-231

Figure 6-79 Configuring local sectors and cells



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

2. In area 1, click SectorNo, and click . Set parameters based on prepared data. Then,

click to add a local sector.3. In area 2, the available antenna channels that can be used by the local sectors are

filtered out. Select the antenna channel, and then click to configurethe antenna channel used by the local sector.

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 . TheULGroup or DLGroup window is displayed. Select an uplink or a downlink resourcegroup, and click Close to return to the NodeB Radio Layer window.

7. Select INHBOARD, and click . The Mac Params Confige Form window isdisplayed, 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



Description

1 Modify Mac-hs scheduling parameters.

2 Modify Mac-hs resource limit parameters.

3 Modify Mac-hs SPI scheduling parameters.



6-233

NOTE

l For the BTS3812AE, BTS3812A, or BTS3812E, if the previously mentioned parametersfor the specified local cells are modified, you must select the HSDPA Capability checkbox, and the INHBOARD is INHBOARD; if you deselect the HSDPA Capability checkbox, the INHBOARD is UNLIMITED.

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

8. Configure other parameters based on the prepared data, and then click to add acell.

9. In area 5, the available RF channels that can be used by the cell are filtered out. Select

the RF channel, and then click to configure the RF channel used bythe cell.

l Configure remote sectors and cells.

NOTE

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

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

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

Figure 6-81 Configuring remote sectors and cells




Issue 01 (2008-06-25)



Description

1 Configuration area for the remote sectors

2 Available antenna channel list for remote sectors


4 Configuration area for the cells of the remote sectors



2. Perform Step 2 through Step 3 to configure remote sectors.

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

l Configure distributed sectors and cells

NOTE

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

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

1. In the NodeB Radio Layer window, click the Distribute Sector tab, the tab page isdisplayed, as shown in Figure 6-82.

Figure 6-82 Configure distributed sectors and cells



6-235



Description

1 Configuration area for the distributed sectors

2 Available antenna channel list for distributed sectors


4 Configuration area for the cells of the distributed sectors



2. Perform Step 2 through Step 3 to configure the distributed sectors.3. Perform Step 4 through Step 9 to configure cells of the distributed sectors.

----End

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


Mandatory/Optional

Mandatory

NOTE

l The MRRU supports four carrier frequencies and the PRRU supports two carrier frequencies.

l The uplink and downlink frequencies of the cell configured in the same MRFU, MRRU, or PRRU mustbe 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 betweentwo 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 betweentwo 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.

Prerequisitel The DBS3800 related physical NodeB is configured. For details, refer to 6.2.1 Manually

Creating a Physical NodeB (Initial).




Issue 01 (2008-06-25)


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

Preparation




RxAntennaNum




2

Networkplanning


TxDiversityMode






TX_DIVERSITY



6-237


Coveragetype



coverage type)

-




Issue 01 (2008-06-25)



Uplinkfrequency

UARFCNUpLink


Common frequencies: 9612through 9888 inclusive.Offset:0Special frequencies: None.Offset: 0

l Band 2Common frequencies: 9262through 9538 inclusive.Offset: 0Special frequencies: {12,37, 62, 87, 112, 137, 162,187, 212, 237, 262, 287}.Offset:1850.1



l Band 5Common frequencies: 4132through 4233 inclusive.Offset:0Special frequencies: {782,787, 807, 812, 837, 862}.Offset:670.1


9612

Networkplanning



6-239


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







Issue 01 (2008-06-25)


Downlinkfrequency

UARFCNDownLink








10562



6-241






ULResourceGroupId


0


DLResourceGroupId


0



GEN_POOL




Issue 01 (2008-06-25)







430


29000

Innerhandoverradius



0



6-243




0



l TRUE (high speed)

FALSE



l 400

l 500

-



100

Procedurel Configure remote sectors and cells.

NOTE

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

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

1. In the NodeB Radio Layer window, click the Remote Sector tab, the tab page isdisplayed, as shown in Figure 6-83.




Issue 01 (2008-06-25)

Figure 6-83 Configuring remote sectors and cells



Description

1 Configuration area for the remote sectors

2 Available antenna channel list for remote sectors


4 Configuration area for the cells of the remote sectors



2. Perform Step 2 through Step 3 in the 6.8.2 Adding Sectors and Cells (Macro

NodeB) to add remote sectors.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.l Configure distributed sectors and cells

NOTE

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

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

1. In the NodeB Radio Layer window, click the Distribute Sector tab, the tab page isdisplayed, as shown in Figure 6-84.



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


4 Configuration area for the cells of the distributed sectors



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




Issue 01 (2008-06-25)

7 Related Concepts of NodeB InitialConfiguration

About This Chapter

This provides the related concepts to be referenced during the process of the NodeB initialconfiguration.

7.1 Cell Related ConceptsThis provides the cell related concepts, including those of the sectors, carriers, cells, physicalresources of cells, local cells, and logical cells.

7.2 ATM Protocol-Related TermsThis describes the terms related to the ATM protocol. The reference model of the ATM protocolconsists 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 ATMadaptation layer (AAL).

7.3 IP Protocol-Related TermsThis describes the terms related to the protocols of the data link layer, network layer, andtransport network layer when the Iub interface uses the IP transport.

7.4 NodeB Treelink PVCThe function of a NodeB treelink PVC is similar to that of the ATM switching. This describeshow 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 ConnectionsThis defines the NodeBs in direct and cascading connections. In addition, it describes theconfiguration differences between these two connections.

NodeBNodeB Initial Configuration Guide 7 Related Concepts of NodeB Initial Configuration


7-1

7.1 Cell Related ConceptsThis provides the cell related concepts, including those of the sectors, carriers, cells, physicalresources of cells, local cells, and logical cells.

7.1.1 Sector, Carrier, and CellThis 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 sectorand a carrier form a cell that is the smallest serving unit for UE access.

7.1.2 Physical Resources of CellsThis describes the physical resources of cells from the perspectives of RF resources of sectorsand resource pools of cells.

7.1.3 Local Cell and Logical CellThis describes local and logical cells. In the 3GPP protocols, a serving cell is called local celland logical cell at the implementation layer of physical layer and the management layer of logicalresources respectively.

7.1.1 Sector, Carrier, and CellThis 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 sectorand a carrier form a cell that is the smallest serving unit for UE access.

Sectors are classified into omnidirectional sectors and directional sectors. An omnidirectionalsector is used in small traffic areas. Centered around the omnidirectional RX/TX antenna, theomnidirectional sector covers 360o circular areas. When the traffic increases, the omnidirectionalsector is split into three or six directional sectors. The directional sectors are covered bydirectional antennas. For example, when there are three directional sectors, each set of directionalantenna covers a 120o area. When there are six directional sectors, each set of directional antennacovers a 60o area. In fact, the azimuth of the antenna is greater than the theoretical value, andtherefore 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. Eachsector 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 primaryscrambling codes are used in neighboring cells of different sectors that use the same frequency.In this way, the inter-cell interference is reduced.

7 Related Concepts of NodeB Initial ConfigurationNodeB



Issue 01 (2008-06-25)

Figure 7-1 Relations among a sector, carrier, and cell

7.1.2 Physical Resources of CellsThis describes the physical resources of cells from the perspectives of RF resources of sectorsand resource pools of cells.

RF Resources of SectorsThe NodeB provides RF resources of cells. Figure 7-2 shows the physical RF resources mappedto a NodeB from sectors. Each sector uses one directional antenna. Each directional antennaprovides 2-way receive channels to enhance the receiving sensitivity, and the two channels workin 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 workin pairs.



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 in2-way receive diversity mode. The mapping may vary with the NodeB configuration. Figure7-3 shows the rules of the mapping between BTS3812E sectors and MAFUs and MTRUs.

l 1MAFU+1MTRU for one sector: The NodeB supports 6 sectors. This mode supports 1-carrier or 2-carrier 1T2R configuration.

l 2MAFUs+2MTRUs for one sector: The NodeB supports three sectors. This mode supports1-carrier or 2-carrier 1T2R or 2T2R configuration, and 3-carrier or 4-carrier 1T2R




Issue 01 (2008-06-25)

configuration. You may change the external interface connections of the MTRUs andMAFUs 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 combinedcabinet is required when there are more than one sector. This mode supports 3-carrier or4-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 typeof 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 ofthe HBBI, HULP, and HDLP. This type of resource pool is commonly used. When theresource pool is used, you must specify uplink baseband resource groups.

l GRP_POOL: indicates the uplink and downlink baseband resource pool that consists of theHBOI in slot 15. When the resource pool is used, you do not need to specify uplink basebandresource groups.

The NodeB divides the uplink baseband resources into different groups, which are called uplinkbaseband resource groups. The uplink baseband resource groups have the following features andrequirements:

l One uplink baseband resource group consists of one or more uplink processing units. Oneuplink 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 uplinkbaseband resource group supports a maximum of 6 cells in 2-way and enhanced 2-waymodes. Each uplink baseband resource group supports a maximum of three cells in 4-wayand economic 4-way modes.

l The softer handover can be performed between the cells in the same uplink basebandresource 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.



7-5

7.1.3 Local Cell and Logical CellThis describes local and logical cells. In the 3GPP protocols, a serving cell is called local celland logical cell at the implementation layer of physical layer and the management layer of logicalresources respectively.

Local CellA local cell is a combination of physical resources, such as hardware and software resources, ina 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 controlthe radio resources in certain cells through the standard Iub interface. These cells are carried onNodeBs from different vendors.

Logical CellA logical cell is a standard logical model that helps the RNC control the radio resources in acell. The model is independent of the implementation of local cells in the NodeB, and ensuresthat the Iub interface is an open interface.

The parameters of a local cell are configured at and managed by the NodeB. The parameters ofa logical cell are configured at and managed by the RNC. A logical cell and a local cell have theone-to-one correspondence.

7.2 ATM Protocol-Related TermsThis describes the terms related to the ATM protocol. The reference model of the ATM protocolconsists 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 ATMadaptation 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




Issue 01 (2008-06-25)

This describes the functions of the ATM user plane, ATM control plane, and ATM managementplane.

7.2.2 ATM Physical Layer, ATM Layer, and AALThis describes the functions of the physical layer, ATM layer, and AAL.

7.2.1 ATM User Plane, ATM Control Plane, and ATM ManagementPlane

This describes the functions of the ATM user plane, ATM control plane, and ATM managementplane.

Table 7-1 describes the functions of the ATM user plane, ATM control plane, and ATMmanagement 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 voicedata.

Control plane The control plane transfers signaling messages, such as connectionsetup and connection release.

Management Plane The management plane transfers network OM data. This plane isclassified into the layer management part and the plane managementpart. The former is responsible for intra-layer management, and thelatter for inter-layer management.

NOTE

As stated in the ATM protocols, the AAL and higher layers process the data on the control plane and theuser plane in different ways. The ATM layer and the physical layer, however, process the data on the twoplanes in the same way.

7.2.2 ATM Physical Layer, ATM Layer, and AALThis describes the functions of the physical layer, ATM layer, and AAL.

Table 7-2 describes the layers and functions of the reference model of the ATM protocol.

Table 7-2 Layers and functions of the reference model of the ATM protocol

Protocol Layer Function

AAL

CS The AAL is a higher layer of the ATM layer andperforms the adaptation from the upper layerapplications to the ATM layer. For various types ofservices, the AAL performs the adaptation in differentways. It segments data from the upper layer into SDUs.Each SDU has 48 bytes. The AAL reassembles and



7-7

Protocol Layer Function

SAR restores the SDUs from the ATM layer, and thentransfers them to the upper layer.The CS layer performs the convergence. The SARlayer performs the segmentation and reassembly.

ATM layer - ATM switching is a fast packet switching technology.In ATM switching, each 53-byte packet is called a cell.At the physical layer, the ATM layer communicateswith the peer layer through ATM cells.l Generic traffic control

l Cell header generation and extraction

l VPI and VCI translation

l Cell multiplexing and demultiplexing

Physical layer

TC (UNI, IMA,FractionalATM,Fractional IMA,or STM-1mode)

The physical layer provides channels for bit streams ofATM cells. During data transmission, the physicallayer adds the overhead to the ATM cells sent by theATM layer to form a consecutive bit stream. Then, thephysical layer puts the stream on a transport channel.During data reception, the physical layer selects validATM cells from the bit stream on the transport channeland then transfers these cells to the ATM layer. Thephysical layer consists of the PM sublayer and the TCsublayer.The TC sublayer performs the following functions:l Generation and recovery of transmission framesl Adaptation of transmission framesl Cell delimitationl Generation and verification of HEC header

sequencel Decoupling of cell rateThe PM sublayer performs the following functions:l Bit timingl Physical medium

PM (PDH overE1/T1, SDH)

7.3 IP Protocol-Related TermsThis describes the terms related to the protocols of the data link layer, network layer, andtransport network layer when the Iub interface uses the IP transport.

7.3.1 Data Link Layer Protocols




Issue 01 (2008-06-25)

This describes the data link layer protocols related to IP transport.

7.3.2 IPThis describes the Internet Protocol (IP). It provides a connectionless service between networksand defines the rules and details for data communication. It is used along with the TransmissionControl Protocol (TCP) to provide guaranteed data transfer.

7.3.3 SCTPThis describes the Stream Control Transmission Protocol (SCTP). It is mainly used fortransmitting reliable datagrams through an unreliable network.

7.3.1 Data Link Layer ProtocolsThis describes the data link layer protocols related to IP transport.

7.3.1.1 PPPThis describes the Point-to-Point Protocol (PPP). The PPP is used at the data link layer. The PPPprovides standard methods for encapsulating the multi-protocol datagrams on point-to-pointlinks. These datagrams include IP, IPX, and Apple Talk.

7.3.1.2 MPThis describes the Multilink PPP (MP). With the wide application of the PPP, the MP emergesas an extended protocol of the PPP. The MP provides a large bandwidth to enable quick datatransfer. In addition, the MP dynamically allocates the link resources to effectively save thevaluable resources.

7.3.1.3 PPPoEThis describes the PPPoE protocol. It is a standard that defines how multiple hosts are connectedto 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 throughthe access equipment.

7.3.1.4 EtherIPThis describes the EtherIP link. It is connected to the Ethernet, and the relay boards use the FEports.

PPPThis describes the Point-to-Point Protocol (PPP). The PPP is used at the data link layer. The PPPprovides standard methods for encapsulating the multi-protocol datagrams on point-to-pointlinks. These datagrams include IP, IPX, and Apple Talk.

Figure 7-5 shows the hierarchy of the PPP.



7-9

Figure 7-5 Hierarchy of the PPP

The PPP consists of the link control protocol (LCP), network control protocol (NCP), andextended 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 theequipment.

l Extended protocols, such as the multilink protocol (MP): The PPP combines multiplephysical links into a logical link through the MP, thus providing a large bandwidth andenabling fast data transfer. Huawei RNC implements the MP by adding MLPPP data.

MPThis describes the Multilink PPP (MP). With the wide application of the PPP, the MP emergesas an extended protocol of the PPP. The MP provides a large bandwidth to enable quick datatransfer. In addition, the MP dynamically allocates the link resources to effectively save thevaluable resources.

The MP can flexibly arrange multiple independent physical links between point-to-pointsystems. It provides a virtual link for the whole system, and the bandwidth of the virtual link isthe 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.

PPPoEThis describes the PPPoE protocol. It is a standard that defines how multiple hosts are connectedto 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 throughthe access equipment.

In this network topology, all hosts can independently initialize PPP protocol stacks, and performcharging and management for the subscribers on this network. To set up and maintain the point-to-point relations between hosts and the AC in a broadcasting-type network, each host shouldbe able to set up a unique point-to-point session with the AC.




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 seriesof PPP processes, and then transfer the network layer datagrams over this point-to-pointlogical channel.

EtherIP

This describes the EtherIP link. It is connected to the Ethernet, and the relay boards use the FEports.

When IP_RAN is selected as the transmission mode of the NodeB, the NodeB can be configuredwith 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 theFE ports.

7.3.2 IPThis describes the Internet Protocol (IP). It provides a connectionless service between networksand defines the rules and details for data communication. It is used along with the TransmissionControl Protocol (TCP) to provide guaranteed data transfer.

IPv4 and IPv6The current and most popular network layer protocol of the TCP/IP is IPv4, which was launchedin 1981. IPv6, which was launched in 1995, is gradually going to replace IPv4. Compared withIPv4, 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 IPaddress. In the application of the RAN, comply with the following principles when planning theIP 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.



7-11

IP Address StructureIn an IP network, IP addresses should be assigned to hosts. If you connect a computer to theInternet, 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 ClassificationIP addresses are categorized into five classes, as shown in Figure 7-6. You can identify an IPaddress 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 areused for multicasting. IP addresses of class E are reserved. For details, refer to the RFC1166Internet Numbers released by IETF.

IP Address RangeSome IP addresses are reserved for special purposes. Table 7-3 describes the ranges of IPaddresses.




Issue 01 (2008-06-25)

Table 7-3 Classification and range of IP addresses

Networ

kTyp

e

Address Range Available Range Description

A 0.0.0.0 to127.255.255.255

1.0.0.0 to126.0.0.0

l An all-zero host number means thatthe IP address is the network addressfor network routing.

l An all-one host number means thatthe IP address is used to broadcastmessages to all the hosts on thenetwork.

l When the DHCP is used, the localhost can take 0.0.0.0 as thetemporary IP address but never asthe valid destination address.

l The IP address with networknumber of 0 represents the currentnetwork that can be referenced byother computers without knowingits network number.

l All the IP addresses in the127.X.X.X format are reserved forloopback testing. The packets sentto this address are not sent to lines.The packets are handled internallyas input packets.

B 128.0.0.0 to191.255.255.255

128.0.0.0 to191.254.0.0



C 192.0.0.0 to223.255.255.255

192.0.0.0 to223.255.254.0



D 224.0.0.0 to239.255.255.255

None. IP addresses of class D are used formulticasting.



7-13

Networ

kTyp

e

Address Range Available Range Description

E 240.0.0.0 to255.255.255.255

None. Reserved. The IP address of255.255.255.255 is used forbroadcasting in the LAN.

7.3.3 SCTPThis describes the Stream Control Transmission Protocol (SCTP). It is mainly used fortransmitting 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 transportaddresses for data transmission to the peer host, or a group of valid originating transportaddresses for transmitting SCTP packets.

All the transport addresses used by an SCTP endpoint must use the same port number but canuse multiple IP addresses. The transport address used by an SCTP endpoint at a time must beunique.

A transport address is defined by the network layer address, transport layer protocols, and portnumber. When the SCTP protocol works on the IP transport layer, the transport address is definedby the IP address and SCTP port number. Then, the SCTP protocol acts as the transport layerprotocol.

SCTP Association

SCTP association is the mapping between two SCTP endpoints. It involves two SCTP endpointsand protocol status data. The protocol status data includes verification tag and transport sequencenumber.




Issue 01 (2008-06-25)

SCTP association is uniquely identified by the transport address of the SCTP endpoint that usesthe SCTP association. There is a maximum of one SCTP association between two SCTPendpoints.

SCTP Message StructureThe SCTP message consists of the common header and the chunks. Figure 7-7 shows the SCTPmessage 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 PVCThe function of a NodeB treelink PVC is similar to that of the ATM switching. This describeshow 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 PrinciplesIf a NodeB is connected to a lower-level NodeB, this parent NodeB must be configured with atreelink PVC for transferring ATM cells to the lower-level node. The red dashed line in Figure7-8 represents the treelink PVC.



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-levelone through a hub NodeB. The treelink PVCs configured on a hub NodeB should be able toswitch 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 PVCsThe NCP, CCP, ALCAP, AAL2 PATH, IPoA, CES, and treelink PVC of the lower-level NodeBcorrespond to different PVCs. The method of adding a treelink PVC is the same as that of addinga 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 needto specify the source (VPI, VCI) and the destination (VPI, VCI).

l Through VPI switching: A treelink PVC corresponds to multiple PVC switching routes.You need to specify only the source VPI and the destination VPI. The VCI is unchanged.

The amount of treelink PVCs depends on the amount of physical bearers, switching methods(VP or VC), and the amount of the upper-level applications.

l For VC switching, the amount of treelink PVCs depends on that of the PVCs of the upper-level node.

l For VP switching, the amount of treelink PVCs depends on that of the PVCs of the upper-level node and the VPI values of all PVCs. Assume that all the PVCs on the Iub interface




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 forthe VPIs and VCIs of treelink PVCs.

Comparison Between VP Switching and VC Switchingl 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 ConnectionsThis defines the NodeBs in direct and cascading connections. In addition, it describes theconfiguration differences between these two connections.

7.5.1 Definitions of NodeBs in Direct/Cascading ConnectionsThe physical connections between an RNC and a NodeB are of two types: direct and cascadingconnections.

7.5.2 Configuration Differences Between NodeBs in Direct/Cascading ConnectionsNodeBy in cascading connection is connected to NodeBx through E1, in which case NodeBxworks as the transmission equipment between NodeBy and the RNC. In this sense, it is similarto configure NodeBs in direct or cascading connection. This, however, describes theconfiguration differences between direct and cascading connections.

7.5.1 Definitions of NodeBs in Direct/Cascading ConnectionsThe physical connections between an RNC and a NodeB are of two types: direct and cascadingconnections.

Direct ConnectionIn 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 ConnectionIn cascading mode, the NodeB is connected to the RNC through another NodeB. Figure7-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.



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 throughmultiple NodeBs that provide cascading connections. Each cascaded NodeB occupies a portion of thebandwidth between the RNC and the upper-level NodeB (that is, the NodeB that provides cascadingconnection). The bandwidth is also required by the upper-level NodeB. Therefore, multi-level cascadingis 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 NodeBxworks as the transmission equipment between NodeBy and the RNC. In this sense, it is similarto configure NodeBs in direct or cascading connection. This, however, describes theconfiguration 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

NodeBxCascading Path

Prerequisites for NodeByConfiguration

Configuration differencesbetween NodeBy and theNodeB in direct connection

Timeslot cross. TheNodeBx works asthe equipment thatprovides thetimeslot crossfunction.

l NodeBx is connected to the RNCthrough E1/T1, including E1 overSDH.

l By default, NodeBx must beconnected to the RNC overfractional ATM. Besides, thereare redundant timeslots betweenNodeBx and the RNC.

l NodeBy must be connectedto NodeBx over fractionalATM and occupies only theredundant timeslots ofNodeBx.

l You need to configure thetimeslot cross connection onNodeBx.




Issue 01 (2008-06-25)

NodeBxCascading Path

Prerequisites for NodeByConfiguration

Configuration differencesbetween NodeBy and theNodeB in direct connection

ATM switching Redundant portions of thebandwidth are available betweenNodeBx and the RNC.

You need to add a treelink PVCto NodeBx.

As the ATM switching equipment, NodeBx is connected to the RNC by E1/T1 or SDH with theapplication as UNI, IMA, or STM-1. NodeBy may also be connected to NodeBx by E1/T1 withthe applications as UNI or IMA. This type of cascading path for the NodeB is recommended.



7-19

nodeb initial configuration guide-(v100r010_01)

Documents