RNC Initial Configuration Guide

RNC

V200R010

RNC Initial Configuration Guide

Issue 03

Date 2008-08-30

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 RNC Initial Configuration...........................................................................1-11.1 Definition of RNC Initial Configuration.........................................................................................................1-21.2 RNC Initial Configuration Tool......................................................................................................................1-21.3 Components of the RNC Initial Configuration Script.....................................................................................1-3

1.3.1 Example: Global Data in the RNC Initial Configuration Script............................................................1-31.3.2 Example: Equipment Data in the RNC Initial Configuration Script......................................................1-41.3.3 Example: Interface Data in the RNC Initial Configuration Script.........................................................1-51.3.4 Example: Cell Data in the RNC Initial Configuration Script...............................................................1-17

1.4 Conventions in Parameter Relationship Diagrams........................................................................................1-18

2 Procedure of RNC Initial Configuration...............................................................................2-1

3 Data Preparation for RNC Initial Configuration.................................................................3-13.1 Global Data and Equipment Data of the RNC................................................................................................3-23.2 Data Negotiated Between RNC and Other Network Elements.......................................................................3-4

3.2.1 Data Negotiated on the Iub Interface (over ATM).................................................................................3-53.2.2 Data Negotiated on the Iub Interface (over IP)......................................................................................3-83.2.3 Data Negotiated on the Iub Interface (over ATM and IP)...................................................................3-123.2.4 Data Negotiated on the Iu-CS Interface (over ATM) ..........................................................................3-213.2.5 Data Negotiated on the Iu-CS Interface (over IP)................................................................................3-243.2.6 Data Negotiated on the Iu-PS Interface (over ATM)...........................................................................3-273.2.7 Data Negotiated on the Iu-PS Interface (over IP)................................................................................3-303.2.8 Data Negotiated on the Iur Interface (over ATM)...............................................................................3-333.2.9 Data Negotiated on the Iur Interface (over IP).....................................................................................3-363.2.10 Data Negotiated on the Iu-BC Interface.............................................................................................3-39

3.3 Cell Data on the RNC....................................................................................................................................3-41

4 Configuring RNC Global Data................................................................................................4-14.1 Example: Global Data in the RNC Initial Configuration Script.....................................................................4-24.2 Setting the RNC to Offline Mode (Initial)......................................................................................................4-34.3 Adding Basic Data to the RNC (Initial)..........................................................................................................4-34.4 Adding OSP to the RNC (Initial)....................................................................................................................4-44.5 Adding RNC Global Location Data (Initial)...................................................................................................4-54.6 Adding a Local M3UA Entity (Initial)............................................................................................................4-7

RNCRNC Initial Configuration Guide Contents

Issue 03 (2008-08-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

i

5 Configuring RNC Equipment Data........................................................................................5-15.1 Example: Equipment Data in the RNC Initial Configuration Script...............................................................5-25.2 Setting RNC Equipment Description (Initial).................................................................................................5-35.3 Modifying the RSS Subrack of the RNC (Initial)...........................................................................................5-35.4 Adding an RBS Subrack (Initial)....................................................................................................................5-55.5 Configuring RNC Clock Data (Initial)............................................................................................................5-65.6 Setting RNC Time (Initial)..............................................................................................................................5-75.7 Adding the IP Address of the EMS Server (Initial)........................................................................................5-7

6 Configuring Iub Interface Data (Initial)................................................................................6-16.1 Example: Iub Data in the RNC Initial Configuration Script...........................................................................6-26.2 Data Configuration Guidelines for the Iub Interface (over ATM)..................................................................6-5

6.2.1 Protocol Structure for the Iub Interface (over ATM).............................................................................6-56.2.2 Links on the Iub Interface (over ATM)..................................................................................................6-66.2.3 OM IPoA Data Configuration on the Iub Interface (over ATM)...........................................................6-7

6.3 Adding Data on the Iub Interface (Initial, over ATM)....................................................................................6-86.3.1 Adding Physical Layer Data (Initial, over ATM)..................................................................................6-96.3.2 Adding ATM Traffic Resources (Initial).............................................................................................6-136.3.3 Adding Control Plane Data on the Iub Interface (Initial, over ATM)..................................................6-146.3.4 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................6-166.3.5 Adding User Plane Data on the Iub Interface (Initial, over ATM)......................................................6-176.3.6 Adding an OM Channel on the Iub Interface (Initial, over ATM).......................................................6-20

6.4 Data Configuration Guidelines for the Iub Interface (over IP).....................................................................6-226.4.1 Protocol Stack on the Iub Interface (over IP).......................................................................................6-226.4.2 Links on the Iub Interface (over IP).....................................................................................................6-236.4.3 IP Addresses and Routes on the Iub Interface (over IP)......................................................................6-256.4.4 OM Channel Configuration on the Iub Interface (over IP)..................................................................6-27

6.5 Adding Data on the Iub Interface (Initial, over IP).......................................................................................6-306.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................6-316.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP).......................................................6-376.5.3 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................6-396.5.4 Adding User Plane Data on the Iub Interface (Initial, over IP)............................................................6-406.5.5 Adding an OM Channel on the Iub Interface (Initial, over IP)............................................................6-42

6.6 Data Configuration Guidelines for the Iub Interface (over ATM and IP).....................................................6-426.6.1 ATM/IP Hybrid Transport on the Iub Interface...................................................................................6-436.6.2 ATM/IP-Based Networking on the Iub Interface.................................................................................6-446.6.3 Hardware Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface...................6-456.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface...........................6-466.6.5 IP Addresses and Routes on the Iub Interface (over IP)......................................................................6-476.6.6 OM Channel Configuration on the Iub Interface (over IP)..................................................................6-50

6.7 Adding Data on the Iub Interface (Initial, over ATM and IP)......................................................................6-52

7 Configuring Iu-CS Interface Data (Initial)............................................................................7-17.1 Example: Iu-CS Data in the RNC Initial Configuration Script.......................................................................7-2

ContentsRNC


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

Issue 03 (2008-08-30)

7.2 Data Configuration Guidelines for the Iu-CS Interface (over ATM)..............................................................7-47.2.1 Protocol Structure for the Iu-CS Interface (over ATM).........................................................................7-57.2.2 Links on the Iu-CS interface (over ATM)..............................................................................................7-57.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6...........................................................7-7

7.3 Adding Data on the Iu-CS Interface (Initial, over ATM)..............................................................................7-107.3.1 Adding Physical Layer Data (Initial, over ATM)................................................................................7-117.3.2 Adding ATM Traffic Resources (Initial).............................................................................................7-117.3.3 Adding Control Plane Data on the Iu-CS Interface (Initial, over ATM).............................................7-127.3.4 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................7-147.3.5 Adding User Plane Data on the Iu-CS Interface (Initial, over ATM)..................................................7-16

7.4 Data Configuration Guidelines for the Iu-CS Interface (over IP).................................................................7-187.4.1 Protocol Structure for the Iu-CS Interface (over IP)............................................................................7-187.4.2 Links on the Iu-CS interface (over IP).................................................................................................7-197.4.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6.........................................................7-20

7.5 Adding Data on the Iu-CS Interface (Initial, over IP)...................................................................................7-237.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................7-247.5.2 Adding Control Plane Data on the Iu-CS Interface (Initial, over IP)...................................................7-247.5.3 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................7-277.5.4 Adding User Plane Data on the Iu-CS Interface (Initial, over IP).......................................................7-28

8 Configuring Iu-PS Interface Data (Initial)............................................................................8-18.1 Example: Iu-PS Data in the RNC Initial Configuration Script.......................................................................8-28.2 Data Configuration Guidelines for the Iu-PS Interface (over ATM)..............................................................8-4

8.2.1 Protocol Structure for the Iu-PS Interface (over ATM).........................................................................8-48.2.2 Links on the Iu-PS Interface (over ATM) .............................................................................................8-58.2.3 IPoA Data Configuration on the Iu-PS User Plane (over ATM)...........................................................8-6

8.3 Adding Data on the Iu-PS Interface (Initial, over ATM)................................................................................8-88.3.1 Adding Physical Layer Data on the Interface (Initial, with UOI_ATM)...............................................8-88.3.2 Adding ATM Traffic Resources (Initial)...............................................................................................8-98.3.3 Adding Control Plane Data on the Iu-PS Interface (Initial, over ATM)..............................................8-108.3.4 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................8-128.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, over ATM)...................................................8-14

8.4 Data Configuration Guidelines for the Iu-PS Interface (over IP).................................................................8-158.4.1 Protocol Structure for the Iu-PS Interface (over IP).............................................................................8-158.4.2 Links on the Iu-PS Interface (over IP) ................................................................................................8-16

8.5 Adding Data on the Iu-PS Interface (Initial, over IP)...................................................................................8-178.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................8-188.5.2 Adding Control Plane Data on the Iu-PS Interface (Initial, over IP)...................................................8-198.5.3 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................8-218.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, over IP)........................................................8-22

9 Configuring Iur Interface Data (Initial).................................................................................9-19.1 Example: Iur Data in the RNC Initial Configuration Script............................................................................9-29.2 Data Configuration Guidelines for the Iur Interface (over ATM)...................................................................9-4



iii

9.2.1 Protocol Structure for the Iur Interface (over ATM)..............................................................................9-59.2.2 Links on the Iur Interface (over ATM) ................................................................................................. 9-59.2.3 Configuration Guidelines for Static Relocation Routes over Iur...........................................................9-7

9.3 Adding Data on the Iur Interface (Initial, over ATM).................................................................................... 9-79.3.1 Adding Physical Layer Data (Initial, over ATM).................................................................................. 9-89.3.2 Adding ATM Traffic Resources (Initial)...............................................................................................9-99.3.3 Adding Control Plane Data on the Iur Interface (Initial, over ATM).................................................... 9-99.3.4 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................9-119.3.5 Adding User Plane Data on the Iur Interface (Initial, over ATM).......................................................9-139.3.6 Adding a Path for Static SRNS Relocation (Initial).............................................................................9-14

9.4 Data Configuration Guidelines for the Iur Interface (over IP)......................................................................9-159.4.1 Protocol Stack on the Iur Interface (over IP).......................................................................................9-169.4.2 Links on the Iur Interface (over IP)......................................................................................................9-169.4.3 Configuration Guidelines for Static Relocation Routes over Iur.........................................................9-18

9.5 Adding Data on the Iur Interface (Initial, over IP)........................................................................................9-189.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................9-199.5.2 Adding Control Plane Data on the Iur Interface (Initial, over IP)........................................................9-199.5.3 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial).............................9-229.5.4 Adding User Plane Data on the Iur Interface (Initial, over IP)............................................................9-239.5.5 Adding a Path for Static SRNS Relocation (Initial).............................................................................9-24

10 Configuring Iu-BC Interface Data (Initial).......................................................................10-110.1 Example: Iu-BC Data in the RNC Initial Configuration Script..................................................................10-310.2 Data Configuration Guidelines for the Iu-BC Interface..............................................................................10-3

10.2.1 Protocol Structure for the Iu-BC Interface.........................................................................................10-410.2.2 Networking on the Iu-BC Interface....................................................................................................10-410.2.3 Links on the Iu-BC Interface..............................................................................................................10-510.2.4 IPoA Data Configuration on the Iu-BC Interface..............................................................................10-6

10.3 Adding Physical Layer Data (Initial, over ATM).......................................................................................10-610.4 Adding ATM Traffic Resources (Initial)....................................................................................................10-710.5 Adding IPoA Data on the Iu-BC Interface (Initial).....................................................................................10-710.6 Adding SABP Data (Initial)........................................................................................................................10-9

11 Configuring Cell Data (Initial)............................................................................................11-111.1 Example: Cell Data in the RNC Initial Configuration Script......................................................................11-211.2 Quickly Setting Up a Cell (Initial)..............................................................................................................11-311.3 Adding an Intra-Frequency Neighboring Cell (Initial)...............................................................................11-411.4 Adding an Inter-Frequency Neighboring Cell (Initial)...............................................................................11-611.5 Adding a Neighboring GSM Cell (Initial)..................................................................................................11-811.6 Setting the RNC to Online Mode (Initial)...................................................................................................11-9

12 Related Information for RNC Initial Configuration.......................................................12-112.1 Types of RNC Optical Ports........................................................................................................................12-312.2 Introduction to RAN Time Synchronization...............................................................................................12-3

ContentsRNC


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

Issue 03 (2008-08-30)

12.3 Numbering Schemes of the RNC................................................................................................................12-312.3.1 RNC ID..............................................................................................................................................12-412.3.2 RNC Subrack Number.......................................................................................................................12-512.3.3 ATM Traffic Record Index................................................................................................................12-512.3.4 RNC Transmission Resource Mapping Record Index.......................................................................12-612.3.5 RNC Activity Factor Table Index......................................................................................................12-612.3.6 SAAL Link Number...........................................................................................................................12-712.3.7 SCTP Link Number............................................................................................................................12-712.3.8 Adjacent Node ID...............................................................................................................................12-812.3.9 MTP3-b/M3UA DSP Index...............................................................................................................12-812.3.10 Signaling Link Set Index..................................................................................................................12-812.3.11 CN Node ID.....................................................................................................................................12-912.3.12 Local Cell ID..................................................................................................................................12-1012.3.13 Logical Cell ID...............................................................................................................................12-1012.3.14 Common Physical Channel ID.......................................................................................................12-1112.3.15 Common Transport Channel ID.....................................................................................................12-1212.3.16 GSM Cell ID..................................................................................................................................12-1312.3.17 NCP and CCP Number...................................................................................................................12-1312.3.18 NRI.................................................................................................................................................12-13

12.4 Area Identifiers..........................................................................................................................................12-1412.4.1 PLMN ID..........................................................................................................................................12-1412.4.2 LA Identifiers...................................................................................................................................12-1512.4.3 SA Identifiers...................................................................................................................................12-1512.4.4 RA Identifiers...................................................................................................................................12-1612.4.5 URA Identifier..................................................................................................................................12-1612.4.6 PLMN Value Tag.............................................................................................................................12-16

12.5 External Specifications for the RNC.........................................................................................................12-1712.5.1 Specifications for Traffic on RNC Boards.......................................................................................12-1812.5.2 RNC Capability for SAAL...............................................................................................................12-1912.5.3 RNC Capability for SCTP................................................................................................................12-1912.5.4 RNC Capability for NodeBs............................................................................................................12-1912.5.5 RNC Capability for MTP3-b............................................................................................................12-1912.5.6 RNC Capability for M3UA..............................................................................................................12-2012.5.7 RNC Capability for AAL2 Paths and AAL2 Routes.......................................................................12-2012.5.8 RNC Capability for IP Paths and IP Routes.....................................................................................12-2012.5.9 RNC Capability for IPoA.................................................................................................................12-2112.5.10 Specifications for Channels in a Cell.............................................................................................12-2112.5.11 Specifications for Neighboring Cells.............................................................................................12-24

12.6 Physical Layer Data Configuration Guidelines.........................................................................................12-2412.6.1 Interface Boards Applicable to Terrestrial Interfaces......................................................................12-2512.6.2 Upper-Layer Applications Supported by Interface Boards..............................................................12-2612.6.3 Numbering of Links Carried on AOUa Optical Ports......................................................................12-26



v

12.6.4 Ports on the AEUa/AOUa................................................................................................................12-2912.6.5 Configuration Requirements for E1/T1 Links and IMA Links........................................................12-3112.6.6 Configuration Specifications for ATM-Based Ports........................................................................12-3112.6.7 Requirements of PPP/MLPPP Configuration..................................................................................12-32

12.7 ATM Transport.........................................................................................................................................12-3212.7.1 UNI Mode........................................................................................................................................12-3312.7.2 Fractional ATM................................................................................................................................12-3412.7.3 Timeslot Cross Connection..............................................................................................................12-3612.7.4 IMA Mode........................................................................................................................................12-37

12.8 PVC Parameters of the RNC.....................................................................................................................12-3912.8.1 VPI and VCI.....................................................................................................................................12-3912.8.2 Service Type.....................................................................................................................................12-4012.8.3 Traffic Parameters............................................................................................................................12-4112.8.4 ATM Traffic Resource Configuration Guidelines...........................................................................12-42

12.9 AAL2 Configuration Guidelines...............................................................................................................12-4212.9.1 Working Principles of AAL2 Paths.................................................................................................12-4312.9.2 AAL2 Route.....................................................................................................................................12-43

12.10 MTP3-b/M3UA Configuration Guidelines.............................................................................................12-4312.10.1 Types of and Specifications for the MTP3-b/M3UA DSPs...........................................................12-4412.10.2 MTP3-b/M3UA DSP Index...........................................................................................................12-4512.10.3 Signaling Route Mask and Signaling Link Mask...........................................................................12-4512.10.4 Configuration Guidelines for MTP3-b/M3UA..............................................................................12-4612.10.5 Adjacent Node ID...........................................................................................................................12-46

12.11 Cell-Related Concepts.............................................................................................................................12-4712.11.1 Definitions of Sector, Carrier, and Cell..........................................................................................12-4712.11.2 Definitions of Local Cell and Logical Cell....................................................................................12-4812.11.3 Logical Cell Model.........................................................................................................................12-4912.11.4 Areas of Logical Cells....................................................................................................................12-5012.11.5 Definition of Neighboring Cell......................................................................................................12-50

12.12 Configurations of RAN Sharing..............................................................................................................12-5012.12.1 Operator-Based License Control....................................................................................................12-5112.12.2 Operator-Based Configuration at the Iub Transport Network Layer.............................................12-5212.12.3 Operator-Based Configuration of Cells and NodeBs.....................................................................12-5312.12.4 Operator-Based Configuration on the Iu Interface.........................................................................12-54

12.13 TRM Configuration Guidelines..............................................................................................................12-5512.14 Activity Factor Configuration Guidelines...............................................................................................12-60

ContentsRNC


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

Issue 03 (2008-08-30)

Figures

Figure 1-1 Interface of the LMT..........................................................................................................................1-2Figure 1-2 Example of the parameter relationship diagram...............................................................................1-18Figure 4-1 Parameter relationship in the addition of the global location data.....................................................4-6Figure 6-1 Protocol stack for the ATM-based Iub interface................................................................................6-5Figure 6-2 Links on the Iub interface (over ATM)..............................................................................................6-6Figure 6-3 IPoA PVCs from the RNC to NodeBs................................................................................................6-8Figure 6-4 Parameter relationship in the addition of the SAAL link.................................................................6-15Figure 6-5 Parameter relationship in the addition of the adjacent node.............................................................6-15Figure 6-6 Parameter relationship in the addition of the port controller on the ATM-based interface..............6-18Figure 6-7 Parameter relationship in the addition of the AAL2 path in the ATM-based interface...................6-19Figure 6-8 Parameter relationship in the addition of the IPoA PVC..................................................................6-20Figure 6-9 Parameter relationship in the addition of the OM IP address of the NodeB in ATM transport mode.............................................................................................................................................................................6-21Figure 6-10 Protocol stack for IP transport on the Iub interface........................................................................6-23Figure 6-11 Links on the Iub interface (over IP)................................................................................................6-24Figure 6-12 Layer 2 networking on the Iub interface.........................................................................................6-25Figure 6-13 Layer 3 networking on the Iub interface.........................................................................................6-26Figure 6-14 Example of routing between the M2000 and the NodeB through the RNC...................................6-28Figure 6-15 Example of routing between the M2000 and the NodeB not through the RNC.............................6-30Figure 6-16 Parameter relationship in the addition of the SCTP link................................................................6-37Figure 6-17 Parameter relationship in the addition of the IP adjacent node......................................................6-37Figure 6-18 Parameter relationship in the addition of the port data...................................................................6-38Figure 6-19 Parameter relationship in the addition of the port controller on the IP-based interface.................6-40Figure 6-20 Parameter relationship in the addition of the IP path.....................................................................6-41Figure 6-21 ATM/IP-based networking.............................................................................................................6-44Figure 6-22 Typical configuration of boards in the RSS subrack for ATM/IP hybrid transport.......................6-45Figure 6-23 Typical configuration of boards in an RBS subrack for ATM/IP hybrid transport........................6-46Figure 6-24 Layer 2 networking on the Iub interface.........................................................................................6-48Figure 6-25 Layer 3 networking on the Iub interface.........................................................................................6-48Figure 6-26 Example of routing between the M2000 and the NodeB through the RNC...................................6-50Figure 6-27 Example of routing between the M2000 and the NodeB not through the RNC.............................6-52Figure 7-1 Protocol stack for the ATM-based Iu-CS interface............................................................................7-5Figure 7-2 Links on the Iu-CS interface (over ATM)..........................................................................................7-6Figure 7-3 Example of connections between the MSC server and the RNC.......................................................7-7

RNCRNC Initial Configuration Guide Figures


vii

Figure 7-4 Iu-CS interface in the 3GPP R4/R5/R6..............................................................................................7-8Figure 7-5 Example of the topology on the Iu-CS interface in the 3GPP R4/R5/R6...........................................7-8Figure 7-6 Protocol stack for the ATM-based Iu-CS interface............................................................................7-9Figure 7-7 Protocol stack for the IP-based Iu-CS interface.................................................................................7-9Figure 7-8 Parameter relationship in the addition of the MTP3-b link..............................................................7-13Figure 7-9 Parameter relationship in the addition of the CN node.....................................................................7-13Figure 7-10 Parameter relationship in the addition of the port controller on the ATM-based interface............7-16Figure 7-11 Parameter relationship in the addition of the AAL2 path and the AAL2 route..............................7-17Figure 7-12 Protocol stack for the IP-based Iu-CS interface.............................................................................7-18Figure 7-13 Links on the Iu-CS interface (over IP)...........................................................................................7-19Figure 7-14 Example of connections between the MSC server and the RNC...................................................7-20Figure 7-15 Iu-CS interface in the 3GPP R4/R5/R6..........................................................................................7-21Figure 7-16 Example of the topology on the Iu-CS interface in the 3GPP R4/R5/R6.......................................7-21Figure 7-17 Protocol stack for the ATM-based Iu-CS interface........................................................................7-22Figure 7-18 Protocol stack for the IP-based Iu-CS interface.............................................................................7-22Figure 7-19 Parameter relationship in the addition of the M3UA link..............................................................7-25Figure 7-20 Parameter relationship in the addition of the CN node...................................................................7-25Figure 7-21 Parameter relationship in the addition of the port controller on the IP-based interface.................7-29Figure 8-1 Protocol stack for the ATM-based Iu-PS interface.............................................................................8-5Figure 8-2 Links on the Iu-PS interface (over ATM)...........................................................................................8-6Figure 8-3 IPoA PVC on the Iu-PS interface.......................................................................................................8-7Figure 8-4 Parameter relationship in the addition of the MTP3-b link..............................................................8-11Figure 8-5 Parameter relationship in the addition of the CN node.....................................................................8-11Figure 8-6 Parameter relationship in the addition of the IP path and IP route on the ATM-based Iu-PS interface.............................................................................................................................................................................8-14Figure 8-7 Protocol stack for the IP-based Iu-PS interface................................................................................8-16Figure 8-8 Links on the Iu-PS interface (over IP)..............................................................................................8-17Figure 8-9 Parameter relationship in the addition of the M3UA link................................................................8-19Figure 8-10 Parameter relationship in the addition of the CN node...................................................................8-20Figure 8-11 Parameter relationship in the addition of the port controller on the IP-based interface.................8-23Figure 9-1 Protocol stack for the ATM-based Iur interface.................................................................................9-5Figure 9-2 Links on the Iur interface (over ATM)...............................................................................................9-6Figure 9-3 IP route configuration on the Iur interface.........................................................................................9-7Figure 9-4 Parameter relationship in the addition of the MTP3-b link..............................................................9-10Figure 9-5 Parameter relationship in the addition of the port controller on the ATM-based interface..............9-13Figure 9-6 Parameter relationship in the addition of the AAL2 path in the ATM-based interface...................9-14Figure 9-7 Protocol stack for IP transport on the Iur interface...........................................................................9-16Figure 9-8 Links on the Iur Interface (over IP)..................................................................................................9-17Figure 9-9 IP route configuration on the Iur interface.......................................................................................9-18Figure 9-10 Parameter relationship in the addition of the M3UA link..............................................................9-20Figure 9-11 Parameter relationship in the addition of the port controller on the IP-based interface.................9-23Figure 10-1 Protocol stack for the Iu-BC interface............................................................................................10-4Figure 10-2 RNC-CBC networking through an SGSN......................................................................................10-5

FiguresRNC


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

Issue 03 (2008-08-30)

Figure 10-3 Links on the Iu-BC interface..........................................................................................................10-5Figure 10-4 IPoA configuration on the Iu-BC interface networked through an SGSN.....................................10-6Figure 10-5 Parameter relationship in the addition of the IPoA PVC................................................................10-8Figure 10-6 Parameter relationship in the addition of the SABP data...............................................................10-9Figure 11-1 Parameter relationship in the quick addition of a cell....................................................................11-3Figure 11-2 Parameter relationship in the addition of an intra-frequency neighboring cell that belongs to the localRNC.....................................................................................................................................................................11-5Figure 11-3 Parameter relationship in the addition of an intra-frequency neighboring cell that belongs to aneighboring RNC................................................................................................................................................11-5Figure 11-4 Parameter relationship in the addition of an inter-frequency neighboring cell that belongs to the localRNC.....................................................................................................................................................................11-7Figure 11-5 Parameter relationship in the addition of an inter-frequency neighboring cell that belongs to aneighboring RNC................................................................................................................................................11-7Figure 11-6 Parameter relationship in the addition of the neighboring GSM cell.............................................11-9Figure 12-1 Numbered subracks........................................................................................................................12-5Figure 12-2 Components of the PLMN ID......................................................................................................12-15Figure 12-3 Components of the LAI................................................................................................................12-15Figure 12-4 Components of the SAI................................................................................................................12-16Figure 12-5 Components of the RAI................................................................................................................12-16Figure 12-6 Example of planning the value ranges of PLMN value tags........................................................12-17Figure 12-7 Relationship between the physical links configured on the AEUa and AOUa boards and the E1/T1physical ports.....................................................................................................................................................12-30Figure 12-8 Mapping between the ATM cell and the E1 timeslots in UNI mode...........................................12-33Figure 12-9 Fractional ATM mode..................................................................................................................12-34Figure 12-10 Fractional ATM function............................................................................................................12-35Figure 12-11 Principles of timeslot cross connection......................................................................................12-36Figure 12-12 Principles of timeslot cross connection......................................................................................12-37Figure 12-13 Working principles of the IMA mode........................................................................................12-38Figure 12-14 IMA frame..................................................................................................................................12-38Figure 12-15 Relationship between VC and VP..............................................................................................12-40Figure 12-16 Relationship between an AAL2 path and AAL2 connections....................................................12-43Figure 12-17 Example of the AAL2 route.......................................................................................................12-43Figure 12-18 Relation between signaling link mask and signaling route mask...............................................12-45Figure 12-19 Relations between sector, frequency, and cell............................................................................12-48Figure 12-20 Logical cell configuration model................................................................................................12-49

RNCRNC Initial Configuration Guide Figures


ix

Tables

Table 3-1 Global data...........................................................................................................................................3-2Table 3-2 Equipment data.....................................................................................................................................3-3Table 3-3 MSP data..............................................................................................................................................3-3Table 3-4 Basic data of the NodeB.......................................................................................................................3-5Table 3-5 Data on the physical layer - 1...............................................................................................................3-5Table 3-6 Data on the physical layer - 2...............................................................................................................3-6Table 3-7 Data of the IMA group.........................................................................................................................3-6Table 3-8 Data on the control plane..................................................................................................................... 3-6Table 3-9 Data on the user plane..........................................................................................................................3-7Table 3-10 Data of the OM channel.....................................................................................................................3-8Table 3-11 Basic data of the NodeB.....................................................................................................................3-8Table 3-12 Data on the physical layer - 1.............................................................................................................3-9Table 3-13 Data on the physical layer - 2.............................................................................................................3-9Table 3-14 Data on the data link layer...............................................................................................................3-10Table 3-15 Data on the physical layer - 3...........................................................................................................3-10Table 3-16 Data on the control plane.................................................................................................................3-11Table 3-17 Data on the user plane......................................................................................................................3-12Table 3-18 Data of the OM channel...................................................................................................................3-12Table 3-19 Iub data transmission mode planning...............................................................................................3-13Table 3-20 Basic data of the NodeB...................................................................................................................3-14Table 3-21 Data on the physical layer - 1...........................................................................................................3-14Table 3-22 Data on the physical layer - 2...........................................................................................................3-14Table 3-23 Data of the IMA group.....................................................................................................................3-15Table 3-24 Data on the physical layer - 1...........................................................................................................3-15Table 3-25 Data on the physical layer - 2...........................................................................................................3-16Table 3-26 Data on the data link layer...............................................................................................................3-16Table 3-27 Data on the physical layer - 3...........................................................................................................3-16Table 3-28 Data on the control plane.................................................................................................................3-17Table 3-29 Data on the control plane.................................................................................................................3-18Table 3-30 Data on the user plane......................................................................................................................3-18Table 3-31 Data on the user plane......................................................................................................................3-19Table 3-32 Data of the OM channel...................................................................................................................3-19Table 3-33 Data of the OM channel...................................................................................................................3-20

RNCRNC Initial Configuration Guide Tables


xi

Table 3-34 Basic data of the CS domain............................................................................................................3-21Table 3-35 Data on the physical layer - 2...........................................................................................................3-21Table 3-36 Data of the IMA group.....................................................................................................................3-22Table 3-37 Data about timers.............................................................................................................................3-22Table 3-38 Data on the Iu-CS control plane.......................................................................................................3-23Table 3-39 Data on the Iu-CS user plane...........................................................................................................3-23Table 3-40 Basic data of the CS domain............................................................................................................3-24Table 3-41 Data on the physical layer - 2...........................................................................................................3-24Table 3-42 Data on the data link layer...............................................................................................................3-25Table 3-43 Data on the physical layer - 3...........................................................................................................3-25Table 3-44 Data on the Iu-CS control plane.......................................................................................................3-26Table 3-45 Data on the Iu-CS user plane...........................................................................................................3-27Table 3-46 Basic data of the PS domain.............................................................................................................3-27Table 3-47 Data on the physical layer - 2...........................................................................................................3-28Table 3-48 Data about timers.............................................................................................................................3-28Table 3-49 Data on the Iu-PS control plane.......................................................................................................3-29Table 3-50 Data on the Iu-PS user plane............................................................................................................3-29Table 3-51 Basic data of the PS domain.............................................................................................................3-30Table 3-52 Data on the physical layer - 2...........................................................................................................3-31Table 3-53 Data on the data link layer...............................................................................................................3-31Table 3-54 Data on the physical layer - 3...........................................................................................................3-31Table 3-55 Data on the Iu-PS control plane.......................................................................................................3-32Table 3-56 Data on the Iu-PS user plane............................................................................................................3-33Table 3-57 Basic data of the neighboring RNC.................................................................................................3-33Table 3-58 Data on the physical layer - 2...........................................................................................................3-34Table 3-59 Data about timers.............................................................................................................................3-34Table 3-60 Data on the Iur control plane............................................................................................................3-35Table 3-61 Data on the Iur user plane................................................................................................................3-35Table 3-62 Basic data of the neighboring RNC.................................................................................................3-36Table 3-63 Data on the physical layer - 2...........................................................................................................3-37Table 3-64 Data on the data link layer...............................................................................................................3-37Table 3-65 Data on the physical layer - 3...........................................................................................................3-38Table 3-66 Data on the Iur control plane............................................................................................................3-38Table 3-67 Data on the Iur user plane................................................................................................................3-39Table 3-68 Data on the physical layer - 2...........................................................................................................3-40Table 3-69 Data Negotiated on the Iu-BC Interface...........................................................................................3-40Table 3-70 Data for quick addition of a cell.......................................................................................................3-41Table 3-71 Intra-/inter-frequency neighboring cells...........................................................................................3-42Table 3-72 Basic data of inter-/intra-frequency neighboring cells.....................................................................3-42Table 3-73 Neighboring GSM cells....................................................................................................................3-42Table 3-74 Basic data of neighboring GSM cells...............................................................................................3-43Table 6-1 Data carried on SAAL links of UNI type.............................................................................................6-7

TablesRNC


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

Issue 03 (2008-08-30)

Table 6-2 TRM mapping data to be negotiated and planned..............................................................................6-17Table 6-3 Activity factor to be negotiated and planned.....................................................................................6-17Table 6-4 Data carried on SCTP links................................................................................................................6-24Table 6-5 IP addresses on the Iub interface........................................................................................................6-26Table 6-6 Route on the Iub Interface..................................................................................................................6-27Table 6-7 Routes for the connection between the M2000 and the NodeB through the RNC............................6-28Table 6-8 Routes for the connection between the M2000 and the NodeB not through the RNC......................6-30Table 6-9 TRM mapping data to be negotiated and planned..............................................................................6-39Table 6-10 Activity factor to be negotiated and planned...................................................................................6-40Table 6-11 IP addresses on the Iub interface......................................................................................................6-49Table 6-12 Route on the Iub Interface................................................................................................................6-49Table 6-13 Routes for the connection between the M2000 and the NodeB through the RNC..........................6-50Table 6-14 Routes for the connection between the M2000 and the NodeB not through the RNC....................6-52Table 7-1 Differences between signaling point configuration in R99 and that in R4/R5/R6.............................7-10Table 7-2 TRM mapping data to be negotiated and planned..............................................................................7-15Table 7-3 Activity factor to be negotiated and planned.....................................................................................7-15Table 7-4 Differences between signaling point configuration in R99 and that in R4/R5/R6.............................7-23Table 7-5 TRM mapping data to be negotiated and planned..............................................................................7-28Table 7-6 Activity factor to be negotiated and planned.....................................................................................7-28Table 8-1 IPoA data on the user plane of the ATM-based Iu-PS interface..........................................................8-7Table 8-2 TRM mapping data to be negotiated and planned..............................................................................8-13Table 8-3 Activity factor to be negotiated and planned.....................................................................................8-13Table 8-4 TRM mapping data to be negotiated and planned..............................................................................8-22Table 8-5 Activity factor to be negotiated and planned.....................................................................................8-22Table 9-1 TRM mapping data to be negotiated and planned..............................................................................9-12Table 9-2 Activity factor to be negotiated and planned.....................................................................................9-12Table 9-3 TRM mapping data to be negotiated and planned..............................................................................9-22Table 9-4 Activity factor to be negotiated and planned.....................................................................................9-23Table 10-1 IPoA data on the Iu-BC interface.....................................................................................................10-6Table 12-1 Types of RNC optical ports..............................................................................................................12-3Table 12-2 Suggested numbering of common physical channels....................................................................12-11Table 12-3 Suggested numbering of common transport channels...................................................................12-12Table 12-4 Traffic specifications for physical links and ports.........................................................................12-18Table 12-5 Specifications for the traffic on boards..........................................................................................12-19Table 12-6 IDs of and specifications for common physical channels..............................................................12-22Table 12-7 IDs of and specifications for common transport channels.............................................................12-23Table 12-8 Default power specifications for cells and channels......................................................................12-23Table 12-9 Recommended ATM interface boards...........................................................................................12-25Table 12-10 Recommended IP interface boards...............................................................................................12-25Table 12-11 Upper-layer applications supported by ATM interface boards....................................................12-26Table 12-12 Upper-layer applications supported by IP interface boards.........................................................12-26Table 12-13 Relationship between link numbers of AOUa optical ports and transmission equipment numbers...........................................................................................................................................................................12-27

RNCRNC Initial Configuration Guide Tables


xiii

Table 12-14 Restrictions on the specifications of physical links for the AEUa and AOUa boards.................12-30Table 12-15 Methods of configuring fractional ATM links and fractional IMA links....................................12-35Table 12-16 Types of service...........................................................................................................................12-40Table 12-17 Features of different ATM services.............................................................................................12-40Table 12-18 ATM traffic parameters................................................................................................................12-41Table 12-19 Recommended service types for links on different interfaces.....................................................12-42Table 12-20 Types of and specifications for the DSPs....................................................................................12-44Table 12-21 Recommended PHB settings on the hybrid-IP-based Iub interface.............................................12-56Table 12-22 Recommended settings of TRM mapping on the hybrid-IP-based Iub interface.........................12-56Table 12-23 Recommended PHB settings on the ATM/IP-based Iub interface...............................................12-58Table 12-24 Recommended settings of TRM mapping on the ATM/IP-based Iub interface..........................12-58Table 12-25 Default settings of activity factors...............................................................................................12-60

TablesRNC


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

Issue 03 (2008-08-30)

About This Document

Purpose

This document describes the initial configuration of Huawei Radio Network Controller.

Version

The following table lists the product version related to this document.

Product Name Model Version

RNC BSC6810 V200R010

Intended Audience

This document is intended for field engineers.

Before performing the tasks in this document, familiarize yourself with the working principles,system architecture, and hardware components of the RNC.

Change History

Refer to Changes in RNC Initial Configuration Guide.

Organization

1 Introduction to RNC Initial Configuration

This defines RNC initial configuration and describes the configuration scenario, configurationmethod, and scripts for configuration.

2 Procedure of RNC Initial Configuration

This describes the procedure of RNC initial configuration. After the initial configuration, a scriptfor loading is available.

3 Data Preparation for RNC Initial Configuration

The data that needs to be prepared for RNC initial configuration consists of the global data,equipment data, cell data, and data negotiated between the RNC and other network elements.

4 Configuring RNC Global Data

RNCRNC Initial Configuration Guide About This Document


1

This describes how to configure RNC global data. This is an essential step in RNC initialconfiguration. Global data configuration takes precedence over configuration of equipment data,interface data, and cell data.

5 Configuring RNC Equipment Data

This describes how to configure RNC equipment data. The data includes RNC clock-relateddata, RNC time, basic data of the RSS subrack, and basic data of each RBS subrack.

6 Configuring Iub Interface Data (Initial)

The Iub interface is the logical interface between the RNC and the NodeB. This topic describeshow to add the transport network layer data on the Iub interface on the RNC side.

7 Configuring Iu-CS Interface Data (Initial)

The Iu-CS is the logical interface between the RNC and the CS domain. The RNC exchangesthe CS data with the CN through the Iu-CS interface. This topic describes how to add the transportnetwork layer data on the Iu-CS interface.

8 Configuring Iu-PS Interface Data (Initial)

The Iu-PS is the logical interface between the RNC and the PS domain. The RNC exchangesthe packet domain data with the CN through the Iu-PS interface. This topic describes how toadd the transport network layer data on the Iu-PS interface.

9 Configuring Iur Interface Data (Initial)

An Iur interface is a logical interface between RNCs. This topic describes how to add thetransport network layer data on the Iur interface.

10 Configuring Iu-BC Interface Data (Initial)

An Iu-BC interface is a logical interface between the RNC and CBC. This topic describes howto add the transport network layer data on the Iu-BC interface.

11 Configuring Cell Data (Initial)

This describes how to configure cell data of the radio network layer. The related activities arethe quick setup of cells, the addition of inter-frequency neighboring cell relationships, intra-frequency neighboring cell relationships, and inter-RAT neighboring cell relationships, andswitching all subracks to the online mode after the cell data configuration is complete.

12 Related Information for RNC Initial Configuration

This reference part covers the concepts, principles, rules, and conventions that should beunderstood before data configuration.

Conventions1. Symbol Conventions

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

Symbol Description

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

About This DocumentRNC


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

Issue 03 (2008-08-30)

Symbol Description

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.

[ 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

RNCRNC Initial Configuration Guide About This Document


3


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 DocumentRNC


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

Issue 03 (2008-08-30)

1 Introduction to RNC Initial Configuration

About This Chapter

This defines RNC initial configuration and describes the configuration scenario, configurationmethod, and scripts for configuration.

1.1 Definition of RNC Initial ConfigurationRNC initial configuration refers to a process of data configuration for the RNC to start to work.The process consists of the composition and execution of configuration scripts.

1.2 RNC Initial Configuration ToolThe RNC initial configuration tool is a text editor that creates the RNC initial configurationscript through the addition, deletion, and modification of MML commands when the MMLcommands are available.

1.3 Components of the RNC Initial Configuration ScriptA complete RNC initial configuration script consists of global data, equipment data, interfacedata, and cell data.

1.4 Conventions in Parameter Relationship DiagramsParameter relationship diagrams show the relationships between the parameters of MMLcommands.

RNCRNC Initial Configuration Guide 1 Introduction to RNC Initial Configuration


1-1

1.1 Definition of RNC Initial ConfigurationRNC initial configuration refers to a process of data configuration for the RNC to start to work.The process consists of the composition and execution of configuration scripts.

After the RNC is initially installed, prepare and configure data based on the hardwareconfiguration of the RNC, network planning, and negotiation between the RNC and otherequipment. Then, you can obtain an MML script in .txt format.

The data in the MML script must be complete, consistent, and valid. After the script is executed,a data file is generated and then loaded onto the RNC host. The RNC then starts to work properly.

The correct initial configuration data is a prerequisite for the RNC to start to run. Modificationof data during the proper running of the RNC is not initial configuration. For details about datareconfiguration, refer to the RAN Reconfiguration Guide.

NOTE

During the execution and modification of the script, a data file is generated and then loaded onto the RNChost to take effect. For details, refer to Loading RNC Software and Data Files.

1.2 RNC Initial Configuration ToolThe RNC initial configuration tool is a text editor that creates the RNC initial configurationscript through the addition, deletion, and modification of MML commands when the MMLcommands are available.

The Local Maintenance Terminal (LMT) is an RNC initial configuration tool. Figure 1-1 showsthe interface of the LMT.

Figure 1-1 Interface of the LMT

1 Introduction to RNC Initial ConfigurationRNC


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

Issue 03 (2008-08-30)

1.3 Components of the RNC Initial Configuration ScriptA complete RNC initial configuration script consists of global data, equipment data, interfacedata, and cell data.

1.3.1 Example: Global Data in the RNC Initial Configuration ScriptThis describes global data in the RNC initial configuration script. The global data includes thebasic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, globallocation data, and data of the local M3UA entity.

1.3.2 Example: Equipment Data in the RNC Initial Configuration ScriptThe equipment data includes the data of the RSS subrack, RBS subrack, RNC time and clock,and IP address of the EMS server.

1.3.3 Example: Interface Data in the RNC Initial Configuration ScriptThis describes interface data in the RNC initial configuration script. The interfaces refer to Iub,Iu-CS, Iu-PS, Iu-BC, and Iur.

1.3.4 Example: Cell Data in the RNC Initial Configuration ScriptThis describes cell data in the RNC initial configuration script. The cell data includes the dataof local cells, logical cells, intra-frequency neighboring cells, inter-frequency neighboring cells,and neighboring GSM cells. This example describes only how to quickly add local cells andlogical cells.

1.3.1 Example: Global Data in the RNC Initial Configuration ScriptThis describes global data in the RNC initial configuration script. The global data includes thebasic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, globallocation data, and data of the local M3UA entity.

//Set the RNC to offline mode.

SET OFFLINE: SRN=ALL, BULKT=OFF;

//Add basic data to the RNC.

//Add the basic data of the RNC.

ADD RNCBASIC: RncId=1, SharingSupport=NO, InterPlmnHoAllowed=NO;

//Add an operator ID.

ADD CNOPERATOR: CnOpIndex=0, CnOperatorName="Operator", PrimaryOperatorFlag=YES, MCC="460", MNC="00";

//Set the Iu-Flex information.

SET IUFLEX: CnOpIndex=0, CsIuFlexFlag=OFF, PsIuFlexFlag=OFF, NNSfTmr=3, NullNRI=0, CsInfoUpdFlag=OFF, PsInfoUpdFlag=OFF;

//Set the internal subnet numbers of the RNC, including the system subnet number and thedebugging subnet number.

SET SUBNET: SUBNET=90, DEBUGSUBNET=193;



1-3

//Plan and configure the IP-based Iu-PS interface and set the SCTP service listening port.

SET SCTPSRVPORT:NBAPSRVPN=58080, M3UASRVPN=2905;

//Add OSP to the RNC.

ADD OPC:NI=NAT, SPCBITS=BIT14, SPC=H'0008B8, RSTFUN=OFF, NSAP=H'45000006598540088F0000000000000000000000, NAME="RNC";

//Add the global location data.

ADD LAC: CnOpIndex=0, LAC=100, PlmnValTagMin=1, PlmnValTagMax=64;ADD SAC: CnOpIndex=0, LAC=100, SAC=100;ADD RAC: CnOpIndex=0, LAC=100, RAC=0, PlmnValTagMin=65, PlmnValTagMax=128;ADD URA: URAId=0, CnOpIndex=0;ADD URA: URAId=1, CnOpIndex=0;

//Plan and configure the IP-based Iu-PS interface and add the data of the local M3UA entity.

ADD M3LE: LENO=0, ENTITYT=M3UA_IPSP, RTCONTEXT=1, NAME="RNC";

1.3.2 Example: Equipment Data in the RNC Initial ConfigurationScript

The equipment data includes the data of the RSS subrack, RBS subrack, RNC time and clock,and IP address of the EMS server.

//Modify the data of the RSS subrack.

MOD SUBRACK: SRN=0, SRName="RSS";SET CLKTYPE: CLKTYPE=GCU;RMV BRD: SRN=0, SN=8;RMV BRD: SRN=0, SN=9;RMV BRD: SRN=0, SN=10;RMV BRD: SRN=0, SN=11;RMV BRD: SRN=0, SN=14;RMV BRD: SRN=0, SN=16;RMV BRD: SRN=0, SN=18;RMV BRD: SRN=0, SN=24;RMV BRD: SRN=0, SN=26;ADD BRD: SRN=0, BRDTYPE=DPU, SN=8;ADD BRD: SRN=0, BRDTYPE=DPU, SN=9;ADD BRD: SRN=0, BRDTYPE=DPU, SN=10;ADD BRD: SRN=0, BRDTYPE=DPU, SN=11;ADD BRD: SRN=0, BRDTYPE=AEU, SN=14, RED=NO;ADD BRD: SRN=0, BRDTYPE=AEU, SN=15, RED=NO;ADD BRD: SRN=0, BRDTYPE=UOI_ATM, SN=16, RED=YES;ADD BRD: SRN=0, BRDTYPE=GOU, SN=18, RED=YES;ADD BRD: SRN=0, BRDTYPE=UOI_ATM, SN=24, RED=YES;ADD BRD: SRN=0, BRDTYPE=UOI_ATM, SN=26, RED=YES;

//Add an RBS subrack.

ADD SUBRACK: SRN=1, SRName="RBS";ADD BRD: SRN=1, BRDTYPE=SPU, SN=8;ADD BRD: SRN=1, BRDTYPE=SPU, SN=10;ADD BRD: SRN=1, BRDTYPE=DPU, SN=14;ADD BRD: SRN=1, BRDTYPE=DPU, SN=16;ADD BRD: SRN=1, BRDTYPE=DPU, SN=18;ADD BRD: SRN=1, BRDTYPE=AOU, SN=20, RED=YES;ADD BRD: SRN=1, BRDTYPE=FG2, SN=22, RED=YES;ADD BRD: SRN=1, BRDTYPE=GOU, SN=24, RED=YES;ADD BRD: SRN=1, BRDTYPE=AEU, SN=26, RED=YES;




Issue 03 (2008-08-30)

//Set the RNC time.

//Set the time zone and daylight saving time.

SET TZ: ZONET=GMT+0800, DST=NO;

//Set the RNC clock data.

//Add clock sources.

ADD CLKSRC:SRCGRD=1, SRCT=BITS1-2MHZ;

ADD CLKSRC:SRCGRD=2, SRCT=LINE1_8KHZ;


//Set the clock source switching strategy.

SET CLKMODE:CLKWMODE=AUTO;

//Set clock sources for boards.

SET CLK: SRT=RBS, SRN=1, SN=20, BT=AOU, REF2MCLKSRC=0, REF2MCLKSW1=ON, REF2MCLKSW2=OFF;

SET CLK: SRT=RSS, SN=16, BT=UOI_ATM, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=ON, BACK8KCLKSW2=OFF;

SET CLK: SRT=RSS, SN=24, BT=UOI_ATM, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=OFF, BACK8KCLKSW2=ON;

//Add the IP address of the EMS server.

ADD EMSIP: EMSIP="10.218.100.4", MASK="255.255.255.0", BAMIP="10.218.100.12", BAMMASK="255.255.255.0";

1.3.3 Example: Interface Data in the RNC Initial ConfigurationScript

This describes interface data in the RNC initial configuration script. The interfaces refer to Iub,Iu-CS, Iu-PS, Iu-BC, and Iur.

1.3.3.1 Example: Iub Data in the RNC Initial Configuration ScriptThis describes an example of Iub data in the RNC initial configuration script. The Iub dataconsists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table,control plane data, user plane data, and OM channel data.

1.3.3.2 Example: Iu-CS Data in the RNC Initial Configuration ScriptThis describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS dataconsists of the physical layer data, ATM traffic resource data, TRM mapping, activity factortable, control plane data, and user plane data.

1.3.3.3 Example: Iu-PS Data in the RNC Initial Configuration ScriptThis describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS dataconsists of the physical layer data, TRM mapping, activity factor table, control plane data, anduser plane data.

1.3.3.4 Example: Iur Data in the RNC Initial Configuration Script



1-5

This describes an example of Iur data in the RNC initial configuration script. The Iur data consistsof the physical layer data, ATM traffic resources, TRM mapping, activity factor table, controlplane data, and user plane data.

1.3.3.5 Example: Iu-BC Data in the RNC Initial Configuration ScriptThis describes an example of Iu-BC data in the RNC initial configuration script. The Iu-BC dataconsists of the physical layer data, ATM traffic records, IPoA data, and SABP data.

Example: Iub Data in the RNC Initial Configuration ScriptThis describes an example of Iub data in the RNC initial configuration script. The Iub dataconsists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table,control plane data, user plane data, and OM channel data.

//Take the script for the ATM-based Iub interface as an example.

//Set E1/T1 parameters. For all the links carried on the AEUa board in slot 14 of subrack 0, setworking mode to E1, set frame structure to E1 CRC4 multi-frame, set coding type to HDB3,and enable scrambling.

SET E1T1: SRN=0, SN=14, BT=AEU, LS=ALL, WORKMODE=E1_UNBA, LNKT=E1_CRC4_MULTI_FRAME, LNKCODE=HDB3, SCRAMBLESW=ON;

//Add an IMA group and add IMA links to the group. Configure an IMA group on the AEUaboard in slot 14 of subrack 0. Then, add IMA links numbered from 1 through 6 to the IMA group.

ADD IMAGRP: SRN=0, SN=14, BT=AEU, IMAGRPN=0, MINLNKNUM=1, IMAID=0, TXFRAMELEN=D128, DCB=25, IMAVER=V1.0,DLYGB=8;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=1;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=2;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=3;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=4;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=5;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=6;

//Add ATM traffic records.

ADD ATMTRF: TRFX=110, ST=RTVBR, UT=CELL/S, PCR=217, SCR=170, MBS=1000, CDVT=1024, REMARK="FOR IUB NCP";ADD ATMTRF: TRFX=120, ST=RTVBR, UT=CELL/S, PCR=2000, SCR=548, MBS=1000, CDVT=1024, REMARK="FOR IUB CCP";ADD ATMTRF: TRFX=130, ST=RTVBR, UT=CELL/S, PCR=83, SCR=76, MBS=1000, CDVT=1024, REMARK="FOR IUB ALCAP";ADD ATMTRF: TRFX=140, ST=RTVBR, UT=CELL/S, PCR=5312, SCR=4831, MBS=1000, CDVT=1024, REMARK="FOR R99 RT";ADD ATMTRF: TRFX=150, ST=NRTVBR, UT=CELL/S, PCR=13154, SCR=10854, MBS=1000, CDVT=1024, REMARK="FOR R99 NRT";ADD ATMTRF: TRFX=160, ST=UBR, CDVT=1024, REMARK="IUB FOR IPOA";

//Add TRM mapping tables to be used by gold, silver, and bronze users.

ADD TRMMAP: TMI=0, ITFT=IUB_IUR_IUCS, TRANST=ATM;ADD TRMMAP: TMI=1, ITFT=IUB_IUR_IUCS, TRANST=ATM;ADD TRMMAP: TMI=2, ITFT=IUB_IUR_IUCS, TRANST=ATM;

//Add an activity factor table.




Issue 03 (2008-08-30)

ADD FACTORTABLE: FTI=0, REMARK="FOR IUB";

//Add the Iub control plane data.

//Add SAAL links. The SAAL links are numbered from 0 through 2. They are terminated atsubsystem 0 of the SPUa board in slot 2 of subrack 0.

//Add an SAAL link used to carry the NCP.

ADD SAALLNK: SRN=0, SN=2, SSN=0, SAALLNKN=0, CARRYT=IMA, CARRYSRN=0, CARRYSN=14, CARRYIMAGRPN=0, CARRYVPI=1, CARRYVCI=40, TXTRFX=110, RXTRFX=110, SAALLNKT=UNI, CCTMR=1000, POLLTMR=750, IDLETMR=15000, RSPTMR=15000, KEEPTMR=2000, MAXCC=4, MAXPD=25, STATLEN=67, WINDOWSIZE=100;

//Add an SAAL link used to carry a CCP.


//Add an SAAL link used to carry the ALCAP.


//Add a NodeB and set the algorithm parameters.

ADD NODEB: NodeBName="NODEB1", NodeBId=1, SRN=0, SN=2, SSN=0, TnlBearerType=ATM_TRANS, TRANSDELAY=10, SATELLITEIND=FALSE, NodeBType=NORMAL, Nsap="H'45000006582414723F0000000000000000000000", NodeBProtclVer=R6, SharingSupport=NON_SHARED, CnOpIndex=0;

ADD NODEBALGOPARA: NODEBNAME="NODEB1", NODEBLDCALGOSWITCH=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CODE_LDR-1, NODEBHSDPAMAXUSERNUM=3840, NODEBHSUPAMAXUSERNUM=3840;

ADD NODEBLDR: NodeBName="NODEB1";

//Add the port data to the Iub interface.

//Add an NCP.

ADD NCP: NODEBNAME="NODEB1", CARRYLNKT=SAAL, SAALLNKN=0;

//Add a CCP.

ADD CCP: NODEBNAME="NODEB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=1;

//Add the Iub user plane data.

//Add a port controller.



1-7

ADD PORTCTRLER: SRN=0, SN=14, PT=IMA, CARRYIMAGRPN=0, CTRLSN=2, CTRLSSN=0, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0;

//Add an adjacent node over the Iub interface, that is, NODEB1. The adjacent node ID is 0 andthe interface type is Iub.

ADD ADJNODE: ANI=0, NAME="NODEB1", NODET=IUB, NODEBID=1, TRANST=ATM, IsROOTNODE=YES, SRN=0, SN=2, SSN=0, SAALLNKN=2, QAAL2VER=CS2;

//Set the mapping between the Iub adjacent node and transmission resources.

ADD ADJMAP: ANI=0, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=0, TMISLV=1, TMIBRZ=2, FTI=0;

//Add AAL2 paths towards NODEB1.

ADD AAL2PATH: ANI=0, PATHID=1, PT=RT, CARRYT=IMA, CARRYF=0, CARRYSN=14, CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=43, TXTRFX=140, RXTRFX=140, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10;


ADD AAL2PATH: ANI=0, PATHID=3, PT=NRT, CARRYT=IMA, CARRYF=0, CARRYSN=14, CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=45, TXTRFX=150, RXTRFX=150, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10;

//Add an AAL2 route towards NODEB1.

ADD AAL2RT: NSAP="H'45000006582414723F0000000000000000000000", ANI=0, RTX=0, OWNERSHIP=YES;

//Add the Iub OM channel data.

//Add the device IP address to a board. The local IP address is 10.218.107.126 and the subnetmask is 255.255.255.0.

ADD DEVIP: SRN=0, SN=14, IPADDR="10.218.107.126", MASK="255.255.255.0";

//Add an IPoA PVC. The local IP address is 10.218.107.126, the peer IP address is10.218.107.11, and the IPoA PVC is carried on IMA group 0.

ADD IPOAPVC: IPADDR="10.218.107.126", PEERIPADDR="10.218.107.11", CARRYT=IMA, CARRYIMAGRPN=0, CARRYVPI=1, CARRYVCI=46, TXTRFX=160, RXTRFX=160, PEERT=IUB;

//Add the OM IP address of the NodeB. The NodeB OM IP address is 10.218.107.11. Thegateway IP address on the RNC side, or the peer IP address of the IPoA PVC, is 10.218.107.11.




Issue 03 (2008-08-30)

ADD NODEBIP: NODEBID=1, NBTRANTP=ATMTRANS_IP, NBATMOAMIP="10.218.107.11", NBATMOAMMASK="255.255.255.0", ATMSRN=0, ATMSN=14, ATMGATEWAYIP="10.218.107.11";

Example: Iu-CS Data in the RNC Initial Configuration ScriptThis describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS dataconsists of the physical layer data, ATM traffic resource data, TRM mapping, activity factortable, control plane data, and user plane data.

//Take the script for the ATM-based Iu-CS interface as an example.

//Add physical layer data of the external interface for the RNC.

//Set attributes of all the optical ports on the UOI_ATM board in slot 16 of subrack 0.

SET OPT: SRN=0, SN=16, BT=UOI, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16byte, J0TXVALUE="SBS HuaWei 155",J0RXT=16byte, J0RXVALUE="SBS HuaWei 155", J1TXT=16byte, J1TXVALUE="SBS HuaWei 155", J1RXT=16byte, J1RXVALUE="SBS HuaWei 155";


//For the ATM traffic record on the control plane, the record index is 170, the service type isCBR, and the peak cell rate is 1500 cell/s.

//For the ATM traffic record on the user plane, the record index is 180, the service type is CBR,and the peak cell rate is 10000 cell/s.

ADD ATMTRF: TRFX=170, ST=CBR, UT=CELL/S, PCR=1500, CDVT=1024, REMARK="IUCS CONTROL PLANE";

ADD ATMTRF: TRFX=180, ST=CBR, UT=CELL/S, PCR=10000, CDVT=1024, REMARK="IUCS USER PLANE";

//Add TRM mapping records for gold, silver, and copper users respectively.


//Add activity factor tables for gold, silver, and copper users respectively.

ADD FACTORTABLE: FTI=3, REMARK="FOR IUCS GOLD USER";ADD FACTORTABLE: FTI=4, REMARK="FOR IUCS SILVER USER";ADD FACTORTABLE: FTI=5, REMARK="FOR IUCS BRONZE USER";

//Add the Iu-CS control plane data.

//Add SAAL links.

ADD SAALLNK: SRN=0, SN=2, SSN=1, SAALLNKN=10, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=16, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=100, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI, MPS=MPS_EMERGENCY, CCTMR=200, POLLTMR=100, IDLETMR=500, RSPTMR=5000, KEEPTMR=100, COMTMR1=2, COMTMR2=30, COMTMR3=10, SRECTMR=60, INHTMR=1500, MAXNRP=0, MAXCC=4, MAXPD=500, STATLEN=67, N1=1000, WINDOWSIZE=100;

ADD SAALLNK: SRN=0, SN=4, SSN=0, SAALLNKN=11, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=16,



1-9

CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=101, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI, MPS=MPS_EMERGENCY, CCTMR=200, POLLTMR=100, IDLETMR=500, RSPTMR=5000, KEEPTMR=100, COMTMR1=2, COMTMR2=30, COMTMR3=10, SRECTMR=60, INHTMR=1500, MAXNRP=0, MAXCC=4, MAXPD=500, STATLEN=67, N1=1000, WINDOWSIZE=100;



//Add RNC DSPs.

ADD N7DPC: DPX=0, DPC=H'0008DB, SLSMASK=B0000, NEIGHBOR=YES, NAME="TO-MGW", DPCT=IUCS, STP=OFF, PROT=ITUT, BEARTYPE=MTP3B;

//Add the MTP3-b data.

ADD MTP3BLKS: SIGLKSX=0, DPX=0, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-MGW";

ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="TO-MGW";

ADD MTP3BLNK: SIGLKSX=0, SIGSLC=0, SRN=0, SN=2, SSN=1, SAALLNKN=10, PRIORITY=0, TCLEN=10, TC=170, NAME="TO_MGW_0";




//Add an adjacent node over the Iu-CS interface.

ADD ADJNODE: ANI=1, NAME="MGW", NODET=IUCS, DPX=0, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS2;

//Configure the mapping between adjacent nodes and transmission resources.

ADD ADJMAP: ANI=1, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=3, TMISLV=4, TMIBRZ=5, FTIGLD=3, FTISLV=4, FTIBRZ=5;

//Add a CN domain and a CN node.




Issue 03 (2008-08-30)

ADD CNDOMAIN: CNDomainId=CS_DOMAIN, T3212=24, ATT=ALLOWED, DRXCycleLenCoef=6;

ADD CNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=ATM_TRANS;

//Add the Iu-CS user plane data.


ADD PORTCTRLER: SRN=0, SN=16, PT=NCOPT, CARRYNCOPTN=0, CTRLSN=4, CTRLSSN=1, FWDHORSVBW=100, BWDHORSVBW=100, FWDCONGBW=500, BWDCONGBW=500, FWDCONGCLRBW=750, BWDCONGCLRBW=750;

//Add AAL2 paths.

ADD AAL2PATH: ANI=1, PATHID=1, PT=RT, CARRYT=NCOPT, CARRYF=0, CARRYSN=16, CARRYNCOPTN=2, ADDTORSCGRP=NO, CARRYVPI=33, CARRYVCI=55, TXTRFX=180, RXTRFX=180, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10;



//Add AAL2 routes.

ADD AAL2RT:NSAP="H'45000006598540056F0000000000000000000000", ANI=1, RTX=1, OWNERSHIP=YES;

Example: Iu-PS Data in the RNC Initial Configuration ScriptThis describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS dataconsists of the physical layer data, TRM mapping, activity factor table, control plane data, anduser plane data.

//Take the script for the IP-based Iu-PS interface as an example.


//Set the attributes of an Ethernet port on a GOUa board.

SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOU, PN=0, MTU=1500, AUTO=ENABLE;

//Add the IP address of an Ethernet port used to connect to the gateway.

ADD ETHIP: SRN=0, SN=18, PN=0, IPTYPE=PRIMARY, IPADDR="10.218.161.50", MASK="255.255.255.192";



1-11

//Add device IP addresses. Among these device IP addresses, two IP addresses are used for dual-homing of SCTP on the control plane, and the other IP address is used for the user plane.

ADD DEVIP: SRN=0, SN=18, IPADDR="10.218.161.100", MASK="255.255.255.192";ADD DEVIP: SRN=0, SN=18, IPADDR="10.218.161.150", MASK="255.255.255.192";ADD DEVIP: SRN=0, SN=18, IPADDR="10.218.161.200", MASK="255.255.255.192";


ADD TRMMAP: TMI=6, ITFT=IUPS, EFDSCP=46, AF4DSCP=38, AF3DSCP=30, AF2DSCP=18, AF1DSCP=10, BEDSCP=0;ADD TRMMAP: TMI=7, ITFT=IUPS, EFDSCP=46, AF4DSCP=38, AF3DSCP=30, AF2DSCP=18, AF1DSCP=10, BEDSCP=0;ADD TRMMAP: TMI=8, ITFT=IUPS, EFDSCP=46, AF4DSCP=38, AF3DSCP=30, AF2DSCP=18, AF1DSCP=10, BEDSCP=0;


ADD FACTORTABLE: FTI=2, REMARK="FOR IUPS";

//Add the Iu-PS control plane data.

//Add SCTP links.

ADD SCTPLNK: SRN=0, SN=2, SSN=2, SCTPLNKN=0, MODE=CLIENT, APP=M3UA, DSCP=62, LOCPTNO=8010, LOCIPADDR1="10.218.161.100", LOCIPADDR2="10.218.161.150", PEERIPADDR1="10.20.18.4", PEERIPADDR2="10.20.18.68", PEERPORTNO=2905, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=60000, RTOINIT=3000, RTOALPHA=12, RTOBETA=25, HBINTER=5000, MAXASSOCRETR=10, MAXPATHRETR=5, CHKSUMTX=NO, CHKSUMRX=NO, CHKSUMTYPE=CRC32, MTU=1500, VLANFlAG=DISABLE, CROSSIPFLAG=UNAVAILABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10;


//Add a destination signaling point over the Iu-PS interface.

ADD N7DPC: DPX=2, DPC=H'0008E2, SLSMASK=B0000, NEIGHBOR=YES, NAME="SGSN", DPCT=IUPS, STP=OFF, PROT=ITUT, BEARTYPE=M3UA;

//Add the M3UA data.

//Add a destination M3UA entity.

ADD M3DE: DENO=10, LENO=0, DPX=2, ENTITYT=M3UA_IPSP, RTCONTEXT=1, NAME="SGSN";

//Add an M3UA signaling link set.




Issue 03 (2008-08-30)

ADD M3LKS: SIGLKSX=1, DENO=10, LNKSLSMASK=B1111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, PDTMRVALUE=5, NAME="SGSN";

//Add an M3UA route.ADD M3RT: DENO=10, SIGLKSX=1, PRIORITY=0, NAME="SGSN";

//Add M3UA signaling links.

ADD M3LNK: SIGLKSX=1, SIGLNKID=0, SRN=0, SN=2, SSN=2, SCTPLNKN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="LINKSGSN-01";


//Add an adjacent node.

ADD ADJNODE: ANI=2, NAME="SGSN", NODET=IUPS, SGSNFLG=YES, DPX=2, TRANST=IP;

//Set the mapping between the Iu-PS adjacent node and transmission resources.



ADD CNDOMAIN: CNDomainId=PS_DOMAIN, NMO=MODE2, DRXCycleLenCoef=6;

ADD CNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS;

//Add the Iu-PS user plane data.


ADD PORTCTRLER: SRN=0, SN=18, PT=ETHER, CARRYEN=0, CTRLSN=2, CTRLSSN=2, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0;

//Add IP paths.

ADD IPPATH: ANI=2, PATHID=0, PATHT=HQ_RT, IPADDR="10.218.161.200", PEERIPADDR="10.20.18.132", PEERMASK="255.255.255.192", TXBW=1000000, RXBW=1000000, CARRYFLAG=NULL, FPMUX=YES, SUBFRLEN=127,MAXFRAMELEN=270, FPTIME=2, DSCP=46, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.20.18.132", PERIOD=5, CHECKCOUNT=5, ICMPPKGLEN=64;

ADD IPPATH: ANI=2, PATHID=1, PATHT=HQ_NRT, IPADDR="10.218.161.200", PEERIPADDR="10.20.18.133",PEERMASK="255.255.255.192", TXBW=1000000, RXBW=1000000, CARRYFLAG=NULL, FPMUX=YES, SUBFRLEN=127,MAXFRAMELEN=270, FPTIME=2, DSCP=18, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.20.18.133", PERIOD=5, CHECKCOUNT=5, ICMPPKGLEN=64;

//Add an IP route.

ADD IPRT: SRN=0, SN=18, DESTIP="10.20.18.0", MASK="255.255.255.0",



1-13

NEXTHOP="10.218.161.1", PRIORITY=HIGH, REMARK="TO SGSN";

Example: Iur Data in the RNC Initial Configuration ScriptThis describes an example of Iur data in the RNC initial configuration script. The Iur data consistsof the physical layer data, ATM traffic resources, TRM mapping, activity factor table, controlplane data, and user plane data.

//Take the script for the ATM-based Iur interface as an example.


//Set the attributes of all the optical ports on the ATM-based UOIa board in slot 24 of subrack0.

SET OPT:SRN=0, SN=24, BT=UOI_ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16BYTE, J0TXVALUE="SBS HuaWei 155", J0RXT=16BYTE, J0RXVALUE="SBS HuaWei 155", J1TXT=16BYTE, J1TXVALUE="SBS HuaWei 155", J1RXT=16BYTE, J1RXVALUE="SBS HuaWei 155";



//For the ATM traffic record on the user plane, the record index is 200, the service type is CBR,and the peak cell rate is 5,000 cell/s.

ADD ATMTRF: TRFX=190, ST=CBR, UT=CELL/S, PCR=530, CDVT=1024, REMARK="IUR CONTROL PLANE";ADD ATMTRF: TRFX=200, ST=CBR, UT=CELL/S, PCR=5000, CDVT=1024, REMARK="IUR USER PLANE";




ADD FACTORTABLE: FTI=3, REMARK="FOR IUR";

//Add the Iur control plane data.

//Add SAAL links.

ADD SAALLNK: SRN=0, SN=4, SSN=0, SAALLNKN=100, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=101, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI, MPS=MPS_NEUTRAL, CCTMR=200, POLLTMR=100, IDLETMR=500, RSPTMR=5000, KEEPTMR=100, COMTMR1=2, COMTMR2=30, COMTMR3=10, SRECTMR=60, INHTMR=1500, MAXNRP=0, MAXCC=4, MAXPD=500, STATLEN=67, N1=1000, WINDOWSIZE=100;

ADD SAALLNK: SRN=0, SN=2, SSN=0, SAALLNKN=101, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=102, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI, MPS=MPS_NEUTRAL, CCTMR=200, POLLTMR=100, IDLETMR=500, RSPTMR=5000, KEEPTMR=100,




Issue 03 (2008-08-30)

COMTMR1=2, COMTMR2=30, COMTMR3=10, SRECTMR=60, INHTMR=1500, MAXNRP=0, MAXCC=4, MAXPD=500, STATLEN=67, N1=1000, WINDOWSIZE=100;



//Add a destination signaling point of the RNC.

ADD N7DPC: DPX=3, DPC=H'0008B5, SLSMASK=B0000, NEIGHBOR=YES, NAME="NRNC1", DPCT=IUR, STP=OFF, PROT=ITUT, BEARTYPE=MTP3B;

//Add a neighboring RNC.

ADD NRNC: NRncId=201, SHOTRIG=CS_SHO_SWTICH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWTICH-1, HHOTRIG=ON, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, Dpx=3, RncProtclVer=R6, StateIndTMR=20, SuppIurCch=NO, HhoRelocProcSwitch=DL_DCCH_SWITCH-1&IUR_TRG_SWITCH-1, TnlBearerType=ATM_TRANS, DSCRInd=FALSE, IurHsdpaSuppInd=OFF, IurHsupaSuppInd=OFF;


ADD MTP3BLKS: SIGLKSX=2, DPX=3, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-RNC1";

ADD MTP3BRT: DPX=3, SIGLKSX=2, PRIORITY=0, NAME="TO-RNC1";

ADD MTP3BLNK: SIGLKSX=2, SIGSLC=0, SRN=0, SN=4, SSN=0, SAALLNKN=100, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC1-1";





ADD ADJNODE: ANI=3, NAME="TO-RNC1", NODET=IUR, DPX=3, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS2;

//Set the mapping between the Iur adjacent node and transmission resources.



1-15


//Add the Iur user plane data.



//Add AAL2 paths.




//Add an AAL2 route.


Example: Iu-BC Data in the RNC Initial Configuration ScriptThis describes an example of Iu-BC data in the RNC initial configuration script. The Iu-BC dataconsists of the physical layer data, ATM traffic records, IPoA data, and SABP data.

//Take the script for the ATM-based Iu-BC interface as an example.



SET OPT: SRN=0, SN=26, BT=UOI_ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=64byte, J0TXVALUE="SBS 155", J0RXT=64byte, J0RXVALUE="SBS 155", J1TXT=64byte, J1TXVALUE="SBS 155", J1RXT=64byte, J1RXVALUE="SBS 155";


ADD ATMTRF: TRFX=210, ST=NRTVBR, UT=KBIT/S, PCR=15000, SCR=10000, MBS=1000, CDVT=1024, REMARK="FOR IUBC";




Issue 03 (2008-08-30)

//Add the IPoA data to the Iu-BC interface.

//Add the device IP address.


//Add an IPoA PVC.

ADD IPOAPVC: IPADDR="172.22.21.50", PEERIPADDR="172.22.21.254", CARRYT=NCOPT, CARRYNCOPTN=0, CARRYVPI=14, CARRYVCI=126, TXTRFX=210, RXTRFX=210, PEERT=IUPS;

//Add an IP route.

ADD IPRT: SRN=0, SN=26, DESTIP="172.22.5.0", MASK="255.255.255.0", NEXTHOP="172.22.21.254", PRIORITY=HIGH, REMARK="IP ROUTE TO CBC";

//Add SABP data.

ADD CBSADDR: SRN=0, SN=4, SSN=3, CnOpIndex=0,RNCIPADDR="172.22.21.50", CBCIPADDR="172.22.5.0", CBCMASK="255.255.0.0";

1.3.4 Example: Cell Data in the RNC Initial Configuration ScriptThis describes cell data in the RNC initial configuration script. The cell data includes the dataof local cells, logical cells, intra-frequency neighboring cells, inter-frequency neighboring cells,and neighboring GSM cells. This example describes only how to quickly add local cells andlogical cells.

//Set up cells quickly.

//Add the basic data of local cells.

ADD LOCELL: NODEBNAME="NodeB1", LOCELL=0;ADD LOCELL: NODEBNAME="NodeB1", LOCELL=1;ADD LOCELL: NODEBNAME="NodeB1", LOCELL=2;

//Set the priorities of different services in cells.

ADD SPG: SpgId=2, PriorityServiceForR99RT=1, PriorityServiceForR99NRT=2, PriorityServiceForHSPA=2, PriorityServiceForExtRab=3;

//Add logical cells quickly.

ADD QUICKCELLSETUP: CellId=0, CellName="CELL 0",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, UARFCNDownlink=10563, PScrambCode=0, TCell=CHIP0, LAC=100, SAC=100, CfgRacInd=REQUIRE, RAC=0, SpgId=2, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=0, SupBmc=FALSE, MaxTxPower=430, PCPICHPower=330;


ADD QUICKCELLSETUP: CellId=2, CellName="CELL 2",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613,



1-17

UARFCNDownlink=10563, PScrambCode=2, TCell=CHIP512, LAC=100, SAC=100, CfgRacInd=REQUIRE, RAC=0, SpgId=2, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=2, SupBmc=FALSE, MaxTxPower=430, PCPICHPower=330;

//Activate the logical cells.

ACT CELL: CELLID=0;ACT CELL: CELLID=1;ACT CELL: CELLID=2;

//Set the RNC to online mode. The initial configuration ends.

SET ONLINE:;

1.4 Conventions in Parameter Relationship DiagramsParameter relationship diagrams show the relationships between the parameters of MMLcommands.

Figure 1-2 shows an example of the parameter relationship diagram.

Figure 1-2 Example of the parameter relationship diagram

The elements in the preceding diagram are explained as follows:

l The parameters in a box marked in solid or dotted lines belong to the command above thebox. For example, parameter 3 belongs to command 2.

l Boxes 1 and 2 list only the parameters related to both commands.

l The command above box 2 in solid lines is executed to perform the current task, and thecommand above box 1 in dotted lines is executed to perform a related task.

l The parameters at both ends of the solid arrow are the same. This parameter is configuredthrough the command at the arrowhead and invoked through the command at the arrowtail. For example, parameter 2 is configured through command 1 and invoked throughcommand 2.

l The parameters at both ends of the dotted arrow are different. The parameter at thearrowhead must be predefined, and the parameter at the arrow tail must be consistent withit. For example, parameter 3 must be consistent with parameter 1.

l The parameter marked with *, such as parameter 3, is a conditional parameter. It isconfigured only in certain conditions.

NOTE

The parameter relationship between the commands to add, modify, and remove a configured object isobvious. This document does not describe such relationships.




Issue 03 (2008-08-30)

2 Procedure of RNC Initial Configuration

This describes the procedure of RNC initial configuration. After the initial configuration, a scriptfor loading is available.

Prerequisitel You are licensed.

l The data negotiated between the RNC and other network elements is ready. For details,refer to 3.2 Data Negotiated Between RNC and Other Network Elements.

Procedure

Step 1 Start the RNC initial configuration tool.

Step 2 Create an RNC script.

Step 3 Perform 4 Configuring RNC Global Data.

Step 4 Perform 5 Configuring RNC Equipment Data.

Step 5 Perform 6 Configuring Iub Interface Data (Initial).

Step 6 Perform 7 Configuring Iu-CS Interface Data (Initial).

Step 7 Perform 8 Configuring Iu-PS Interface Data (Initial).

Step 8 Perform 10 Configuring Iu-BC Interface Data (Initial).

Step 9 Perform 9 Configuring Iur Interface Data (Initial).

Step 10 Perform 11 Configuring Cell Data (Initial).

Step 11 Save the RNC initial configuration script.

----End

PostrequisiteThe RNC initial configuration data is loaded during the commissioning of the RNC. For details,refer to Loading RNC Software and Data Files.

RNCRNC Initial Configuration Guide 2 Procedure of RNC Initial Configuration


2-1

3 Data Preparation for RNC InitialConfiguration

About This Chapter

The data that needs to be prepared for RNC initial configuration consists of the global data,equipment data, cell data, and data negotiated between the RNC and other network elements.

3.1 Global Data and Equipment Data of the RNCThe global and equipment data configuration takes precedence over configuration of other dataduring RNC initial configuration. Therefore, the readiness of global data and equipment data isnecessary for the RNC initial configuration.

3.2 Data Negotiated Between RNC and Other Network ElementsDuring RNC initial configuration, some data is available on the negotiation between the RNCand other network elements. The negotiated data is necessary for RNC initial configuration.

3.3 Cell Data on the RNCThis describes how to plan the cell data and neighboring cell relationship data before configuringcell data script.

RNCRNC Initial Configuration Guide 3 Data Preparation for RNC Initial Configuration


3-1

3.1 Global Data and Equipment Data of the RNCThe global and equipment data configuration takes precedence over configuration of other dataduring RNC initial configuration. Therefore, the readiness of global data and equipment data isnecessary for the RNC initial configuration.

Global Data

Table 3-1 lists the global data to be prepared.

Table 3-1 Global data

Item Value

Local basic data

RNC Name

RNC ID

Whether to support network sharing

Number of operators supported

Whether to support inter-PLMNhandover

Basic information about theoperator

Operator index

Operator name

Primary operator flag

Mobile country code

Mobile network code

Basic data for Iu-Flex

Timer NNSF

NullNRI value

Bit length of the binary NRI value of theCS domain

Bit length of the binary NRI value of thePS domain

Duration of the synchronous updateprotection timer of the CS domain

Duration of the synchronous updateprotection timer of the PS domain

OSP data

Network ID

OSP code bits

OSP code

3 Data Preparation for RNC Initial ConfigurationRNC



Issue 03 (2008-08-30)

Item Value

Source ATM address

Location area dataLocation area code

Minimum and maximum PLMN valuetags

Service area data Service area code

Routing area dataRouting area code

Minimum and maximum PLMN valuetags

UTRAN registration areadata

URA ID

Equipment Data

Table 3-2 lists the equipment data to be prepared.

Table 3-2 Equipment data

Item Value

RNC timesource data

Time zone

Daylight saving time flag

Start time of the daylight saving time

End time of the daylight saving time

Time offset

RNC clockdata

Clock source level

Clock source type

Clock source working mode

If the backup of the AOUa, POUa, and UOIa is enabled, the MSP parameters must be negotiated.Table 3-3 lists the MSP data to be prepared.

Table 3-3 MSP data

Item Value

Revertive type

K2 mode



3-3

Item Value

SDSF priority

Backup mode

3.2 Data Negotiated Between RNC and Other NetworkElements

During RNC initial configuration, some data is available on the negotiation between the RNCand other network elements. The negotiated data is necessary for RNC initial configuration.

3.2.1 Data Negotiated on the Iub Interface (over ATM)When ATM transport is applied to the Iub interface, unless otherwise stated, the data of the Iubinterface is negotiated between the RNC and the NodeB.

3.2.2 Data Negotiated on the Iub Interface (over IP)When IP transport is applied to the Iub interface, unless otherwise stated, the data of the Iubinterface is negotiated between the RNC and the NodeB.

3.2.3 Data Negotiated on the Iub Interface (over ATM and IP)This describes the data negotiated on the Iub interface where the NodeB is based on the ATM/IP dual stack. Before data configuration on the Iub interface, the Transmission ResourceManagement (TRM) module of the RNC determines whether the data is transmitted on the ATMnetwork or IP network.

3.2.4 Data Negotiated on the Iu-CS Interface (over ATM)When ATM transport is applied to the Iu-CS interface, the data of the Iu-CS interface isnegotiated between the RNC and the CS domain.

3.2.5 Data Negotiated on the Iu-CS Interface (over IP)When IP transport is applied to the Iu-CS interface, the data of the Iu-CS interface is negotiatedbetween the RNC and the CS domain.

3.2.6 Data Negotiated on the Iu-PS Interface (over ATM)When ATM transport is applied to the Iu-PS interface, the data of the Iu-PS interface is negotiatedbetween the RNC and the SGSN.

3.2.7 Data Negotiated on the Iu-PS Interface (over IP)When IP transport is applied to the Iu-PS interface, the data of the Iu-PS interface is negotiatedbetween the RNC and the SGSN.

3.2.8 Data Negotiated on the Iur Interface (over ATM)When ATM transport is applied to the Iur interface, the data of the Iur interface is negotiatedbetween the local RNC and the neighboring RNC.

3.2.9 Data Negotiated on the Iur Interface (over IP)When IP transport is applied to the Iur interface, the data of the Iur interface is negotiated betweenthe local RNC and the neighboring RNC.

3.2.10 Data Negotiated on the Iu-BC InterfaceThe data of the Iu-BC interface is negotiated between the RNC and the CBC. If the CBC connectsto the RNC through the SGSN, the data of the Iu-BC interface is negotiated between the RNCand the SGSN. This topic describes the data negotiated between the RNC and the CBC.




Issue 03 (2008-08-30)

3.2.1 Data Negotiated on the Iub Interface (over ATM)When ATM transport is applied to the Iub interface, unless otherwise stated, the data of the Iubinterface is negotiated between the RNC and the NodeB.

Basic Data of the NodeBTable 3-4 lists the basic data of the NodeB.

Table 3-4 Basic data of the NodeB

Item Value

NodeB ATM address

NodeB type

NodeB protocol version

CAUTIONThe protocol version on the NodeB side must be later than or the same as that on the RNC side.

Data on the Physical LayerBefore configuring physical layer data, determine the type of the interface board, and thennegotiate and plan the associated data.

l Table 3-5 lists the physical layer data to be prepared when the AEUa serves as the interfaceboard.

l Table 3-5 and Table 3-6 list the physical layer data to be prepared when the AOUa servesas the interface board.

l Table 3-6 lists the physical layer data to be prepared when the UOI_ATM serves as theinterface board.

Table 3-5 Data on the physical layer - 1

Item Value

Working mode

Line code

Scrambling switch



3-5


Item Description Value

Scrambling switch The data must be negotiated only in thecase of non-channelized optical port.

Standard of optical port Optical ports comply with either of thefollowing standards: SDH andSONET.

(Optional) J0 TX type, J0 TX value,expected J0 RX type, and expected J0RX value

When setting the RX and TX bytes ofJ0 and J1, ensure that the attributes ofthe TX byte at the local end areconsistent with those of the RX byte atthe peer end.


(Optional) J2 TX value and expected J2RX value

The data must be negotiated only in thecase of channelized optical port.When the RNC is connected to SDHproducts of other vendors, the valuesof these parameters should benegotiated with the peer equipment.

Table 3-7 lists the data to be prepared when the upper-layer application of the physical layer isconfigured as the IMA group.

Table 3-7 Data of the IMA group

Item Value

TX frame length

IMA protocolversion

Data on the Control Plane

The Iub control plane data includes data of SAAL links and basic data of the NodeB, as listedin Table 3-8.

Table 3-8 Data on the control plane

Item Value

Bearing VPI and VCI of SAAL links

CCP No.




Issue 03 (2008-08-30)

Item Value

ATM traffic resources

Service Type

Traffic description

Peak cell rate

Sustainable cell rate

Minimum cell rate

Max burst size

Cell delay variation tolerance

NOTE

When the RNC is directly connected to the NodeB, the VPI and VCI on the RNC side and those on theNodeB side must be consistent through negotiation and configured on one physical link. If the VPIs andVCIs at the two ends are negotiated but not configured on one physical link, the link fails.

Data on the User PlaneThe Iub user plane data includes data of AAL2 paths, as listed in Table 3-9.

Table 3-9 Data on the user plane

Item Value

AAL2 path ID

Bearing VPI and VCI of AAL2 paths


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


NOTE

The type of an AAL2 path configured on both the RNC and NodeB sides must be consistent. For example,if the type of the AAL2 path is set to RT on the RNC side, the path type must also be RT on the NodeBside.



3-7

Data of the OM ChannelThe Iub OM channel data includes the data of the IPoA PVC, as listed in Table 3-10.

Table 3-10 Data of the OM channel

Item Value

(Optional) Gateway IP address on the RNC side

OM IP address and subnet mask of the NodeB

Local IP address of the IPoA PVC

Peer IP address of the IPoA PVC

Bearing VPI and VCI of the IPoA PVC

ATM trafficresources

Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


NOTE

l The gateway IP address on the RNC side is required only when layer 3 networking is applied to theIub interface.

l The local IP address of the IPoA PVC is the device IP address configured on the ATM interface boardat the RNC.

l The peer IP address of the IPoA PVC is the gateway IP address on the RNC side over the Iub interfacein layer 3 networking or the OM IP address of the NodeB over the Iub interface in layer 2 networking.

3.2.2 Data Negotiated on the Iub Interface (over IP)When IP transport is applied to the Iub interface, unless otherwise stated, the data of the Iubinterface is negotiated between the RNC and the NodeB.

Basic Data of the NodeBTable 3-11 lists the basic data of the NodeB.


Item Value

NodeB type




Issue 03 (2008-08-30)

Item Value


Data on the Physical Layer and Data Link Layer

Before configuring physical layer data, determine the type of the interface board, and thennegotiate and plan the associated data.

l Table 3-12 and Table 3-14 list the physical layer data to be prepared when the PEUa servesas the interface board.

l Table 3-12, Table 3-13, and Table 3-14 list the physical layer data to be prepared whenthe POUa serves as the interface board.

l Table 3-13 and Table 3-14 list the physical layer data to be negotiated and planned whenthe UOI_IP serves as the interface board. The UOI_IP supports only the PPP link and doesnot support the MLPPP link.

l Table 3-15 lists the physical layer data to be negotiated and planned when the FG2a servesas the interface board.

l Table 3-15 lists the physical layer data to be negotiated and planned when the GOUa servesas the interface board.


Item Value

Working mode

Line code

Scrambling switch










3-9




Table 3-14 Data on the data link layer

Item Value

PPP or MLPPP linkdata

Local IP address and subnet mask

Peer IP address

Bearing timeslot


Item Value

Device IP address of the interface board

Ethernet port data Port IP address and subnet mask

FE electrical port

Maximum transmitting unit

Whether to enable auto negotiation

Transmission rate over the FE port

Working mode

Whether to enable flow control

GE electrical port Maximum transmitting unit

GE optical port







Issue 03 (2008-08-30)

NOTE

l If auto negotiation is enabled, the transmission rate over the FE port, working mode, and whether toenable flow control depend on the negotiation results.

l If auto negotiation is disabled, the transmission rate over the FE port, working mode, and whether toenable flow control are user-defined. In addition, you must ensure that the configured parameters areconsistent with the parameters at the peer end. If they are inconsistent, transmission failure may occur.

Data on the Control PlaneTable 3-16 lists the control plane data to be negotiated.


Item Value

SCTP Link

Working mode

Local SCTP port No.

Local IP address

Peer IP address

Destination SCTP port No.

Whether to calculate checksum whentransmitting messages

Whether to calculate checksum whenreceiving messages

Checksum algorithm

VLAN ID setting flag

VLAN ID

CCP Port No.

NOTE

l Local SCTP port No. is required only when Signalling link mode is CLIENT.

l It is recommended that Checksum arithmetic be set to CRC32.

l When the SCTP link is carried on a PPP or MLPPP link, VLAN is not supported. In this case, you donot need to configure VLAN ID.

Data on the User PlaneThe Iub user plane data includes the IP path data, as listed in Table 3-17.



3-11


Item Value

IP Path

IP address and subnet mask for the interfaceon the RNC side

User plane IP address and subnet mask of theNodeB

TX bandwidth and RX bandwidth

FPMUX Flag

DSCP


VLAN ID

Data of the OM Channel

Table 3-18 lists the OM channel data to be negotiated.


Item Value

IP address for the interface at the RNC

IP address for the interface at the NodeB


(Optional) Gateway IP address on the NodeB side


(Optional) Electronic serial number of the NodeB

NOTE

l The gateway IP addresses on the RNC and NodeB sides are required only when layer 3 networking isapplied to the Iub interface.

l The electronic serial number of the NodeB is required only when the NodeB uses DHCP.

3.2.3 Data Negotiated on the Iub Interface (over ATM and IP)This describes the data negotiated on the Iub interface where the NodeB is based on the ATM/IP dual stack. Before data configuration on the Iub interface, the Transmission ResourceManagement (TRM) module of the RNC determines whether the data is transmitted on the ATMnetwork or IP network.




Issue 03 (2008-08-30)

IP Network Planning

When data transmission on the Iub interface uses the ATM/IP dual stack, the IP network planningconsists of IP networking, IP address planning, and route configuration.

For IP networking, check the following information:

l Whether to use layer 2 or layer 3 networking

l Whether to use the VLAN

l Whether to use IP over Ethernet or IP over E1/T1

Transport Type Planning

Before negotiating and planning the control plane, user plane, and management plane data,determine the mode for data transmission, as shown in Table 3-19.

Table 3-19 Iub data transmission mode planning

Data Type Description

Control plane data One or both of the two types can be used at atime.It is recommended that both ATM and IPtransport modes be used for transmissionsecurity.

User plane data One or both of the two types can be used at atime. It is recommended that:l ATM transport be applied to signaling,

voice services, CS conversational services,CS streaming services, PS conversationalservices, and PS streaming services.

l IP transport be applied to PS interactiveservices, PS background services, HSDPAconversational services, HSDPAstreaming services, HSDPA interactiveservices, HSDPA background services,HSUPA conversational services, HSUPAstreaming services, HSUPA interactiveservices, and HSUPA backgroundservices.

OM channel Only one of the two modes can be used at atime.It is recommended that IP transport be used.

Basic Data of the NodeB

Table 3-20 lists the basic data of the NodeB.



3-13


Item Value

NodeB ATM address (required only whenATM transport is applied to the control plane)

NodeB type


Data on the Physical Layer and Data Link Layer

When the ATM/IP dual stack is applied to the Iub interface, negotiate and plan both ATM andIP data on the physical layer and data link layer.

l Table 3-21 lists the physical layer data to be prepared when the AEUa serves as the interfaceboard.

l Table 3-21 and Table 3-22 list the physical layer data to be prepared when the AOUaserves as the interface board.

l Table 3-22 lists the physical layer data to be prepared when the UOI_ATM serves as theinterface board.


Item Value

Working mode

Line code

Scrambling switch











Issue 03 (2008-08-30)




Table 3-23 lists the data to be prepared when the upper-layer application of the physical layeris configured as the IMA group.


Item Value

TX frame length

IMA protocolversion

Table 3-24, Table 3-25, Table 3-26, and Table 3-27 list the data to be negotiated on the physicallayer and data link layer of the IP-based Iub interface.

l Table 3-24 and Table 3-26 list the physical layer data to be prepared when the PEUa servesas the interface board.

l Table 3-24, Table 3-25, and Table 3-26 list the physical layer data to be prepared whenthe POUa serves as the interface board.





Item Value

Working mode

Line code

Scrambling switch



3-15











Item Value



Peer IP address

Bearing timeslot


Item Value



FE electrical port




Working mode





Issue 03 (2008-08-30)

Item Value


GE optical port




NOTE



Data on the Control PlaneBased on the planning result of Table 3-19, prepare data as follows:l If ATM transport is applied to the Iub interface, negotiate and plan the control plane data

listed in Table 3-28.l If IP transport is applied to the Iub interface, negotiate and plan the control plane data listed

in Table 3-29.


Item Value

Bearing VPI and VCI of SAAL links

CCP No.


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


NOTE

When the RNC is directly connected to the NodeB, the VPI and VCI on the RNC side and those on theNodeB side must be consistent through negotiation and configured on one physical link. If the VPIs andVCIs at the two ends are negotiated but not configured on one physical link, the link fails.



3-17


Item Value

SCTP Link

Working mode

Local SCTP port No.

Local IP address

Peer IP address


Whether to calculate checksum whentransmitting messages

Whether to calculate checksum whenreceiving messages

Checksum algorithm


VLAN ID

CCP Port No.

NOTE

l Local SCTP port No. is required only when Signalling link mode is CLIENT.



Data on the User Plane

Based on the planning result of Table 3-19, prepare data as follows:

l If ATM transport is applied to the Iub interface, negotiate and plan the user plane data listedin Table 3-30.

l If IP transport is applied to the Iub interface, negotiate and plan user plane the data shownin Table 3-31.


Item Value

AAL2 path ID

Bearing VPI and VCI of AAL2 paths

ATM traffic resourcesService Type

Traffic description




Issue 03 (2008-08-30)

Item Value

Peak cell rate


Minimum cell rate

Max burst size


NOTE

The type of an AAL2 path configured on both the RNC and NodeB sides must be consistent. For example,if the type of the AAL2 path is set to RT on the RNC side, the path type must also be RT on the NodeBside.


Item Value

IP Path

IP address and subnet mask for the interfaceon the RNC side

User plane IP address and subnet mask of theNodeB


FPMUX Flag

DSCP


VLAN ID

Data of the OM Channel

Based on the planning result of Table 3-19, prepare data as follows:

l If ATM transport is applied to the Iub interface, negotiate and plan the OM channel datalisted in Table 3-32.

l If IP transport is applied to the Iub interface, negotiate and plan the OM channel data listedin Table 3-33.


Item Value




3-19

Item Value


Local IP address of the IPoA PVC

Peer IP address of the IPoA PVC

Bearing VPI and VCI of the IPoA PVC


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


NOTE

l The gateway IP address on the RNC side is required only when layer 3 networking is applied to theIub interface.

l The local IP address of the IPoA PVC is the device IP address configured on the ATM interface boardat the RNC.

l The peer IP address of the IPoA PVC is the gateway IP address on the RNC side over the Iub interfacein layer 3 networking or the OM IP address of the NodeB over the Iub interface in layer 2 networking.


Item Value

IP address for the interface at the RNC

IP address for the interface at the NodeB


(Optional) Gateway IP address on the NodeB side


(Optional) Electronic serial number of the NodeB

NOTE

l The gateway IP addresses on the RNC and NodeB sides are required only when layer 3 networking isapplied to the Iub interface.

l The electronic serial number of the NodeB is required only when the NodeB uses DHCP.




Issue 03 (2008-08-30)

3.2.4 Data Negotiated on the Iu-CS Interface (over ATM)When ATM transport is applied to the Iu-CS interface, the data of the Iu-CS interface isnegotiated between the RNC and the CS domain.

Basic Data of the CS Domain

Before configuring the Iu-CS interface data, familiarize yourself with the basic data of the CSdomain. Table 3-34 lists the basic data of the CS domain.

Table 3-34 Basic data of the CS domain

Item Value

DSP Type

DSP code

Signaling route mask

Adjacency flag

ATM address

SS7 protocol type

Q.AAL2 protocol version

CN protocol version

CR support type

Data on the Physical Layer

Table 3-35 lists the physical layer data to be prepared when the UOI_ATM serves as the interfaceboard.









3-21





Table 3-36 lists the data to be prepared when the upper-layer application of the physical layeris configured as the IMA group.


Item Value

TX frame length

IMA protocolversion

Data About TimersTable 3-37 lists the data to be prepared for SAAL and SCCP timers.

Table 3-37 Data about timers

Item RNC MSC

(Optional) SAAL(ms)

Timer CC

Timer POLL

Timer NO_RESPONSE

Timer T1

Timer T2

Timer T3

SCCP (s)Inactive TX timer

Inactive RX timer




Issue 03 (2008-08-30)

Data on the Control PlaneTable 3-38 lists the control plane data, including data on the transport network layer controlplane and that on the radio network layer control plane.

Table 3-38 Data on the Iu-CS control plane

Item Value

MTP3-bSignaling Link

Signaling link code

VPI/VCI


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


Data on the User PlaneTable 3-39 lists the data on the radio network layer user plane.

Table 3-39 Data on the Iu-CS user plane

Item Value

AAL2 PathAAL2 path ID

VPI/VCI


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size




3-23

3.2.5 Data Negotiated on the Iu-CS Interface (over IP)When IP transport is applied to the Iu-CS interface, the data of the Iu-CS interface is negotiatedbetween the RNC and the CS domain.

Basic Data of the CS Domain

Before configuring the Iu-CS interface data, familiarize yourself with the basic data of the CSdomain. Table 3-40 lists the basic data of the CS domain.

Table 3-40 Basic data of the CS domain

Item Value

DSP Type

DSP code


Adjacency flag

SS7 protocol type

CN protocol version

CR support type


Before configuring physical layer data, determine the type of the interface board, and thennegotiate and plan the associated data.











Issue 03 (2008-08-30)








Item Value



Peer IP address

Bearing timeslot


Item Value



FE electrical port




Working mode



GE optical port






3-25

NOTE




Table 3-44 lists the control plane data to be negotiated.

Table 3-44 Data on the Iu-CS control plane

Item Value

SCTP Link

Working mode

Local SCTP port No.

Local IP address and destination IP address


Whether to calculate checksum when transmitting messages

Whether to calculate checksum when receiving messages

Checksum algorithm


VLAN ID

M3UA

Traffic mode

Working mode

(Optional) Routing context of the local M3UA entity

(Optional) Routing context of the destination M3UA entity

NOTE

l Local SCTP port No. is required only when Signalling link mode of the SCTP link is CLIENT.



l It is not recommended to configure the routing context of the local M3UA entity. If the context needsto be configured, it must be consistent with the routing context of the destination M3UA entity at thepeer through negotiation.

l It is not recommended to configure the routing context of the destination M3UA entity. If the contextneeds to be configured, it must be consistent with the routing context of the local M3UA entity at thepeer through negotiation.




Issue 03 (2008-08-30)

Data on the User PlaneThe Iu-CS user plane data includes the IP path data, as listed in Table 3-45.

Table 3-45 Data on the Iu-CS user plane

Item Value

IP Path

IP address and subnet mask for the interface on theRNC side

IP address and subnet mask of the MSC server


DSCP


VLAN ID

3.2.6 Data Negotiated on the Iu-PS Interface (over ATM)When ATM transport is applied to the Iu-PS interface, the data of the Iu-PS interface is negotiatedbetween the RNC and the SGSN.

Basic Data of the PS DomainBefore configuring the Iu-PS interface data, familiarize yourself with the basic data of the PSdomain. Table 3-46 lists the basic data of the PS domain.

Table 3-46 Basic data of the PS domain

Item Value

DSP Type

DSP code


Adjacency flag

SS7 protocol type

CN protocol version

CR support type

Data on the Physical LayerTable 3-47 lists the physical layer data to be prepared when the UOI_ATM serves as the interfaceboard.



3-27












Item RNC SGSN

(Optional) SAAL(ms)

Timer CC

Timer POLL

TimerNO_RESPONSE

Timer T1

Timer T2

Timer T3


Inactive RX timer





Issue 03 (2008-08-30)

Table 3-49 Data on the Iu-PS control plane

Item Value


Signaling link code

VPI/VCI


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


Data on the User Plane

Table 3-50 lists the user plane data to be negotiated.

Table 3-50 Data on the Iu-PS user plane

Item Value

IPoA PVC

IP address and subnet mask of the RNC

IP address and subnet mask of the gateway onthe SGSN side

VPI/VCI

IP Path

User plane IP address and subnet mask of theSGSN


DSCP


VLAN ID


Service Type

Traffic description

Peak cell rate


Minimum cell rate



3-29

Item Value

Max burst size


3.2.7 Data Negotiated on the Iu-PS Interface (over IP)When IP transport is applied to the Iu-PS interface, the data of the Iu-PS interface is negotiatedbetween the RNC and the SGSN.

Basic Data of the PS DomainBefore configuring the Iu-PS interface data, familiarize yourself with the basic data of the PSdomain. Table 3-51 lists the basic data of the PS domain.

Table 3-51 Basic data of the PS domain

Item Value

DSP Type

DSP code


Adjacency flag

SS7 protocol type

CN protocol version

CR support type








Issue 03 (2008-08-30)











Item Value



Peer IP address

Bearing timeslot


Item Value



FE electrical port




Working mode




3-31

Item Value


GE optical port




NOTE




Table 3-55 Data on the Iu-PS control plane

Item Value

SCTP Link

Working mode

Local SCTP port No.





Checksum algorithm


VLAN ID

M3UA

Traffic mode

Working mode






Issue 03 (2008-08-30)

NOTE






Data on the User PlaneThe Iu-CS user plane data includes the IP path data, as listed in Table 3-56.

Table 3-56 Data on the Iu-PS user plane

Item Value

IP Path


IP address and subnet mask of the SGSN


DSCP


VLAN ID

3.2.8 Data Negotiated on the Iur Interface (over ATM)When ATM transport is applied to the Iur interface, the data of the Iur interface is negotiatedbetween the local RNC and the neighboring RNC.

Basic Data of the Neighboring RNCBefore configuring the Iur interface data, familiarize yourself with the basic data of theneighboring RNC. Table 3-57 lists the basic data of the neighboring RNC.

Table 3-57 Basic data of the neighboring RNC

Item Value

DSP Type

DSP code




3-33

Item Value

ATM address

Adjacency flag

SS7 protocol type

Protocol version of the neighboring RNC

Data on the Physical LayerTable 3-58 lists the physical layer data to be prepared when the UOI_ATM serves as the interfaceboard.












Item RNC Neighboring RNC

(Optional) SAAL(ms)

Timer CC




Issue 03 (2008-08-30)

Item RNC Neighboring RNC

Timer POLL

TimerNO_RESPONSE

Timer T1

Timer T2

Timer T3


Inactive RX timer


Table 3-60 Data on the Iur control plane

Item Value


Signaling link code

VPI/VCI


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


Q.AAL2 protocol version

Data on the User PlaneTable 3-61 lists the user plane data to be negotiated.

Table 3-61 Data on the Iur user plane

Item Value

AAL2 Path AAL2 path ID



3-35

Item Value

VPI/VCI


Service Type

Traffic description

Peak cell rate


Minimum cell rate

Max burst size


NOTE

l When the path type is RT, HSDPA_RT, or HSUPA_RT, the type of TX traffic record index and RXtraffic record index must be CBR or RTVBR.

l When the path type is NRT, HSDPA_NRT, or HSUPA_NRT, the type of TX traffic record indexand RX traffic record index must be NRTVBR, UBR, or UBR+.

3.2.9 Data Negotiated on the Iur Interface (over IP)When IP transport is applied to the Iur interface, the data of the Iur interface is negotiated betweenthe local RNC and the neighboring RNC.

Basic Data of the Neighboring RNCBefore configuring the Iur interface data, familiarize yourself with the basic data of theneighboring RNC. Table 3-62 lists the basic data of the neighboring RNC.

Table 3-62 Basic data of the neighboring RNC

Item Value

DSP Type

DSP code


Adjacency flag

SS7 protocol type

RNC protocol version




Issue 03 (2008-08-30)















Item Value



Peer IP address

Bearing timeslot



3-37


Item Value



FE electrical port




Working mode



GE optical port




NOTE




Table 3-66 lists the control plane data to be negotiated.

Table 3-66 Data on the Iur control plane

Item Value

SCTP Link

Working mode

Local SCTP port No.





Checksum algorithm





Issue 03 (2008-08-30)

Item Value

VLAN ID

M3UA

Traffic mode

Working mode



NOTE






Data on the User PlaneThe Iur user plane data includes the IP path data, as listed in Table 3-67.

Table 3-67 Data on the Iur user plane

Item Value

IP Path


IP address and subnet mask of the neighboringRNC


DSCP


VLAN ID

3.2.10 Data Negotiated on the Iu-BC InterfaceThe data of the Iu-BC interface is negotiated between the RNC and the CBC. If the CBC connectsto the RNC through the SGSN, the data of the Iu-BC interface is negotiated between the RNCand the SGSN. This topic describes the data negotiated between the RNC and the CBC.



3-39


Table 3-68 lists the physical layer data to be prepared when the UOI_ATM serves as the interfaceboard.










Data on the Iu-BC Interface

Table 3-69 lists the data to be negotiated on the Iu-BC interface.

Table 3-69 Data Negotiated on the Iu-BC Interface

Item Value

IP address and subnet mask for the interface on the RNC side

IP address and subnet mask of the CBC

IPoA PVC

Local IP address

Peer IP address

VPI/VCI

ATM traffic resourcesService Type

Traffic description




Issue 03 (2008-08-30)

Item Value

Peak cell rate


Minimum cell rate

Max burst size


3.3 Cell Data on the RNCThis describes how to plan the cell data and neighboring cell relationship data before configuringcell data script.

Data for Quick Addition of a Cell on the RNC

Table 3-70 lists the data to be prepared before you quickly set up a cell on the RNC.

Table 3-70 Data for quick addition of a cell

Item Value

Cell ID

Cell name

NodeB name

Local cell ID

Operator index

Location area code

Service area code

Routing area code

URA ID

Band indicator

UL frequency No.

DL frequency No.

DL primary scrambling code

Time offset

Maximum TX power of a cell

PCPICH TX power



3-41

Data for Addition of an Intra- or Inter-Frequency Neighboring CellTable 3-71 and Table 3-72 list the data to be prepared before you add an intra- or inter-frequencyneighboring cell.

Table 3-71 Intra-/inter-frequency neighboring cells

Item Value

Cell ID

ID of the RNC that controls the neighboringcell

Neighboring cell ID

Table 3-72 Basic data of inter-/intra-frequency neighboring cells

Item Value

Neighboring RNC ID

Cell ID

Cell name

Mobile country code

Mobile network code

Band indicator

DL primary scrambling code

DL frequency No.

Location area code

Routing area code

TX diversity indicator

Data for Addition of a Neighboring GSM CellTable 3-73 and Table 3-74 list the data to be prepared before you add a neighboring GSM cell.

Table 3-73 Neighboring GSM cells

Item Value

Cell ID




Issue 03 (2008-08-30)

Item Value

GSM Cell Index

Table 3-74 Basic data of neighboring GSM cells

Item Value

GSM Cell Index

Mobile country code

Mobile network code

Location area code

Routing area code

Network color code

BS color code

Frequency number of the inter-RAT cell

Band indicator of the inter-RAT cell

Inter-RAT cell type



3-43

4 Configuring RNC Global Data

About This Chapter

This describes how to configure RNC global data. This is an essential step in RNC initialconfiguration. Global data configuration takes precedence over configuration of equipment data,interface data, and cell data.

1. 4.2 Setting the RNC to Offline Mode (Initial)This describes how to set all subracks of the RNC to offline mode. This is the first step inthe RNC initial configuration.

2. 4.3 Adding Basic Data to the RNC (Initial)This describes how to add basic data to the RNC. The basic data includes the RNC ID,operator information, Iu-Flex information, internal subnet numbers, SCTP service listeningports, and whether to support network sharing and inter-operator handover.

3. 4.4 Adding OSP to the RNC (Initial)This describes how to add the Originating Signaling Point (OSP) data to the RNC. The dataincludes the network ID, Originating signaling Point Code (OPC), and ATM address of theRNC. As a signaling point in a mobile network, the RNC has specified signaling pointcodes.

4. 4.5 Adding RNC Global Location Data (Initial)This describes how to add global location data, including LA data (such as LAC and PLMNvalue tag range of the LA), RA data (such as RAC and PLMN value tag range of RA), CSSA data, PS SA data, and URA data.

5. 4.6 Adding a Local M3UA Entity (Initial)This describes how to add a local M3UA entity on the IP-based Iu or Iur interface.

RNCRNC Initial Configuration Guide 4 Configuring RNC Global Data


4-1

4.1 Example: Global Data in the RNC Initial ConfigurationScript

This describes global data in the RNC initial configuration script. The global data includes thebasic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, globallocation data, and data of the local M3UA entity.

//Set the RNC to offline mode.

SET OFFLINE: SRN=ALL, BULKT=OFF;

//Add basic data to the RNC.

//Add the basic data of the RNC.

ADD RNCBASIC: RncId=1, SharingSupport=NO, InterPlmnHoAllowed=NO;

//Add an operator ID.

ADD CNOPERATOR: CnOpIndex=0, CnOperatorName="Operator", PrimaryOperatorFlag=YES, MCC="460", MNC="00";

//Set the Iu-Flex information.

SET IUFLEX: CnOpIndex=0, CsIuFlexFlag=OFF, PsIuFlexFlag=OFF, NNSfTmr=3, NullNRI=0, CsInfoUpdFlag=OFF, PsInfoUpdFlag=OFF;

//Set the internal subnet numbers of the RNC, including the system subnet number and thedebugging subnet number.

SET SUBNET: SUBNET=90, DEBUGSUBNET=193;

//Plan and configure the IP-based Iu-PS interface and set the SCTP service listening port.

SET SCTPSRVPORT:NBAPSRVPN=58080, M3UASRVPN=2905;

//Add OSP to the RNC.

ADD OPC:NI=NAT, SPCBITS=BIT14, SPC=H'0008B8, RSTFUN=OFF, NSAP=H'45000006598540088F0000000000000000000000, NAME="RNC";

//Add the global location data.

ADD LAC: CnOpIndex=0, LAC=100, PlmnValTagMin=1, PlmnValTagMax=64;ADD SAC: CnOpIndex=0, LAC=100, SAC=100;ADD RAC: CnOpIndex=0, LAC=100, RAC=0, PlmnValTagMin=65, PlmnValTagMax=128;ADD URA: URAId=0, CnOpIndex=0;ADD URA: URAId=1, CnOpIndex=0;

//Plan and configure the IP-based Iu-PS interface and add the data of the local M3UA entity.

ADD M3LE: LENO=0, ENTITYT=M3UA_IPSP, RTCONTEXT=1, NAME="RNC";

4 Configuring RNC Global DataRNC



Issue 03 (2008-08-30)

4.2 Setting the RNC to Offline Mode (Initial)This describes how to set all subracks of the RNC to offline mode. This is the first step in theRNC initial configuration.

Scenario RNC initial configuration

Mandatory/Optional

Mandatory

PrerequisiteNone.

Preparation

None.

Procedure

Run the SET OFFLINE command. Set Subrack No. to All to set the configuration mode of allsubracks to the offline mode.

----End

4.3 Adding Basic Data to the RNC (Initial)This describes how to add basic data to the RNC. The basic data includes the RNC ID, operatorinformation, Iu-Flex information, internal subnet numbers, SCTP service listening ports, andwhether to support network sharing and inter-operator handover.


Mandatory/Optional

Mandatory

CAUTIONl This task takes precedence over any other initial configuration task.

l The RNC must be configured with at least one operator ID and have one primary operator,no matter whether the RNC supports network sharing or not.

Prerequisitel All the RNC subracks are switched to the offline mode.

l The basic data is not configured to the RNC.



4-3

PreparationFor the data to be negotiated and planned before you add basic data to the RNC (initial), referto 3.1 Global Data and Equipment Data of the RNC.

ProcedureStep 1 Run the ADD RNCBASIC command to set the RNC ID and whether to support network sharing.

When the network sharing is enabled, you must also set Max Cn Operator Num and InterPlmn Ho Allowed.

CAUTIONThe data added through the ADD RNCBASIC command can be modified or viewed but cannotbe deleted.

Step 2 Run the ADD CNOPERATOR command to add the information of the primary operator. SetPrimary Operator Flag to YES.

Step 3 To add the information of a secondary operator, run the ADD CNOPERATOR command. SetPrimary Operator Flag to NO.

Step 4 (Optional. Perform this step only when Iu-Flex is enabled as required.) Run the SETIUFLEX command to set the Iu-Flex data.

CAUTIONl To configure multiple CS or PS CN nodes, you must set associated Iu-Flex supporting flag

to ON (Support IU-Flex). Based on the requirements, you can turn on the CS/PS informationupdate switch and specify the CS/PS information update protection timer.

l If Iu-Flex is enabled, up to 32 CN nodes can be configured in a CS or PS domain. In addition,the protocol version at each CN node must be R5 or later.

Step 5 (Optional. Perform this step only when the internal and external subnet numbers of the RNCconflict.) Run the SET SUBNET command to set the subnet number to the specified value.

NOTE

The internal subnet numbers of the RNC consist of the system subnet number and the debugging subnetnumber. By default, the system subnet number is 80, and the debugging subnet number is 192.

Step 6 (Optional. Perform this step only when the RNC acts as an SCTP server.) Run the SETSCTPSRVPORT command to set the service listening ports on the SCTP server.

----End

4.4 Adding OSP to the RNC (Initial)This describes how to add the Originating Signaling Point (OSP) data to the RNC. The dataincludes the network ID, Originating signaling Point Code (OPC), and ATM address of the RNC.As a signaling point in a mobile network, the RNC has specified signaling point codes.




Issue 03 (2008-08-30)


Mandatory/Optional

Mandatory

NOTE

l An RNC can be configured with only one OSP.

l The network ID and the OPC must be planned in the Signaling System Number 7 (SS7) network.

Prerequisitel All the RNC subracks are switched to the offline mode.

l The basic data of the RNC is configured. For details, refer to 4.3 Adding Basic Data tothe RNC (Initial).

Preparation

For the data to be negotiated and planned before you add OSP data to the RNC (initial), refer to3.1 Global Data and Equipment Data of the RNC.

Procedure

Run the ADD OPC command to add OSP to the RNC.

----End

4.5 Adding RNC Global Location Data (Initial)This describes how to add global location data, including LA data (such as LAC and PLMNvalue tag range of the LA), RA data (such as RAC and PLMN value tag range of RA), CS SAdata, PS SA data, and URA data.


Mandatory/Optional

Mandatory

CAUTIONl The RNC supports a maximum of 2,550 LA codes, 2,550 RA codes, 5,100 CS/PS SA codes,

5,100 URA IDs, and 5,100 classified zones.

l Only the global location data that is configured by this task can be used by cells.

Figure 4-1 shows the parameter relationship in the addition of the global location data.



4-5

Figure 4-1 Parameter relationship in the addition of the global location data

PrerequisiteThe basic data of the RNC is configured. For details, refer to 4.3 Adding Basic Data to theRNC (Initial).

PreparationFor the data to be negotiated and planned before you add the RNC global location data (initial),refer to 3.1 Global Data and Equipment Data of the RNC.

ProcedureStep 1 Run the ADD LAC command to add an LA. To add more LAs, run this command repeatedly.

Step 2 Run the ADD RAC command to add an RA. To add more RAs, run this command repeatedly.

Step 3 Run the ADD SAC command to add a CS/PS SA. To add more SAs, run this commandrepeatedly.

Step 4 Run the ADD URA command to add a URA ID. To add more URA IDs, run this commandrepeatedly.

Step 5 (Optional) Run the ADD CZ command to set an SA to be a classified zone. To add moreclassified zones, run this command repeatedly.

----End




Issue 03 (2008-08-30)

4.6 Adding a Local M3UA Entity (Initial)This describes how to add a local M3UA entity on the IP-based Iu or Iur interface.


Mandatory/Optional

Optional. This task is mandatory only for the IP-based Iu or Iur interface.

CAUTIONThe OSP data must be configured before a local M3UA entity is configured.

Prerequisitel The basic data of the RNC is configured. For details, refer to 4.3 Adding Basic Data to

the RNC (Initial).l The OSP data of the RNC is configured. For details, refer to 4.4 Adding OSP to the RNC

(Initial).

PreparationFor the data to be negotiated and planned before you add a local M3UA entity, refer to 3.2 DataNegotiated Between RNC and Other Network Elements. Prepare the related data for theinterface as required.

ProcedureRun the ADD M3LE command to add a local M3UA entity.

CAUTIONAn RNC supports a maximum of two local M3UA entities. For local entities of theM3UA_ASPand M3UA_IPSP types, you need to configure the entity only once for each type.It is recommended that one local M3UA entity be configured for each type.

----End



4-7

5 Configuring RNC Equipment Data

About This Chapter

This describes how to configure RNC equipment data. The data includes RNC clock-relateddata, RNC time, basic data of the RSS subrack, and basic data of each RBS subrack.

1. 5.2 Setting RNC Equipment Description (Initial)This describes how to set basic equipment attributes of the RNC. The data includes thesystem description, system ID, contact information of the vendor, system location, andsystem services.

2. 5.3 Modifying the RSS Subrack of the RNC (Initial)This describes how to modify the attributes of the RNC Switching Subrack (RSS). Theattributes include the subrack name, slot numbers of boards, types of board, backup ofinterface boards, and type of clock board.

3. 5.4 Adding an RBS Subrack (Initial)This describes how to add the subrack information and board information. In the initialconfiguration, perform this task for all RBS subracks configured in the hardware system.

4. 5.5 Configuring RNC Clock Data (Initial)This describes the configuration of the RNC clock data. The data refers to the clock sourceof the interface board, clock source of the system, and working modes of the clocks.

5. 5.6 Setting RNC Time (Initial)This describes how to set RNC time. The related activities are the setting of the time zonethat the RNC is in, whether the daylight saving time (DST) is used, and the DSTinformation. If the RNC obtains the time information from the CN by connecting to theSimple Network Time Protocol (SNTP) server, you must also set the information of theSNTP client.

6. 5.7 Adding the IP Address of the EMS Server (Initial)This describes how to add the IP address of the Element Management System (EMS) serverthat is used to perform OM on the NodeB through the RNC.

RNCRNC Initial Configuration Guide 5 Configuring RNC Equipment Data


5-1

5.1 Example: Equipment Data in the RNC InitialConfiguration Script

The equipment data includes the data of the RSS subrack, RBS subrack, RNC time and clock,and IP address of the EMS server.

//Modify the data of the RSS subrack.

MOD SUBRACK: SRN=0, SRName="RSS";SET CLKTYPE: CLKTYPE=GCU;RMV BRD: SRN=0, SN=8;RMV BRD: SRN=0, SN=9;RMV BRD: SRN=0, SN=10;RMV BRD: SRN=0, SN=11;RMV BRD: SRN=0, SN=14;RMV BRD: SRN=0, SN=16;RMV BRD: SRN=0, SN=18;RMV BRD: SRN=0, SN=24;RMV BRD: SRN=0, SN=26;ADD BRD: SRN=0, BRDTYPE=DPU, SN=8;ADD BRD: SRN=0, BRDTYPE=DPU, SN=9;ADD BRD: SRN=0, BRDTYPE=DPU, SN=10;ADD BRD: SRN=0, BRDTYPE=DPU, SN=11;ADD BRD: SRN=0, BRDTYPE=AEU, SN=14, RED=NO;ADD BRD: SRN=0, BRDTYPE=AEU, SN=15, RED=NO;ADD BRD: SRN=0, BRDTYPE=UOI_ATM, SN=16, RED=YES;ADD BRD: SRN=0, BRDTYPE=GOU, SN=18, RED=YES;ADD BRD: SRN=0, BRDTYPE=UOI_ATM, SN=24, RED=YES;ADD BRD: SRN=0, BRDTYPE=UOI_ATM, SN=26, RED=YES;

//Add an RBS subrack.

ADD SUBRACK: SRN=1, SRName="RBS";ADD BRD: SRN=1, BRDTYPE=SPU, SN=8;ADD BRD: SRN=1, BRDTYPE=SPU, SN=10;ADD BRD: SRN=1, BRDTYPE=DPU, SN=14;ADD BRD: SRN=1, BRDTYPE=DPU, SN=16;ADD BRD: SRN=1, BRDTYPE=DPU, SN=18;ADD BRD: SRN=1, BRDTYPE=AOU, SN=20, RED=YES;ADD BRD: SRN=1, BRDTYPE=FG2, SN=22, RED=YES;ADD BRD: SRN=1, BRDTYPE=GOU, SN=24, RED=YES;ADD BRD: SRN=1, BRDTYPE=AEU, SN=26, RED=YES;

//Set the RNC time.

//Set the time zone and daylight saving time.

SET TZ: ZONET=GMT+0800, DST=NO;

//Set the RNC clock data.

//Add clock sources.

ADD CLKSRC:SRCGRD=1, SRCT=BITS1-2MHZ;



//Set the clock source switching strategy.

5 Configuring RNC Equipment DataRNC



Issue 03 (2008-08-30)

SET CLKMODE:CLKWMODE=AUTO;

//Set clock sources for boards.

SET CLK: SRT=RBS, SRN=1, SN=20, BT=AOU, REF2MCLKSRC=0, REF2MCLKSW1=ON, REF2MCLKSW2=OFF;

SET CLK: SRT=RSS, SN=16, BT=UOI_ATM, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=ON, BACK8KCLKSW2=OFF;

SET CLK: SRT=RSS, SN=24, BT=UOI_ATM, REF2MCLKSRC=0, REF2MCLKSW1=OFF, REF2MCLKSW2=OFF, BACK8KCLKSW1=OFF, BACK8KCLKSW2=ON;

//Add the IP address of the EMS server.

ADD EMSIP: EMSIP="10.218.100.4", MASK="255.255.255.0", BAMIP="10.218.100.12", BAMMASK="255.255.255.0";

5.2 Setting RNC Equipment Description (Initial)This describes how to set basic equipment attributes of the RNC. The data includes the systemdescription, system ID, contact information of the vendor, system location, and system services.


Mandatory/Optional

Optional. During the initialization of the RNC, the default RNC equipmentdescription is automatically generated in the BAM database. You can modify itas required.

NOTE

The RNC equipment description is stored only in the BAM database, instead of being sent to the host.


PreparationNone.

ProcedureRun the SET SYS command to configure the RNC system description data.

----End

5.3 Modifying the RSS Subrack of the RNC (Initial)This describes how to modify the attributes of the RNC Switching Subrack (RSS). The attributesinclude the subrack name, slot numbers of boards, types of board, backup of interface boards,and type of clock board.



5-3


Mandatory/Optional

Optional. Perform this task when you need to change any attribute of the RSSsubrack.

NOTE

l The information of the RSS subrack is automatically generated during the initialization of the RNC.You can modify the RSS data during initial configuration in accordance with the hardwareconfiguration of the RSS subrack.

l For the restrictions on slot numbers of the boards in the RSS subrack, refer to Boards in the RSSSubrack.


PreparationPrepare the data based on the actual hardware configuration of the RSS subrack.

Procedure

Step 1 Run the LST SUBRACK command and set Subrack No. to 0 to check the information of theRSS subrack, such as the subrack name, slot number of the controlling SPUa board, boarddistribution, backup of boards, and type of clock board.

Step 2 Perform the operations described in the following table according to the hardware planning.

Option Description

Change the name of the RSS subrack. Run the MOD SUBRACK command, setSubrack No. to 0, and enter the new name inthe Subrack name box.

Change the slot number of the controllingSPUa board.

Run the MOD SUBRACK command, setSubrack No. to 0, and set MPU slot No. to thenew slot number.

Change the type of clock board. Run the SET CLKTYPE command and setClock board type to the new type.

l Change the slot number and backupsituation of an interface board.

l Change the slot number of an SPUa or aDPUb board.

1. Run the RMV BRD command to remove theboard.

2. Run the ADD BRD command to add theboard. When adding an interface board, youneed to set the backup mode of the board.




Issue 03 (2008-08-30)

NOTE

l The interface board can be one of the following types of board: AEUa, AOUa, UOI_ATM, PEUa,POUa, UOI_IP, FG2a, and GOUa.

l The UOI_ATM is the UOIa board used in ATM transport. The UOI_IP is the UOIa board used in IPtransport.

Step 3 (Optional. Perform this step only when the AOUa, UOIa, or POUa boards are configured inboard backup mode.) Run the SET MSP command to set the MSP attributes. The MSP attributesrefer to Revertive type, WTR Time (required only when Revertive type is set toREVERTIVE), K2 Mode, SDSF Priority, and Backup mode. The settings of these parametersmust be consistent with those at the peer end through negotiation.

----End

5.4 Adding an RBS Subrack (Initial)This describes how to add the subrack information and board information. In the initialconfiguration, perform this task for all RBS subracks configured in the hardware system.


Mandatory/Optional

Optional. Perform this task only when the RNC requires the RBS subrack.

NOTE

l The type of the interface board positioned in the subrack must be consistent with the type of the interfaceboard that is configured.

l For the configuration specifications for slots of the RBS subrack of the RNC, refer to Boards in theRBS Subrack.


the RNC (Initial).

l The active and standby SCUa boards in the new RBS subrack are correctly connected tothe active and standby SCUa boards in the RSS subrack through Ethernet cables.

Preparation

Prepare configuration data according to the hardware configured in the RBS subrack.

Procedure

Step 1 Run the ADD SUBRACK command to set the subrack number and name, and the number ofthe slot housing the controlling SPUa board. Then, add the RBS subrack.

Step 2 Run the ADD BRD command to set the type of board in each slot of the RBS subrack andrelationship between these boards in backup.



5-5

NOTE

l Run the ADD BRD command to add the RINT boards and set the backup.

l RINT board (interface board) is of the following types: AEUa, AOUa, UOI_ATM, PEUa, POUa,UOI_IP, FG2a and GOUa.

----End

5.5 Configuring RNC Clock Data (Initial)This describes the configuration of the RNC clock data. The data refers to the clock source ofthe interface board, clock source of the system, and working modes of the clocks.


Mandatory/Optional

Optional. Perform this task only when the settings of the clock source of theinterface board, clock source of the system, working modes of the clock areinconsistent with the default settings of the database.

NOTE

l If the clock source is derived from the interface board and there are two or more interface boardsavailable for extracting timing signals, it is recommended that two interface board clock sources beconfigured. In this situation, the two interface boards cannot work in active/standby mode.

l For details about the clock synchronization subsystem of the RNC, refer to RNC Clock Sources.


PreparationDetermine the clock source in the interface board of the RSS or RBS subrack, clock source ofthe system, and working modes of the clocks through network planning.

Procedure

Step 1 Run the SET CLK command to set the clock source of the interface board in the RSS or RBSsubrack.

Step 2 Run the ADD CLKSRC command to set the clock source of the system.l You can configure Clock source priority from 1 to 4. The clock source of priority 0 is

delivered with the RNC, where extra configuration is not required.l Configure Clock source type based on the clock extracting mode:

– If the clock source is extracted in this way, that is, an interface board in the RBS subrackextracts the clock from the CN domain and sends it to the GCUa/GCGa board throughthe line clock signal cable, set Clock source type to BITS1-2MHZ or BITS2-2MHZ.

– If the clock source is extracted in this way, that is, an interface board in the RSS subrackextracts the clock from the CN domain and sends it to the GCUa/GCGa board throughthe backplane channel in the RSS subrack, set Clock source type to LINE1_8KHZ orINE2_8KHZ.




Issue 03 (2008-08-30)

– If the external BITS equipment provides the clock source, set Clock source type toBITS1-2MBPS, BITS2-2MBPS,, BITS1-T1BPS, or BITS2-T1BPS.

– If the clock source is the synchronous clock supplied by the GPS satellite and the GCGaserves as the clock board, set Clock source type to GPS.

– If the clock source is external 8 kHz clock, set Clock source type to 8KHZ.

Step 3 Run the SET CLKMODE command to set the working mode.

NOTE

The recommended System clock working mode is AUTO. In this case, when the current clock source isunavailable, the system automatically switches to the clock source of the highest priority.

----End

5.6 Setting RNC Time (Initial)This describes how to set RNC time. The related activities are the setting of the time zone thatthe RNC is in, whether the daylight saving time (DST) is used, and the DST information. If theRNC obtains the time information from the CN by connecting to the Simple Network TimeProtocol (SNTP) server, you must also set the information of the SNTP client.


Mandatory/Optional

Optional. During the initialization of the RNC, the time information of the RNCis automatically set. You can use default settings or modify them as required.


the RNC (Initial).l If the time source of the RNC is a SNTP server, the connection between the SNTP server

and the OMUa board must work properly.

PreparationNone.

Procedurel Run the SET TZ command to set the time zone of the RNC so as to adjust the system time

of the RNC to the correct local time.l (Optional. Perform this step only when the RNC obtains the time information by connecting

to the SNTP server.) Run the SET SNTPCLTPARA command to set the information ofthe SNTP client.

----End

5.7 Adding the IP Address of the EMS Server (Initial)This describes how to add the IP address of the Element Management System (EMS) server thatis used to perform OM on the NodeB through the RNC.



5-7


Mandatory/Optional

Optional. Perform this task only when the EMS server is used to perform OM onthe NodeB through the RNC.

PrerequisiteNone.

PreparationFor the data to be negotiated and planned before you add the IP address of the EMS server(initial), refer to 3.1 Global Data and Equipment Data of the RNC.

ProcedureRun the ADD EMSIP command to add the IP address of the EMS server.

NOTE

The value of the EMS IP Address parameter must be different from the value of the BAM ExternalNetwork Virtual IP parameter.

----End




Issue 03 (2008-08-30)

6 Configuring Iub Interface Data (Initial)

About This Chapter

The Iub interface is the logical interface between the RNC and the NodeB. This topic describeshow to add the transport network layer data on the Iub interface on the RNC side.

6.1 Example: Iub Data in the RNC Initial Configuration ScriptThis describes an example of Iub data in the RNC initial configuration script. The Iub dataconsists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table,control plane data, user plane data, and OM channel data.

6.2 Data Configuration Guidelines for the Iub Interface (over ATM)Related information is required for performing data configuration on the ATM-based Iubinterface. Such information refers to the protocol stack, links on the Iub interface, and OMchannel configuration guidelines.

6.3 Adding Data on the Iub Interface (Initial, over ATM)This describes how to add the transport network layer data on the ATM-based Iub interface.

6.4 Data Configuration Guidelines for the Iub Interface (over IP)Related information is required for performing data configuration on the IP-based Iub interface.Such information refers to the protocol stack, links on the Iub interface, IP address and routeconfiguration, and OM channel configuration guidelines.

6.5 Adding Data on the Iub Interface (Initial, over IP)This describes how to add the transport network layer data on the IP-based Iub interface.

6.6 Data Configuration Guidelines for the Iub Interface (over ATM and IP)Related information is required for performing data configuration on the ATM/IP dual stack–based Iub interface. Such information refers to the ATM/IP hybrid transport, ATM/IP-basednetworking, hardware configuration guidelines, data configuration guidelines, IP addresses androutes configuration, and OM channel configuration guidelines.

6.7 Adding Data on the Iub Interface (Initial, over ATM and IP)This describes how to add the transport network layer data on the ATM/IP dual stack-based Iubinterface.

RNCRNC Initial Configuration Guide 6 Configuring Iub Interface Data (Initial)


6-1

6.1 Example: Iub Data in the RNC Initial ConfigurationScript

This describes an example of Iub data in the RNC initial configuration script. The Iub dataconsists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table,control plane data, user plane data, and OM channel data.

//Take the script for the ATM-based Iub interface as an example.

//Set E1/T1 parameters. For all the links carried on the AEUa board in slot 14 of subrack 0, setworking mode to E1, set frame structure to E1 CRC4 multi-frame, set coding type to HDB3,and enable scrambling.

SET E1T1: SRN=0, SN=14, BT=AEU, LS=ALL, WORKMODE=E1_UNBA, LNKT=E1_CRC4_MULTI_FRAME, LNKCODE=HDB3, SCRAMBLESW=ON;

//Add an IMA group and add IMA links to the group. Configure an IMA group on the AEUaboard in slot 14 of subrack 0. Then, add IMA links numbered from 1 through 6 to the IMA group.

ADD IMAGRP: SRN=0, SN=14, BT=AEU, IMAGRPN=0, MINLNKNUM=1, IMAID=0, TXFRAMELEN=D128, DCB=25, IMAVER=V1.0,DLYGB=8;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=1;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=2;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=3;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=4;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=5;ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=6;


ADD ATMTRF: TRFX=110, ST=RTVBR, UT=CELL/S, PCR=217, SCR=170, MBS=1000, CDVT=1024, REMARK="FOR IUB NCP";ADD ATMTRF: TRFX=120, ST=RTVBR, UT=CELL/S, PCR=2000, SCR=548, MBS=1000, CDVT=1024, REMARK="FOR IUB CCP";ADD ATMTRF: TRFX=130, ST=RTVBR, UT=CELL/S, PCR=83, SCR=76, MBS=1000, CDVT=1024, REMARK="FOR IUB ALCAP";ADD ATMTRF: TRFX=140, ST=RTVBR, UT=CELL/S, PCR=5312, SCR=4831, MBS=1000, CDVT=1024, REMARK="FOR R99 RT";ADD ATMTRF: TRFX=150, ST=NRTVBR, UT=CELL/S, PCR=13154, SCR=10854, MBS=1000, CDVT=1024, REMARK="FOR R99 NRT";ADD ATMTRF: TRFX=160, ST=UBR, CDVT=1024, REMARK="IUB FOR IPOA";




ADD FACTORTABLE: FTI=0, REMARK="FOR IUB";

//Add the Iub control plane data.

6 Configuring Iub Interface Data (Initial)RNC



Issue 03 (2008-08-30)

//Add SAAL links. The SAAL links are numbered from 0 through 2. They are terminated atsubsystem 0 of the SPUa board in slot 2 of subrack 0.

//Add an SAAL link used to carry the NCP.


//Add an SAAL link used to carry a CCP.


//Add an SAAL link used to carry the ALCAP.


//Add a NodeB and set the algorithm parameters.

ADD NODEB: NodeBName="NODEB1", NodeBId=1, SRN=0, SN=2, SSN=0, TnlBearerType=ATM_TRANS, TRANSDELAY=10, SATELLITEIND=FALSE, NodeBType=NORMAL, Nsap="H'45000006582414723F0000000000000000000000", NodeBProtclVer=R6, SharingSupport=NON_SHARED, CnOpIndex=0;

ADD NODEBALGOPARA: NODEBNAME="NODEB1", NODEBLDCALGOSWITCH=IUB_LDR-1&NODEB_CREDIT_LDR-1&LCG_CODE_LDR-1, NODEBHSDPAMAXUSERNUM=3840, NODEBHSUPAMAXUSERNUM=3840;

ADD NODEBLDR: NodeBName="NODEB1";

//Add the port data to the Iub interface.

//Add an NCP.

ADD NCP: NODEBNAME="NODEB1", CARRYLNKT=SAAL, SAALLNKN=0;

//Add a CCP.

ADD CCP: NODEBNAME="NODEB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=1;

//Add the Iub user plane data.


ADD PORTCTRLER: SRN=0, SN=14, PT=IMA, CARRYIMAGRPN=0, CTRLSN=2, CTRLSSN=0, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0;



6-3

//Add an adjacent node over the Iub interface, that is, NODEB1. The adjacent node ID is 0 andthe interface type is Iub.

ADD ADJNODE: ANI=0, NAME="NODEB1", NODET=IUB, NODEBID=1, TRANST=ATM, IsROOTNODE=YES, SRN=0, SN=2, SSN=0, SAALLNKN=2, QAAL2VER=CS2;

//Set the mapping between the Iub adjacent node and transmission resources.


//Add AAL2 paths towards NODEB1.



ADD AAL2PATH: ANI=0, PATHID=3, PT=NRT, CARRYT=IMA, CARRYF=0, CARRYSN=14, CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=45, TXTRFX=150, RXTRFX=150, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10;

//Add an AAL2 route towards NODEB1.

ADD AAL2RT: NSAP="H'45000006582414723F0000000000000000000000", ANI=0, RTX=0, OWNERSHIP=YES;

//Add the Iub OM channel data.

//Add the device IP address to a board. The local IP address is 10.218.107.126 and the subnetmask is 255.255.255.0.


//Add an IPoA PVC. The local IP address is 10.218.107.126, the peer IP address is10.218.107.11, and the IPoA PVC is carried on IMA group 0.

ADD IPOAPVC: IPADDR="10.218.107.126", PEERIPADDR="10.218.107.11", CARRYT=IMA, CARRYIMAGRPN=0, CARRYVPI=1, CARRYVCI=46, TXTRFX=160, RXTRFX=160, PEERT=IUB;

//Add the OM IP address of the NodeB. The NodeB OM IP address is 10.218.107.11. Thegateway IP address on the RNC side, or the peer IP address of the IPoA PVC, is 10.218.107.11.

ADD NODEBIP: NODEBID=1, NBTRANTP=ATMTRANS_IP, NBATMOAMIP="10.218.107.11", NBATMOAMMASK="255.255.255.0", ATMSRN=0, ATMSN=14, ATMGATEWAYIP="10.218.107.11";




Issue 03 (2008-08-30)

6.2 Data Configuration Guidelines for the Iub Interface(over ATM)

Related information is required for performing data configuration on the ATM-based Iubinterface. Such information refers to the protocol stack, links on the Iub interface, and OMchannel configuration guidelines.

6.2.1 Protocol Structure for the Iub Interface (over ATM)When ATM transport is applied to the Iub interface, the sequence of adding Iub interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.6.2.2 Links on the Iub Interface (over ATM)The links on the ATM-based Iub interface are of three types: SAAL link of User-NetworkInterface (UNI) type, AAL2 path, and IPoA PVC.6.2.3 OM IPoA Data Configuration on the Iub Interface (over ATM)On the ATM-based Iub interface, the IPoA PVC serves as the Operation and Maintenance (OM)channel.

6.2.1 Protocol Structure for the Iub Interface (over ATM)When ATM transport is applied to the Iub interface, the sequence of adding Iub interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

Figure 6-1 shows the protocol stack for the ATM-based Iub interface.

Figure 6-1 Protocol stack for the ATM-based Iub interface



6-5

The transport network layer of the Iub interface consists of the transport network layer user plane(area A), the transport network layer control plane (area B), and the transport network layer userplane (area C).

l Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the threeareas can be carried on common physical links.

l Links in areas A and B are carried on SAAL links. Based on the type of carried information,the upper layer of area A is classified into the NCP and CCPs. Only Q.AAL2 links arecarried in area B.

l In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is theATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set upor released for the transmission of upper-layer services. Therefore, each AAL2 path musthave its corresponding controlling Q.AAL2.

6.2.2 Links on the Iub Interface (over ATM)The links on the ATM-based Iub interface are of three types: SAAL link of User-NetworkInterface (UNI) type, AAL2 path, and IPoA PVC.

Links on the Iub InterfaceFigure 6-2 shows the links on the ATM-based Iub interface.

Figure 6-2 Links on the Iub interface (over ATM)

The links on the Iub interface are of three types: SAAL link of UNI type, AAL2 path, and IPoAPVC, as shown in Figure 6-2. The SAAL links of UNI type carry the NCP, CCPs, and ALCAP.




Issue 03 (2008-08-30)

NOTE

l Figure 6-2 does not depict the links in the NodeB, because the data configuration does not involve theinternal information of the NodeB.

l The RINT shown in Figure 6-2 refers to ATM interface boards UOI_ATM, AOUa, and AEUa.

SAAL Link of UNI Type

An SAAL link of UNI type carries signaling messages on the Iub interface. The signalingmessages carried on the SAAL links are classified into NCP, CCP, and ALCAP, as describedin Table 6-1.

Table 6-1 Data carried on SAAL links of UNI type


NCP The NCP carries common process messages of NBAP over the Iub interface.An Iub interface has only one NCP.

CCP A CCP carries dedicated process messages of NBAP over the Iub interface. AnIub interface may have multiple CCPs. The number of CCPs depends onnetwork planning.

ALCAP ALCAP is also called Q.AAL2. Typically, an Iub interface has one ALCAP.

An SAAL link of UNI type is carried on a PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the RNC and the NodeB.

AAL2 path

An AAL2 path is a group of links between the RNC and the NodeB. An Iub interface has at leastone AAL2 path. It is recommended that more than one AAL2 path be planned.

An AAL2 path is carried on a PVC. The PVC identifier (VPI/VCI) and other attributes of thePVC must be negotiated between the RNC and the NodeB.

IPoA PVC

An IPoA PVC, also called management plane PVC, transmits the OM information of the NodeB.

6.2.3 OM IPoA Data Configuration on the Iub Interface (over ATM)On the ATM-based Iub interface, the IPoA PVC serves as the Operation and Maintenance (OM)channel.

IPoA PVC

Figure 6-3 shows the IPoA PVCs from the RNC to NodeBs.



6-7

Figure 6-3 IPoA PVCs from the RNC to NodeBs

NOTE

The RINT shown in Figure 6-3 refers to ATM interface boards AEUa, AOUa, and UOI_ATM.

Description on Network Segments

Each IPoA PVC travels through the following network segments before reaching the NodeB:

l 80.168.3.0 segment (with address mask of 255.0.0.0) between the OMUa board and theATM interface board. This network segment is set before delivery of the RNC.

l 12.13.1.0 segment (with address mask of 255.255.255.0) between the ATM interface boardand the NodeBs. When setting this network segment, you should take field conditions intoconsideration.

6.3 Adding Data on the Iub Interface (Initial, over ATM)This describes how to add the transport network layer data on the ATM-based Iub interface.


Mandatory/Optional

Optional. Perform this task when the RNC connects to the NodeB in ATMtransport mode.

NOTE

l This task configures only the transport network layer data on the Iub interface. To enable cells controlledby the NodeB to enter the serving state, you also need to configure cell-related parameters.

l For the recommended interface boards and configuration of the physical layer for the ATM-based Iubinterface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.

l For the guidelines of the transport network layer configuration on the Iub interface when the RANsharing function is enabled, refer to 12.12.2 Operator-Based Configuration at the Iub TransportNetwork Layer.

l When adding data on the Iub interface, take the related capabilities and specifications of the RNC intoconsideration. For details, refer to 12.5 External Specifications for the RNC.

l All the data of a NodeB, including data of cells and links, should be controlled by one SPUa subsystem.When the NodeB carries an HSDPA or HSUPA cell, configure at least one AAL2 path of HSDPA_RT/HSDPA_NRT/HSUPA_RT/HSUPA_NRT type on the Iub interface.




Issue 03 (2008-08-30)

Prerequisite

The OSP data of the RNC is configured. For details, refer to 4.4 Adding OSP to the RNC(Initial).

Preparation

For the data to be negotiated and planned before you add data on the Iub interface (initial, overATM), refer to 3.2.1 Data Negotiated on the Iub Interface (over ATM).

1. 6.3.1 Adding Physical Layer Data (Initial, over ATM)This describes how to add physical layer data on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iurinterfaces. It is a subtask of data configuration on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iurinterfaces. The types of interface boards should be determined before the relatedconfiguration.

2. 6.3.2 Adding ATM Traffic Resources (Initial)This describes how to add ATM traffic records at the RNC based on the traffic models ofSAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directlyused through their indexes during the configuration of these links.

3. 6.3.3 Adding Control Plane Data on the Iub Interface (Initial, over ATM)This describes how to add control plane data on the ATM-based Iub interface. The relatedactivities are the addition of SAAL links, basic data and algorithm parameters of the NodeB,an adjacent node, and the NCP and CCPs.

4. 6.3.4 Adding Mapping Between Adjacent Nodes and Transmission Resources (Initial)This describes how to set the mapping between adjacent nodes and transmission resourcesby configuring the TRM mapping for users of specific priorities and configuring the activityfactor table.

5. 6.3.5 Adding User Plane Data on the Iub Interface (Initial, over ATM)This describes how to add user plane data on the ATM-based Iub interface. The relatedactivities are the addition of the port controller, virtual port, and AAL2 paths.

6. 6.3.6 Adding an OM Channel on the Iub Interface (Initial, over ATM)This describes how to add an OM channel on the ATM-based Iub interface. The relatedactivities are the setting of the device IP address of an interface board, the addition of anIPoA PVC between the RNC and the NodeB, and the setting of the OM IP address of theNodeB in ATM transport mode.

6.3.1 Adding Physical Layer Data (Initial, over ATM)This describes how to add physical layer data on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iur interfaces.It is a subtask of data configuration on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iur interfaces. Thetypes of interface boards should be determined before the related configuration.

NOTE

For the recommended interface board types for different interfaces, refer to 12.6.1 Interface BoardsApplicable to Terrestrial Interfaces.

6.3.1.1 Adding Physical Layer Data on the Interface (Initial, with AEUa)This describes how to add physical layer data on an interface when the AEUa serves as theinterface board. The associated type of application on the E1/T1 link can be IMA link, UNI link,fractional IMA link, fractional ATM link, or timeslot cross connection.

6.3.1.2 Adding Physical Layer Data on the Interface (Initial, with AOUa)



6-9

This describes how to add physical layer data on an interface when the AOUa board serves asthe interface board. The associated type of application on E1/T1 links may be of the followingtypes: IMA link and UNI link.

6.3.1.3 Adding Physical Layer Data on the Interface (Initial, with UOI_ATM)This describes how to add physical layer data on an interface when the UOI_ATM serves as theinterface board.

Adding Physical Layer Data on the Interface (Initial, with AEUa)

This describes how to add physical layer data on an interface when the AEUa serves as theinterface board. The associated type of application on the E1/T1 link can be IMA link, UNI link,fractional IMA link, fractional ATM link, or timeslot cross connection.


Mandatory/Optional

Optional. Perform this task only when the AEUa serves as the interface board.

CAUTIONl To configure the upper-layer application for the ATM physical port, adhere to the principles

listed in 12.6.6 Configuration Specifications for ATM-Based Ports.

l For the configuration restrictions on each type of upper-layer link carried on the AEUa board,refer to 12.6.4 Ports on the AEUa/AOUa.

Prerequisite

The basic data of the RNC is configured. For details, refer to 4.3 Adding Basic Data to theRNC (Initial).

Preparation

For the data to be negotiated and planned before you add the physical layer data on the interface(initial, with AEUa), refer to 3.2 Data Negotiated Between RNC and Other NetworkElements. Prepare the related data for the interface as required.

Procedure

Step 1 (Optional. Perform this step only when the planned data is inconsistent with the default data ofthe database.) Run the SET E1T1 command to set the parameters of one or all E1/T1 links.

NOTE

In T1 mode, use the SET E1T1 command to set the link to the required T1 type and keep other settingsthe same as those in E1 mode.

Step 2 Determine the E1/T1 application type and perform the corresponding configuration. Note thatthe E1/T1 application type can be only one of IMA, UNI, fractional IMA, fractional ATM, andtimeslot cross connection.




Issue 03 (2008-08-30)

If the E1/T1 link carries... Then...

IMA link Go to Step 3.

UNI link Go to Step 4.

Fractional IMA link Go to Step 5.

Fractional ATM link Go to Step 6.

Timeslot cross connection Go to Step 7.

Step 3 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, performthis step repeatedly.1. Run the ADD IMAGRP command to add an IMA group.2. Run the ADD IMALNK command to add an IMA link to the IMA group. To add more

IMA links, run this command repeatedly. This task is complete.

Step 4 Run the ADD UNILNK command to add a UNI link. Run this command repeatedly if multipleUNI links are required. This task is complete.

Step 5 Add fractional IMA links by performing the following steps:1. Run the ADD IMAGRP command to add a fractional IMA group.2. Run the ADD FRALNK command to add a fractional IMA link to the fractional IMA

group. Set Fractional link type to FRAIMA. To add more fractional IMA links, run thiscommand repeatedly. This task is complete.

Step 6 Run the ADD FRALNK command to add a fractional ATM link. Set Fractional link type toFRAATM. To add more fractional ATM links, run this command repeatedly. This task iscomplete.

Step 7 If the source and destination timeslots are not used, run the ADD TSCROSS command to adda timeslot cross connection. This task is complete.

----End

Adding Physical Layer Data on the Interface (Initial, with AOUa)This describes how to add physical layer data on an interface when the AOUa board serves asthe interface board. The associated type of application on E1/T1 links may be of the followingtypes: IMA link and UNI link.


Mandatory/Optional

Optional. Perform this task only when the AOUa serves as the interface board.



6-11

CAUTIONFor the configuration restrictions on each type of upper-layer link carried on the AOUa board,refer to 12.6.4 Ports on the AEUa/AOUa.

Prerequisite


Preparation

For the data to be negotiated and planned before you add the physical layer data on the interface(initial, with AOUa), refer to 3.2 Data Negotiated Between RNC and Other NetworkElements. Prepare the related data for the interface as required.

Procedure

Step 1 (Optional. Perform this step only when the planned data is inconsistent with the default data inthe database.) Run the SET E1T1 command to set the parameters of one or more E1/T1 links.

Step 2 (Optional. Perform this step only when the planned data is inconsistent with the default data inthe database.) Run the SET OPT command to set the parameters of the optical ports on theAOUa board.

Step 3 (Optional. Perform this step only when the RNC needs to interwork with equipment from anothervendor.) Run the SET COPTLNK command to set the parameters of a channelized optical porton the AOUa board.

Step 4 Determine the E1/T1 application type and perform the corresponding configuration. Note thatthe E1/T1 application type can be either IMA or UNI, not both.

If the E1/T1 link carries... Then...

IMA link Go to Step 5.

UNI link Go to Step 6.

Step 5 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, performthis step repeatedly.

1. Run the ADD IMAGRP command to add an IMA group.

2. Run the ADD IMALNK command to add an IMA link to the IMA group. To add moreIMA links, run this command repeatedly. This task is complete.

Step 6 Run the ADD UNILNK command to add a UNI link. To add more UNI links, run this commandrepeatedly. This task is complete.

----End




Issue 03 (2008-08-30)

Adding Physical Layer Data on the Interface (Initial, with UOI_ATM)

This describes how to add physical layer data on an interface when the UOI_ATM serves as theinterface board.


Mandatory/Optional

Optional. Perform this task only when the UOI_ATM serves as the interface board.


Preparation

For the data to be negotiated and planned before you add the physical layer data on the interface(initial, with UOI_ATM), refer to 3.2 Data Negotiated Between RNC and Other NetworkElements. Prepare the related data for the interface as required.

Procedure

(Optional. Perform this step only when the planned data is inconsistent with the default data inthe database.) Run the SET OPT command to set the parameters of the optical ports on theUOI_ATM board.

----End

6.3.2 Adding ATM Traffic Resources (Initial)This describes how to add ATM traffic records at the RNC based on the traffic models of SAALlinks, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used throughtheir indexes during the configuration of these links.


Mandatory/Optional

Mandatory

NOTE

l When adding the RNC ATM traffic resources, observe 12.5.1 Specifications for Traffic on RNCBoards.

l For types of service, traffic parameters, and configuration guidelines of ATM traffic resources, referto 12.8 PVC Parameters of the RNC.

Prerequisite




6-13

PreparationFor the data to be negotiated and planned before you add ATM traffic resources, refer to 3.2Data Negotiated Between RNC and Other Network Elements. Prepare the related data forthe interface as required.

ProcedureRun the ADD ATMTRF command to add an ATM traffic record. To add more ATM trafficrecords, run this command repeatedly.

----End

6.3.3 Adding Control Plane Data on the Iub Interface (Initial, overATM)

This describes how to add control plane data on the ATM-based Iub interface. The relatedactivities are the addition of SAAL links, basic data and algorithm parameters of the NodeB, anadjacent node, and the NCP and CCPs.


Mandatory/Optional

Mandatory

CAUTIONl The Iub interface should be configured with at least three SAAL UNI links: one for the NCP,

one for a CCP, and one for ALCAP (that is, Q.AAL2 link).l The SAAL UNI links used to carry the NCP, CCP, and ALCAP links on the same Iub interface

can be controlled only by the same SPUa subsystem.l Between an RNC and a NodeB, only one NCP can be configured, but multiple CCPs are

allowed.

Figure 6-4 shows the parameter relationship in the addition of the SAAL link.




Issue 03 (2008-08-30)

Figure 6-4 Parameter relationship in the addition of the SAAL link

Figure 6-5 shows the parameter relationship in the addition of the adjacent node.

Figure 6-5 Parameter relationship in the addition of the adjacent node

Prerequisitel The physical layer data on the external interface of the RNC is configured. For details, refer

to 6.3.1 Adding Physical Layer Data (Initial, over ATM).l Traffic resources at the ATM layer are configured. For details, refer to 6.3.2 Adding ATM

Traffic Resources (Initial).

PreparationFor the data to be negotiated and planned before you configure the Iub control plane on the RNC(initial, over ATM), refer to 3.2.1 Data Negotiated on the Iub Interface (over ATM).



6-15

Procedure

Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to UNI. To addmore SAAL links, run this command repeatedly.

Step 2 Run the ADD NODEB command to add the basic data of a NodeB. The details are as follows:

l Set IUB trans bearer type to ATM_TRANS(ATM circuit transmission).

l When satellite-based networking is applied to the Iub interface, set Satellite Trans Ind toTRUE and IUB Trans Apart Delay[ms] to the recommended 500. The value of IUB TransDelay varies with the satellite transmission techniques. You may adjust the value of IUBTrans Delay based on the actual conditions.

Step 3 Run the ADD NODEBALGOPARA command to add algorithm parameters for the NodeB.

Step 4 Run the ADD NODEBLDR command to add load reshuffling algorithm parameters for theNodeB.

Step 5 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriateTRM mapping and activity factor tables for users of different priorities. The details are asfollows:

l Set Adjacent Node Type to IUB.

l Set Transport Type to ATM.

Step 6 Run the ADD NCP command to add an NCP. Set Bearing link type to SAAL.

Step 7 Run the ADD CCP command to add a CCP. Set Bearing link type to SAAL. To add moreCCPs, run this command repeatedly.

----End

6.3.4 Adding Mapping Between Adjacent Nodes and TransmissionResources (Initial)

This describes how to set the mapping between adjacent nodes and transmission resources byconfiguring the TRM mapping for users of specific priorities and configuring the activity factortable.


Mandatory/Optional

Mandatory

NOTE

l For the guidelines for configuring the TRM mapping between service types and transmission resources,refer to 12.13 TRM Configuration Guidelines.

l For the guidelines for configuring the activity factor table, refer to 12.14 Activity FactorConfiguration Guidelines.

Prerequisite





Issue 03 (2008-08-30)

PreparationTable 6-2 describes the data to be negotiated and planned before you configure the TRMmapping.

Table 6-2 TRM mapping data to be negotiated and planned

Item Description Source

Mapping betweenservice types andtransmissionresources

Based on the requirements, configure the preferred pathand candidate path for each type of service on Iub, Iu,and Iur interfaces.

Dataplanning inthe RNC

Table 6-3 describes the data to be negotiated and planned before you add the activity factortable.

Table 6-3 Activity factor to be negotiated and planned


Activity factors forservices

Activity factor used by each type of service Dataplanning inthe RNC

Procedure

Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mappingtables, run this command repeatedly.

Step 2 Run the ADD FACTORTABLE command to add an activity factor table.

Step 3 Run the ADD ADJMAP command to configure the TRM mapping tables for users of specificpriorities and the activity factor table.

----End

6.3.5 Adding User Plane Data on the Iub Interface (Initial, overATM)

This describes how to add user plane data on the ATM-based Iub interface. The related activitiesare the addition of the port controller, virtual port, and AAL2 paths.


Mandatory/Optional

Mandatory

NOTE

When adding the Iub user plane data to the RNC, take the constraints on the RNC processing capabilityinto consideration. For details, refer to 12.5.7 RNC Capability for AAL2 Paths and AAL2 Routes.



6-17

Figure 6-6 shows the parameter relationship in the addition of the port controller on the ATM-based Iub interface.

Figure 6-6 Parameter relationship in the addition of the port controller on the ATM-basedinterface

Figure 6-7 shows the parameter relationship in the addition of the AAL2 path.




Issue 03 (2008-08-30)

Figure 6-7 Parameter relationship in the addition of the AAL2 path in the ATM-based interface

PrerequisiteThe control plane data of the ATM-based Iub interface is configured. For details, refer to 6.3.3Adding Control Plane Data on the Iub Interface (Initial, over ATM).

PreparationFor the data to be negotiated and planned before you configure the Iub user plane on the RNC(initial, over ATM), refer to 3.2.1 Data Negotiated on the Iub Interface (over ATM).

Procedure

Step 1 Run the ADD PORTCTRLER command to specify a TRM controlling subsystem on an SPUaboard for a specific port.

Step 2 (Optional. Perform this step when the ATM traffic shaping and congestion control functions areenabled.) Run the ADD VP command to add an ATM virtual port.

NOTE

If the RAN sharing function is enabled and the user plane resources are separated by operators, set ResourceManagement Mode to EXCLUSIVE and set Cn Operator Index.

Step 3 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, run thiscommand repeatedly.



6-19

NOTE

If the ATM traffic shaping and congestion control functions or the user plane resource separation byoperators in RAM sharing is already enabled by running the ADD VP command, set The bearing type ofthe virtual port to VP, which indicates that the AAL2 path is used to carry the user plan resources of thespecified operator.

----End

6.3.6 Adding an OM Channel on the Iub Interface (Initial, overATM)

This describes how to add an OM channel on the ATM-based Iub interface. The related activitiesare the setting of the device IP address of an interface board, the addition of an IPoA PVCbetween the RNC and the NodeB, and the setting of the OM IP address of the NodeB in ATMtransport mode.


Mandatory/Optional

Mandatory

Figure 6-8 shows the parameter relationship in the addition of the IPoA PVC.

Figure 6-8 Parameter relationship in the addition of the IPoA PVC




Issue 03 (2008-08-30)

Figure 6-9 shows how to add parameter relationship in the addition of the OM IP address of theNodeB in ATM transport mode.

Figure 6-9 Parameter relationship in the addition of the OM IP address of the NodeB in ATMtransport mode

Prerequisitel The Iub control plane data is configured. For details, refer to 6.3.3 Adding Control Plane

Data on the Iub Interface (Initial, over ATM).

l The Iub user plane data is configured. For details, refer to 6.3.5 Adding User Plane Dataon the Iub Interface (Initial, over ATM).

Preparation

For the data to be negotiated and planned before you add the OM channel on the Iub interface(initial, over ATM), refer to 3.2.1 Data Negotiated on the Iub Interface (over ATM).

Procedure

Step 1 Run the ADD DEVIP command to add the device IP address of an interface board.

Step 2 Run the ADD IPOAPVC command to add an IPoA PVC between the RNC and the NodeB. SetPeer type to IUB.

Step 3 Run the ADD NODEBIP command to add the IP address of the NodeB. The details are asfollows:

l Set NodeB TransType to ATMTRANS_IP.

l Set NodeB ATM_TRANS IP address and NodeB ATM_TRANS IP Mask to the OM IPaddress and mask of the NodeB in ATM transport mode.

l Set NodeB ATM_TRANS Next hop IP address to peer IP address of the IPoA PVC.

----End



6-21

6.4 Data Configuration Guidelines for the Iub Interface(over IP)

Related information is required for performing data configuration on the IP-based Iub interface.Such information refers to the protocol stack, links on the Iub interface, IP address and routeconfiguration, and OM channel configuration guidelines.

6.4.1 Protocol Stack on the Iub Interface (over IP)If IP transport is applied to the Iub interface, the sequence of adding Iub interface data shouldbe consistent with the protocol structure, that is, from the lowest layer to the highest layer andfrom the control plane to the user plane.

6.4.2 Links on the Iub Interface (over IP)This describes the links on the IP-based Iub interface.

6.4.3 IP Addresses and Routes on the Iub Interface (over IP)On the IP-based or ATM/IP dual stack–based Iub interface, IP addresses and routes are required.

6.4.4 OM Channel Configuration on the Iub Interface (over IP)Two ways are available for configuring routes for the OM channel on the Iub interface. Theyare routing between the M2000 and the NodeB through the RNC and routing between the M2000and the NodeB not through the RNC.

6.4.1 Protocol Stack on the Iub Interface (over IP)If IP transport is applied to the Iub interface, the sequence of adding Iub interface data shouldbe consistent with the protocol structure, that is, from the lowest layer to the highest layer andfrom the control plane to the user plane.

Figure 6-10 shows the protocol stack for IP transport on the Iub interface.




Issue 03 (2008-08-30)

Figure 6-10 Protocol stack for IP transport on the Iub interface

6.4.2 Links on the Iub Interface (over IP)This describes the links on the IP-based Iub interface.

Links on the Iub InterfaceFigure 6-11 shows the links on the Iub interface.



6-23

Figure 6-11 Links on the Iub interface (over IP)

The links on the Iub interface are of two types: SCTP link and IP path, as shown in Figure6-11. The SCTP links carry the NCP and CCPs.

NOTE

l The preceding figure does not depict the links in the NodeB, because the data configuration does notinvolve the internal information of the NodeB.

l The RINT shown in the preceding figure refers to IP interface boards PEUa, POUa, UOI_IP, FG2a,and GOUa.

SCTP Link

An SCTP link carries signaling messages on the Iub interface. The signaling messages carriedon the SCTP links are classified into NCP and CCP, as described in Table 6-4.

Table 6-4 Data carried on SCTP links


NCP The NCP carries common process messages of NBAP over the Iub interface.An Iub interface has only one NCP.

CCP A CCP carries dedicated process messages of NBAP over the Iub interface. AnIub interface may have multiple CCPs. The number of CCPs depends onnetwork planning.

The SCTP link can work in two modes, SERVER and CLIENT, on the RNC and the NodeBsides. On the RNC side, the differences between the two working modes are as follows:




Issue 03 (2008-08-30)

l SERVER: The local end enables only the listening port and the peer end sends theinitialization request.In SERVER mode, all SCTP links use the listening port as a local port. The listening portalso becomes the local port of NCP or CCP on the control plane. On the NodeB side, a portnumber is added to each new NCP and CCP.

l CLIENT: The local end sends the initialization request during the setup of the link.In CLIENT mode, each SCTP link must be configured with a local port, which means thata local port number is added to each NCP and CCP. On the NodeB side, only one portnumber needs to be configured.

It is recommended that the working mode of the RNC be set to SERVER when you configurean SCTP link.

IP Path

An IP path is a group of connections between the RNC and the NodeB. An Iub interface has atleast one AAL2 path. It is recommended that more than one AAL2 path be planned.


Networking on the Iub Interface

There are two types of networking on the Iub interface, namely, layer 2 networking and layer 3networking. Compared with layer 3 networking, layer 2 networking is simpler. That is becausethe port IP addresses of the RNC and NodeB are located on the same network segment and noroute is required.

Figure 6-12 shows an example of layer 2 networking on the Iub interface.

Figure 6-12 Layer 2 networking on the Iub interface



6-25

NOTE

IP 1 and IP 2 are port IP addresses.



NOTE

IP 1 and IP 2 are device IP addresses on the IP interface board. IP 3 and IP 4 are port IP addresses on theIP interface board. IP 5 and IP 6 are gateway IP addresses on the RNC side. IP 7 is the gateway IP addresson the NodeB side. IP 8 is the IP address of the NodeB.

IP Addresses on the Iub Interface

As shown in Figure 6-12 and Figure 6-13, the Iub IP addresses at the RNC consist of IPaddresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP groups,and device IP addresses. Table 6-5 describes these IP addresses.

Table 6-5 IP addresses on the Iub interface

IP Address Configuration Scenario Configuration Restriction

IP address of anEthernet port

Required when the FG2a orGOUa serves as theinterface board

l Each Ethernet port can be configuredwith only one primary IP address and 5secondary addresses.

l The IP address of an Ethernet port and theinternal IP address of the BAM must belocated on different network segments.For these network segments, one cannotcover another.

l In the RNC, the IP addresses of differentEthernet ports must be located ondifferent network segments. For thesenetwork segments, one cannot coveranother.




Issue 03 (2008-08-30)


Local IPaddress of aPPP link

Required when the PEUa,POUa, or UOI_IP serves asthe interface board

Each PPP link can be configured with onlyone local IP address.

Local IPaddress of anMLPPP group

Required when the PEUa orPOUa serves as the interfaceboard

Each MLPPP group can be configured withonly one local IP address.

Device IPaddress

Required in layer 3networking

l Each interface board can be configuredwith a maximum of five device IPaddresses.

l The IP addresses of any two differentdevices must be located on differentsubnets.

Route on the Iub InterfaceOn the Iub interface where layer 2 networking is applied, no route is required. On the Iub interfacewhere layer 3 networking is applied, you should configure the route described in Table 6-6 onthe RNC.

Table 6-6 Route on the Iub Interface

Device Route Description

IP interfaceboard

The route travels from the RNC to the network segment where the NodeB islocated.You can use the ADD IPRT command on the RNC to configure the route.Destination IP address is the address of the network segment where theNodeB is located, and Next Hop Address is the gateway IP address on theRNC side, for example, IP 5 or IP 6.


Routing Between the M2000 and the NodeB Through the RNCFigure 6-14 shows an example of routing between the M2000 and the NodeB through the RNC.Table 6-7 describes the routes.



6-27

Figure 6-14 Example of routing between the M2000 and the NodeB through the RNC

NOTE

l Figure 6-14 takes layer 2 networking on the Iub interface for an example. When layer 3 networkingis applied to the Iub interface, the IP interface board and the NodeB communicate through a router.

l The RINT shown in Figure 6-14 refers to IP interface boards PEUa, POUa, UOI_IP, FG2a, and GOUa.

Table 6-7 Routes for the connection between the M2000 and the NodeB through the RNC

Equipment Forward Route Reverse Route

M2000 From the M2000 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the external virtual IPaddress of the BAM, that is,172.121.139.200

-

RNC From the OMUa board to the NodeBOM network segment 19.19.19.X, withthe next hop to be the internal IPaddress of the IP interface board at theRNC, that is, 80.168.3.66

From the IP interface board of theRNC to the M2000 IP networksegment 172.121.139.XYou can run the ADD EMSIPcommand on the RNC toconfigure the route. When you runthis command, set EMS IPAddress to the IP address of theM2000, set Subnet mask to thesubnet mask of the M2000, andspecify the values of BAMExternal Network Virtual IPand BAM External NetworkMask. In this example, EMS IPAddress is 172.121.139.56, andBAM External Network VirtualIP is 172.121.139.200.




Issue 03 (2008-08-30)


From the IP interface board of the RNCto the NodeB OM network segment19.19.19.Xl If layer 2 networking is applied to

the Iub interface, the next hop is theIP address of the interface board atthe NodeB, that is, 16.16.16.2.

l If layer 3 networking is applied tothe Iub interface, the next hop is thegateway IP address on the RNC side.

You can run the ADD NODEBIPcommand on the RNC to configure theroute. IP address is the OM IP addressof the NodeB.l If layer 2 networking is applied to

the Iub interface, Gateway IPaddress is the IP address of theinterface board at the NodeB.

l If layer 3 networking is applied tothe Iub interface, Gateway IPaddress is the gateway IP address onthe RNC side.

NodeB - From the NodeB to the M2000 IPnetwork segment 172.121.139.Xl If layer 2 networking is applied

to the Iub interface, the nexthop is the IP address of the IPinterface board at the RNC, thatis, 16.16.16.1.

l If layer 3 networking is appliedto the Iub interface, the nexthop is the gateway IP addresson the NodeB side.

Routing Between the M2000 and the NodeB Not Through the RNCIf the OM subnet where the M2000 is located is connected to the IP network that covers theNodeB, routes can be configured between the M2000 and the NodeB not through the RNC.Figure 6-15 shows an example of routing between the M2000 and the NodeB not through theRNC. Table 6-8 describes the routes.



6-29

Figure 6-15 Example of routing between the M2000 and the NodeB not through the RNC

Table 6-8 Routes for the connection between the M2000 and the NodeB not through the RNC


M2000 From the M2000 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the port IP address ofrouter 1, that is, 10.161.215.200

-

Router 1 From router 1 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the port IP address ofrouter 2, that is, 172.16.16.10

-

Router 2 From router 2 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the IP address of the IPinterface board at the NodeB, that is,16.16.16.2

From router 2 to the M2000network segment10.161.215.100, with the next hopto be the port IP address of router1, that is, 172.16.16.9

NodeB - From the NodeB to the M2000network segment10.161.215.100, with the next hopto be the port IP address of router2, that is, 16.16.16.20

6.5 Adding Data on the Iub Interface (Initial, over IP)This describes how to add the transport network layer data on the IP-based Iub interface.


Mandatory/Optional

Optional. Perform this task when the RNC connects to the NodeB in IP transportmode.




Issue 03 (2008-08-30)

NOTE


l For the recommended interface boards and configuration of the physical layer for the ATM-based Iubinterface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.

l For the guidelines of the transport network layer configuration on the Iub interface when the RANsharing function is enabled, refer to 12.12.2 Operator-Based Configuration at the Iub TransportNetwork Layer.

l When adding data on the Iub interface, take the related capabilities of and specifications for the RNCinto consideration. For details, refer to 12.5 External Specifications for the RNC.

l All the data of a NodeB, including data of cells and links, should be controlled by one SPUa subsystem.When the NodeB carries the HSDPA/HSUPA cell, at least one IP path of the type HQ_HSDPART/HQ_HSDPANRT/HQ_HSUPART/HQ_HSUPANRT should be configured on the Iub interface.


PreparationFor the data to be negotiated and planned before you add data on the Iub interface (initial, overIP), refer to 3.2.2 Data Negotiated on the Iub Interface (over IP).

1. 6.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)The addition of physical layer and data link layer data is necessary for the data configurationof the IP-based Iub, Iu-CS, Iu-PS, and Iur interfaces. Before the interface data configuration,you need to determine the type of the interface board. Then, configure the data of thecorresponding physical layer and data link layer data according to the interface board type.

2. 6.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP)This describes how to add control plane data on the IP-based Iub interface. The relatedactivities are the addition of SCTP signaling links, basic data and algorithm parameters ofthe NodeB, an adjacent node, and the NCP and CCPs.


4. 6.5.4 Adding User Plane Data on the Iub Interface (Initial, over IP)This describes how to add user plane data on the IP-based Iub interface. The relatedactivities are the addition of the port controller, IP path, IP route, and transmission resourcegroup.

5. 6.5.5 Adding an OM Channel on the Iub Interface (Initial, over IP)This describes how to add an OM channel on the IP-based Iub interface. The relatedactivities are the setting of the OM IP address of the NodeB and the addition of the electronicserial number of the NodeB that uses DHCP.

6.5.1 Adding Physical Layer and Data Link Layer Data (Initial, overIP)

The addition of physical layer and data link layer data is necessary for the data configuration ofthe IP-based Iub, Iu-CS, Iu-PS, and Iur interfaces. Before the interface data configuration, you



6-31

need to determine the type of the interface board. Then, configure the data of the correspondingphysical layer and data link layer data according to the interface board type.

NOTE

For the recommended interface board types of different interfaces, refer to 12.6.1 Interface BoardsApplicable to Terrestrial Interfaces.

6.5.1.1 Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, withFG2a/GOUa)This describes how to add physical layer and data link layer data on interfaces of the RNC whenthe FG2a or GOUa serves as the IP interface board. The related activities are the setting theproperties of the Ethernet port, adding the primary and secondary IP addresses for the Ethernetport, and setting the device IP addresses in the layer-3 networking.

6.5.1.2 Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, withPEUa)This describes how to add physical layer and data link layer data on interfaces of the RNC whenthe PEUa serves as the IP interface board. At least one of the PPP link data and MLPPP linkdata must be configured.

6.5.1.3 Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, withPOUa)This describes how to add the physical layer and data link layer data on the interfaces of theRNC when the POUa serves as the IP interface board. The related activities are the setting ofE1/T1 attributes, optical port attributes, and channel attributes of the channelized optical port,and the addition of PPP links or MLPPP groups.

6.5.1.4 Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, withUOI_IP)This describes how to add the physical layer and data link layer data on the interfaces of theRNC when the UOI_IP board serves as the IP interface board. The related activities are theconfiguration of optical port attributes and the addition of PPP links.

Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial,with FG2a/GOUa)

This describes how to add physical layer and data link layer data on interfaces of the RNC whenthe FG2a or GOUa serves as the IP interface board. The related activities are the setting theproperties of the Ethernet port, adding the primary and secondary IP addresses for the Ethernetport, and setting the device IP addresses in the layer-3 networking.


Mandatory/Optional

Optional. Perform this task only when the FG2a/GOUa serves as the interfaceboard.


PreparationFor the data to be negotiated and planned before you add the physical layer and data link layerdata on the external interface (initial, with FG2a/GOUa) of the RNC, refer to 3.2 Data




Issue 03 (2008-08-30)

Negotiated Between RNC and Other Network Elements. Prepare the related data for theinterface as required.

Procedure

Step 1 Run the SET ETHPORT command to set the properties of the Ethernet port.

Step 2 Run the ADD ETHIP command to add the IP address of the Ethernet port. In the command, setIP address type to PRIMARY.

NOTE

Each Ethernet port can be configured with only one primary IP address.

Step 3 (Optional. Perform this step only when gateways of multiple VLANs are planned.) Run theADD ETHIP command to set a secondary IP address of the Ethernet port. In this step, set IPaddress type to SECOND.

NOTE

An Ethernet port can be configured with a maximum of 5 secondary IP addresses.

Step 4 (Optional. Perform this step only when using layer 3 networking.) Run the ADD DEVIPcommand to add the device IP address of a board.

----End

Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial,with PEUa)

This describes how to add physical layer and data link layer data on interfaces of the RNC whenthe PEUa serves as the IP interface board. At least one of the PPP link data and MLPPP linkdata must be configured.


Mandatory/Optional

Optional. Perform this task only when the PEUa serves as the interface board.

Prerequisite


Preparation

For the data to be negotiated and planned before you add the physical layer and data link layerdata on the external interface (initial, with PEUa) of the RNC, refer to 3.2 Data NegotiatedBetween RNC and Other Network Elements. Prepare the related data for the interface asrequired.

Procedure

Step 1 (Optional. Perform this step only when the planned data is inconsistent with the default data inthe database.) Run the SET E1T1 command to set the parameters of E1/T1 links.



6-33

NOTE

In T1 mode, use the SET E1T1 command to set the link to the required T1 type and keep other settingsthe same as those in E1 mode.

Step 2 Determine the type of the upper-layer application in E1/T1 (PPP link or MLPPP groups) andthen perform the associated step as described in the following table.

If... Then...

PPP links need to be configured Go to Step 3.

MLPPP groups need to be configured Go to Step 4.

Step 3 Add the PPP link data.

1. Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run thiscommand repeatedly.

Step 4 Add the MLPPP group data.

1. Run the ADD MPGRP command to add an MLPPP group.

2. Run the ADD MPLNK command to add an MLPPP link.

CAUTIONl One MLPPP group can be configured with a maximum of eight MLPPP links.

l The number of each PPP link and that of each MLPPP link must be unique within aboard.

l Slot 0 is beyond the value range of Bearing time slot. The values of bearing timeslotfor the same Digital Signaling level 1 (DS1) must be consecutive. Timeslot 16 on anE1 link is optional. That is, timeslots 15, 16, and 17 are regarded as consecutive, andthe same is true for timeslots 15 and 17. A timeslot on an E1/T1 link can be used byonly one PPP or MLPPP link.

----End

Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial,with POUa)

This describes how to add the physical layer and data link layer data on the interfaces of theRNC when the POUa serves as the IP interface board. The related activities are the setting ofE1/T1 attributes, optical port attributes, and channel attributes of the channelized optical port,and the addition of PPP links or MLPPP groups.


Mandatory/Optional

Optional. Perform this task only when the POUa serves as the interface board.




Issue 03 (2008-08-30)


PreparationFor the data to be negotiated and planned before you add the physical layer and data link layerdata on the interface (initial, with POUa), refer to 3.2 Data Negotiated Between RNC andOther Network Elements. Prepare the related data for the interface as required.

Procedure

Step 1 Run the SET E1T1 command to set the attributes of the E1/T1.

Step 2 Run the SET OPT command to set the attributes of the optical port.

NOTE

J0 TX Type, J0 TX Value, Expected J0 RX Type, Expected J0 RX Value, J1 TX Type, J1 TXValue, Expected J1 RX type, and Expected J1 RX Value must be consistent with the peer.

Step 3 Run the SET COPTLNK command to set the channel attributes of the channelized optical port.Set the parameters as follows:

NOTE

J2 TX Value and Expected J2 RX Value must be consistent with the peer.

Step 4 Determine the type of the upper-layer application (PPP links or MLPPP link groups) and thenperform the associated step as described in the following table.

If... Then...

PPP links need to be configured Go to Step 5.

MLPPP link groups need to be configured Go to Step 6.

Step 5 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly.

Step 6 To add an MLPPP link group, perform the following steps:1. Run the ADD MPGRP command to add an MLPPP group.2. Run the ADD MPLNK command to add an MLPPP link.



6-35

CAUTIONl One MLPPP link group can be configured with a maximum of eight MLPPP links.

l The number of each PPP link and that of each MLPPP link must be unique within aboard.

l Slot 0 is beyond the value range of Bearing time slot. The values of bearing timeslotfor the same Digital Signaling level 1 (DS1) must be consecutive. Timeslot 16 on anE1 link is optional. That is, timeslots 15, 16, and 17 are regarded as consecutive, andthe same is true for timeslots 15 and 17. A timeslot on an E1/T1 link can be used byonly one PPP or MLPPP link.

----End

Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial,with UOI_IP)

This describes how to add the physical layer and data link layer data on the interfaces of theRNC when the UOI_IP board serves as the IP interface board. The related activities are theconfiguration of optical port attributes and the addition of PPP links.


Mandatory/Optional

Optional. Perform this task only when the UOI_IP board serves as the interfaceboard.

Prerequisite


Preparation

For the data to be negotiated and planned before you add the physical layer and data link layerdata on the interface (initial, with UOI_IP), refer to 3.2 Data Negotiated Between RNC andOther Network Elements. Prepare the related data for the interface as required.

Procedure

Step 1 Run the SET OPT command to set the attributes of the optical port.

NOTE

J0 TX Type, J0 TX Value, Expected J0 RX Type, Expected J0 RX Value, J1 TX Type, J1 TXValue, Expected J1 RX Type, and Expected J1 RX Value must be consistent with the peer.

Step 2 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this commandrepeatedly.

----End




Issue 03 (2008-08-30)

6.5.2 Adding Control Plane Data on the Iub Interface (Initial, overIP)

This describes how to add control plane data on the IP-based Iub interface. The related activitiesare the addition of SCTP signaling links, basic data and algorithm parameters of the NodeB, anadjacent node, and the NCP and CCPs.


Mandatory/Optional

Mandatory

NOTE

l The IP-based Iub interface needs to be configured with at least two SCTP links: one for the NCP andthe other for a CCP. The number of SCTP links should increase with the number of CCPs.

l If the Iub interface supports hybrid IP transport, the IP transport over Ethernet and that over E1/T1share the control plane. That is, you need to add the Iub control plane data only once.

l When adding the control plane data on the IP-based Iub interface, take the constraints on the RNCprocessing capability into consideration. For details, refer to 12.5.3 RNC Capability for SCTP.

Figure 6-16 shows the parameter relationship in the addition of the SCTP link.

Figure 6-16 Parameter relationship in the addition of the SCTP link

Figure 6-17 shows the parameter relationship in the addition of the IP adjacent node.

Figure 6-17 Parameter relationship in the addition of the IP adjacent node

Figure 6-18 shows the parameter relationship in the addition of the port data.



6-37

Figure 6-18 Parameter relationship in the addition of the port data

Prerequisitel The physical layer data for IP transport is configured. For details, refer to 6.5.1.1 Adding

Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, withFG2a/GOUa).

l The data on the data link layer for IP transport is configured. For details, refer to 6.5.1.2Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial,with PEUa).

PreparationFor the data to be negotiated and planned before you configure the Iub control plane on the RNC(initial, over IP), refer to 3.2.2 Data Negotiated on the Iub Interface (over IP).

Procedure

Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, run thiscommand repeatedly. The details are as follows:l Set Signalling link model to SERVER.

l Set Application type to NBAP.

Step 2 Run the ADD NODEB command to add the basic data of a NodeB. Set IUB trans bearertype to IP_TRANS.

NOTE

When satellite-based networking is applied to the Iub interface, set Satellite Trans Ind to TRUE and IUBTrans Delay[ms] to 500. The value of IUB Trans Delay varies with the satellite transmission techniques.You may adjust the value of IUB Trans Delay based on the actual conditions.

Step 3 Run the ADD NODEBALGOPARA command to set the NodeB algorithm parameters.




Issue 03 (2008-08-30)

Step 4 Run the ADD NODEBLDR command to add load reshuffling algorithm parameters for theNodeB.

Step 5 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriateTRM mapping and activity factor tables for users of different priorities. The details are asfollows:l Set Adjacent Node Type to IUB.

l Set Transport Type to IP.

Step 6 Run the ADD NCP command to add an NCP. Set Bearing link type to SCTP.

Step 7 Run the ADD CCP command to add a CCP. Set Bearing link type to SCTP. To add more CCPs,run this command repeatedly.

----End




Mandatory/Optional

Mandatory

NOTE












6-39






Procedure




----End

6.5.4 Adding User Plane Data on the Iub Interface (Initial, over IP)This describes how to add user plane data on the IP-based Iub interface. The related activitiesare the addition of the port controller, IP path, IP route, and transmission resource group.


Mandatory/Optional

Mandatory

Figure 6-19 shows the parameter relationship in the addition of the port controller on the IP-based Iub interface.

Figure 6-19 Parameter relationship in the addition of the port controller on the IP-based interface

Figure 6-20 shows the parameter relationship in the addition of the IP path.




Issue 03 (2008-08-30)

Figure 6-20 Parameter relationship in the addition of the IP path

Prerequisite

The control plane data for the Iub interface in IP transport is successfully configured. For details,refer to 6.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP).

Preparation

For the data to be negotiated and planned before you configure the Iub user plane on the RNC(initial, over IP), refer to 3.2.2 Data Negotiated on the Iub Interface (over IP).

Procedure

Step 1 Run the ADD PORTCTRLER command to specify a TRM controlling SPUa subsystem for aspecific port.

Step 2 (Optional. Perform this step when the RAN sharing function is used) Run the ADDLGCPORT command to add a logical port.

NOTE

If the user plane resources on the Iub interface are separated by operators, set Resource ManagementMode to EXCLUSIVE and set Cn Operator Index.

Step 3 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this commandrepeatedly.

NOTE

l If the user plane resources on the IP-based Iub interface are already separated by running the ADDLGCPORT command, set Bear Type to LGCPORT, which indicates that the IP path is used to carrythe user plan resources of the specified operator.

l The Iub interface supports the FP MUX function. To enable the FP MUX function, set FPMUXEnable to YES, and configure Maximum Subframe Length, Maximum Multiplexing PacketNumber, and Maximum Multiplexing Delay.

Step 4 (Optional. Perform this step only when the Iub interface uses layer 3 networking.) Run the ADDIPRT command to add an IP route.

----End



6-41

6.5.5 Adding an OM Channel on the Iub Interface (Initial, over IP)This describes how to add an OM channel on the IP-based Iub interface. The related activitiesare the setting of the OM IP address of the NodeB and the addition of the electronic serial numberof the NodeB that uses DHCP.


Mandatory/Optional

Mandatory

PrerequisiteThe control plane data for the Iub interface in IP transport is successfully configured. For details,refer to 6.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP).

PreparationFor the data to be negotiated and planned before you add the OM channel on the Iub interface(initial, over IP), refer to 3.2.2 Data Negotiated on the Iub Interface (over IP).

Procedure

Step 1 Run the ADD NODEBIP command to add the OM IP address of the NodeB. The details are asfollows:l Set NodeB TransType to IPTRANS_IP.

l Set NodeB IP_TRANS IP address and NodeB IP_TRANS IP Mask to the OM IP addressand mask in IP transport mode.

l When L3 networking is used between the RNC and the NodeB, set NodeB IP_TRANS Nexthop IP address to the IP address of the RNC gateway. When L2 networking is used betweenthe RNC and the NodeB, set NodeB IP_TRANS Next hop IP address to the IP address ofthe NodeB interface board.

Step 2 If the peer NodeB uses the DHCP, perform the following steps:1. Run the ADD NODEBESN command to add the electronic serial number of the NodeB.2. (Optional. Perform this step only when the VLAN is configured in the transport networking

between the RNC and NodeB) Run the STR NODEBDETECT command to start theNodeB detecting function. With this function, the NodeB can obtain the VLAN ID of theRNC broadcast from the network when the NodeB is set up or faulty. Hence, the NodeBcan start up normally and the local maintenance is avoided.

----End

6.6 Data Configuration Guidelines for the Iub Interface(over ATM and IP)

Related information is required for performing data configuration on the ATM/IP dual stack–based Iub interface. Such information refers to the ATM/IP hybrid transport, ATM/IP-basednetworking, hardware configuration guidelines, data configuration guidelines, IP addresses androutes configuration, and OM channel configuration guidelines.




Issue 03 (2008-08-30)

6.6.1 ATM/IP Hybrid Transport on the Iub InterfaceWith the development of data services, especially with the introduction of HSDPA and HSUPA,there is an increasing demand for bandwidth on the Iub interface. The transmission based onATM over E1, however, causes high cost. Data services produce a decreasing efficiency foroperators. Therefore, the operators require a low-cost Iub transmission solution. In such asituation, ATM/IP hybrid transport, which is based on the ATM/IP dual stack, is introduced. Inaddition to the guarantee of services, this transport reduces costs of data transmission on the Iubinterface.

6.6.2 ATM/IP-Based Networking on the Iub InterfaceThe ATM/IP-based networking on the Iub interface refers to the case where the ATM/IP dualstack is used between the RNC and the NodeB.

6.6.3 Hardware Configuration Guidelines for ATM/IP Hybrid Transport on the Iub InterfaceThis describes the hardware configuration guidelines for ATM/IP hybrid transport on the Iubinterface in terms of board configuration, cable connections, and hardware-related precautions.

6.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transport on the Iub InterfaceThis describes the data configuration guidelines for ATM/IP hybrid transport on the Iub interfacein terms of VLAN planning, transmission resource allocation, and traffic distribution.



6.6.1 ATM/IP Hybrid Transport on the Iub InterfaceWith the development of data services, especially with the introduction of HSDPA and HSUPA,there is an increasing demand for bandwidth on the Iub interface. The transmission based onATM over E1, however, causes high cost. Data services produce a decreasing efficiency foroperators. Therefore, the operators require a low-cost Iub transmission solution. In such asituation, ATM/IP hybrid transport, which is based on the ATM/IP dual stack, is introduced. Inaddition to the guarantee of services, this transport reduces costs of data transmission on the Iubinterface.

Based on the Quality of Service (QoS) and bandwidth requirements, ATM/IP hybrid transportimplements data transmission as follows:l Voice, streaming, and signaling services have a relatively low requirement for the

bandwidth and high requirement for the QoS. Such services are transmitted on ATMnetworks.

l BE services and HSDPA/HSUPA services have a relatively high requirement for thebandwidth and low requirement for the QoS. Such services are transmitted on IP networks.

NOTE

l BE means best effort.

l HSDPA/HSUPA stands for high speed downlink/uplink packet access.

ATM/IP hybrid transport protects the investment of the existing ATM networks, reduces impactof IP transport on the ATM networks, and meets the requirements of operators for highly efficientand low-cost networks and for flexible networking.



6-43

6.6.2 ATM/IP-Based Networking on the Iub InterfaceThe ATM/IP-based networking on the Iub interface refers to the case where the ATM/IP dualstack is used between the RNC and the NodeB.

With the development of data services, especially the introduction of High Speed DownlinkPacket Access (HSDPA) and High Speed Uplink Packet Access (HSUPA), the Iub interface hasan increasing demand for the bandwidth. A pure ATM network is expensive to operate. The IPtechnology saves the transmission cost but provides a lower guarantee of Quality of Service(QoS) than ATM. Thus, the ATM/IP dual stack transport is introduced. Services of differentQoS requirements are transmitted on different types of network.

Scenario

The RNC and NodeB communicate through the ATM and IP networks at the same time.

Description

The ATM/IP dual stack enables hybrid transport of services that have different QoSrequirements. Services of high QoS requirements, such as voice services, streaming services,and the signaling, are transmitted on the ATM network. Services of low QoS requirements, suchas HSDPA and HSUPA services, are transmitted on the IP network.

Figure 6-21 shows the ATM/IP-based networking.

Figure 6-21 ATM/IP-based networking

The RSS or RBS subrack of the RNC is configured with an ATM interface board and an IPinterface board.l The ATM interface board can be an AEUa, AOUa, or UOI_ATM board. It is connected to

the ATM network through the E1/T1 port, channelized STM-1 port, or OC-3C port.l The IP interface board can be an FG2a, GOUa, PEUa, POUa, or UOI_IP board. It is

connected to the IP network through the E1/T1 port, channelized STM-1 port, or OC-3Cport.

The NodeB is connected to the ATM and IP networks through the corresponding ATM and IPinterface boards respectively.

Advantagesl The ATM network ensures the QoS.




Issue 03 (2008-08-30)

l The IP network saves the transmission cost and meets the requirement for high bandwidthon the Iub interface.

DisadvantagesWhen the ATM/IP-based networking is applied, maintenance is required for both ATM networkand IP network. Thus, the difficulty in and cost of maintaining the networks are increased.

6.6.3 Hardware Configuration Guidelines for ATM/IP HybridTransport on the Iub Interface

This describes the hardware configuration guidelines for ATM/IP hybrid transport on the Iubinterface in terms of board configuration, cable connections, and hardware-related precautions.

Hardware Configuration Guidelines for ATM/IP Hybrid TransportWhen implementing ATM/IP hybrid transport, insert ATM and IP interface boards into the slotsof the RSS and RBS subracks. That is, an ATM/IP dual stack–based NodeB can be connectedto an ATM interface board and an IP interface board at the same time. The two interface boardscan be positioned in different subracks.

NOTE

Though the RNC ATM and IP interface boards for one NodeB can be positioned in different subracks, itis recommended that the interface boards be positioned in one subrack if possible.

Interface Board Configuration for ATM/IP Hybrid TransportAll ATM and IP interface boards are available for ATM/IP hybrid transport.

The recommended interface boards are as follows:l ATM interface board: UOI_ATM, AOUa, and AEUa

l IP interface board: GOUa, FG2a, POUa, and UOI_IP

Figure 6-22 and Figure 6-23 show the typical configurations of interface boards for ATM/IPhybrid transport. As shown in the figures, the AOUa serves as the ATM interface board and theGOUa serves as the IP interface board.

Figure 6-22 Typical configuration of boards in the RSS subrack for ATM/IP hybrid transport



6-45

Figure 6-23 Typical configuration of boards in an RBS subrack for ATM/IP hybrid transport

Cable ConnectionsWhen ATM/IP hybrid transport is applied, the ATM interface at the RNC connects to the NodeBthrough an ATM network, and the IP interface at the RNC connects to the NodeB through anIP network.

6.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transporton the Iub Interface

This describes the data configuration guidelines for ATM/IP hybrid transport on the Iub interfacein terms of VLAN planning, transmission resource allocation, and traffic distribution.

VLAN PlanningVirtual Local Area Network (VLAN) helps shield the RNC from network storms and improvethe security of layer 2 networking. The priorities in VLAN tags are used for servicedifferentiation. The specifications for VLANs in ATM/IP hybrid transport are the same as thosein IP transport on the Iub interface.

The VLAN can be planned as VLAN setting in layer 2 networking and as VLAN setting in layer3 networking.

l VLAN setting in layer 2 networking

The value range of VLAN ID is from 2 to 4094. Due to the limited VLAN ID resources, itis recommended that an identical VLAN ID be allocated to the NodeBs whose traffic isconverged to the same layer 2 transmission device LAN switch. If the layer 2 transmissiondevice supports the setting of VLAN priorities, the priorities of services need to be mappedonto those of VLANs. If the layer 2 transmission device identifies the priorities based onthe VLAN IDs, the priorities of services need to be mapped onto VLAN IDs based on theservice types, so as to implement differentiated services.

l VLAN setting in layer 3 networking

VLANs apply to layer 2 networking only. It does not apply to layer 3 transmission devices.Therefore, interface boards at the RNC do not need to be configured with VLAN tags. Ifthe RNC connects to a layer 3 transmission device through a layer 2 network that supportsconfiguration of VLAN priorities, the interface board at the RNC can map the priorities of




Issue 03 (2008-08-30)

services either onto the priorities of VLANs or, based on the service types, onto the VLANIDs. In layer 3 networking, the VLANs configured at the RNC apply to the RNC and thelayer 3 transmission device only. Therefore, the typical practice is to set VLAN IDs andpriorities based on the service types, rather than to set them based on the NodeB.

Transmission Resource AllocationWhen you allocate resources for ATM/IP hybrid transport on the Iub interface, take the followingsuggestions into consideration:

ATM transport, IP transport, or ATM/IP hybrid transport is applicable to control plane data. Itis recommended that ATM/IP hybrid transport be applied to control plane data for security. Inother words, the SAAL and SCTP links carry the NCP or a CCP at the same time, and the activelink is the SAAL link.

ATM transport, IP transport, or ATM/IP hybrid transport is applicable to user plane data. It isrecommended that:

l ATM transport be applied to signaling, voice services, CS conversational services, CSstreaming services, PS conversational services, and PS streaming services.

l IP transport be applied to PS interactive services, PS background services, HSDPAconversational services, HSDPA streaming services, HSDPA interactive services, HSDPAbackground services, HSUPA conversational services, HSUPA streaming services,HSUPA interactive services, and HSUPA background services.

Either ATM or IP transport is applicable to management plane data. It is recommended that IPtransport be applied.

Traffic DistributionFor ATM traffic distribution principles and the correlation between ATM traffic description andservice type, refer to 12.8.4 ATM Traffic Resource Configuration Guidelines.


Networking on the Iub InterfaceThere are two types of networking on the Iub interface, namely, layer 2 networking and layer 3networking. Compared with layer 3 networking, layer 2 networking is simpler. That is becausethe port IP addresses of the RNC and NodeB are located on the same network segment and noroute is required.




6-47


NOTE

IP 1 and IP 2 are port IP addresses.



NOTE

IP 1 and IP 2 are device IP addresses on the IP interface board. IP 3 and IP 4 are port IP addresses on theIP interface board. IP 5 and IP 6 are gateway IP addresses on the RNC side. IP 7 is the gateway IP addresson the NodeB side. IP 8 is the IP address of the NodeB.

IP Addresses on the Iub InterfaceAs shown in Figure 6-24 and Figure 6-25, the Iub IP addresses at the RNC consist of IPaddresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP groups,and device IP addresses. Table 6-11 describes these IP addresses.




Issue 03 (2008-08-30)

Table 6-11 IP addresses on the Iub interface


IP address of anEthernet port

Required when the FG2a orGOUa serves as theinterface board

l Each Ethernet port can be configuredwith only one primary IP address and 5secondary addresses.

l The IP address of an Ethernet port and theinternal IP address of the BAM must belocated on different network segments.For these network segments, one cannotcover another.

l In the RNC, the IP addresses of differentEthernet ports must be located ondifferent network segments. For thesenetwork segments, one cannot coveranother.

Local IPaddress of aPPP link

Required when the PEUa,POUa, or UOI_IP serves asthe interface board

Each PPP link can be configured with onlyone local IP address.

Local IPaddress of anMLPPP group

Required when the PEUa orPOUa serves as the interfaceboard

Each MLPPP group can be configured withonly one local IP address.

Device IPaddress

Required in layer 3networking

l Each interface board can be configuredwith a maximum of five device IPaddresses.

l The IP addresses of any two differentdevices must be located on differentsubnets.

Route on the Iub Interface

On the Iub interface where layer 2 networking is applied, no route is required. On the Iub interfacewhere layer 3 networking is applied, you should configure the route described in Table 6-12 onthe RNC.

Table 6-12 Route on the Iub Interface

Device Route Description

IP interfaceboard

The route travels from the RNC to the network segment where the NodeB islocated.You can use the ADD IPRT command on the RNC to configure the route.Destination IP address is the address of the network segment where theNodeB is located, and Next Hop Address is the gateway IP address on theRNC side, for example, IP 5 or IP 6.



6-49


Routing Between the M2000 and the NodeB Through the RNCFigure 6-26 shows an example of routing between the M2000 and the NodeB through the RNC.Table 6-13 describes the routes.

Figure 6-26 Example of routing between the M2000 and the NodeB through the RNC

NOTE

l Figure 6-26 takes layer 2 networking on the Iub interface for an example. When layer 3 networkingis applied to the Iub interface, the IP interface board and the NodeB communicate through a router.

l The RINT shown in Figure 6-26 refers to IP interface boards PEUa, POUa, UOI_IP, FG2a, and GOUa.

Table 6-13 Routes for the connection between the M2000 and the NodeB through the RNC


M2000 From the M2000 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the external virtual IPaddress of the BAM, that is,172.121.139.200

-

RNC From the OMUa board to the NodeBOM network segment 19.19.19.X, withthe next hop to be the internal IPaddress of the IP interface board at theRNC, that is, 80.168.3.66

From the IP interface board of theRNC to the M2000 IP networksegment 172.121.139.XYou can run the ADD EMSIPcommand on the RNC toconfigure the route. When you runthis command, set EMS IPAddress to the IP address of the




Issue 03 (2008-08-30)


From the IP interface board of the RNCto the NodeB OM network segment19.19.19.Xl If layer 2 networking is applied to

the Iub interface, the next hop is theIP address of the interface board atthe NodeB, that is, 16.16.16.2.

l If layer 3 networking is applied tothe Iub interface, the next hop is thegateway IP address on the RNC side.

You can run the ADD NODEBIPcommand on the RNC to configure theroute. IP address is the OM IP addressof the NodeB.l If layer 2 networking is applied to

the Iub interface, Gateway IPaddress is the IP address of theinterface board at the NodeB.

l If layer 3 networking is applied tothe Iub interface, Gateway IPaddress is the gateway IP address onthe RNC side.

M2000, set Subnet mask to thesubnet mask of the M2000, andspecify the values of BAMExternal Network Virtual IPand BAM External NetworkMask. In this example, EMS IPAddress is 172.121.139.56, andBAM External Network VirtualIP is 172.121.139.200.

NodeB - From the NodeB to the M2000 IPnetwork segment 172.121.139.Xl If layer 2 networking is applied

to the Iub interface, the nexthop is the IP address of the IPinterface board at the RNC, thatis, 16.16.16.1.

l If layer 3 networking is appliedto the Iub interface, the nexthop is the gateway IP addresson the NodeB side.

Routing Between the M2000 and the NodeB Not Through the RNCIf the OM subnet where the M2000 is located is connected to the IP network that covers theNodeB, routes can be configured between the M2000 and the NodeB not through the RNC.Figure 6-27 shows an example of routing between the M2000 and the NodeB not through theRNC. Table 6-14 describes the routes.



6-51

Figure 6-27 Example of routing between the M2000 and the NodeB not through the RNC

Table 6-14 Routes for the connection between the M2000 and the NodeB not through the RNC


M2000 From the M2000 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the port IP address ofrouter 1, that is, 10.161.215.200

-

Router 1 From router 1 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the port IP address ofrouter 2, that is, 172.16.16.10

-

Router 2 From router 2 to the NodeB OMnetwork segment 19.19.19.X, with thenext hop to be the IP address of the IPinterface board at the NodeB, that is,16.16.16.2

From router 2 to the M2000network segment10.161.215.100, with the next hopto be the port IP address of router1, that is, 172.16.16.9

NodeB - From the NodeB to the M2000network segment10.161.215.100, with the next hopto be the port IP address of router2, that is, 16.16.16.20

6.7 Adding Data on the Iub Interface (Initial, over ATM andIP)

This describes how to add the transport network layer data on the ATM/IP dual stack-based Iubinterface.


Mandatory/Optional

Optional. Perform this task for each ATM and IP dual stack-based Iub interface.




Issue 03 (2008-08-30)

NOTE


l For the recommended interface boards and configuration of the physical layer for the Iub interface,refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.

l When adding data on the Iub interface, take the related capabilities and specifications of the RNC intoconsideration. For details, refer to 12.5 External Specifications for the RNC.

l All the data of a NodeB, including data of cells and links, should be controlled by one SPUa subsystem.When the NodeB carries an HSDPA or HSUPA cell, at least one AAL2 path of HSDPA_RT/HSDPA_NRT/HSUPA_RT/HSUPA_NRT type on the Iub interface should be configured.

For the data configuration rules for data transmission based on the ATM/IP dual stack on theIub interface, refer to 6.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transporton the Iub Interface.


PreparationFor the data to be negotiated and planned before you add data on the Iub interface (over ATMand IP), refer to 3.2.3 Data Negotiated on the Iub Interface (over ATM and IP).

ProcedureStep 1 Add the physical layer data and ATM layer traffic resource data in the ATM transport:

1. For details about adding the physical layer data in the ATM transport, refer to 6.3.1 AddingPhysical Layer Data (Initial, over ATM).

2. For details about adding the ATM layer traffic resource, refer to 6.3.2 Adding ATM TrafficResources (Initial).

Step 2 Add the physical layer data and data link layer data in the IP transport. For details, refer to 6.5.1Adding Physical Layer and Data Link Layer Data (Initial, over IP).

Step 3 Configure the control plane.l If ATM transport is applied to the control plane, add related data by referring to 6.3.3 Adding

Control Plane Data on the Iub Interface (Initial, over ATM).l If IP transport is applied to the control plane, add related data by referring to 6.5.2 Adding

Control Plane Data on the Iub Interface (Initial, over IP).NOTE

l Run the ADD NODEB command and set IUB trans bearer type to ATMANDIP_TRANS~2(ATMcircuit & IP transmission).

l Run the ADD ADJNODE command and set Adjacent Node Type to IUB and Transport Type toATM_IP.

l The NCP/CCP supports the SAAL and SCTP dual link bearer to improve the security. To implementthis function, configure the NCP/CCP as follows: Run the ADD NCP and ADD CCP commands andset Bearing Link Type to SAAL-SCTP and input the bearing SAAL link No. and SCTP link No.. Therecommended Main link type is SAAL.

Step 4 Add the TRM mapping of adjacent nodes. For details, refer to 6.3.4 Adding Mapping BetweenAdjacent Nodes and Transmission Resources (Initial).



6-53

When you run the ADD TRMMAP command to add the TRM mapping of the dual stack-basedNodeB:

l Set Interface Type to IUB_IUR_IUCS.

l Set Transport Type to ATM_IP.

Step 5 Configure the user plane.l If ATM transport is applied to the user plane, add related data by referring to 6.3.5 Adding

User Plane Data on the Iub Interface (Initial, over ATM).l If IP transport is applied to the user plane, add related data by referring to 6.5.4 Adding User

Plane Data on the Iub Interface (Initial, over IP).

Step 6 Configure the OM channel.l To operate the OM channel and use ATM/IP dual stack for data transmission, perform the

following steps:– Run the commands ADD DEVIP and ADD IPOAPVC to create one IPoA PVC channel

for operation and maintenance between RNC and NodeB.– Run the ADD NODEBIP command to add the OM IP address of the dual stack-based

NodeB. Set NodeB TransType to ATMANDIPTRANS_IP. For ATM stack-based OMchannel parameters for the NodeB, refer to 6.3.6 Adding an OM Channel on the IubInterface (Initial, over ATM). For IP stack-based OM channel parameters for theNodeB, refer to 6.5.5 Adding an OM Channel on the Iub Interface (Initial, overIP).

l If ATM transport is applied to the OM channel, add related data by referring to 6.3.6 Addingan OM Channel on the Iub Interface (Initial, over ATM).

l If IP transport is applied to the OM channel, add related data by referring to 6.5.5 Addingan OM Channel on the Iub Interface (Initial, over IP).

----End




Issue 03 (2008-08-30)

7 Configuring Iu-CS Interface Data (Initial)

About This Chapter

The Iu-CS is the logical interface between the RNC and the CS domain. The RNC exchangesthe CS data with the CN through the Iu-CS interface. This topic describes how to add the transportnetwork layer data on the Iu-CS interface.

7.1 Example: Iu-CS Data in the RNC Initial Configuration ScriptThis describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS dataconsists of the physical layer data, ATM traffic resource data, TRM mapping, activity factortable, control plane data, and user plane data.

7.2 Data Configuration Guidelines for the Iu-CS Interface (over ATM)Related information is required for performing data configuration on the ATM-based Iu-CSinterface. Such information refers to the protocol stack, links on the Iu-CS interface, and thedifferences between R99 and R4/R5/R6.

7.3 Adding Data on the Iu-CS Interface (Initial, over ATM)This describes how to add the transport network layer data on the ATM-based Iu-CS interface.

7.4 Data Configuration Guidelines for the Iu-CS Interface (over IP)Related information is required for performing data configuration on the IP-based Iu-CSinterface. Such information refers to the protocol structure, links on the Iu-CS interface, and thedifferences between R99 and R4/R5/R6.

7.5 Adding Data on the Iu-CS Interface (Initial, over IP)This describes how to add the transport network layer data on the IP-based Iu-CS interface.

RNCRNC Initial Configuration Guide 7 Configuring Iu-CS Interface Data (Initial)


7-1

7.1 Example: Iu-CS Data in the RNC Initial ConfigurationScript

This describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS dataconsists of the physical layer data, ATM traffic resource data, TRM mapping, activity factortable, control plane data, and user plane data.

//Take the script for the ATM-based Iu-CS interface as an example.



SET OPT: SRN=0, SN=16, BT=UOI, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16byte, J0TXVALUE="SBS HuaWei 155",J0RXT=16byte, J0RXVALUE="SBS HuaWei 155", J1TXT=16byte, J1TXVALUE="SBS HuaWei 155", J1RXT=16byte, J1RXVALUE="SBS HuaWei 155";



//For the ATM traffic record on the user plane, the record index is 180, the service type is CBR,and the peak cell rate is 10000 cell/s.

ADD ATMTRF: TRFX=170, ST=CBR, UT=CELL/S, PCR=1500, CDVT=1024, REMARK="IUCS CONTROL PLANE";

ADD ATMTRF: TRFX=180, ST=CBR, UT=CELL/S, PCR=10000, CDVT=1024, REMARK="IUCS USER PLANE";

//Add TRM mapping records for gold, silver, and copper users respectively.


//Add activity factor tables for gold, silver, and copper users respectively.

ADD FACTORTABLE: FTI=3, REMARK="FOR IUCS GOLD USER";ADD FACTORTABLE: FTI=4, REMARK="FOR IUCS SILVER USER";ADD FACTORTABLE: FTI=5, REMARK="FOR IUCS BRONZE USER";

//Add the Iu-CS control plane data.

//Add SAAL links.


ADD SAALLNK: SRN=0, SN=4, SSN=0, SAALLNKN=11, CARRYT=NCOPT, CARRYSRN=0,

7 Configuring Iu-CS Interface Data (Initial)RNC



Issue 03 (2008-08-30)

CARRYSN=16, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=101, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI, MPS=MPS_EMERGENCY, CCTMR=200, POLLTMR=100, IDLETMR=500, RSPTMR=5000, KEEPTMR=100, COMTMR1=2, COMTMR2=30, COMTMR3=10, SRECTMR=60, INHTMR=1500, MAXNRP=0, MAXCC=4, MAXPD=500, STATLEN=67, N1=1000, WINDOWSIZE=100;



//Add RNC DSPs.

ADD N7DPC: DPX=0, DPC=H'0008DB, SLSMASK=B0000, NEIGHBOR=YES, NAME="TO-MGW", DPCT=IUCS, STP=OFF, PROT=ITUT, BEARTYPE=MTP3B;


ADD MTP3BLKS: SIGLKSX=0, DPX=0, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-MGW";

ADD MTP3BRT: DPX=0, SIGLKSX=0, NAME="TO-MGW";





//Add an adjacent node over the Iu-CS interface.

ADD ADJNODE: ANI=1, NAME="MGW", NODET=IUCS, DPX=0, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS2;

//Configure the mapping between adjacent nodes and transmission resources.

ADD ADJMAP: ANI=1, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=3, TMISLV=4, TMIBRZ=5, FTIGLD=3, FTISLV=4, FTIBRZ=5;




7-3

ADD CNDOMAIN: CNDomainId=CS_DOMAIN, T3212=24, ATT=ALLOWED, DRXCycleLenCoef=6;

ADD CNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=ATM_TRANS;

//Add the Iu-CS user plane data.



//Add AAL2 paths.




//Add AAL2 routes.


7.2 Data Configuration Guidelines for the Iu-CS Interface(over ATM)

Related information is required for performing data configuration on the ATM-based Iu-CSinterface. Such information refers to the protocol stack, links on the Iu-CS interface, and thedifferences between R99 and R4/R5/R6.

7.2.1 Protocol Structure for the Iu-CS Interface (over ATM)If ATM transport is applied to the Iu-CS interface, the sequence of adding Iu-CS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

7.2.2 Links on the Iu-CS interface (over ATM)The links on the ATM-based Iu-CS interface appear to the CN as two types: MTP3-b link andAAL2 path.




Issue 03 (2008-08-30)

7.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6In the 3GPP R99, the MSC connects to the RNC as one entity. In the 3GPP R4/R5/R6, the MSCconnects to the RNC after being split into two entities, namely, MSC server and MGW.

7.2.1 Protocol Structure for the Iu-CS Interface (over ATM)If ATM transport is applied to the Iu-CS interface, the sequence of adding Iu-CS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

Figure 7-1 shows the protocol stack for the Iu-CS interface.

Figure 7-1 Protocol stack for the ATM-based Iu-CS interface

The transport network layer of the Iu-CS interface consists of the following areas:

l Transport network layer user plane (area A)

l Transport network layer control plane (area B)

l Transport network layer user plane (area C)

Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areascan be carried on common physical links.

7.2.2 Links on the Iu-CS interface (over ATM)The links on the ATM-based Iu-CS interface appear to the CN as two types: MTP3-b link andAAL2 path.



7-5

Links on the Iu-CS Interface

Figure 7-2 shows the links on the ATM-based Iu-CS interface.

Figure 7-2 Links on the Iu-CS interface (over ATM)

NOTE

The RINT shown in the preceding figure refers to ATM interface boards of the RNC. Only the UOI_ATMcan be used for the ATM-based Iu-CS interface.

MTP3-b Link

MTP3-b links are contained in an MTP3-b link set. The numbers of MTP3-b links range from0 to 15.

At least one MTP3-b link should be configured between the RNC and the MGW. Configurationof more than one MTP3-b link is recommended.

The configuration of MTP3-b links depends on the networking between the MSC server and theRNC:

l If the MSC server is directly connected to the RNC, at least one MTP3-b link is requiredfor the MSC server (IUCS_RANAP signaling point). It is recommended that more thanone MTP3-b link be planned.

l If the MSC server is connected to the RNC through the MGW, the MSC server(IUCS_RANAP signaling point) does not require any MTP3-b link.

l If the MSC server is connected to the RNC not only directly but also through the MGW,as shown in Figure 7-3, the MSC server (IUCS-RANAP) requires at least one MTP3-blink. It is recommended that more than one MTP3-b link be planned.




Issue 03 (2008-08-30)

Figure 7-3 Example of connections between the MSC server and the RNC

MTP3-b links are carried on the SAAL links of Network-to-Network Interface (NNI) type. It isrecommended that the SAAL links of NNI type be evenly distributed to the SPUa subsystemsin the RSS subrack or an RBS subrack so that the signaling exchange can be reduced betweenthe SPUa subsystems.

An SAAL link of NNI type is carried on an ATM PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the RNC and the peer.

AAL2 PathAn AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to4294967295.

An Iu-CS interface has at least one AAL2 path. It is recommended that more than one AAL2path be configured.

An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVCattributes must be negotiated between the RNC and the peer.


Iu-CS Interface Defined in the 3GPP R4/R5/R6Figure 7-4 shows the Iu-CS interface in the 3GPP R4/R5/R6.



7-7

Figure 7-4 Iu-CS interface in the 3GPP R4/R5/R6

The network may require multiple MGWs depending on the traffic volume.

In practice, the MSC server is often not directly connected to the RNC. Data is forwardedbetween the MSC server and the RNC through the routes configured on the MGW. Figure7-5 shows an example topology on the Iu-CS interface in the 3GPP R4/R5/R6.

Figure 7-5 Example of the topology on the Iu-CS interface in the 3GPP R4/R5/R6

Functions of the MSC and of the MSC Server and MGWFigure 7-6 and Figure 7-7 show the protocol stacks for the ATM- and IP-based Iu-CS interfacesrespectively.




Issue 03 (2008-08-30)


Figure 7-7 Protocol stack for the IP-based Iu-CS interface

The MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack.The MSC server and MGW in an R4/R5/R6 network implement their functions as follows:



7-9

l The MSC server implements the functions in area A.

l On the ATM-based Iu-CS interface, the MGW implements the functions in areas B and Cshown in Figure 7-6. On the IP-based Iu-CS interface, the MGW implements the functionsin area C shown in Figure 7-7.

Data Configuration on the RNCIn the 3GPP R99, the RNC needs to be configured with only one type of Iu-CS signaling point,that is, the MSC.

In the 3GPP R4/R5/R6, the RNC needs to be configured with the following two types of Iu-CSsignaling point:l MSC server (also called Iu-CS RANAP signaling point)

l MGW (also called Iu-CS ALCAP signaling point)

Table 7-1 describes the differences between signaling point configuration in R99 and that inR4/R5/R6.

Table 7-1 Differences between signaling point configuration in R99 and that in R4/R5/R6

Item R4/R5/R6 R99

Type Iu-CS RANAP signaling point and Iu-CSALCAP signaling point

Iu-CS signalingpoint

Quantity More than one One

7.3 Adding Data on the Iu-CS Interface (Initial, over ATM)This describes how to add the transport network layer data on the ATM-based Iu-CS interface.


Mandatory/Optional

Mandatory. Perform this task once on each Iu-CS interface when the RNCconnects to multiple CS CN nodes over ATM.

NOTE

l This task configures only the transport network layer of the ATM-based Iu-CS interface.

l For the recommended interface boards and configuration of the physical layer for the ATM-based Iu-CS interface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.

PrerequisiteThe OSP data of the RNC is configured. For details, refer to 4.4 Adding OSP to the RNC(Initial).

PreparationFor the data to be negotiated and planned before you add data on the Iu-CS interface (initial,over ATM), refer to 3.2.4 Data Negotiated on the Iu-CS Interface (over ATM) .




Issue 03 (2008-08-30)



3. 7.3.3 Adding Control Plane Data on the Iu-CS Interface (Initial, over ATM)This describes how to add control plane data on the ATM-based Iu-CS interface. The relatedactivities are the addition of the SAAL links, Destination Signaling Point (DSP), MTP3-bdata, adjacent node, and CN node.


5. 7.3.5 Adding User Plane Data on the Iu-CS Interface (Initial, over ATM)This describes how to add user plane data on the ATM-based Iu-CS interface. The relatedactivities are the addition of the port controller, AAL2 path, and AAL2 route.


NOTE




Mandatory/Optional

Mandatory

NOTE






7-11



----End

7.3.3 Adding Control Plane Data on the Iu-CS Interface (Initial, overATM)

This describes how to add control plane data on the ATM-based Iu-CS interface. The relatedactivities are the addition of the SAAL links, Destination Signaling Point (DSP), MTP3-b data,adjacent node, and CN node.


Mandatory/Optional

Mandatory

NOTE

l When you configure a DSP code, specify the signaling route mask for load sharing. When you configurea signaling link set, specify the signaling link mask to determine the strategy of routing betweensignaling links within that signaling link set. The result of the signaling route mask AND the signalinglink mask should be 0. For the method and example of configuring the signaling route mask and thesignaling link mask, refer to 12.10.3 Signaling Route Mask and Signaling Link Mask.

l When adding MTP3-b data, take the constraints on the RNC processing capability into consideration.For details, refer to 12.5.5 RNC Capability for MTP3-b.

l When adding the CS CN node, pay attention to 12.3.11 CN Node ID.

Figure 7-8 shows the parameter relationship in the addition of the MTP3-b link.




Issue 03 (2008-08-30)

Figure 7-8 Parameter relationship in the addition of the MTP3-b link

Figure 7-9 shows the parameter relationship in the addition of the CN node.

Figure 7-9 Parameter relationship in the addition of the CN node

Prerequisitel The OSP data of the RNC is configured. For details, refer to 4.4 Adding OSP to the RNC

(Initial).l The physical layer data for ATM transport is configured. For details, refer to 7.3.1 Adding

Physical Layer Data (Initial, over ATM).l Traffic resources at the ATM layer are configured. For details, refer to 7.3.2 Adding ATM


PreparationFor the data to be negotiated and planned before you configure the Iu-CS control plane on theRNC (initial, over ATM), refer to 3.2.4 Data Negotiated on the Iu-CS Interface (overATM) .



7-13

Procedure

Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To addmore SAAL NNI links, run this command repeatedly.

Step 2 Run the ADD N7DPC command to add a DSP. To add more DSPs, run this command repeatedly.l You are advised to set Signalling route mask to B0000.

l When you set the Media Gateway as a DSP, set Adjacent flag to YES, and set DSP type toIUCS-ALCAP. This configuration indicates that the DSP has the functionality of transportnetwork layer control plane on the Iu-CS interface.

l When you set the MSC server as a DSP, set Adjacent flag to NO, and set DSP type to IUCS-RANAP. This configuration indicates that the DSP has the functionality of radio networklayer control plane on the Iu-CS interface.

CAUTIONEach DSP code must be unique and be different from any Originating Signaling Point (OSP)code.

Step 3 Run the ADD MTP3BLKS command to add an MTP3-b signaling link set. To enable loadsharing between MTP3-b signaling links, it is recommended that Signaling link mask be set toB1111.

Step 4 Run the ADD MTP3BRT command to add an MTP3-b route. To add more MTP3-b routes, runthis command repeatedly.

Step 5 Run the ADD MTP3BLNK command to add an MTP3-b signaling link. To add more MTP3-b signaling links, run this command repeatedly.

Step 6 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriateTRM mapping and activity factor tables for users of different priorities. The details are asfollows:l Set Adjacent Node Type to IUCS.


Step 7 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID toCS_DOMAIN.

Step 8 Run the ADD CNNODE command to add a CN node. The details are as follows:l Set CN domain ID to CS_DOMAIN.

l Set IU trans bearer type to ATM_TRANS.

----End






Issue 03 (2008-08-30)


Mandatory/Optional

Mandatory

NOTE



Prerequisite


Preparation

Table 7-2 describes the data to be negotiated and planned before you configure the TRMmapping.











Procedure





7-15


----End

7.3.5 Adding User Plane Data on the Iu-CS Interface (Initial, overATM)

This describes how to add user plane data on the ATM-based Iu-CS interface. The relatedactivities are the addition of the port controller, AAL2 path, and AAL2 route.


Mandatory/Optional

Mandatory

NOTE

The AAL2 path capability of the Iu-CS adjacent node must comply with those stipulated in 12.5.7 RNCCapability for AAL2 Paths and AAL2 Routes.

Figure 7-10 shows the parameter relationship in the addition of the port controller on the ATM-based interface.


Figure 7-11 shows the parameter relationship in the addition of the AAL2 path and AAL2 route.




Issue 03 (2008-08-30)

Figure 7-11 Parameter relationship in the addition of the AAL2 path and the AAL2 route

Prerequisite

The control plane data of the ATM-based Iu-CS interface is configured. For details, refer to7.3.3 Adding Control Plane Data on the Iu-CS Interface (Initial, over ATM).

Preparation

For the data to be negotiated and planned before you configure the Iu-CS user plane on the RNC(initial, over ATM), refer to 3.2.4 Data Negotiated on the Iu-CS Interface (over ATM) .

Procedure



Step 3 Run the ADD AAL2RT command to add an AAL2 route.

----End



7-17

7.4 Data Configuration Guidelines for the Iu-CS Interface(over IP)

Related information is required for performing data configuration on the IP-based Iu-CSinterface. Such information refers to the protocol structure, links on the Iu-CS interface, and thedifferences between R99 and R4/R5/R6.

7.4.1 Protocol Structure for the Iu-CS Interface (over IP)If IP transport is applied to the Iu-CS interface, the sequence of adding Iu-CS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

7.4.2 Links on the Iu-CS interface (over IP)The links on the IP-based Iu-CS interface appear to the CN as two types: M3UA link and IPpath.


7.4.1 Protocol Structure for the Iu-CS Interface (over IP)If IP transport is applied to the Iu-CS interface, the sequence of adding Iu-CS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

Figure 7-12 shows the protocol stack for the Iu-CS interface.





Issue 03 (2008-08-30)

7.4.2 Links on the Iu-CS interface (over IP)The links on the IP-based Iu-CS interface appear to the CN as two types: M3UA link and IPpath.

Links on the Iu-CS Interface

Figure 7-13 shows the links on the IP-based Iu-CS interface.

Figure 7-13 Links on the Iu-CS interface (over IP)

NOTE

The RINT shown in the preceding figure refers to IP interface boards GOUa, FG2a, and UOI_IP.

M3UA Link

M3UA links are contained in an M3UA link set. The numbers of M3UA links range from 0 to63.

At least one M3UA link should be configured between the RNC and the MGW. Configurationof more than one M3UA link is recommended.

The configuration of M3UA links between the RNC and MSC Server depends on the networkingbetween the MSC server and the RNC:

l If the MSC server is directly connected to the RNC, at least one M3UA link is required forthe MSC server (IUCS_RANAP signaling point). It is recommended that more than oneMTP3-b link be configured.

l If the MSC server is connected to the RNC through the MGW, the MSC server(IUCS_RANAP signaling point) does not require any M3UA link.



7-19

l If the MSC server is connected to the RNC not only directly but also through the MGW,as shown in Figure 7-14, the MSC server (IUCS-RANAP) requires at least one M3UAlink. It is recommended that more than one M3UA link be configured.

Figure 7-14 Example of connections between the MSC server and the RNC

M3UA links are carried on SCTP links. It is recommended that the SCTP links are evenlydistributed to the SPUa subsystems in the RSS subrack or an RBS subrack so that the signalingexchange can be reduced between the SPUa subsystems.

IP PathAn IP path is a group of connections to the adjacent node. The path IDs range from 0 to 65535.

An Iu-CS interface has at least one IP path. It is recommended that more than one AAL2 pathbe configured.


Iu-CS Interface Defined in the 3GPP R4/R5/R6Figure 7-15 shows the Iu-CS interface in the 3GPP R4/R5/R6.




Issue 03 (2008-08-30)

Figure 7-15 Iu-CS interface in the 3GPP R4/R5/R6

The network may require multiple MGWs depending on the traffic volume.

In practice, the MSC server is often not directly connected to the RNC. Data is forwardedbetween the MSC server and the RNC through the routes configured on the MGW. Figure7-16 shows an example topology on the Iu-CS interface in the 3GPP R4/R5/R6.

Figure 7-16 Example of the topology on the Iu-CS interface in the 3GPP R4/R5/R6

Functions of the MSC and of the MSC Server and MGWFigure 7-17 and Figure 7-18 show the protocol stacks for the ATM- and IP-based Iu-CSinterfaces respectively.



7-21



The MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack.The MSC server and MGW in an R4/R5/R6 network implement their functions as follows:




Issue 03 (2008-08-30)

l The MSC server implements the functions in area A.

l On the ATM-based Iu-CS interface, the MGW implements the functions in areas B and Cshown in Figure 7-17. On the IP-based Iu-CS interface, the MGW implements the functionsin area C shown in Figure 7-18.

Data Configuration on the RNCIn the 3GPP R99, the RNC needs to be configured with only one type of Iu-CS signaling point,that is, the MSC.

In the 3GPP R4/R5/R6, the RNC needs to be configured with the following two types of Iu-CSsignaling point:l MSC server (also called Iu-CS RANAP signaling point)

l MGW (also called Iu-CS ALCAP signaling point)

Table 7-4 describes the differences between signaling point configuration in R99 and that inR4/R5/R6.

Table 7-4 Differences between signaling point configuration in R99 and that in R4/R5/R6

Item R4/R5/R6 R99

Type Iu-CS RANAP signaling point and Iu-CSALCAP signaling point

Iu-CS signalingpoint

Quantity More than one One

7.5 Adding Data on the Iu-CS Interface (Initial, over IP)This describes how to add the transport network layer data on the IP-based Iu-CS interface.


Mandatory/Optional

Mandatory. Perform this task once on each Iu-CS interface when the RNCconnects to multiple CS CN nodes over IP.

NOTE

l This task configures only the transport network layer of the IP-based Iu-CS interface.

l For the recommended interface boards and configuration of the physical layer for the IP-based Iu-CSinterface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.


PreparationFor the data to be negotiated and planned before you add data on the Iu-CS interface (initial,over IP), refer to 3.2.5 Data Negotiated on the Iu-CS Interface (over IP).



7-23


2. 7.5.2 Adding Control Plane Data on the Iu-CS Interface (Initial, over IP)This describes how to add control plane data on the IP-based Iu-CS interface. The relatedactivities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UAdata, adjacent node, CN domain data, and CN node data.


4. 7.5.4 Adding User Plane Data on the Iu-CS Interface (Initial, over IP)This describes how to add user plane data on the IP-based Iu-CS interface. The relatedactivities are the addition of the port controller, IP path, and IP route.


The addition of physical layer and data link layer data is necessary for the data configuration ofthe IP-based Iub, Iu-CS, Iu-PS, and Iur interfaces. Before the interface data configuration, youneed to determine the type of the interface board. Then, configure the data of the correspondingphysical layer and data link layer data according to the interface board type.

NOTE


7.5.2 Adding Control Plane Data on the Iu-CS Interface (Initial, overIP)

This describes how to add control plane data on the IP-based Iu-CS interface. The relatedactivities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UA data,adjacent node, CN domain data, and CN node data.


Mandatory/Optional

Mandatory

NOTE


l When adding the M3UA data, take the constraints on the RNC processing capability into consideration.For details, refer to 12.5.6 RNC Capability for M3UA.

l When adding the CS CN node, pay attention to 12.3.11 CN Node ID.

Figure 7-19 shows the parameter relationship in the addition of the M3UA link.




Issue 03 (2008-08-30)

Figure 7-19 Parameter relationship in the addition of the M3UA link




(Initial).l The physical layer data for IP transport is configured. For details, refer to 6.5.1.1 Adding




7-25

l The data at the data link layer for IP transport is configured. For details, refer to 6.5.1.2Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial,with PEUa).

Preparation

For the data to be negotiated and planned before you configure the Iu-CS control plane on theRNC (initial, over IP), refer to 3.2.5 Data Negotiated on the Iu-CS Interface (over IP).

Procedure

Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, run thiscommand repeatedly. The details are as follows:l Set Signalling link mode to CLIENT, and specify Local SCTP port No..

l Set Application type to M3UA.

Step 2 Run the ADD N7DPC command to add a DSP. To add more DSPs, run this command repeatedly.The details are as follows:l You are advised to set Signalling route mask to B0000.

l When you add a Media Gateway to be the DSP, set Adjacent flag to YES, and set DSPtype to IUCS-ALCAP. This configuration indicates that the DSP has the functionality oftransport network layer control plane on the Iu-CS interface.

l When you add an MSC server to be the DSP, set Adjacent flag to NO, and set DSP type toIUCS-RANAP. This configuration indicates that the DSP has the functionality of radionetwork layer control plane on the Iu-CS interface.


Step 3 Run the ADD M3DE command to add a destination M3UA entity. The details are as follows:l When Local entity type is set to M3UA_ASP, Destination entity type must be set to

M3UA_SGP, M3UA_SS7SP, or M3UA_SP. If Destination entity type is set toM3UA_SS7SP, the DSP that this destination M3UA entity corresponds to cannot be adjacentto the local RNC, that is, you must set Adjacent flag to NO when running the ADDN7DPC command to add that DSP.

l When Local entity type is set to M3UA_IPSP, Destination entity type must be set toM3UA_IPSP.

Step 4 Run the ADD M3LKS command to add an M3UA link set. Set the parameters as follows:l When Local entity type is set to M3UA_IPSP, Work mode of the M3UA link set must be

set to M3UA_IPSP.l When Local entity type is set to M3UA_ASP, Work mode of the M3UA link set must be

set to M3UA_IPSP if Destination entity type is set to M3UA_SP, or Work mode of theM3UA link set must be set to M3UA_ASP if the destination entity type is either of the othertwo values.




Issue 03 (2008-08-30)

l To enable load sharing between M3UA links, it is recommended that Signalling linkmask be set to B1111.

Step 5 Run the ADD M3RT command to add an M3UA route.

Step 6 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, run thiscommand repeatedly.


l Set Adjacent Node Type to IUCS.


Step 8 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID toCS_DOMAIN.

Step 9 Run the ADD CNNODE command to add a CN node. The details are as follows:

l Set CN domain ID to CS_DOMAIN.

l Set IU trans bearer type to IP_TRANS.

----End




Mandatory/Optional

Mandatory

NOTE



Prerequisite


Preparation




7-27











Procedure




----End

7.5.4 Adding User Plane Data on the Iu-CS Interface (Initial, overIP)

This describes how to add user plane data on the IP-based Iu-CS interface. The related activitiesare the addition of the port controller, IP path, and IP route.


Mandatory/Optional

Mandatory

NOTE

When adding IP paths, take the constraints on the RNC processing capability into consideration. For details,refer to 12.5.8 RNC Capability for IP Paths and IP Routes.

Figure 7-21 shows the parameter relationship in the addition of the port controller on the IP-based Iu-CS interface.




Issue 03 (2008-08-30)


PrerequisiteThe control plane data of the IP-based Iu-CS interface is configured. For details, refer to 7.5.2Adding Control Plane Data on the Iu-CS Interface (Initial, over IP).

PreparationFor the data to be negotiated and planned before you configure the Iu-CS user plane on the RNC(initial, over IP), refer to 3.2.5 Data Negotiated on the Iu-CS Interface (over IP).

Procedure



Step 3 (Optional. Perform this step only when the Iu-CS interface uses layer 3 networking.) Run theADD IPRT command to add an IP route.

----End



7-29

8 Configuring Iu-PS Interface Data (Initial)

About This Chapter

The Iu-PS is the logical interface between the RNC and the PS domain. The RNC exchangesthe packet domain data with the CN through the Iu-PS interface. This topic describes how toadd the transport network layer data on the Iu-PS interface.

8.1 Example: Iu-PS Data in the RNC Initial Configuration ScriptThis describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS dataconsists of the physical layer data, TRM mapping, activity factor table, control plane data, anduser plane data.

8.2 Data Configuration Guidelines for the Iu-PS Interface (over ATM)Related information is required for performing data configuration on the ATM-based Iu-PSinterface. Such information refers to the protocol structure, links on the ATM-based Iu-PSinterface, and IPoA configuration principle on the user plane.

8.3 Adding Data on the Iu-PS Interface (Initial, over ATM)This describes how to add the transport network layer data on the ATM-based Iu-PS interface.

8.4 Data Configuration Guidelines for the Iu-PS Interface (over IP)Related information is required for performing data configuration on the IP-based Iu-PSinterface. Such information refers to the protocol structure and links on the IP-based Iu-PSinterface.

8.5 Adding Data on the Iu-PS Interface (Initial, over IP)This describes how to add the transport network layer data on the IP-based Iu-PS interface.

RNCRNC Initial Configuration Guide 8 Configuring Iu-PS Interface Data (Initial)


8-1

8.1 Example: Iu-PS Data in the RNC Initial ConfigurationScript

This describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS dataconsists of the physical layer data, TRM mapping, activity factor table, control plane data, anduser plane data.

//Take the script for the IP-based Iu-PS interface as an example.


//Set the attributes of an Ethernet port on a GOUa board.

SET ETHPORT: SRN=0, SN=18, BRDTYPE=GOU, PN=0, MTU=1500, AUTO=ENABLE;

//Add the IP address of an Ethernet port used to connect to the gateway.

ADD ETHIP: SRN=0, SN=18, PN=0, IPTYPE=PRIMARY, IPADDR="10.218.161.50", MASK="255.255.255.192";

//Add device IP addresses. Among these device IP addresses, two IP addresses are used for dual-homing of SCTP on the control plane, and the other IP address is used for the user plane.

ADD DEVIP: SRN=0, SN=18, IPADDR="10.218.161.100", MASK="255.255.255.192";ADD DEVIP: SRN=0, SN=18, IPADDR="10.218.161.150", MASK="255.255.255.192";ADD DEVIP: SRN=0, SN=18, IPADDR="10.218.161.200", MASK="255.255.255.192";


ADD TRMMAP: TMI=6, ITFT=IUPS, EFDSCP=46, AF4DSCP=38, AF3DSCP=30, AF2DSCP=18, AF1DSCP=10, BEDSCP=0;ADD TRMMAP: TMI=7, ITFT=IUPS, EFDSCP=46, AF4DSCP=38, AF3DSCP=30, AF2DSCP=18, AF1DSCP=10, BEDSCP=0;ADD TRMMAP: TMI=8, ITFT=IUPS, EFDSCP=46, AF4DSCP=38, AF3DSCP=30, AF2DSCP=18, AF1DSCP=10, BEDSCP=0;


ADD FACTORTABLE: FTI=2, REMARK="FOR IUPS";

//Add the Iu-PS control plane data.

//Add SCTP links.


ADD SCTPLNK: SRN=0, SN=4, SSN=2, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, DSCP=62,

8 Configuring Iu-PS Interface Data (Initial)RNC



Issue 03 (2008-08-30)

LOCPTNO=8012, LOCIPADDR1="10.218.161.100", LOCIPADDR2="10.218.161.150", PEERIPADDR1="10.20.18.5", PEERIPADDR2="10.20.18.69", PEERPORTNO=2905, LOGPORTFLAG=NO, RTOMIN=1000, RTOMAX=60000, RTOINIT=3000, RTOALPHA=12, RTOBETA=25, HBINTER=5000, MAXASSOCRETR=10, MAXPATHRETR=5, CHKSUMTX=NO, CHKSUMRX=NO, CHKSUMTYPE=CRC32, MTU=1500, VLANFlAG=DISABLE, CROSSIPFLAG=UNAVAILABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10;

//Add a destination signaling point over the Iu-PS interface.

ADD N7DPC: DPX=2, DPC=H'0008E2, SLSMASK=B0000, NEIGHBOR=YES, NAME="SGSN", DPCT=IUPS, STP=OFF, PROT=ITUT, BEARTYPE=M3UA;

//Add the M3UA data.

//Add a destination M3UA entity.

ADD M3DE: DENO=10, LENO=0, DPX=2, ENTITYT=M3UA_IPSP, RTCONTEXT=1, NAME="SGSN";

//Add an M3UA signaling link set.

ADD M3LKS: SIGLKSX=1, DENO=10, LNKSLSMASK=B1111, TRAMODE=M3UA_LOADSHARE_MOD, WKMODE=M3UA_IPSP, PDTMRVALUE=5, NAME="SGSN";

//Add an M3UA route.

ADD M3RT: DENO=10, SIGLKSX=1, PRIORITY=0, NAME="SGSN";

//Add M3UA signaling links.




ADD ADJNODE: ANI=2, NAME="SGSN", NODET=IUPS, SGSNFLG=YES, DPX=2, TRANST=IP;

//Set the mapping between the Iu-PS adjacent node and transmission resources.



ADD CNDOMAIN: CNDomainId=PS_DOMAIN, NMO=MODE2, DRXCycleLenCoef=6;

ADD CNNODE: CnOpIndex=0, CNId=1, CNDomainId=PS_DOMAIN, Dpx=2, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=IP_TRANS;

//Add the Iu-PS user plane data.


ADD PORTCTRLER: SRN=0, SN=18, PT=ETHER, CARRYEN=0, CTRLSN=2, CTRLSSN=2,



8-3

FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0;

//Add IP paths.

ADD IPPATH: ANI=2, PATHID=0, PATHT=HQ_RT, IPADDR="10.218.161.200", PEERIPADDR="10.20.18.132", PEERMASK="255.255.255.192", TXBW=1000000, RXBW=1000000, CARRYFLAG=NULL, FPMUX=YES, SUBFRLEN=127,MAXFRAMELEN=270, FPTIME=2, DSCP=46, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.20.18.132", PERIOD=5, CHECKCOUNT=5, ICMPPKGLEN=64;

ADD IPPATH: ANI=2, PATHID=1, PATHT=HQ_NRT, IPADDR="10.218.161.200", PEERIPADDR="10.20.18.133",PEERMASK="255.255.255.192", TXBW=1000000, RXBW=1000000, CARRYFLAG=NULL, FPMUX=YES, SUBFRLEN=127,MAXFRAMELEN=270, FPTIME=2, DSCP=18, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="10.20.18.133", PERIOD=5, CHECKCOUNT=5, ICMPPKGLEN=64;

//Add an IP route.

ADD IPRT: SRN=0, SN=18, DESTIP="10.20.18.0", MASK="255.255.255.0", NEXTHOP="10.218.161.1", PRIORITY=HIGH, REMARK="TO SGSN";

8.2 Data Configuration Guidelines for the Iu-PS Interface(over ATM)

Related information is required for performing data configuration on the ATM-based Iu-PSinterface. Such information refers to the protocol structure, links on the ATM-based Iu-PSinterface, and IPoA configuration principle on the user plane.

8.2.1 Protocol Structure for the Iu-PS Interface (over ATM)If ATM transport is applied to the Iu-PS interface, the sequence of adding Iu-PS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

8.2.2 Links on the Iu-PS Interface (over ATM)If ATM transport is applied to the Iu-PS interface, the Iu-PS links on the CN side are of twotypes: MTP3-b link and IPoA PVC.

8.2.3 IPoA Data Configuration on the Iu-PS User Plane (over ATM)On the ATM-based Iu-PS interface, the IPoA PVC is implemented on the user plane.

8.2.1 Protocol Structure for the Iu-PS Interface (over ATM)If ATM transport is applied to the Iu-PS interface, the sequence of adding Iu-PS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

Figure 8-1 shows the protocol stack for the Iu-PS interface.




Issue 03 (2008-08-30)

Figure 8-1 Protocol stack for the ATM-based Iu-PS interface

The transport network layer of the Iu-PS interface consists of the transport network layer userplane (area A) and the transport network layer user plane (area C).

Areas A and C share the physical layer and ATM layer. Therefore, all links in the two areas canbe carried on common physical links.

8.2.2 Links on the Iu-PS Interface (over ATM)If ATM transport is applied to the Iu-PS interface, the Iu-PS links on the CN side are of twotypes: MTP3-b link and IPoA PVC.

Links on the Iu-PS InterfaceFigure 8-2 shows the links on the Iu-PS interface.



8-5

Figure 8-2 Links on the Iu-PS interface (over ATM)

NOTE

The RINT shown in the preceding figure refers to the UOI_ATM board.

MTP3-b Link

MTP3-b links are contained in an MTP3-b link set. The numbers of MTP3-b links range from0 to 15.

An Iu-PS interface requires at least one MTP3-b link. It is recommended that more than oneMTP3-b link be planned.


An SAAL link of NNI type is carried on a PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the RNC and the peer.

IPoA PVC

The IPoA PVC on the Iu-PS interface is a PVC to the gateway of the SGSN.

An Iu-PS interface requires at least one IPoA PVC. It is recommended that more than one IPoAPVC be planned.

8.2.3 IPoA Data Configuration on the Iu-PS User Plane (over ATM)On the ATM-based Iu-PS interface, the IPoA PVC is implemented on the user plane.




Issue 03 (2008-08-30)

IPoA PVC on the Iu-PS User Plane

Figure 8-3 shows the IPoA PVC on the Iu-PS user plane.

Figure 8-3 IPoA PVC on the Iu-PS interface

NOTE

The RINT shown in the preceding figure refers to ATM interface boards UOI_ATM, AOUa, and AEUa.

IPoA Data on the Iu-PS User Plane

Table 8-1 describes the IPoA data to be configured on the user plane of the ATM-based Iu-PSinterface.

Table 8-1 IPoA data on the user plane of the ATM-based Iu-PS interface

Item Description

Local IP address of the IPoA PVC Device IP address on the ATM interface board ofthe RNC

Peer IP address of the IPoA PVC IP address of the gateway on the SGSN side

PVC between the interface boardcarrying the IPoA and the peer gatewayon the SGSN side

-

Route between the interface boardcarrying the IPoA and each destinationnetwork segment of the connectedSGSN

If the IP address of the interface board carrying theIPoA and the IP address of the SGSN are locatedon different subnets, routes to the destination IPaddress should be configured at the RNC.Destination IP address is the IP address of theSGSN, and Forward route address is the IPaddress of the gateway on the SGSN side.

CAUTIONOn the Iu-PS interface, a route to the network segment to which the IP address of the RNCinterface board belongs must be configured at the SGSN. The next hop is the gateway on theRNC side connected to the SGSN. Otherwise, PS services cannot be provided.



8-7

8.3 Adding Data on the Iu-PS Interface (Initial, over ATM)This describes how to add the transport network layer data on the ATM-based Iu-PS interface.


Mandatory/Optional

Mandatory. Perform this task once on each Iu-PS interface when the RNCconnects to multiple PS CN nodes over ATM.

NOTE

l This task configures only the transport network layer of the ATM-based Iu-PS interface.

l For the recommended interface boards and configuration of the physical layer for the ATM-based Iu-PS interface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.


PreparationFor the data to be negotiated and planned before you add data on the Iu-PS interface (initial,over ATM), refer to 3.2.6 Data Negotiated on the Iu-PS Interface (over ATM).

1. 8.3.1 Adding Physical Layer Data on the Interface (Initial, with UOI_ATM)This describes how to add physical layer data on an interface when the UOI_ATM servesas the interface board.


3. 8.3.3 Adding Control Plane Data on the Iu-PS Interface (Initial, over ATM)This describes how to add control plane data on the ATM-based Iu-PS interface. The relatedactivities are the addition of the SAAL links, Destination Signaling Point (DSP), MTP3-bsignaling link, adjacent node, and CN node.


5. 8.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, over ATM)This describes how to add user plane data on the ATM-based Iu-PS interface. The relatedactivities are the addition of the port controller, the setting of the device IP address, and theaddition of the IPoA PVC, IP path, and IP route.

8.3.1 Adding Physical Layer Data on the Interface (Initial, withUOI_ATM)

This describes how to add physical layer data on an interface when the UOI_ATM serves as theinterface board.




Issue 03 (2008-08-30)


Mandatory/Optional

Optional. Perform this task only when the UOI_ATM serves as the interface board.


Preparation

For the data to be negotiated and planned before you add the physical layer data on the interface(initial, with UOI_ATM), refer to 3.2 Data Negotiated Between RNC and Other NetworkElements. Prepare the related data for the interface as required.

Procedure

(Optional. Perform this step only when the planned data is inconsistent with the default data inthe database.) Run the SET OPT command to set the parameters of the optical ports on theUOI_ATM board.

----End



Mandatory/Optional

Mandatory

NOTE



Prerequisite


Preparation

For the data to be negotiated and planned before you add ATM traffic resources, refer to 3.2Data Negotiated Between RNC and Other Network Elements. Prepare the related data forthe interface as required.



8-9


----End

8.3.3 Adding Control Plane Data on the Iu-PS Interface (Initial, overATM)

This describes how to add control plane data on the ATM-based Iu-PS interface. The relatedactivities are the addition of the SAAL links, Destination Signaling Point (DSP), MTP3-bsignaling link, adjacent node, and CN node.


Mandatory/Optional

Mandatory

NOTE



l When adding the PS CN node, pay attention to 12.3.11 CN Node ID.





Issue 03 (2008-08-30)





(Initial).l The physical layer data for ATM transport is configured. For details, refer to 6.3.1 Adding



PreparationFor the data to be negotiated and planned before you configure the Iu-PS control plane on theRNC (initial, over ATM), refer to 3.2.6 Data Negotiated on the Iu-PS Interface (overATM).



8-11

Procedure


Step 2 Run the ADD N7DPC command to add a DSP. To add more DSPs, run this command repeatedly.The details are as follows:

l You are advised to set Signalling route mask to B0000.

l Set DSP type to IUPS.


Step 3 Run the ADD MTP3BLKS command to add an MTP3-b signaling link set. To enable loadsharing between the signaling links, it is recommended that Signalling link mask be set toB1111.




l Set Adjacent Node Type to IUPS.


Step 7 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID toPS_DOMAIN.

Step 8 Run the ADD CNNODE command to add a CN node. The details are as follows:

l Set CN domain ID to PS_DOMAIN.

l Set IU trans bearer type to ATM_TRANS.

----End







Issue 03 (2008-08-30)

Mandatory/Optional

Mandatory

NOTE















Procedure




----End



8-13

8.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, overATM)

This describes how to add user plane data on the ATM-based Iu-PS interface. The relatedactivities are the addition of the port controller, the setting of the device IP address, and theaddition of the IPoA PVC, IP path, and IP route.


Mandatory/Optional

Mandatory

NOTE


Figure 8-6 shows the parameter relationship in the addition of the IP path and IP route on theATM-based Iu-PS interface.

Figure 8-6 Parameter relationship in the addition of the IP path and IP route on the ATM-basedIu-PS interface

Prerequisite

The control plane data of the ATM-based Iu-PS interface is configured. For details, refer to 8.3.3Adding Control Plane Data on the Iu-PS Interface (Initial, over ATM).

Preparation

For the data to be negotiated and planned before you configure the Iu-PS user plane on the RNC(initial, over ATM), refer to 3.2.6 Data Negotiated on the Iu-PS Interface (over ATM).

Procedure

Step 1 Run the ADD PORTCTRLER command to specify a TRM SPUa controlling subsystem for aspecific port. Set Interface type to NCOPT.




Issue 03 (2008-08-30)

Step 2 Run the ADD DEVIP command to add the device IP address to the interface board that carriesthe user plane data.

Step 3 Run the ADD IPOAPVC command to add an IPoA PVC. The details are as follows:l Set Interface type to NCOPT.

l Set Peer type to OTHER.


CAUTIONl When the IP path is carried on the IPoA PVC, the bandwidth of the IP path cannot be higher

than the physical bandwidth of the IPoA PVC.l Only one Local IP address can correspond to one Peer IP address. In addition, only one

IP path can exist between one pair of local and peer IP addresses.

Step 5 (Optional. Perform this step only when the Iu-PS interface uses layer 3 networking.) Run theADD IPRT command to add an IP route.

----End

8.4 Data Configuration Guidelines for the Iu-PS Interface(over IP)

Related information is required for performing data configuration on the IP-based Iu-PSinterface. Such information refers to the protocol structure and links on the IP-based Iu-PSinterface.

8.4.1 Protocol Structure for the Iu-PS Interface (over IP)If IP transport is applied to the Iu-PS interface, the sequence of adding Iu-PS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

8.4.2 Links on the Iu-PS Interface (over IP)The links on the IP-based Iu-PS interface appear on the CN as two types: M3UA link and IPpath.

8.4.1 Protocol Structure for the Iu-PS Interface (over IP)If IP transport is applied to the Iu-PS interface, the sequence of adding Iu-PS interface datashould be consistent with the protocol structure, that is, from the lowest layer to the highest layerand from the control plane to the user plane.

Figure 8-7 shows the protocol stack for the Iu-PS interface.



8-15

Figure 8-7 Protocol stack for the IP-based Iu-PS interface

The transport network layer of the Iu-PS interface consists of the transport network layer userplane (area A) and the transport network layer user plane (area C).

Areas A and C share the physical layer and data link layer. Therefore, all links in the two areascan be carried on common physical links.

8.4.2 Links on the Iu-PS Interface (over IP)The links on the IP-based Iu-PS interface appear on the CN as two types: M3UA link and IPpath.

Links on the Iu-PS InterfaceFigure 8-8 shows the links on the IP-based Iu-PS interface.




Issue 03 (2008-08-30)

Figure 8-8 Links on the Iu-PS interface (over IP)

NOTE

The RINT shown in the preceding figure refers to IP interface boards GOUa, FG2a, and UOI_IP.

M3UA Link


An Iu-PS interface requires at least one M3UA link. It is recommended that more than oneM3UA link be planned.


IP Path

An IP path is a group of connections to the adjacent node. The path IDs range from 0 to 65535.

An Iu-PS interface has at least one IP path. It is recommended that more than one IP path beplanned.

8.5 Adding Data on the Iu-PS Interface (Initial, over IP)This describes how to add the transport network layer data on the IP-based Iu-PS interface.




8-17

Mandatory/Optional

Mandatory. Perform this task once on each Iu-PS interface when the RNCconnects to multiple PS CN nodes over IP.

NOTE

l This task configures only the transport network layer of the IP-based Iu-PS interface.

l For the recommended interface boards and configuration of the physical layer for the IP-based Iu-PSinterface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.

Prerequisitel You are licensed to apply IP transport to the Iu interface.

l The OSP data of the RNC is configured. For details, refer to 4.4 Adding OSP to the RNC(Initial).

Preparation

For the data to be negotiated and planned before you add data on the Iu-PS interface (initial,over IP), refer to 3.2.7 Data Negotiated on the Iu-PS Interface (over IP).


2. 8.5.2 Adding Control Plane Data on the Iu-PS Interface (Initial, over IP)This describes how to add control plane data on the IP-based Iu-PS interface. The relatedactivities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UAlink set, adjacent node, CN domain data, and CN node data.


4. 8.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, over IP)This describes how to add user plane data on the IP-based Iu-PS interface. The relatedactivities are the addition of the port controller, IP path, and IP route.



NOTE





Issue 03 (2008-08-30)

8.5.2 Adding Control Plane Data on the Iu-PS Interface (Initial, overIP)

This describes how to add control plane data on the IP-based Iu-PS interface. The relatedactivities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UA link set,adjacent node, CN domain data, and CN node data.


Mandatory/Optional

Mandatory

NOTE



l When adding the PS CN node, pay attention to 12.3.11 CN Node ID.

Figure 8-9 shows the parameter relationship in the addition of the M3UA link on the IP-basedIu-PS interface.




8-19




(Initial).l The physical layer data for IP transport is configured. For details, refer to 6.5.1.1 Adding



PreparationFor the data to be negotiated and planned before you configure the Iu-PS control plane on theRNC (initial, over IP), refer to 3.2.7 Data Negotiated on the Iu-PS Interface (over IP).

ProcedureStep 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, run this

command repeatedly. The details are as follows:l Set Signalling link mode to CLIENT, and specify Local SCTP port No..l Set Application type to M3UA.



l Set DSP type to IUPS.

Step 3 Run the ADD M3DE command to add a destination M3UA entity.l When Local entity type is set to M3UA_ASP, Destination entity type must be set to

M3UA_SGP, M3UA_SS7SP, or M3UA_SP. If Destination entity type is set to




Issue 03 (2008-08-30)

M3UA_SS7SP, the DSP that this destination M3UA entity corresponds to cannot be adjacentto the local RNC, that is, you must set Adjacent flag to NO when running the ADDN7DPC command to add that DSP.


Step 4 Run the ADD M3LKS command to add an M3UA link set. The details are as follows:l When Local entity type is set to M3UA_IPSP, Work mode of the M3UA link set must be



l To enable load sharing between M3UA links, it is recommended that Signalling linkmask be set to B1111.


Step 6 Run the ADD M3LNK command to add an M3UA link.

Step 7 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriateTRM mapping and activity factor tables for users of different priorities. The details are asfollows:l Set Adjacent Node Type to IUPS.


Step 8 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID toPS_DOMAIN.

Step 9 Run the ADD CNNODE command to add a CN node. The details are as follows:l Set CN domain ID to PS_DOMAIN.

l Set IU trans bearer type to IP_TRANS.

----End




Mandatory/Optional

Mandatory

NOTE





8-21

Prerequisite


Preparation












Procedure




----End

8.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, overIP)

This describes how to add user plane data on the IP-based Iu-PS interface. The related activitiesare the addition of the port controller, IP path, and IP route.





Issue 03 (2008-08-30)

Mandatory/Optional

Mandatory

NOTE


Figure 8-11 shows the parameter relationship in the addition of the port controller on the IP-based Iu-PS interface.


Prerequisite

The control plane data of the IP-based Iu-PS interface is configured. For details, refer to 8.5.2Adding Control Plane Data on the Iu-PS Interface (Initial, over IP).

Preparation

For the data to be negotiated and planned before you configure the Iu-PS user plane on the RNC(initial, over IP), refer to 3.2.7 Data Negotiated on the Iu-PS Interface (over IP).

Procedure

Step 1 Run the ADD PORTCTRLER command to specify a TRM SPUa controlling subsystem for aspecific port.


CAUTIONOnly one Local IP address can correspond to one Peer IP address. In addition, only one IPpath can exist between one pair of local and peer IP addresses.



8-23

Step 3 (Optional. Perform this step only when the Iu-PS interface uses layer 3 networking.) Run theADD IPRT command to add an IP route.

----End




Issue 03 (2008-08-30)

9 Configuring Iur Interface Data (Initial)

About This Chapter

An Iur interface is a logical interface between RNCs. This topic describes how to add thetransport network layer data on the Iur interface.

9.1 Example: Iur Data in the RNC Initial Configuration ScriptThis describes an example of Iur data in the RNC initial configuration script. The Iur data consistsof the physical layer data, ATM traffic resources, TRM mapping, activity factor table, controlplane data, and user plane data.

9.2 Data Configuration Guidelines for the Iur Interface (over ATM)Related information is required for performing data configuration on the ATM-based Iurinterface. Such information refers to the protocol structure, links on the ATM-based Iur interface,and configuration of paths for static relocation routes reallocation.

9.3 Adding Data on the Iur Interface (Initial, over ATM)This describes how to add transport network layer data on the ATM-based Iur interface.

9.4 Data Configuration Guidelines for the Iur Interface (over IP)Related information is required for performing data configuration on the IP-based Iur interface.Such information refers to the protocol structure, links on the IP-based Iur interface, andconfiguration of paths for static SRNS relocation.

9.5 Adding Data on the Iur Interface (Initial, over IP)This describes how to add transport network layer data on the IP-based Iur interface.

RNCRNC Initial Configuration Guide 9 Configuring Iur Interface Data (Initial)


9-1

9.1 Example: Iur Data in the RNC Initial ConfigurationScript

This describes an example of Iur data in the RNC initial configuration script. The Iur data consistsof the physical layer data, ATM traffic resources, TRM mapping, activity factor table, controlplane data, and user plane data.

//Take the script for the ATM-based Iur interface as an example.


//Set the attributes of all the optical ports on the ATM-based UOIa board in slot 24 of subrack0.

SET OPT:SRN=0, SN=24, BT=UOI_ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16BYTE, J0TXVALUE="SBS HuaWei 155", J0RXT=16BYTE, J0RXVALUE="SBS HuaWei 155", J1TXT=16BYTE, J1TXVALUE="SBS HuaWei 155", J1RXT=16BYTE, J1RXVALUE="SBS HuaWei 155";



//For the ATM traffic record on the user plane, the record index is 200, the service type is CBR,and the peak cell rate is 5,000 cell/s.

ADD ATMTRF: TRFX=190, ST=CBR, UT=CELL/S, PCR=530, CDVT=1024, REMARK="IUR CONTROL PLANE";ADD ATMTRF: TRFX=200, ST=CBR, UT=CELL/S, PCR=5000, CDVT=1024, REMARK="IUR USER PLANE";




ADD FACTORTABLE: FTI=3, REMARK="FOR IUR";

//Add the Iur control plane data.

//Add SAAL links.


ADD SAALLNK: SRN=0, SN=2, SSN=0, SAALLNKN=101, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=102, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI,

9 Configuring Iur Interface Data (Initial)RNC



Issue 03 (2008-08-30)

MPS=MPS_NEUTRAL, CCTMR=200, POLLTMR=100, IDLETMR=500, RSPTMR=5000, KEEPTMR=100, COMTMR1=2, COMTMR2=30, COMTMR3=10, SRECTMR=60, INHTMR=1500, MAXNRP=0, MAXCC=4, MAXPD=500, STATLEN=67, N1=1000, WINDOWSIZE=100;



//Add a destination signaling point of the RNC.

ADD N7DPC: DPX=3, DPC=H'0008B5, SLSMASK=B0000, NEIGHBOR=YES, NAME="NRNC1", DPCT=IUR, STP=OFF, PROT=ITUT, BEARTYPE=MTP3B;

//Add a neighboring RNC.

ADD NRNC: NRncId=201, SHOTRIG=CS_SHO_SWTICH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWTICH-1, HHOTRIG=ON, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, Dpx=3, RncProtclVer=R6, StateIndTMR=20, SuppIurCch=NO, HhoRelocProcSwitch=DL_DCCH_SWITCH-1&IUR_TRG_SWITCH-1, TnlBearerType=ATM_TRANS, DSCRInd=FALSE, IurHsdpaSuppInd=OFF, IurHsupaSuppInd=OFF;


ADD MTP3BLKS: SIGLKSX=2, DPX=3, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-RNC1";

ADD MTP3BRT: DPX=3, SIGLKSX=2, PRIORITY=0, NAME="TO-RNC1";






ADD ADJNODE: ANI=3, NAME="TO-RNC1", NODET=IUR, DPX=3, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS2;



9-3

//Set the mapping between the Iur adjacent node and transmission resources.


//Add the Iur user plane data.



//Add AAL2 paths.




//Add an AAL2 route.


9.2 Data Configuration Guidelines for the Iur Interface(over ATM)

Related information is required for performing data configuration on the ATM-based Iurinterface. Such information refers to the protocol structure, links on the ATM-based Iur interface,and configuration of paths for static relocation routes reallocation.

9.2.1 Protocol Structure for the Iur Interface (over ATM)If ATM transport is applied to the Iur interface, the sequence of adding Iur interface data shouldbe consistent with the protocol structure, that is, from the lowest layer to the highest layer andfrom the control plane to the user plane.

9.2.2 Links on the Iur Interface (over ATM)If ATM transport is applied to the Iur interface, the Iur links on the CN side are of two types:MTP3-b link and AAL2 path.




Issue 03 (2008-08-30)

9.2.3 Configuration Guidelines for Static Relocation Routes over IurThe IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites toconfiguration of IP routes on the Iur interface are that the IP paths between the local RNC andthe SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC)and the Drift RNC (DRNC) are configured.

9.2.1 Protocol Structure for the Iur Interface (over ATM)If ATM transport is applied to the Iur interface, the sequence of adding Iur interface data shouldbe consistent with the protocol structure, that is, from the lowest layer to the highest layer andfrom the control plane to the user plane.

Figure 9-1 shows the protocol stack for the Iur interface.

Figure 9-1 Protocol stack for the ATM-based Iur interface

The transport network layer of the ATM-based Iur interface consists of the following areas:l Transport network layer user plane (area A)l Transport network layer control plane (area B)l Transport network layer user plane (area C)

9.2.2 Links on the Iur Interface (over ATM)If ATM transport is applied to the Iur interface, the Iur links on the CN side are of two types:MTP3-b link and AAL2 path.

Links on the Iur InterfaceFigure 9-2 shows the links on the ATM-based Iur interface.



9-5

Figure 9-2 Links on the Iur interface (over ATM)

NOTE


MTP3-b LinkMTP3-b links are contained in an MTP3-b link set. The numbers of MTP3-b links range from0 to 15.

The configuration of MTP3-b links depends on the networking between the RNC and theneighboring RNC. See specifics as follows:

l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at leastone MTP3-b link. It is recommended that more than one MTP3-b link be planned.

l If the RNC is connected to the neighboring RNC through a Signaling Transfer Point (STP),no MTP3-b link is required.


An SAAL link of NNI type is carried on an ATM PVC. The PVC identifier (VPI/VCI) and otherattributes of the PVC must be negotiated between the RNC and the peer.

AAL2 PathAn AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to4294967295.

An Iub interface has at least one AAL2 path. It is recommended that more than one AAL2 pathbe planned.




Issue 03 (2008-08-30)

An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVCattributes must be negotiated between the RNC and the peer.

9.2.3 Configuration Guidelines for Static Relocation Routes overIur

The IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites toconfiguration of IP routes on the Iur interface are that the IP paths between the local RNC andthe SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC)and the Drift RNC (DRNC) are configured.

Figure 9-3 shows the configuration of IP routes on the Iur interface. The IP routes configuredin multiple subsystems are similar.

Figure 9-3 IP route configuration on the Iur interface

NOTE

The RINT shown in the preceding figure refers to IP interface boards PEUa, POUa, UOI_IP, FG2a, andGOUa.

9.3 Adding Data on the Iur Interface (Initial, over ATM)This describes how to add transport network layer data on the ATM-based Iur interface.


Mandatory/Optional

Mandatory. Perform this task once on each Iur interface when the RNC connectsto multiple neighboring RNCs over ATM.



9-7

NOTE

l An RNC can be configured with a maximum of 15 neighboring RNCs.

l This task configures only the transport network layer of the Iur interface.

l For the recommended interface boards and configuration of the physical layer for the ATM-based Iurinterface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.


PreparationFor the data to be negotiated and planned before you add data on the Iur interface (initial, overATM), refer to 3.2.8 Data Negotiated on the Iur Interface (over ATM).



3. 9.3.3 Adding Control Plane Data on the Iur Interface (Initial, over ATM)This describes how to add control plane data on the ATM-based Iur interface. The relatedactivities are the addition of the SAAL links, Destination Signaling Point (DSP), basic dataof the neighboring RNC, MTP3-b data, and adjacent node.


5. 9.3.5 Adding User Plane Data on the Iur Interface (Initial, over ATM)This describes how to add user plane data on the ATM-based Iur interface. The relatedactivities are the addition of the port controller, AAL2 path, and transmission resourcegroup.

6. 9.3.6 Adding a Path for Static SRNS Relocation (Initial)To reduce the bandwidth occupied by the Iur interface and the transport delay on the userplane, you can perform static SRNC relocation from the DRNC. This topic describes howto add a path for static relocation routes reallocation.


NOTE





Issue 03 (2008-08-30)



Mandatory/Optional

Mandatory

NOTE






----End

9.3.3 Adding Control Plane Data on the Iur Interface (Initial, overATM)

This describes how to add control plane data on the ATM-based Iur interface. The relatedactivities are the addition of the SAAL links, Destination Signaling Point (DSP), basic data ofthe neighboring RNC, MTP3-b data, and adjacent node.


Mandatory/Optional

Mandatory



9-9

NOTE





Prerequisitel The physical layer data for ATM transport is configured. For details, refer to 9.3.1 Adding



PreparationFor the data to be planned and negotiated before you configure the Iur control plane on the RNC(initial, over ATM), refer to 3.2.8 Data Negotiated on the Iur Interface (over ATM).

Procedure





Issue 03 (2008-08-30)


l Set DSP type to IUR.

l Set DSP bear type to MTP3B.


Step 3 Run the ADD NRNC command to add the basic data of the neighboring RNC. Set the parametersas follows:l Set Iur Interface Existing Indication to TRUE.

l Set IUR trans bearer type to ATM_TRANS.

Step 4 Run the ADD MTP3BLKS command to add an MTP3-b signaling link set. To enable loadsharing between the signaling links, it is recommended that Signalling link mask be set toB1111.



CAUTIONThe SAAL link specified by the Signalling Link Code parameter must be not in use and beconfigured on the SPUa subsystem that is specified by the Subrack No. and Subsystem No.parameters. That SAAL link should be of NNI type.

Step 7 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriateTRM mapping and activity factor tables for users of different priorities. The details are asfollows:l Set Adjacent Node Type to IUR.


----End





9-11


Mandatory/Optional

Mandatory

NOTE



Prerequisite


Preparation












Procedure






Issue 03 (2008-08-30)


----End

9.3.5 Adding User Plane Data on the Iur Interface (Initial, overATM)

This describes how to add user plane data on the ATM-based Iur interface. The related activitiesare the addition of the port controller, AAL2 path, and transmission resource group.


Mandatory/Optional

Mandatory

NOTE

The AAL2 path capability of the Iur adjacent node must comply with those stipulated in 12.5.7 RNCCapability for AAL2 Paths and AAL2 Routes.

Figure 9-5 shows the parameter relationship in the addition of the port controller on the ATM-based interface.


Figure 9-6 shows the parameter relationship in the addition of the AAL2 path.



9-13

Figure 9-6 Parameter relationship in the addition of the AAL2 path in the ATM-based interface

Prerequisite

The control plane data of the ATM-based Iur interface is configured. For details, refer to 9.3.3Adding Control Plane Data on the Iur Interface (Initial, over ATM).

Preparation

For the data to be planned and negotiated before you configure the Iur user plane on the RNC(initial, over ATM), refer to 3.2.8 Data Negotiated on the Iur Interface (over ATM).

Procedure



----End

9.3.6 Adding a Path for Static SRNS Relocation (Initial)To reduce the bandwidth occupied by the Iur interface and the transport delay on the user plane,you can perform static SRNC relocation from the DRNC. This topic describes how to add a pathfor static relocation routes reallocation.





Issue 03 (2008-08-30)

Mandatory/Optional

Optional. Perform this task only when the setting for static relocation routesreallocation is required.

PrerequisiteThe IP path on the Iu-PS user plane is configured. For details, refer to 8.3.5 Adding User PlaneData on the Iu-PS Interface (Initial, over ATM) or 8.5.4 Adding User Plane Data on theIu-PS Interface (Initial, over IP).

PreparationFor the data to be negotiated and planned before you add a path for static relocation routesreallocation (initial), refer to 3.2.6 Data Negotiated on the Iu-PS Interface (over ATM) and3.2.7 Data Negotiated on the Iu-PS Interface (over IP).

Procedure

Step 1 Run the ADD IPRT command to add an IP route towards the DRNC. The details are as follows:l Set Subrack No. and Slot No. to the numbers of the subrack and slot that accommodate the

Iu-PS interface board carrying IP paths.l Set Destination IP address to the user plane IP address of the DRNC.

l Set Next hop IP address to the service IP address of the SGSN.

Step 2 Run the ADD IPPATH command to add an IP path for static SRNS relocation. The details areas follows:l Set Adjacent Node ID to the adjacent node ID of the SGSN.

l Set Local IP Address to the user plane IP address of the SRNC.

l Set Peer IP Address to the user plane IP address of the DRNC.

CAUTIONFor the IP interface boards configured with Iu-PS user plane data, it is recommended that eachboard be configured with an IP route and IP path towards the DRNC. If multiple destination IPnetwork segments exist at the DRNC, it is also recommended that each board be configured withIP routes and IP paths towards each of the network segments. This facilitates load sharingbetween Iu-PS and Iur interfaces.

----End

9.4 Data Configuration Guidelines for the Iur Interface(over IP)

Related information is required for performing data configuration on the IP-based Iur interface.Such information refers to the protocol structure, links on the IP-based Iur interface, andconfiguration of paths for static SRNS relocation.



9-15

9.4.1 Protocol Stack on the Iur Interface (over IP)If IP transport is applied to the Iur interface, the sequence of adding Iur interface data should beconsistent with the protocol structure, that is, from the lowest layer to the highest layer and fromthe control plane to the user plane.

9.4.2 Links on the Iur Interface (over IP)The Iur interface (over IP) has two types of links, that is, the M3UA link and IP Path.

9.4.3 Configuration Guidelines for Static Relocation Routes over IurThe IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites toconfiguration of IP routes on the Iur interface are that the IP paths between the local RNC andthe SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC)and the Drift RNC (DRNC) are configured.

9.4.1 Protocol Stack on the Iur Interface (over IP)If IP transport is applied to the Iur interface, the sequence of adding Iur interface data should beconsistent with the protocol structure, that is, from the lowest layer to the highest layer and fromthe control plane to the user plane.

Figure 9-7 shows the protocol stack for the Iur interface.

Figure 9-7 Protocol stack for IP transport on the Iur interface

The transport network layer of the IP-based Iur interface consists of the transport network layeruser plane (area A) and the transport network layer user plane (area C).

9.4.2 Links on the Iur Interface (over IP)The Iur interface (over IP) has two types of links, that is, the M3UA link and IP Path.




Issue 03 (2008-08-30)

Links on the Iur Interface

Figure 9-8 shows the links on the Iur interface.

Figure 9-8 Links on the Iur Interface (over IP)

NOTE

The RINT shown in the preceding figure refers to IP interface boards GOUa, FG2a, and PEUa.

M3UA Link


The configuration of M3UA links depends on the networking between the RNC and theneighboring RNC. See specifics as follows:

l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at leastone M3UA link. It is recommended that more than one M3UA link be planned.

l If the RNC is connected to the neighboring RNC through a Signaling Transfer Point (STP),no M3UA link is required.


IP Path

An IP path is a group of connections to the adjacent node. The path IDs range from 0 to 65535.

An Iur interface has at least one IP path. It is recommended that more than one IP path be planned.



9-17

9.4.3 Configuration Guidelines for Static Relocation Routes overIur

The IP routes on the Iur interface are used to forward the PS data during Serving Radio NetworkSubsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from thelocal RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites toconfiguration of IP routes on the Iur interface are that the IP paths between the local RNC andthe SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC)and the Drift RNC (DRNC) are configured.

Figure 9-9 shows the configuration of IP routes on the Iur interface. The IP routes configuredin multiple subsystems are similar.

Figure 9-9 IP route configuration on the Iur interface

NOTE

The RINT shown in the preceding figure refers to IP interface boards PEUa, POUa, UOI_IP, FG2a, andGOUa.

9.5 Adding Data on the Iur Interface (Initial, over IP)This describes how to add transport network layer data on the IP-based Iur interface.


Mandatory/Optional

Mandatory . Perform this task once on each Iur interface when the RNC connectsto multiple neighboring RNCs over IP.

NOTE

l An RNC can be configured with a maximum of 15 neighboring RNCs.

l This task configures only the transport network layer of the Iur interface.

l For the recommended interface boards and configuration of the physical layer for the IP-based Iurinterface, refer to 12.6.1 Interface Boards Applicable to Terrestrial Interfaces.




Issue 03 (2008-08-30)

Prerequisite


Preparation

For the data to be negotiated and planned before you add data to the Iur interface (initial, overIP), refer to 3.2.9 Data Negotiated on the Iur Interface (over IP).


2. 9.5.2 Adding Control Plane Data on the Iur Interface (Initial, over IP)This describes how to add control plane data on the IP-based Iur interface. The relatedactivities are the addition of the SCTP links, Destination Signaling Point (DSP), basic dataof the neighboring RNC, M3UA data, and adjacent node.


4. 9.5.4 Adding User Plane Data on the Iur Interface (Initial, over IP)This describes how to add user plane data on the IP-based Iur interface. The related activitiesare the addition of the port controller, IP path, IP route, and transmission resource group.

5. 9.5.5 Adding a Path for Static SRNS Relocation (Initial)To reduce the bandwidth occupied by the Iur interface and the transport delay on the userplane, you can perform static SRNC relocation from the DRNC. This topic describes howto add a path for static relocation routes reallocation.



NOTE


9.5.2 Adding Control Plane Data on the Iur Interface (Initial, overIP)

This describes how to add control plane data on the IP-based Iur interface. The related activitiesare the addition of the SCTP links, Destination Signaling Point (DSP), basic data of theneighboring RNC, M3UA data, and adjacent node.



9-19


Mandatory/Optional

Mandatory

NOTE



Figure 9-10 shows the parameter relationship in the addition of the M3UA link.


Prerequisitel The physical layer data for IP transport is configured. For details, refer to 6.5.1.1 Adding





Issue 03 (2008-08-30)


PreparationFor the data to be planned and negotiated before you configure the Iur control plane on the RNC(initial, over IP), refer to 3.2.9 Data Negotiated on the Iur Interface (over IP).

Procedure

Step 1 Run the ADD SCTPLNK command to add an SCTP link. To add more SCTP links, run thiscommand repeatedly. Set Application type to M3UA.

Step 2 Run the ADD N7DPC command to add a DSP. To add more DSPs, run this command repeatedly.The details are as follows:l You are advised to set Signaling route mask to B0000.

l Set DSP type to IUR.

l Set DSP bear type to M3UA.


Step 3 Run the ADD NRNC command to add the basic data of the neighboring RNC. Set the parametersas follows:l Set Iur Interface Existing Indication to TRUE.

l Set IUR trans bearer type to IP_TRANS.

Step 4 Run the ADD M3DE command to add a destination M3UA entity.l When Local entity type is set to M3UA_ASP, Destination entity type must be set to

M3UA_SGP, M3UA_SS7SP, or M3UA_SP. If Destination entity type is set toM3UA_SS7SP, the DSP that this destination M3UA entity corresponds to cannot be adjacentto the local RNC, that is, you must set Adjacent flag to NO when running the ADDN7DPC command to add that DSP.


Step 5 Run the ADD M3LKS command to add an M3UA link set. Set the parameters as follows:l When Local entity type is set to M3UA_IPSP, Work mode of the M3UA link set must be



l To enable load sharing between M3UA links, it is recommended that Signaling link maskbe set to B1111.



9-21


Step 7 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, run thiscommand repeatedly.

Step 8 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriateTRM mapping table and activity factor tables for users of different priorities. The details are asfollows:l Set Adjacent node type to IUR.

l Set Transport type to IP.

----End




Mandatory/Optional

Mandatory

NOTE














Issue 03 (2008-08-30)





Procedure




----End

9.5.4 Adding User Plane Data on the Iur Interface (Initial, over IP)This describes how to add user plane data on the IP-based Iur interface. The related activitiesare the addition of the port controller, IP path, IP route, and transmission resource group.


Mandatory/Optional

Mandatory

NOTE

The IP path capability of the Iur adjacent node must comply with those stipulated in 12.5.8 RNC Capabilityfor IP Paths and IP Routes.

Figure 9-11 shows the parameter relationship in the addition of the port controller on the IP-based Iur interface.




9-23

PrerequisiteThe control plane data of the IP-based Iur interface is configured. For details, refer to 9.5.2Adding Control Plane Data on the Iur Interface (Initial, over IP).

PreparationFor the data to be planned and negotiated before you configure the Iur user plane on the RNC(initial, over IP), refer to 3.2.9 Data Negotiated on the Iur Interface (over IP).

Procedure



Step 3 (Optional. Perform this step only when the Iur interface uses layer 3 networking.) Run the ADDIPRT command to add an IP route.

----End

9.5.5 Adding a Path for Static SRNS Relocation (Initial)To reduce the bandwidth occupied by the Iur interface and the transport delay on the user plane,you can perform static SRNC relocation from the DRNC. This topic describes how to add a pathfor static relocation routes reallocation.


Mandatory/Optional

Optional. Perform this task only when the setting for static relocation routesreallocation is required.

PrerequisiteThe IP path on the Iu-PS user plane is configured. For details, refer to 8.3.5 Adding User PlaneData on the Iu-PS Interface (Initial, over ATM) or 8.5.4 Adding User Plane Data on theIu-PS Interface (Initial, over IP).

PreparationFor the data to be negotiated and planned before you add a path for static relocation routesreallocation (initial), refer to 3.2.6 Data Negotiated on the Iu-PS Interface (over ATM) and3.2.7 Data Negotiated on the Iu-PS Interface (over IP).

Procedure

Step 1 Run the ADD IPRT command to add an IP route towards the DRNC. The details are as follows:l Set Subrack No. and Slot No. to the numbers of the subrack and slot that accommodate the

Iu-PS interface board carrying IP paths.l Set Destination IP address to the user plane IP address of the DRNC.




Issue 03 (2008-08-30)

l Set Next hop IP address to the service IP address of the SGSN.

Step 2 Run the ADD IPPATH command to add an IP path for static SRNS relocation. The details areas follows:l Set Adjacent Node ID to the adjacent node ID of the SGSN.

l Set Local IP Address to the user plane IP address of the SRNC.

l Set Peer IP Address to the user plane IP address of the DRNC.

CAUTIONFor the IP interface boards configured with Iu-PS user plane data, it is recommended that eachboard be configured with an IP route and IP path towards the DRNC. If multiple destination IPnetwork segments exist at the DRNC, it is also recommended that each board be configured withIP routes and IP paths towards each of the network segments. This facilitates load sharingbetween Iu-PS and Iur interfaces.

----End



9-25

10 Configuring Iu-BC Interface Data(Initial)

About This Chapter

An Iu-BC interface is a logical interface between the RNC and CBC. This topic describes howto add the transport network layer data on the Iu-BC interface.


Mandatory/Optional

Optional. Perform this task only when the RNC is connected to the CBC.

NOTE

This task configures only the transport network layer of the Iu-BC interface. To enable the RNC to providethe Cell Broadcast Service (CBS), you also need to configure CBS data. For details, refer to the RANFeature Description.

Prerequisite

The OSP data of the RNC is configured. For details, refer to 4.4 Adding OSP to the RNC(Initial).

Preparation

For the data to be negotiated and planned before you add data on the Iu-BC interface, refer to3.2.10 Data Negotiated on the Iu-BC Interface.

1. 10.1 Example: Iu-BC Data in the RNC Initial Configuration ScriptThis describes an example of Iu-BC data in the RNC initial configuration script. The Iu-BC data consists of the physical layer data, ATM traffic records, IPoA data, and SABPdata.

2. 10.2 Data Configuration Guidelines for the Iu-BC InterfaceRelated information is required for performing data configuration on the Iu-BS interface.Such information refers to the protocol structure, networking, links on the Iu-BC interface,and the IPoA configuration principle.

RNCRNC Initial Configuration Guide 10 Configuring Iu-BC Interface Data (Initial)


10-1

3. 10.3 Adding Physical Layer Data (Initial, over ATM)This describes how to add physical layer data on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iurinterfaces. It is a subtask of data configuration on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iurinterfaces. The types of interface boards should be determined before the relatedconfiguration.

4. 10.4 Adding ATM Traffic Resources (Initial)This describes how to add ATM traffic records at the RNC based on the traffic models ofSAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directlyused through their indexes during the configuration of these links.

5. 10.5 Adding IPoA Data on the Iu-BC Interface (Initial)This describes how to set up the IPoA PVC for connections to the SGSN and CBC.

6. 10.6 Adding SABP Data (Initial)This describes how to add the SABP data, that is, to add the radio network layer data of theCBS.

10 Configuring Iu-BC Interface Data (Initial)RNC



Issue 03 (2008-08-30)

10.1 Example: Iu-BC Data in the RNC Initial ConfigurationScript

This describes an example of Iu-BC data in the RNC initial configuration script. The Iu-BC dataconsists of the physical layer data, ATM traffic records, IPoA data, and SABP data.

//Take the script for the ATM-based Iu-BC interface as an example.



SET OPT: SRN=0, SN=26, BT=UOI_ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=64byte, J0TXVALUE="SBS 155", J0RXT=64byte, J0RXVALUE="SBS 155", J1TXT=64byte, J1TXVALUE="SBS 155", J1RXT=64byte, J1RXVALUE="SBS 155";


ADD ATMTRF: TRFX=210, ST=NRTVBR, UT=KBIT/S, PCR=15000, SCR=10000, MBS=1000, CDVT=1024, REMARK="FOR IUBC";

//Add the IPoA data to the Iu-BC interface.

//Add the device IP address.


//Add an IPoA PVC.

ADD IPOAPVC: IPADDR="172.22.21.50", PEERIPADDR="172.22.21.254", CARRYT=NCOPT, CARRYNCOPTN=0, CARRYVPI=14, CARRYVCI=126, TXTRFX=210, RXTRFX=210, PEERT=IUPS;

//Add an IP route.

ADD IPRT: SRN=0, SN=26, DESTIP="172.22.5.0", MASK="255.255.255.0", NEXTHOP="172.22.21.254", PRIORITY=HIGH, REMARK="IP ROUTE TO CBC";

//Add SABP data.

ADD CBSADDR: SRN=0, SN=4, SSN=3, CnOpIndex=0,RNCIPADDR="172.22.21.50", CBCIPADDR="172.22.5.0", CBCMASK="255.255.0.0";

10.2 Data Configuration Guidelines for the Iu-BC InterfaceRelated information is required for performing data configuration on the Iu-BS interface. Suchinformation refers to the protocol structure, networking, links on the Iu-BC interface, and theIPoA configuration principle.

10.2.1 Protocol Structure for the Iu-BC Interface



10-3

The Iu-BC interface is the logical interface between the RNC and the CBC. The sequence ofadding Iu-BC interface data should be consistent with the protocol structure, that is, from thelowest layer to the highest layer.

10.2.2 Networking on the Iu-BC InterfaceThe RNC connects to the CBC through an SGSN.

10.2.3 Links on the Iu-BC InterfaceThe Iu-BC interface has only one type of link, that is, IPoA PVC.

10.2.4 IPoA Data Configuration on the Iu-BC InterfaceThe IPoA PVC configured on the Iu-BC interface enables the RNC to indirectly connect to theCBC.

10.2.1 Protocol Structure for the Iu-BC InterfaceThe Iu-BC interface is the logical interface between the RNC and the CBC. The sequence ofadding Iu-BC interface data should be consistent with the protocol structure, that is, from thelowest layer to the highest layer.

Figure 10-1 shows the protocol stack of the Iu-BC interface.

Figure 10-1 Protocol stack for the Iu-BC interface

10.2.2 Networking on the Iu-BC InterfaceThe RNC connects to the CBC through an SGSN.

The connection of the RNC and CBC through an SGSN can make full use of the physicaltransport resources on the Iu-PS interface. Figure 10-2 shows the networking on the Iu-BCinterface.




Issue 03 (2008-08-30)

Figure 10-2 RNC-CBC networking through an SGSN

10.2.3 Links on the Iu-BC InterfaceThe Iu-BC interface has only one type of link, that is, IPoA PVC.

Links on the Iu-BC Interface

Figure 10-3 shows the links on the Iu-BC interface.

Figure 10-3 Links on the Iu-BC interface

NOTE


IPoA PVC

Because the CBC connects to the RNC through an SGSN, an IPoA PVC must be configured onthe Iu-BC interface for connecting the RNC and SGSN gateway. In this case, the data on the Iu-BC interface is transmitted to the SGSN through the IPoA PVC and then routed to the CBC bythe SGSN.



10-5

10.2.4 IPoA Data Configuration on the Iu-BC InterfaceThe IPoA PVC configured on the Iu-BC interface enables the RNC to indirectly connect to theCBC.

IPoA PVC for the Iu-BC Interface

On the Iu-BC interface, the RNC connects to the CBC through an SGSN, as shown in Figure10-4.

Figure 10-4 IPoA configuration on the Iu-BC interface networked through an SGSN

NOTE

The RINT shown in the preceding figure refers to ATM interface boards AEUa, AOUa, and UOI_ATM.

IPoA Data on the Iu-BC Interface

Table 10-1 describes the IPoA data to be configured on the Iu-BC interface.

Table 10-1 IPoA data on the Iu-BC interface

Item Description

Local IP address of the IPoA PVC Device IP address on the ATM interfaceboard of the RNC

Peer IP address of the IPoA PVC IP address of the gateway on the SGSN side

PVC between the interface board carrying theIPoA and the peer gateway on the SGSN side

-

Route between the interface board carryingthe IPoA and each destination networksegment of the connected SGSN

If the IP address of the interface boardcarrying the IPoA and the destination IPaddresses are located on different subnets,routes to the destination IP addresses must beconfigured on the RNC.

10.3 Adding Physical Layer Data (Initial, over ATM)This describes how to add physical layer data on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iur interfaces.It is a subtask of data configuration on the Iub, Iu-CS, Iu-PS, Iu-BC, and Iur interfaces. Thetypes of interface boards should be determined before the related configuration.




Issue 03 (2008-08-30)

NOTE


10.4 Adding ATM Traffic Resources (Initial)This describes how to add ATM traffic records at the RNC based on the traffic models of SAALlinks, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used throughtheir indexes during the configuration of these links.


Mandatory/Optional

Mandatory

NOTE






----End

10.5 Adding IPoA Data on the Iu-BC Interface (Initial)This describes how to set up the IPoA PVC for connections to the SGSN and CBC.


Mandatory/Optional

Mandatory

NOTE

For details about guidelines for IPoA configuration on the Iu-BC interface, refer to 10.2.4 IPoA DataConfiguration on the Iu-BC Interface.



10-7

Figure 10-5 shows the parameter relationship in the addition of the IPoA data on the Iu-BCinterface.

Figure 10-5 Parameter relationship in the addition of the IPoA PVC

Prerequisitel The data of the physical link or port that carries the IPoA PVC is configured, and the link

or port is not in use. For details, refer to 10.3 Adding Physical Layer Data (Initial, overATM).

l The ATM traffic resources of the IPoA PVC are configured. For details, refer to 10.4Adding ATM Traffic Resources (Initial).

PreparationFor the data to be negotiated and planned before you add the IPoA data on the Iu-BC interface(initial), refer to 3.2.10 Data Negotiated on the Iu-BC Interface.

Procedure

Step 1 Run the ADD DEVIP command to add the device IP address of the board.

NOTE

Each interface board can be configured with a maximum of five device IP addresses.




Issue 03 (2008-08-30)

Step 2 Run the ADD IPOAPVC command to establish an IPoA PVC between the RNC and the SGSNgateway. The details are as follows:l Set Peer type to IUPS.

l Set IP Address to the device IP address of the board.

l Set Peer IP Address to the IP address of the SGSN gateway.

Step 3 (Optional. Perform this step only when the Iu-BC interface uses layer 3 networking.) Run theADD IPRT command to add a route from the RNC to the CBC.

----End

10.6 Adding SABP Data (Initial)This describes how to add the SABP data, that is, to add the radio network layer data of the CBS.


Mandatory/Optional

Mandatory

Figure 10-6 shows the parameter relationship in the addition of SABP data.

Figure 10-6 Parameter relationship in the addition of the SABP data

Prerequisite

The IPoA data is configured for the Iu-BC interface. For details, refer to 10.5 Adding IPoAData on the Iu-BC Interface (Initial).



10-9

PreparationFor the data to be negotiated and planned before you add SABP data (initial), refer to 3.2.10Data Negotiated on the Iu-BC Interface.

ProcedureRun the ADD CBSADDR command to specify the SPUa subsystem for SABP and set the CBCIP address.

----End




Issue 03 (2008-08-30)

11 Configuring Cell Data (Initial)

About This Chapter

This describes how to configure cell data of the radio network layer. The related activities arethe quick setup of cells, the addition of inter-frequency neighboring cell relationships, intra-frequency neighboring cell relationships, and inter-RAT neighboring cell relationships, andswitching all subracks to the online mode after the cell data configuration is complete.

1. 11.2 Quickly Setting Up a Cell (Initial)This describes how to quickly set up a cell on the RNC. You need to manually configuresome of the parameters while keeping default settings for other parameters.

2. 11.3 Adding an Intra-Frequency Neighboring Cell (Initial)This describes how to add an intra-frequency neighboring cell to a cell. The two cells maybelong to either one RNC or two RNCs.

3. 11.4 Adding an Inter-Frequency Neighboring Cell (Initial)This describes how to add an inter-frequency neighboring cell to a cell. The two cells maybelong to either one RNC or two RNCs.

4. 11.5 Adding a Neighboring GSM Cell (Initial)This describes how to add a neighboring GSM cell to a cell.

5. 11.6 Setting the RNC to Online Mode (Initial)This describes how to set all the subracks to online mode at the end of the initialconfiguration.

RNCRNC Initial Configuration Guide 11 Configuring Cell Data (Initial)


11-1

11.1 Example: Cell Data in the RNC Initial ConfigurationScript

This describes cell data in the RNC initial configuration script. The cell data includes the dataof local cells, logical cells, intra-frequency neighboring cells, inter-frequency neighboring cells,and neighboring GSM cells. This example describes only how to quickly add local cells andlogical cells.

//Set up cells quickly.

//Add the basic data of local cells.

ADD LOCELL: NODEBNAME="NodeB1", LOCELL=0;ADD LOCELL: NODEBNAME="NodeB1", LOCELL=1;ADD LOCELL: NODEBNAME="NodeB1", LOCELL=2;

//Set the priorities of different services in cells.

ADD SPG: SpgId=2, PriorityServiceForR99RT=1, PriorityServiceForR99NRT=2, PriorityServiceForHSPA=2, PriorityServiceForExtRab=3;

//Add logical cells quickly.




//Activate the logical cells.

ACT CELL: CELLID=0;ACT CELL: CELLID=1;ACT CELL: CELLID=2;

//Set the RNC to online mode. The initial configuration ends.

SET ONLINE:;

11 Configuring Cell Data (Initial)RNC



Issue 03 (2008-08-30)

11.2 Quickly Setting Up a Cell (Initial)This describes how to quickly set up a cell on the RNC. You need to manually configure someof the parameters while keeping default settings for other parameters.


Mandatory/Optional

Optional. Perform this task when both of the following requirements are met:– A cell needs to be set up.

– Parameters of the cell are in standard configuration.

NOTE

l The cell data and the data of the NodeB that carries the local cell are processed by the same SPUasubsystem.

l For the configuration of new cells when the RAN sharing function is used, refer to 12.12.3 Operator-Based Configuration of Cells and NodeBs.

l For the cell-related concepts, refer to 12.11 Cell-Related Concepts.

Figure 11-1 shows the parameter relationship in the quick addition of a cell.

Figure 11-1 Parameter relationship in the quick addition of a cell



11-3

NOTE

The parameter Routing area code of the ADD QUICKCELLSETUP command is optional. When theNon Access Stratum (NAS) data of the PS domain is configured on the RNC through the ADDCNDOMAIN command, the parameter Routing area code must be configured for the cell.

Prerequisitel The transport layer data of the RNC is configured.

l The data of the areas that the cell is located in is configured as global location data of theRNC. For details, refer to 4.5 Adding RNC Global Location Data (Initial).

l The equipment data of the RNC is configured. For details, refer to 5 Configuring RNCEquipment Data.

PreparationFor the data to be planned and negotiated before you quickly set up a cell on the RNC (initial),refer to 3.3 Cell Data on the RNC.

Procedure

Step 1 Run the ADD LOCELL command to add basic information of a local cell.

Step 2 Run the ADD SPG command to set the priorities of different service types in the cell.

Step 3 Run the ADD QUICKCELLSETUP command to quickly set up a cell.

Step 4 Run the ACT CELL command to activate the cell.

----End

11.3 Adding an Intra-Frequency Neighboring Cell (Initial)This describes how to add an intra-frequency neighboring cell to a cell. The two cells may belongto either one RNC or two RNCs.


Mandatory/Optional

Optional. Perform this task when intra-frequency neighboring cells are plannedfor a cell in the local RNC.

CAUTIONEach intra-frequency neighboring cell of a cell must have a unique primary scrambling code.




Issue 03 (2008-08-30)

NOTE

l In the sense of neighboring relations, the concept of local cell is relative to the concept of neighboringcell. The concept of local RNC is relative to the concept of neighboring RNC.

l In the RNC, the cell neighboring relationship is unidirectional. Therefore, after adding cell B as anintra-frequency neighboring cell of cell A, check whether cell A should also be an intra-frequencyneighboring cell of cell B. If so, configure cell A as an intra-frequency neighboring cell of cell B onthe RNC that controls cell B.

l Neighboring RNCs may be from vendors other than Huawei.

l When you add the intra-frequency neighboring cell, adhere to the principles described in 12.5.11Specifications for Neighboring Cells.

Figure 11-2 shows the parameter relationship in the addition of an intra-frequency neighboringcell that belongs to the local RNC.

Figure 11-2 Parameter relationship in the addition of an intra-frequency neighboring cell thatbelongs to the local RNC

Figure 11-3 shows the parameter relationship in the addition of an intra-frequency neighboringcell that belongs to a neighboring RNC.

Figure 11-3 Parameter relationship in the addition of an intra-frequency neighboring cell thatbelongs to a neighboring RNC



11-5

Prerequisite

When the intra-frequency neighboring cell belongs to a neighboring RNC, the data of theneighboring RNC and that of the Iur interface are configured. For details, refer to 9 ConfiguringIur Interface Data (Initial).

Preparation

For the data to be negotiated and planned before you add an intra-frequency neighboring cell(initial), refer to 3.3 Cell Data on the RNC.

Procedurel If the target cell and the local cell belong to the same RNC, perform the following step:

1. Run the ADD INTRAFREQNCELL command to set the target cell as an intra-frequency neighboring cell of the local cell.

l If the target cell and the local cell belong to different RNCs, perform the following steps:

1. Run the ADD NRNCCELL command to add the basic information of the target cell.

2. If the URA information is not configured for the neighboring RNC, run the ADDNRNCURA command to add the information.

CAUTIONThe URA ID in the ADD NRNCURA command must have been added through theADD URA command.

3. Run the ADD INTRAFREQNCELL command to set the target cell as an intra-frequency neighboring cell of the local cell.

----End

11.4 Adding an Inter-Frequency Neighboring Cell (Initial)This describes how to add an inter-frequency neighboring cell to a cell. The two cells may belongto either one RNC or two RNCs.


Mandatory/Optional

Optional. Perform this task when inter-frequency neighboring cells are plannedfor a cell in the local RNC.

CAUTIONEach inter-frequency neighboring cell of a cell must have a unique combination of uplinkfrequency, downlink frequency, and scrambling code.




Issue 03 (2008-08-30)

NOTE

l In the sense of neighboring relations, the concept of local cell is relative to the concept of neighboringcell. The concept of local RNC is relative to the concept of neighboring RNC.

l In the RNC, the cell neighboring relationship is unidirectional. Therefore, after adding cell B as aninter-frequency neighboring cell of cell A, check whether cell A should also be an inter-frequencyneighboring cell of cell B. If so, configure cell A as an inter-frequency neighboring cell of cell B onthe RNC that controls cell B.

l Neighboring RNCs may be from vendors other than Huawei.

l When you add the inter-frequency neighboring cell, adhere to the principles described in 12.5.11Specifications for Neighboring Cells.

Figure 11-4 shows the parameter relationship in the addition of an inter-frequency neighboringcell that belongs to the local RNC.

Figure 11-4 Parameter relationship in the addition of an inter-frequency neighboring cell thatbelongs to the local RNC

Figure 11-5 shows the parameter relationship in the addition of an inter-frequency neighboringcell that belongs to a neighboring RNC.

Figure 11-5 Parameter relationship in the addition of an inter-frequency neighboring cell thatbelongs to a neighboring RNC



11-7

Prerequisite

When the inter-frequency neighboring cell belongs to a neighboring RNC, the data of theneighboring RNC and that of the Iur interface are configured. For details, refer to 9 ConfiguringIur Interface Data (Initial).

Preparation

For the data to be negotiated and planned before you add an inter-frequency neighboring cell(initial), refer to 3.3 Cell Data on the RNC.

Procedurel If the target cell and the local cell belong to the same RNC, perform the following step:

1. Run the ADD INTERFREQNCELL command to set the target cell as an inter-frequency neighboring cell of the local cell.

l If the target cell and the local cell belong to different RNCs, perform the following steps:

1. Run the ADD NRNCCELL command to add the basic information of the target cell.

2. If the homing URA information is not configured for the neighboring RNC thatcontrols the target cell, run the ADD NRNCURA command to add the information.

CAUTIONThe URA ID in the ADD NRNCURA command must have been added through theADD URA command.

3. Run the ADD INTERFREQNCELL command to set the target cell as an inter-frequency neighboring cell of the local cell.

----End

11.5 Adding a Neighboring GSM Cell (Initial)This describes how to add a neighboring GSM cell to a cell.


Mandatory/Optional

Optional. Perform this task when neighboring GSM cells are planned for a cell inthe local RNC.

CAUTIONEach neighboring GSM cell of a cell must have a unique combination of BS color code, networkcolor code, frequency number, and frequency band.




Issue 03 (2008-08-30)

NOTE

l In the sense of neighboring relations, the concept of local cell is relative to the concept of neighboringcell.

l In the RNC, the cell neighboring relationship is unidirectional. Therefore, after the configuration bythis task, GSM cell B becomes a neighboring cell of WCDMA cell A in the local RNC, but WCDMAcell A is not automatically configured as a neighboring cell of GSM cell B.

l When you add the neighboring GSM cell, adhere to the principles describes in 12.5.11 Specificationsfor Neighboring Cells.

Figure 11-6 shows the parameter relationship in the addition of the neighboring GSM cell.

Figure 11-6 Parameter relationship in the addition of the neighboring GSM cell

Prerequisite

Each cell is configured on the RNC in a WCDMA network or Base Station Controller (BSC) ina GSM network. All data is complete and correct.

Preparation

For the data to be negotiated and planned before you add a neighboring GSM cell (initial), referto 3.3 Cell Data on the RNC.

Procedure

Step 1 Run the ADD GSMCELL command to add the basic information of the GSM cell.

Step 2 Run the ADD GSMNCELL command to set the GSM cell as a neighboring cell of the WCDMAcell.

----End

11.6 Setting the RNC to Online Mode (Initial)This describes how to set all the subracks to online mode at the end of the initial configuration.


Mandatory/Optional

Mandatory



11-9

NOTE

This is the last task of initial configuration.

PrerequisiteNone.

PreparationNone.

ProcedureRun the SET ONLINE command to set the RNC to online mode.

----End




Issue 03 (2008-08-30)

12 Related Information for RNC InitialConfiguration

About This Chapter

This reference part covers the concepts, principles, rules, and conventions that should beunderstood before data configuration.

12.1 Types of RNC Optical PortsThis describes the types of RNC optical ports.

12.2 Introduction to RAN Time SynchronizationThe time synchronization function enables the time at the nodes of the RAN system to besynchronized.

12.3 Numbering Schemes of the RNCThis describes the schemes of numbering the RNC hardware components and applications onthe transport network layer and radio network layer.

12.4 Area IdentifiersThis describes the principles of and suggestions for numbering PLMNs, LAs, SAs, RAs, andURAs.

12.5 External Specifications for the RNCThis describes the capability specifications of the RNC for boards, links, and cells. Theconfiguration of interface data and cell data must conform to the external specifications for theRNC.

12.6 Physical Layer Data Configuration GuidelinesThis describes the guidelines for configuring physical layer data.

12.7 ATM TransportATM transport has four modes: UNI, fractional ATM, timeslot cross connection, and IMA.

12.8 PVC Parameters of the RNCDuring the setting of PVC attributes of the ATM layer at Huawei BSC6810, the associatedparameters of the ATM Adaptation Layer (AAL) are also configured. Thus, you need to takethe associated AAL parameters into consideration when setting the PVC attributes.

12.9 AAL2 Configuration Guidelines

RNCRNC Initial Configuration Guide 12 Related Information for RNC Initial Configuration


12-1

This describes AAL2 configuration guidelines in terms of the working principles of AAL2 paths,destination boards of AAL2 paths, and AAL2 routes.

12.10 MTP3-b/M3UA Configuration GuidelinesThis describes the MTP3-b/M3UA configuration guidelines.

12.11 Cell-Related ConceptsThis describes the cell-related concepts, such as sector, carrier, cell, local cell and logical cell,cell ID, logical cell model, and areas of logical cells.

12.12 Configurations of RAN SharingThis describes the configuration principles of the RAN sharing. The data refers to the operator-based license control, operator-based transport network layer configuration of the Iub interface,operator-based cell and NodeB configuration, and operator-based Iu interface configuration.

12.13 TRM Configuration GuidelinesThe Transmission Resource Management (TRM) of the RNC manages the transmissionresources of the interfaces, thus improving efficiency of resource utilization and guaranteeingthe Quality of Service (QoS). The RNC determines which type of bearer should be used forcurrent services, depending on certain conditions. These conditions are the service type, thepreset mapping between service types and transmission resources, and the utilization of thetransmission resources.

12.14 Activity Factor Configuration GuidelinesConfiguration of activity factors improves resource efficiency.

12 Related Information for RNC Initial ConfigurationRNC



Issue 03 (2008-08-30)

12.1 Types of RNC Optical PortsThis describes the types of RNC optical ports.

Table 12-1 describes the types of RNC optical ports.

Table 12-1 Types of RNC optical ports

Type Board TransportMode

Applicable Interfaces

Channelizedoptical port

AOUa ATM Iub, Iu-CS, Iu-PS, Iur and Iu-BC

POUa IP Iub, Iu-CS, and Iur

Unchannelizedoptical port

UOIa ATM/IP Iub, Iu-CS, Iu-PS, Iur, and Iu-BC

GE optical port GOUa IP Iub, Iu-CS, Iu-PS, Iur, and Iu-BC

12.2 Introduction to RAN Time SynchronizationThe time synchronization function enables the time at the nodes of the RAN system to besynchronized.

Synchronization is critical for identifying faults. For example, if the E1 link between the RNCand the NodeB is broken, time synchronization between the RNC and the NodeB ensures thatthe same fault reported to the M2000 by the RNC and the NodeB is at the same time point.

The Simple Network Time Protocol (SNTP) is used to synchronize the time at the nodes ofHuawei RAN system. SNTP serves the time synchronization between a server and multipleclients. Therefore, an SNTP server must be configured in the RAN system. The SNTP serverbroadcasts time synchronization information to the SNTP clients.

Either the RNC or the M2000 can serve as an SNTP server. You can configure an SNTP serverby taking the field condition into consideration.

SNTP works on the basis of the Greenwich Mean Time (GMT). Therefore, when setting thetime at different nodes, you should set the time zone where the node is located and decide whetherto set the Daylight Saving Time (DST). If the DST is set, you need to configure the start timeand end time of the DST and the time offset.

12.3 Numbering Schemes of the RNCThis describes the schemes of numbering the RNC hardware components and applications onthe transport network layer and radio network layer.

12.3.1 RNC IDThe RNC ID is a 12-bit binary code, ranging from 0 to 4095.

12.3.2 RNC Subrack Number



12-3

This describes the principles of and suggestions for numbering RNC subracks.

12.3.3 ATM Traffic Record IndexThis describes the principles of and suggestions for numbering ATM traffic records.

12.3.4 RNC Transmission Resource Mapping Record IndexThis describes the principles of and suggestions for numbering RNC transmission resourcemapping records.

12.3.5 RNC Activity Factor Table IndexThis describes the principle of numbering RNC activity factor tables.

12.3.6 SAAL Link NumberThis describes the principles of and suggestions for numbering SAAL links.

12.3.7 SCTP Link NumberThis describes the principles of and suggestions for numbering SCTP links.

12.3.8 Adjacent Node IDThis describes the principles of and suggestions for numbering all adjacent nodes.

12.3.9 MTP3-b/M3UA DSP IndexThis describes the principles of and suggestions for numbering MTP3-b/M3UA DestinationSignaling Points (DSPs).

12.3.10 Signaling Link Set IndexThis describes the principles of and suggestions for numbering signaling link sets. The signalinglink set can be the MTP3-b signaling link set or the M3UA signaling link set.

12.3.11 CN Node IDThis describes the principles of and suggestions for numbering CN nodes.

12.3.12 Local Cell IDThis describes the principles of and suggestions for numbering local cells.

12.3.13 Logical Cell IDThis describes the principles of and suggestions for numbering logical cells.

12.3.14 Common Physical Channel IDThis describes the principles of and suggestions for numbering common physical channels.

12.3.15 Common Transport Channel IDThis describes the principles of and suggestions for numbering common transport channels.

12.3.16 GSM Cell IDThis describes the principles of numbering GSM cells.

12.3.17 NCP and CCP NumberThis describes the principle of numbering the NodeB Control Port (NCP) and CommunicationControl Ports (CCPs).

12.3.18 NRIThis describes the principles of setting a Network Resource Identifier (NRI). NRI uniquelyidentifies a CN node that serves a pool area.

12.3.1 RNC IDThe RNC ID is a 12-bit binary code, ranging from 0 to 4095.

The RNC ID uniquely identifies an RNC node within a PLMN. When being used with the PLMNID, the RNC ID can uniquely identify an RNC node worldwide. Being used either independently




Issue 03 (2008-08-30)

or jointly with the PLMN ID, the RNC ID can identify an RNC on the Iub, Iur, and Iu interfacesof the UTRAN.

12.3.2 RNC Subrack NumberThis describes the principles of and suggestions for numbering RNC subracks.

PrinciplesA cabinet of Huawei BSC6810, which supports a maximum of six subracks, has two types ofsubrack: RSS and RBS. Each subrack is uniquely but not necessarily consecutively numberedwithin an RNC.

l The mandatory RSS subrack is the switching subrack whose number is always set to 0.

l The optional RBS subrack is the business subrack whose number is set within the range 1to 5. The numbering of RBS subracks depends on the traffic requirement.

Figure 12-1 shows the numbered subracks.

Figure 12-1 Numbered subracks

SuggestionsIt is recommended that the RBS subracks are numbered in ascending order in the directions fromleft to right and from bottom to top, seen from the front.

12.3.3 ATM Traffic Record IndexThis describes the principles of and suggestions for numbering ATM traffic records.

PrinciplesATM traffic record indexes are used by the upper layers of the ATM layer. The upper layers ofthe ATM layer consist of the SAAL link, AAL2 path, and IPoA PVC.

Each ATM traffic record is uniquely numbered within an RNC. That is, an index uniquelyidentifies an ATM traffic record within the RNC. An ATM traffic record index is set within the



12-5

range 100 to 1999 (1 to 99 are reserved for internal use). The numbering is not necessarilyconsecutive.

Suggestions

For clear numbering and easy identification, the following suggestions are provided:

Specify different ranges of SCTP link numbers based on different interfaces. For example,specify the range of 100 to 199 for ATM traffic record indexes over the Iub interface, the rangeof 200 to 299 for ATM traffic record indexes over the Iur interface, the range of 300 to 399 forATM traffic record indexes over the Iu-CS interface, and the range of 400 to 499 for ATM trafficrecord indexes over the Iu-PS interface.

Specify different ranges of ATM traffic record indexes based on the different links over aninterface. For example, on the Iub interface, specify the range of 100 to 149 for ATM trafficrecord indexes of SAAL links, the range of 150 to 179 for ATM traffic record indexes of AAL2paths, and the range of 180 to 189 for ATM traffic record indexes of IPoA PVCs.

NOTE

The numbering of ATM traffic record indexes is closely related to the planning of network traffic. Forexample, some networks may have detailed planning for various links, which thus requires a large quantityof ATM traffic record indexes. In this case, the allocated ranges in the previous suggestions may need tobe extended.

12.3.4 RNC Transmission Resource Mapping Record IndexThis describes the principles of and suggestions for numbering RNC transmission resourcemapping records.

Principles

A Huawei BSC6810 supports a maximum of 32 transmission resource mapping records. Thenumbers of such records range from 0 to 63.

Suggestions

For clear numbering and easy identification, the following suggestions are provided:

l Within the range of 0 to 63, number the transmission resource mapping records for the Iub,Iur, and Iu-CS interfaces and those for the Iu-PS interface from two ends. For example,number the transmission resource mapping records for the Iub, Iur, and Iu-CS interfacesfrom 0 up and number those for the Iu-PS interface from 63 down.

l For the transmission resource mapping records over the Iub, Iur, and Iu-CS interfaces, it isrecommended that different ranges be allocated to the transmission resource mappingrecords depending on the interfaces. For example, specify the range of 0 to 9 fortransmission resource mapping records over Iub, the range of 10 to 19 for records over Iur,and the range of 10 to 29 for records over Iu-CS.

12.3.5 RNC Activity Factor Table IndexThis describes the principle of numbering RNC activity factor tables.




Issue 03 (2008-08-30)

PrinciplesA Huawei BSC6810 supports a maximum of 32 activity factor tables. The numbers of suchtables range from 0 to 31.

12.3.6 SAAL Link NumberThis describes the principles of and suggestions for numbering SAAL links.

PrinciplesIn a Huawei BSC6810, the numbers of SAAL links range from 0 to 174.

The SAAL links are numbered within an SPUa subsystem. The numbering for SAAL links ofthe same type is not necessarily consecutive. For example, specify an SAAL UNI link on oneIub interface to 10 and number an SAAL UNI link another Iub interface to 12.

SuggestionsFor clear numbering and easy identification, the following suggestions are provided:

Number the SAAL UNI and SAAL NNI links from 0 up or 174 down. For example, number theSAAL UNI links from 0 up and SAAL NNI links from 174 down. The SAAL NNI links areeasy to identify because there are a small number of SAAL NNI links.

l SAAL UNI linksIt is recommended that the SAAL UNI links of the same NodeB be numbered consecutively.For example, number the SAAL UNI links of NodeB 1 from 0 through 2 and those ofNodeB 2 from 3 through 5. If there are sufficient SAAL UNI links, it is recommended thatsome numbers be reserved for each NodeB. For example, number the SAAL UNI links ofNodeB 1 from 0 through 2 and those of NodeB 2 from 4 through 6. Therefore, when anSAAL UNI link is added to NodeB 1, the number 3 can be used.

l SAAL NNI linksIt is recommended that different ranges of numbers be allocated to the SAAL NNI linksdepending on the interfaces. For example, specify the range from 155 to 174 for SAALNNI links over Iu-CS, the range from 135 to 154 for SAAL NNI links over Iu-PS, and therange from 115 to 134 for SAAL NNI links over Iur.

12.3.7 SCTP Link NumberThis describes the principles of and suggestions for numbering SCTP links.

PrinciplesIn a Huawei BSC6810, the numbers of SCTP links range from 0 to 149.

The SCTP links are numbered within an SPUa subsystem. The numbering for SCTP links of thesame type is not necessarily consecutive. For example, specify an SCTP link on one Iub interfaceto the number 10 and an SCTP link on another Iub interface to the number 12.




12-7

Specify different ranges of SCTP link numbers based on different interfaces. For example,specify the range from 0 to 59 for SCTP links over Iub, the range from 60 to 89 for SCTP linksover Iur, the range from 90 to 119 for SCTP links over Iu-CS, and the range from 120 to 149for SCTP links over Iu-PS.


PrinciplesIn a Huawei BSC6810, the numbers of adjacent nodes range from 0 to 1999. Each adjacent nodeis uniquely but not necessarily consecutively numbered within an RNC. For example, set thenumber of an adjacent NodeB to 10 and that of the next adjacent node to 12.


Within the range of 0 to 1999, number the Iub adjacent nodes and the Iur and Iu adjacent nodesfrom the two ends. For example, number the Iub adjacent nodes from 0 up and number the Iurand Iu adjacent nodes from 1999 down.

For Iur and Iu adjacent nodes, it is recommended that different ranges be allocated to adjacentnode numbers depending on the interfaces. For example, specify the range of 1995 to 1999 foradjacent nodes over Iu-CS, the range of 1990 to 1994 for adjacent nodes over Iu-PS, and therange of 1985 to 1989 for adjacent nodes over Iur.


PrinciplesA Huawei BSC6810 supports a maximum of 119 DSPs, including the DSPs that are eitherdirectly or indirectly connected to the Originating Signaling Points (OSPs). The numbers of theMTP3-b or M3UA DSPs range from 0 to 118. Each DSP is uniquely but not necessarilyconsecutively numbered within an RNC. The number is the DSP index. For example, set thenumber of an MSC signaling point to 10 and that of the next MSC signaling point to 12.


Specify different ranges for DSPs depending on the DSP types. For example, specify the rangeof 0 to 59 for DSPs over Iu-CS, the range of 60 to 69 for DSPs over Iu-PS, the range of 70 to79 for DSPs over Iur, the range of 80 to 89 for DSPs of the STP type, and the range of 90 to 99for DSPs of the AAL2 switch type. There are three types of DSP over Iu-CS: IuCS,IuCS_RANAP, and IuCS_ALCAP.

12.3.10 Signaling Link Set IndexThis describes the principles of and suggestions for numbering signaling link sets. The signalinglink set can be the MTP3-b signaling link set or the M3UA signaling link set.




Issue 03 (2008-08-30)

Principles of Numbering MTP3-b Signaling Link SetsIn a Huawei BSC6810, the numbers of MTP3-b link sets range from 0 to 118. Each MTP3-bsignaling link set is uniquely but not necessarily consecutively numbered within an RNC. Thenumber is the signaling link set index. For example, set the number of an MTP3-b signaling linkset towards a neighboring MGW to 10 and the number of an MTP3-b signaling link set towardsanother neighboring MGW to 12.

Suggestions for Numbering MTP3-b Signaling Link SetsFor clear numbering and easy identification, the following suggestions are provided:

Specify different ranges for the signaling link sets that reach different DSPs. For example,specify the range of 0 to 59 for signaling link sets over Iu-CS, the range of 60 to 79 for signalinglink sets over Iu-PS, the range of 80 to 99 for signaling link sets over Iur, the range of 100 to109 for signaling link sets of the STP type, and the range of 110 to 118 for signaling link setsof the AAL2 switch type. There are three types of signaling link set over Iu-CS: IuCS,IuCS_RANAP, and IuCS_ALCAP.

Principles of Numbering M3UA Signaling Link SetsIn a Huawei BSC6810, the numbers of M3UA links range from 0 to 118. Each M3UA signalinglink set is uniquely but not necessarily consecutively numbered within an RNC. The number isthe signaling link set index. For example, set the number of an M3UA signaling link set towardsa neighboring MGW to 11 and the number of an M3UA signaling link set towards anotherneighboring MGW to 13.

Suggestions for Numbering M3UA Signaling Link SetsFor clear numbering and easy identification, the following suggestions are provided:

Specify different ranges for the signaling link sets that reach different DSPs. For example,specify the range of 0 to 59 for signaling link sets over Iu-CS, the range of 60 to 79 for signalinglink sets over Iu-PS, the range of 80 to 99 for signaling link sets over Iur, and the range of 100to 109 for signaling link sets of the STP type. There are three types of signaling link set over Iu-CS: IuCS, IuCS_RANAP, and IuCS_ALCAP.

12.3.11 CN Node IDThis describes the principles of and suggestions for numbering CN nodes.

PrinciplesWhen the Iu-Flex feature is enabled, a maximum of 32 CN nodes can be configured in each CNdomain, either CS domain or PS domain. Each CN node is uniquely but not necessarilyconsecutively numbered within an RNC. For example, set the number of an MSC to 0 and thatof the next MSC to 2.

NOTE

Though the number of a CN node can range from 0 to 4095, a maximum of 64 CN nodes can be configured.




12-9

Specify different ranges for CN nodes in different domains. For example, specify the range of0 to 31 for CN nodes in the CS domain and the range of 32 to 63 for CN nodes in the PS domain.

12.3.12 Local Cell IDThis describes the principles of and suggestions for numbering local cells.

PrinciplesThe local cell ID uniquely identifies a local cell in a NodeB. The ID of a local cell is requiredto be unique in a NodeB. In addition, for easy management, this ID should also be unique in theUTRAN.

A Huawei BSC6810 supports a maximum of 5,100 local cells. Each local cell is uniquely butnot necessarily consecutively numbered within the UTRAN. For example, set the number of acell to 0 and that of the next cell to 2.


Specify different ranges for local cells depending on the subracks. For example, specify therange of 0 to 899 for the local cells in subrack 0 (the RSS subrack) and the range of 900 to 1799for the local cells in subrack 1 (an RBS subrack).

12.3.13 Logical Cell IDThis describes the principles of and suggestions for numbering logical cells.

PrinciplesThe logical cell ID uniquely identifies a cell in a Radio Network Subsystem (RNS).

The logical cell ID is configured at the CRNC, which then sends the cell ID to the NodeB duringthe cell setup procedure. The correlations between logical cell IDs and local cell IDs areconfigured on the RNC.

A Huawei BSC6810 supports a maximum of 5,100 logical cells. Each logical cell is uniquelybut not necessarily consecutively numbered within an RNC. For example, set the number of acell to 0 and that of the next cell to 2.

NOTE

l During the setup of a cell, the RNC sends a CELL SETUP REQUEST message to the NodeB andinforms the NodeB of the local cell ID and the logical cell ID. The NodeB then acquires the correlationbetween the cell IDs. After the logical cell is set up, the cell is identified only through the logical cellID over the Iub interface.

l Though logical cell IDs range from 0 to 65535, a maximum of 5,100 logical cells can be configured.


Specify different ranges for logical cells depending on the subracks. For example, specify therange of 0 to 899 for the logical cells in subrack 0 (the RSS subrack) and the range of 900 to1799 for the logical cells in subrack 1 (an RBS subrack).




Issue 03 (2008-08-30)

12.3.14 Common Physical Channel IDThis describes the principles of and suggestions for numbering common physical channels.

PrinciplesThe ID of a common physical channel is used to identify the channel in a cell. Each commonphysical channel is uniquely numbered within a cell. The IDs of common physical channelsshould be planned before the channels are configured for the cell.

SuggestionsTable 12-2 shows the suggested numbering of common physical channels at the RNC.

Table 12-2 Suggested numbering of common physical channels

Number CommonPhysical Channel

Full Spelling Description

0 PSCH PrimarySynchronizationChannel

One cell has one and onlyone PSCH.

1 SSCH SecondarySynchronizationChannel

One cell has one and onlyone SSCH.

2 P-CPICH Primary Common PilotChannel

One cell has one and onlyone P-CPICH.

3 P-CCPCH Primary CommonControl PhysicalChannel

One cell has one and onlyone P-CCPCH.

4 PRACH 1

Physical RandomAccess Channel

One cell can beconfigured with one ortwo PRACHs. It isrecommended that onePRACH be configured.

5 PRACH 2

6 AICH 1 Acquisition IndicatorChannel

AICHs and PRACHshave a one-to-onemapping.7 AICH 2

8 S-CCPCH 1

Secondary CommonControl PhysicalChannel

One cell can beconfigured with one toeight S-CCPCHs. It isrecommended that oneS-CCPCH beconfigured.

9 S-CCPCH 2



12-11

Number CommonPhysical Channel


10 PICH Paging IndicatorChannel

One cell has one and onlyone PICH. The PICH hasa one-to-one relationshipwith the Paging Channel(PCH).

11 S-CCPCH 3 Secondary CommonControl PhysicalChannel

One cell can beconfigured with one toeight S-CCPCHs.12 S-CCPCH 4

12.3.15 Common Transport Channel IDThis describes the principles of and suggestions for numbering common transport channels.

PrinciplesThe ID of a common transport channel is used to identify the channel in a cell. Each commontransport channel is uniquely numbered within a cell. The IDs of common transport channelsshould be planned before the channels are configured for the cell.

SuggestionsTable 12-3 shows the suggested numbering of common transport channels.

Table 12-3 Suggested numbering of common transport channels

NumberCommonTransportChannel


0 BCH Broadcast Channel One cell has one and onlyone BCH. The BCH iscarried by the P-CCPCH.

1 RACH 1 (carried byPRACH 1) Random Access

ChannelOne PRACH carries oneRACH.2 RACH 2 (carried by

PRACH 2)

3 PCH (carried by S-CCPCH 1) Paging Channel

One cell has one and onlyone PCH. It is carried onthe S-CCPCH of theminimum ID.

4 FACH 1 (carried byS-CCPCH 1) Forward Access

Channel

One cell has at least oneFACH. One S-CCPCHcarries zero to twoFACHs.




Issue 03 (2008-08-30)

NumberCommonTransportChannel


5 FACH 2 (carried byS-CCPCH 1)







12.3.16 GSM Cell IDThis describes the principles of numbering GSM cells.

The ID of a GSM cell is used to identify the GSM cell. A Huawei BSC6810 supports a maximumof 9,600 GSM cells.

Each GSM cell is uniquely but not necessarily consecutively numbered within an RNC. Forexample, set the number of a GSM cell to 0 and that of the next GSM cell to 3.

12.3.17 NCP and CCP NumberThis describes the principle of numbering the NodeB Control Port (NCP) and CommunicationControl Ports (CCPs).

When configuring the NCP, you do not need to specify the port number.

When configuring CCPs, you need to specify Port number, because there are multiple CCPs.Each CCP has a unique number within a NodeB. Before configuration, the numbering of CCPsshould be negotiated between the RNC and the NodeB.

12.3.18 NRIThis describes the principles of setting a Network Resource Identifier (NRI). NRI uniquelyidentifies a CN node that serves a pool area.

The value range of NRI is variable. The value range depends on the scale of a CN domain andexpansion requirements. The maximum number of NRIs is 1,024. For example, a CS domainhas a maximum of 16 nodes. If Length of CS NRI in bits is set to 4, an NRI is represented byfour binary digits. Then, the value range of NRI is 0 to 15.



12-13

Because of the independence between the CS domain and the PS domain, the NRIs of the CSdomain are independent from those of the PS domain. The NullNRI, however, is different.

NullNRI is special. It is shared by the CS and PS domains. NullNRI occupies an NRI in eachdomain. For example, if NullNRI is 10, both the NullNRIs in the CS and PS domains are 10.

NOTE

You can use the SET IUFLEX command to set Length of NRI in bits and NullNRI.

12.4 Area IdentifiersThis describes the principles of and suggestions for numbering PLMNs, LAs, SAs, RAs, andURAs.

12.4.1 PLMN IDThis defines the PLMN ID, describes the components of the PLMN ID, and provides principlesof and suggestions for numbering PLMNs.

12.4.2 LA IdentifiersThe identifiers related to the Location Area (LA) consist of Location Area Code (LAC) andLocation Area Identification (LAI).

12.4.3 SA IdentifiersThe identifiers related to the Service Area (SA) consist of Service Area Code (SAC) and ServiceArea Identification (SAI).

12.4.4 RA IdentifiersThe identifiers related to the Routing Area (RA) consist of Routing Area Code (RAC) andRouting Area Identification (RAI).

12.4.5 URA IdentifierThe UTRAN Registration Area (URA) is an area covered by a number of cells. In this area, aUE in URA_PCH state does not have to frequently perform cell update. One cell may belong tomultiple URAs. The RNC identifies a URA by URA ID. Each URA ID is uniquely numberedwithin an RNC. The URA IDs range from 0 to 65535.

12.4.6 PLMN Value TagAs an information element, the PLMN value tag is included in the Master Information Block(MIB) and System Information Block 1 (SIB1). The PLMN value tag in the MIB changes uponan SIB1 update. After detecting the change in the PLMN value tag, the UE automatically readsthe new SIB1.

12.4.1 PLMN IDThis defines the PLMN ID, describes the components of the PLMN ID, and provides principlesof and suggestions for numbering PLMNs.

PLMNPublic Land Mobile Networks (PLMNs), which are established and operated by executivebranches or recognized private carriers, are networks that provide public land mobile radiotelecommunication services.

PLMNs identify different mobile communication carriers of different countries. PLMNs ofdifferent carriers have different PLMN IDs.




Issue 03 (2008-08-30)

PLMN IDThe PLMN ID is used to uniquely identify a PLMN worldwide.

The PLMN ID consists of two parts: MCC and MNC. Figure 12-2 shows the components ofthe PLMN ID.

Figure 12-2 Components of the PLMN ID

l Mobile Country Code (MCC) is used to identify different countries or regions.

l Mobile Network Code (MNC) is used to identify different network carriers.

12.4.2 LA IdentifiersThe identifiers related to the Location Area (LA) consist of Location Area Code (LAC) andLocation Area Identification (LAI).

LACThe LAC is used to uniquely identify an LA within a PLMN.

The LAC is a 2-byte hexadecimal code. It ranges from 0000 to FFFE. The codes 0000 and FFFEare reserved. The LAC is presented in the format of h'X1X2X3X4 or H'X1X2X3X4. h' and H' arethe hexadecimal symbols.

LAIThe LAI is used to uniquely identify an LA worldwide.

The LAI consists of three parts: MCC, MNC, and LAC. Figure 12-3 shows the components ofthe LAI.

Figure 12-3 Components of the LAI

12.4.3 SA IdentifiersThe identifiers related to the Service Area (SA) consist of Service Area Code (SAC) and ServiceArea Identification (SAI).

SACThe SAC is a 2-byte hexadecimal code. It is used to uniquely identify an SA within an LA.



12-15

SAIThe SAI is used to uniquely identify an SA worldwide.

The SAI consists of four parts: MCC, MNC, LAC, and SAC. It can also be presented by LAI +SAC. Figure 12-4 shows the components of the SAI.

Figure 12-4 Components of the SAI

12.4.4 RA IdentifiersThe identifiers related to the Routing Area (RA) consist of Routing Area Code (RAC) andRouting Area Identification (RAI).

RACThe RAC is a 1-byte hexadecimal code. It is used to uniquely identify a routing area within aLA.

RAIThe RAI is used to uniquely identify a routing area worldwide.

The RAI consists of four parts: MCC, MNC, LAC, and RAC. It can also be presented by LAI+ RAC. Figure 12-5 shows the components of the RAI.

Figure 12-5 Components of the RAI

12.4.5 URA IdentifierThe UTRAN Registration Area (URA) is an area covered by a number of cells. In this area, aUE in URA_PCH state does not have to frequently perform cell update. One cell may belong tomultiple URAs. The RNC identifies a URA by URA ID. Each URA ID is uniquely numberedwithin an RNC. The URA IDs range from 0 to 65535.

12.4.6 PLMN Value TagAs an information element, the PLMN value tag is included in the Master Information Block(MIB) and System Information Block 1 (SIB1). The PLMN value tag in the MIB changes uponan SIB1 update. After detecting the change in the PLMN value tag, the UE automatically readsthe new SIB1.




Issue 03 (2008-08-30)

When a UE moves between two neighboring cells that belong to different LAs or RAs, the UEneeds to read the SIB1 of the destination cell to initiate the location update process, whichrequires that the two cells have different PLMN value tags.

Therefore, during network planning, different value ranges should be allocated to the PLMNvalue tags of any two geographically neighboring areas (including the case where one area ispart of the other area). The two areas can be two LAs, two RAs, or one LA and one RA.

During parameter configuration, the PLMN value tags of different value ranges should beassigned to any neighboring areas after negotiation. There is no overlap between the valueranges. The area can be a LA or an RA. The PLMN value tags of LAs or RAs vary within thespecified range. As a result, a UE can always read different PLMN value tags when movingacross the areas and thus correctly reads the SIB1.

NOTE

In practice, if a cell supports PS services, the PLMN value tag of the cell varies within the specified valuerange of the RA to which the cell belongs. If a cell does not support PS services, the PLMN value tag ofthe cell varies within the specified value range of the LA to which the cell belongs.

Figure 12-6 shows an example of planning the value ranges of PLMN value tags.

Figure 12-6 Example of planning the value ranges of PLMN value tags

12.5 External Specifications for the RNCThis describes the capability specifications of the RNC for boards, links, and cells. Theconfiguration of interface data and cell data must conform to the external specifications for theRNC.

12.5.1 Specifications for Traffic on RNC BoardsThe RNC has ATM traffic specifications for physical links, ports, and upper-layer applications.

12.5.2 RNC Capability for SAALThe RNC has capability specifications for SAAL.

12.5.3 RNC Capability for SCTPThe RNC has capability specifications for SCTP links.

12.5.4 RNC Capability for NodeBsThe RNC has capability specifications for NodeBs.

12.5.5 RNC Capability for MTP3-bThe RNC has capability specifications for MTP3-b.

12.5.6 RNC Capability for M3UAThe RNC has capability specifications for M3UA.

12.5.7 RNC Capability for AAL2 Paths and AAL2 RoutesThe RNC has capability specifications for AAL2 paths and AAL2 routes.



12-17

12.5.8 RNC Capability for IP Paths and IP RoutesThe RNC has capability specifications for IP paths and IP routes.

12.5.9 RNC Capability for IPoAThe RNC has capability specifications for IPoA.

12.5.10 Specifications for Channels in a CellThis describes the IDs, specifications, default configuration, and full configuration of commontransport channels and common physical channels and the default power specifications for cells.

12.5.11 Specifications for Neighboring CellsThis describes the specifications for neighboring cells at an RNC.

12.5.1 Specifications for Traffic on RNC BoardsThe RNC has ATM traffic specifications for physical links, ports, and upper-layer applications.

Traffic Specifications for Physical Links and PortsWhen configuring the ATM traffic for SAAL links, AAL2 paths, or IPoA PVCs, adhere to theprinciple that the sum of the average traffic values of all links carried on a physical link or portcannot be larger than the maximum traffic bandwidth of the physical link or port. Table 12-4describes the traffic specifications for physical links and ports.

Table 12-4 Traffic specifications for physical links and ports

Physical Link or Port Link Carried Maximum Traffic

E1 link UNI link 4528 cell/s, namely 1.92 Mbit/s

IMA link 4507 cell/s, namely 1.91 Mbit/s

T1 link UNI link 3622 cell/s, namely 1.54 Mbit/s

IMA link 3606 cell/s, namely 1.53 Mbit/s

UOI_ATM board (inSTM-1 mode)

- 353207 cell/s, namely 149.76 Mbit/s

The conversion between units of kbit/s and cell/s are as follows:

l 1 kbit/s = ((1 x 1000) / (53 x 8)) cell/s

l 1 cell/s = ((1 x 53 x 8) / 1000) kbit/s

Traffic Specifications for Upper-Layer LinksThe peak cell rate of each single upper-layer link carried on or terminated at different boardsmust comply with the specifications in terms of maximum and minimum traffic. Table 12-5lists the specifications for the traffic on associated boards.




Issue 03 (2008-08-30)

Table 12-5 Specifications for the traffic on boards

LinkBoard Carrying orTerminating theLink

Minimum Traffic(cell/s)

Maximum Traffic(cell/s)

SAAL link SPUa 71 353207

AAL2 Path l AEUal AOUal UOI_ATM

71 353207

IPoA PVC 71 353207

12.5.2 RNC Capability for SAALThe RNC has capability specifications for SAAL.

The RNC capability for supporting SAAL is as follows:

l A subsystem of an SPUa board supports a maximum of 125 SAAL links of UNI type and50 SAAL links of NNI type.

l An AEUa or AOUa board supports a maximum of 1,500 SAAL links or 1,600 AAL2 pathsor 300 IPoA PVCs. The total number of the three types of link cannot exceed 2,000.

l A UOI_ATM board supports a maximum of 1,500 SAAL links or 1,600 AAL2 paths or400 IPoA PVCs. The total number of the three types of link cannot exceed 2,000.

12.5.3 RNC Capability for SCTPThe RNC has capability specifications for SCTP links.

The RNC capability for supporting SCTP links is as follows:

l For an IP-based Iub interface, a subsystem of an SPUa board supports a maximum of 100SCTP links.

l For an IP-based Iu or Iur interface, a subsystem of an SPUa board supports a maximum of50 SCTP links.

l A PEUa, FG2a, or GOUa board supports a maximum of 1,200 SCTP links.

12.5.4 RNC Capability for NodeBsThe RNC has capability specifications for NodeBs.

The RNC capability for supporting NodeBs is as follows:

l The RSS subrack supports a maximum of 200 NodeBs and 600 cells.

l An RBS subrack supports a maximum of 300 NodeBs and 900 cells.

12.5.5 RNC Capability for MTP3-bThe RNC has capability specifications for MTP3-b.

The RNC capability for supporting MTP3-b is as follows:



12-19

l A Huawei BSC6810 supports a maximum of 119 MTP3-b signaling link sets.

l A Huawei BSC6810 supports a maximum of 119 MTP3-b destination signaling points.

l An MTP3-b signaling link set supports a maximum of 16 MTP3-b signaling links.

l A subsystem of an SPUa board supports a maximum of 50 MTP3-b signaling links.

l A Huawei BSC6810 supports a maximum of 1,904 MTP3-b signaling links.

l A Huawei BSC6810 supports a maximum of 366 MTP3-b signaling routes.

12.5.6 RNC Capability for M3UAThe RNC has capability specifications for M3UA.

The RNC capability for supporting M3UA is as follows:

l A Huawei BSC6810 supports a maximum of 2 local M3UA entities and 119 destinationM3UA entities.

l A Huawei BSC6810 supports a maximum of 119 M3UA link sets.

l A Huawei BSC6810 supports a maximum of 1,904 M3UA links.

l A subsystem of an SPUa board supports a maximum of 50 M3UA links.

l A Huawei BSC6810 supports a maximum of 366 M3UA routes.

12.5.7 RNC Capability for AAL2 Paths and AAL2 RoutesThe RNC has capability specifications for AAL2 paths and AAL2 routes.

The RNC capability for supporting AAL2 paths is as follows:

l A subsystem of an SPUa board supports a maximum of 500 AAL2 paths. The total numberof AAL2 paths and IP paths, however, cannot exceed 1,200.

l A Huawei BSC6810 supports a maximum of 12,000 AAL2 paths. The total number ofAAL2 paths and IP paths, however, cannot exceed 12,000.

l An ATM interface board of a Huawei BSC6810 supports a maximum of 1,600 AAL2 paths.The total number of AAL2 paths, SAAL links, and IPoA PVCs cannot exceed 2,000. TheATM interface board refers to the AEUa, AOUa, or UOI_ATM.

l For adjacent nodes of Iu-CS, Iur, or NNI_AAL2SWITCH type, the RNC supports amaximum of 210 AAL2 paths towards each adjacent node. The total number of AAL2paths and IP paths, however, cannot exceed 210.

l For adjacent nodes of Iub or UNI_AAL2SWITCH type, the RNC supports a maximum of36 AAL2 paths towards each adjacent node. The total number of AAL2 paths and IP paths,however, cannot exceed 36.

The RNC capability for supporting AAL2 routes is as follows:

l A Huawei BSC6810 supports a maximum of 160 AAL2 routes.

l For the Iu-CS/Iur interface, the RNC supports a maximum of five AAL2 routes towardseach adjacent node.

l For the Iu-CS/Iur interface, the RNC supports a maximum of two AAL2 routes towardseach adjacent node.

12.5.8 RNC Capability for IP Paths and IP RoutesThe RNC has capability specifications for IP paths and IP routes.




Issue 03 (2008-08-30)

The RNC capability for supporting IP paths is as follows:

l A subsystem of an SPUa board supports a maximum of 1,200 IP paths. The total numberof AAL2 paths and IP paths, however, cannot exceed 1,200.

l A Huawei BSC6810 supports a maximum of 12,000 IP paths. The total number of AAL2paths and IP paths, however, cannot exceed 12,000.

l An IP interface board of a Huawei BSC6810 supports a maximum of 1,800 IP paths. TheIP interface board refers to the PEUa, POUa, UOI_IP, FG2a, or GOUa.

l For adjacent nodes of Iu-CS or Iur type, the RNC supports a maximum of 210 IP pathstowards each adjacent node. The total number of AAL2 paths and IP paths, however, cannotexceed 210.

l For adjacent nodes of Iub type, the RNC supports a maximum of 36 IP paths towards eachadjacent node. The total number of AAL2 paths and IP paths, however, cannot exceed 36.

l For adjacent nodes of Iu-PS type, the RNC supports a maximum of 32 IP paths towardseach adjacent node.

The RNC capability for supporting IP routes is as follows:

An IP interface board of Huawei BSC6810 supports a maximum of 512 IP routes, among whicha maximum of 128 IP routes can reach network segments instead of hosts. The IP interface boardrefers to the PEUa, POUa, UOI_IP, FG2a, or GOUa.

12.5.9 RNC Capability for IPoAThe RNC has capability specifications for IPoA.

The RNC capability for supporting IPoA is as follows:

l An AEUa or AOUa board supports a maximum of 300 IPoA PVCs. The total number ofAAL2 paths, SAAL links, and IPoA PVCs, however, cannot exceed 2,000.

l A UOI_ATM board supports a maximum of 400 IPoA PVCs. The total number of AAL2paths, SAAL links, and IPoA PVCs, however, cannot exceed 2,000.

12.5.10 Specifications for Channels in a CellThis describes the IDs, specifications, default configuration, and full configuration of commontransport channels and common physical channels and the default power specifications for cells.

IDs of and Specifications for Common Physical ChannelsTable 12-6 describes the IDs of and specifications for common physical channels that aresupported by Huawei BSC6810.



12-21

Table 12-6 IDs of and specifications for common physical channels

CommonPhysicalChannel IDs

Channel Specification

DefaultConfiguration

FullConfiguration

0 PSCH One cell has one and only one PSCH. 1 1

1 SSCH One cell has one and only one SSCH. 1 1

2 P-CPICH One cell has one and only one P-CPICH. 1 1

3 P-CCPCH One cell has one and only one P-CCPCH. 1 1

4 PRACH One cell can be configured with one or twoPRACHs.

1 2

6 AICH AICHs and PRACHs have a one-to-onerelationship.

1 2

8 S-CCPCH One cell can be configured with one to 16 S-CCPCHs. The details are as follows:l A maximum of two S-CCPSHs that carry

non-MBMS services can be configured.One S-CCPCH is configured by default.

l If the cell supports the MBMS function, theS-CCPCH that carries the MBMS servicemust be configured. A maximum of 15 S-CCPCHs can be configured. It isrecommended that the S-CCPCHs benumbered from 11.

1 16

10 PICH One cell has one and only one PICH. The PICHcorresponds to the PCH.

1 1

IDs of and Specifications for Common Transport ChannelsTable 12-7 describes the common transport channel IDs and specifications supported by theHuawei BSC6810.




Issue 03 (2008-08-30)

Table 12-7 IDs of and specifications for common transport channels

CommonTransportChannel IDs

Channel

Type andID of theCarriedCommonPhysicalChannel

Specification

DefaultConfiguration

FullConfiguration

0 BCH P-CCPCH(3)

One cell has one and only oneBCH. The BCH is carried by theP-CCPCH.

1 1

1 RACH PRACH (4) One cell can be configured withone to two RACHs.One PRACH can carry only oneRACH.

1 2

3 PCH

S-CCPCH(8)

One cell has one and only onePCH. The PCH is carried by theS-CCPCH of the minimum ID.

1 1

4 FACH(signaling)

One cell has at least one FACH.l One S-CCPCH that carries

non-MBMS services can carryzero to two FACHs.

l One S-CCPCH that carries theMBMS service can carry oneor two FACHs.

2 325 FACH(traffic)

Default Power Specifications

Table 12-8 lists the default power specifications for cells and channels of the RNC.

Table 12-8 Default power specifications for cells and channels

Item Default Value Description

Maximum TX power of a cell 430 dBm Absolute power

P-CPICH TX power 330 dBm Absolute power

PSCH power -50 dB

Power offset from the P-CPICH TXpower

SSCH power -50 dB

AICH power offset -6 dB

PICH power offset -7 dB

BCH power -20 dB

PCH power -20 dB



12-23

Item Default Value Description

Maximum TX power of theFACH

10 dB

12.5.11 Specifications for Neighboring CellsThis describes the specifications for neighboring cells at an RNC.

The RNC capabilities for supporting neighboring cells are as follows:

l A cell can be configured with a maximum of 32 intra-frequency neighboring cells, includingthe cell itself.

l A cell can be configured with a maximum of 64 inter-frequency neighboring cells.

l A cell can be configured with a maximum of 32 neighboring GSM/GPRS/EDGE cells.

l The neighboring cells of a cell can be distributed in a maximum of 16 RNCs, including thelocal RNC and 15 neighboring RNCs.

l An RNC can be configured with a maximum of 5,100 cells, including intra- and inter-frequency cells, in the local RNC.

l An RNC can be configured with a maximum of 7,680 cells, including intra- and inter-frequency cells, in neighboring RNCs.

l An RNC can be configured with a maximum of 9,600 GSM cells.

l The total number of intra-frequency neighboring cells that can be configured for an RNCcannot exceed 163,200.

l The total number of inter-frequency neighboring cells that can be configured for an RNCcannot exceed 326400.

l The total number of neighboring GSM cells that can be configured for an RNC cannotexceed 163,200.

12.6 Physical Layer Data Configuration GuidelinesThis describes the guidelines for configuring physical layer data.

12.6.1 Interface Boards Applicable to Terrestrial InterfacesBefore planning the configuration data, you need to select the appropriate interface boards basedon the features of terrestrial interfaces.

12.6.2 Upper-Layer Applications Supported by Interface BoardsRelated information is required for the data configuration of the physical layer and data linklayer. The information refers to the upper-layer applications supported by each interface board.

12.6.3 Numbering of Links Carried on AOUa Optical PortsThe numbering of links carried on the optical ports of the AOUa board is different from that ofcommon SDH transmission equipment.

12.6.4 Ports on the AEUa/AOUaThis describes the relationship between the physical links configured on the AEUa and AOUaboards and the E1/T1 physical ports.




Issue 03 (2008-08-30)

12.6.5 Configuration Requirements for E1/T1 Links and IMA LinksThis describes the configuration requirements of the RNC for E1/T1 links and IMA links.

12.6.6 Configuration Specifications for ATM-Based PortsThis describes the guidelines for configuring upper-layer applications for ATM-based physicalports. The ATM-based physical ports consist of E1/T1 ports and optical ports.

12.6.7 Requirements of PPP/MLPPP ConfigurationThis describes the requirements of and specifications for PPP and MLPPP configuration.

12.6.1 Interface Boards Applicable to Terrestrial InterfacesBefore planning the configuration data, you need to select the appropriate interface boards basedon the features of terrestrial interfaces.

ATM Interface Boards

Table 12-9 lists the recommended interface boards for ATM-based interfaces.

Table 12-9 Recommended ATM interface boards

Interface Recommended ATM Interface Board

Iub AOUa, UOI_ATM, and AEUa

Iu-CS UOI_ATM

Iu-PS UOI_ATM

Iur UOI_ATM

Iu-BC UOI_ATM

NOTE

l The Iu-BC interface can share physical transmission resources with the Iu-PS interface. In thisnetworking, if the physical layer data of the Iu-PS interface exists, the physical layer configuration isnot necessary for the Iu-BC interface.

l The boards in Recommended ATM interface board are listed in descending order of priority.

IP Interface Boards

Table 12-10 lists the recommended interface boards for IP-based interfaces.

Table 12-10 Recommended IP interface boards

Interface Recommended IP Interface Board

Iub POUa, UOI_IP, GOUa, FG2a, and PEUa

Iu-CS GOUa, FG2a, and UOI_IP

Iu-PS GOUa, FG2a, and UOI_IP



12-25

Interface Recommended IP Interface Board

Iur UOI_IP, FG2a, and GOUa

NOTE

The boards in Recommended IP interface board are listed in descending order of priority.

12.6.2 Upper-Layer Applications Supported by Interface BoardsRelated information is required for the data configuration of the physical layer and data linklayer. The information refers to the upper-layer applications supported by each interface board.

Upper-Layer Applications Supported by ATM Interface BoardsTable 12-11 shows the upper-layer applications supported by ATM interface boards.

Table 12-11 Upper-layer applications supported by ATM interface boards

ATM Interface Board Upper-Layer Applications

AEUa IMA, UNI, fractional ATM, fractional IMA, andtimeslot cross connection

AOUa IMA and UNI

UOI_ATM Optical port transmission

Upper-Layer Applications Supported by IP Interface BoardsTable 12-12 shows the upper-layer applications supported by IP interface boards.

Table 12-12 Upper-layer applications supported by IP interface boards

IP Interface Board Upper-Layer Applications

PEUa PPP link and MLPPP link group

POUa PPP link and MLPPP link group

UOI_IP PPP link

FG2a Ethernet transmission

GOUa Ethernet transmission

12.6.3 Numbering of Links Carried on AOUa Optical PortsThe numbering of links carried on the optical ports of the AOUa board is different from that ofcommon SDH transmission equipment.




Issue 03 (2008-08-30)

The methods used by companies or organizations for numbering transmission equipment are asfollows:

l Huawei: TUG3 + (TUG2 - 1) x 3 + (TU12 - 1) x 21

l Lucent: TU12 + (TUG2 - 1) x 3 + (TUG3 - 1) x 21

l ITU-T: TUG2 + (TU12 - 1) x 7 + (TUG3 - 1) x 21

Table 12-13 describes the relationship between link numbers of optical ports on the AOUa boardand transmission equipment numbers.

Table 12-13 Relationship between link numbers of AOUa optical ports and transmissionequipment numbers

Numberof TUG3Blocks

Numberof TUG2Columns

Numberof TU12Lines

HuaweiTransmissionEquipment

LucentTransmissionEquipment

ITU-TStandard

LinkNumberof AOUaOpticalPorts

1 1 1 1 1 1 0

1 2 1 4 4 2 1

1 3 1 7 7 3 2

1 4 1 10 10 4 3

1 5 1 13 13 5 4

1 6 1 16 16 6 5

1 7 1 19 19 7 6

1 1 2 22 2 8 7

1 2 2 25 5 9 8

1 3 2 28 8 10 9

1 4 2 31 11 11 10

1 5 2 34 14 12 11

1 6 2 37 17 13 12

1 7 2 40 20 14 13

1 1 3 43 3 15 14

1 2 3 46 6 16 15

1 3 3 49 9 17 16

1 4 3 52 12 18 17

1 5 3 55 15 19 18

1 6 3 58 18 20 19



12-27

Numberof TUG3Blocks


Numberof TU12Lines



ITU-TStandard


1 7 3 61 21 21 20

2 1 1 2 22 22 21

2 2 1 5 25 23 22

2 3 1 8 28 24 23

2 4 1 11 31 25 24

2 5 1 14 34 26 25

2 6 1 17 37 27 26

2 7 1 20 40 28 27

2 1 2 23 23 29 28

2 2 2 26 26 30 29

2 3 2 29 29 31 30

2 4 2 32 32 32 31

2 5 2 35 35 33 32

2 6 2 38 38 34 33

2 7 2 41 41 35 34

2 1 3 44 24 36 35

2 2 3 47 27 37 36

2 3 3 50 30 38 37

2 4 3 53 33 39 38

2 5 3 56 36 40 39

2 6 3 59 39 41 40

2 7 3 62 42 42 41

3 1 1 3 43 43 42

3 2 1 6 46 44 43

3 3 1 9 49 45 44

3 4 1 12 52 46 45

3 5 1 15 55 47 46

3 6 1 18 58 48 47




Issue 03 (2008-08-30)

Numberof TUG3Blocks


Numberof TU12Lines



ITU-TStandard


3 7 1 21 61 49 48

3 1 2 24 44 50 49

3 2 2 27 47 51 50

3 3 2 30 50 52 51

3 4 2 33 53 53 52

3 5 2 36 56 54 53

3 6 2 39 59 55 54

3 7 2 42 62 56 55

3 1 3 45 45 57 56

3 2 3 48 48 58 57

3 3 3 51 51 59 58

3 4 3 54 54 60 59

3 5 3 57 57 61 60

3 6 3 60 60 62 61

3 7 3 63 63 63 62

12.6.4 Ports on the AEUa/AOUaThis describes the relationship between the physical links configured on the AEUa and AOUaboards and the E1/T1 physical ports.

Figure 12-7 shows the relationship between the physical links configured on the AEUa andAOUa boards and the E1/T1 physical ports.



12-29

Figure 12-7 Relationship between the physical links configured on the AEUa and AOUa boardsand the E1/T1 physical ports

Table 12-14 describes the restrictions on the specifications of physical links for the AEUa andAOUa boards.

Table 12-14 Restrictions on the specifications of physical links for the AEUa and AOUa boards

Board Restrictions

Quantityof IMAGroups

Quantityof IMALinks

Other Restrictions

AEUa ≤32 ≤32 l Quantity of IMA groups + quantity ofUNI links + quantity of fractional links≤ 32

l Quantity of IMA links + quantity of UNIlinks + quantity of fractional links ≤ 32

AOUa ≤84 ≤ 126 (E1) l Quantity of IMA groups + quantity ofUNI links ≤ 126

l Quantity of IMA links + quantity of UNIlinks ≤ 126

≤ 168 (T1) l Quantity of IMA groups + quantity ofUNI links ≤ 168

l Quantity of IMA links + quantity of UNIlinks ≤ 168




Issue 03 (2008-08-30)

12.6.5 Configuration Requirements for E1/T1 Links and IMA LinksThis describes the configuration requirements of the RNC for E1/T1 links and IMA links.

Configuration requirements of the RNC for E1/T1 links are as follows:

l The physical layer applications of E1/T1 links include IMA links, UNI links, fractionalATM links, and fractional IMA links.

l For a single link or links carried on a single port, the link type cannot be changed from E1to T1 or from T1 to E1. All the links must be set to the T1 or E1 type uniformly.

l An E1/T1 link can serve only one application, such as the IMA link or UNI link. It cannotwork as an IMA link and a UNI link at the same time.

l If an E1/T1 link serves multiple fractional ATM links or fractional IMA links, the fractionalATM or IMA links must be carried on different timeslots.

l One type of upper-layer application can be carried on different types of physical layer link.For example, one AAL2 path is carried on a UNI link and another AAL2 path on an IMAlink.

l The configurations of frame structure, line code, and scrambling switch must be identicalat both ends of an E1/T1 link.

Configuration requirements of the RNC for IMA links are as follows:

l All links in an IMA group must be of the same type, either E1 or T1.

l The configurations of scrambling switches of all E1/T1 links in an IMA group must beidentical.

l All IMA links in an IMA group must be of the same type, either common IMA link orfractional IMA link.

l For a fractional IMA group, the quantities of timeslots that carry the fractional IMA linksmust be identical. A fractional IMA group refers to the IMA group that contains onlyfractional IMA links.

l The E1/T1 links whose link numbers are congruent modulo 32 cannot be in the same IMAgroup.

l Links carried on different optical ports of the AOUa board cannot be gathered in the sameIMA group.

12.6.6 Configuration Specifications for ATM-Based PortsThis describes the guidelines for configuring upper-layer applications for ATM-based physicalports. The ATM-based physical ports consist of E1/T1 ports and optical ports.

Port Compatibility

When an E1/T1 port carries a UNI or IMA link, the port cannot carry any fractional IMA link,fractional ATM link, or timeslot cross connection. Fractional IMA links, fractional ATM links,and timeslot cross connections can be carried on the same E1/T1 port on condition that theyoccupy different timeslots.



12-31

Timeslot CompatibilityAt one time point, a timeslot can be occupied by only one upper-layer application. Take an AEUaboard for example: If a timeslot is occupied by a fractional ATM link, the timeslot cannot beused by any fractional IMA link or timeslot cross connection.

Application CompatibilityIf IMA links are configured in an IMA group, no fractional IMA link can be added to the group.Similarly, if fractional IMA links are configured in an IMA group, no IMA link can be addedto the group. In a fractional IMA group, each fractional IMA link occupies the same quantity ofidle timeslots.

If an E1/T1 port carries a UNI link, it can no longer carry the IMA link, fractional IMA link,fractional ATM link, or timeslot cross connection.

12.6.7 Requirements of PPP/MLPPP ConfigurationThis describes the requirements of and specifications for PPP and MLPPP configuration.

Requirements of PPP/MLPPP Configurationl The number of each PPP link and that of each MLPPP link must be unique within each

PEUa.l Timeslot 0 is unavailable for configuration. In addition, one timeslot cannot carry both PPP

and MLPPP links at the same time.l During configuration, the slot number must be that of an active board.

l For a PPP link or an MLPPP group, the local and peer IP addresses must be on the samenetwork segment and unique across the network.

l Neither the local IP address nor the peer IP address can be set to 0.0.0.0.

l If the IP address set on the RNC side is inconsistent with that set on the NodeB side, theIP address set on the RNC side applies.

Configuration Specifications for PPP/MLPPPl A PEUa supports a maximum of 128 PPP and MLPPP links in total.

l The total number of PPP and MLPPP links configured in each POUa cannot exceed 126in E1 mode or 168 in T1 mode.

l Each UOI_IP supports a maximum of four PPP links.

l A PEUa supports a maximum of 64 MLPPP groups. Each MLPPP group supports amaximum of eight MLPPP links.

l The total number of MLPPP groups configured in each POUa cannot exceed 42 in E1 modeor 64 in T1 mode.

12.7 ATM TransportATM transport has four modes: UNI, fractional ATM, timeslot cross connection, and IMA.

12.7.1 UNI Mode




Issue 03 (2008-08-30)

The UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of thephysical layer.

12.7.2 Fractional ATMFractional ATM is a transport application at the Transmission Convergence (TC) sublayer ofthe physical layer. This describes the principles and functions of fractional ATM, introduces thetwo implementation modes (that is, fractional IMA and fractional ATM), and provides theguidelines for configuring fractional IMA links and fractional ATM links.

12.7.3 Timeslot Cross ConnectionThe timeslot cross function implements cross connections between timeslots on two E1/T1s atthe PM sublayer of the physical layer. This describes the principles and functions of timeslotcross connection.

12.7.4 IMA ModeThe Inverse Multiplexing on ATM (IMA) mode is a transport application at the TransmissionConvergence (TC) sublayer of the physical layer. This topic describes the IMA mode in termsof its working principles, clock modes, and features.

12.7.1 UNI ModeThe UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of thephysical layer.

In UNI mode, an ATM cell is directly carried on an E1/T1 and the bits of the ATM cell aresequentially mapped to the valid timeslots on the E1/T1. Figure 12-8 shows the mappingbetween the ATM cell and the E1 timeslots in UNI mode. The 53 octets of the ATM cell aresequentially carried on E1 timeslots. Each E1 provides 31 timeslots (with slot 0 unavailable) forcarrying the ATM cell.

Figure 12-8 Mapping between the ATM cell and the E1 timeslots in UNI mode



12-33

12.7.2 Fractional ATMFractional ATM is a transport application at the Transmission Convergence (TC) sublayer ofthe physical layer. This describes the principles and functions of fractional ATM, introduces thetwo implementation modes (that is, fractional IMA and fractional ATM), and provides theguidelines for configuring fractional IMA links and fractional ATM links.

Principles of Fractional ATMFor fractional ATM, multiple timeslots out of the 32 timeslots on an E1/T1 are used to transmitan ATM cell. At the TX end, an ATM cell is mapped to multiple timeslots among the 31 timeslotson an E1/T1. At the RX end, the ATM cell is restored from the associated timeslots on the E1/T1. Figure 12-9 shows the fractional ATM mode. An E1 frame has timeslots numbered from 0to 31. All the timeslots except timeslot 0 are available for service data transmission. A T1 framehas timeslots numbered from 1 to 24. All the timeslots are available for service data transmission.The timeslots to which the ATM cell is not mapped can transmit other data.

Figure 12-9 Fractional ATM mode

If multiple E1/T1 trunks exist between the TX end and the RX end and work in IMA mode, suchan IMA mode is called fractional IMA. In fractional IMA mode, an IMA group contains multiplefractional ATM links.

Function of Fractional ATMAfter the fractional ATM function is enabled, the ATM cells of a 3G network can be transmittedover an existing 2G network, as shown in Figure 12-10.




Issue 03 (2008-08-30)

Figure 12-10 Fractional ATM function

Two Modes of the Fractional ATM FunctionThere are the following two modes of the fractional ATM function:

l Fractional ATMIn fractional ATM mode, multiple idle timeslots can be used for transmission.The fractional ATM mode is applicable to only the AEUa board.

l Fractional IMAIn fractional IMA mode, multiple fractional IMA links are logically gathered into a groupwith each fractional IMA link occupying the same quantity of idle timeslots.The fractional IMA mode can be applied to only the AEUa board.

Configuration of Fractional ATM Links and Fractional IMA LinksTable 12-15 describes the methods of configuring fractional ATM links and fractional IMAlinks.

Table 12-15 Methods of configuring fractional ATM links and fractional IMA links

Link Method

FractionalATM link

Use the ADD FRALNK command. The timeslot that carries the FRA ATMlink should be specified during the configuration. The timeslot number stayswithin the range of 1 to 31 and cannot be 0.



12-35

Link Method

FractionalIMA link

1. Use the ADD IMAGRP command to add an IMA group.2. Use the ADD FRALNK command to add a fractional IMA link to the

IMA group. To add more fractional IMA links to the IMA group, run thiscommand repeatedly.

NOTEWithin the IMA group, the fractional IMA links must carry the same quantity oftimeslots.

12.7.3 Timeslot Cross ConnectionThe timeslot cross function implements cross connections between timeslots on two E1/T1s atthe PM sublayer of the physical layer. This describes the principles and functions of timeslotcross connection.

Principles of Timeslot Cross ConnectionFigure 12-11 shows an example of timeslot cross connection. The timeslot cross connectiondevice cross-connects the timeslots on one E1/T1 to the timeslots on another E1/T1. In theexample shown in the following figure, the device cross-connects slots 2 and 3 on one E1/T1 toslots 4 and 8 on another E1/T1 respectively.

Figure 12-11 Principles of timeslot cross connection

Function of Timeslot Cross ConnectionThe AEUa board supports timeslot cross connection. Through the configured timeslot crossconnection, the E1 data in timeslot A of the source port is transmitted to timeslot B of the targetport. Thus, the timeslot cross connection helps provide a transparent data transmission channelfor the 2G equipment or NodeB monitoring equipment.

Figure 12-12 shows implementation of timeslot cross connection.




Issue 03 (2008-08-30)

Figure 12-12 Principles of timeslot cross connection

NOTE

l Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by othermodes, such as fractional ATM, IMA, and UNI.

l If an E1 link is configured with a timeslot cross connection, the E1 link cannot carry any IMA or UNIlink. The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.

12.7.4 IMA ModeThe Inverse Multiplexing on ATM (IMA) mode is a transport application at the TransmissionConvergence (TC) sublayer of the physical layer. This topic describes the IMA mode in termsof its working principles, clock modes, and features.

Working PrinciplesFigure 12-13 shows the working principles of the IMA mode based on the assumption that eachIMA group contains three E1/T1 links.

l At the TX end, the IMA group receives the ATM cell stream from the ATM layer anddistributes the cells among the E1/T1 links.

l At the RX end, the IMA group reassembles the cells to restore the ATM cell stream to theoriginal sequence, and then transfers the cell stream to the ATM layer.

The physical layer provides high-speed transport channels for ATM cells from or to the ATMlayer.



12-37

Figure 12-13 Working principles of the IMA mode

In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells build up an IMAframe to implement necessary controlling functions.

The length of an IMA frame, m, is defined during the setup of an IMA group. Figure 12-14shows an IMA frame. The mapping between the ATM cell and the physical link (E1/T1) issimilar to that in UNI mode.

Figure 12-14 IMA frame

Clock Modes

The clock mode of an IMA group is defined from the perspective of an IMA group rather thana single link. The IMA group has the following two clock modes:

l Common Transmit Clock (CTC): In CTC clock mode, all links in an IMA group share oneclock source. The clock source may be extracted from the same external clock or from alink.

l Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within anIMA group are derived from at least two clock sources. The loopback clock mode is aspecial case of the ITC mode.




Issue 03 (2008-08-30)

Features

The IMA mode has the following features:

l The clock modes at the two ends of the IMA group should be identical.

l All E1/T1s within an IMA group are simultaneously scrambled or none of them isscrambled. In other words, the states of the scrambling switches at both ends of E1/T1smust be identical.

l All IMA links within an IMA group must be of the same type. In other words, within anIMA group, either all links are common IMA links or all links are fractional IMA links.

l If an IMA group is made up of fractional IMA links, the quantities of timeslots on thefractional IMA links must be identical. The same is true for the numbers of each timeslotson the fractional IMA links.

12.8 PVC Parameters of the RNCDuring the setting of PVC attributes of the ATM layer at Huawei BSC6810, the associatedparameters of the ATM Adaptation Layer (AAL) are also configured. Thus, you need to takethe associated AAL parameters into consideration when setting the PVC attributes.

12.8.1 VPI and VCIThe ATM technologies features multiplexing, switching, and transmitting of ATM cells. Allthese operations are performed over VCs. VCs and VPs are identified by VCIs and VPIsrespectively.

12.8.2 Service TypeThe ATM services are of four types: Constant Bit Rate (CBR), Real-Time Variable Bit Rate(RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), and Unspecified Bit Rate (UBR).

12.8.3 Traffic ParametersTraffic parameters refer to the parameters used by each PVC for flow control. The trafficparameters include traffic rate and delay variation.

12.8.4 ATM Traffic Resource Configuration GuidelinesThis provides suggestions for configuring service types during configuration of ATM trafficresources for links on the interfaces.

12.8.1 VPI and VCIThe ATM technologies features multiplexing, switching, and transmitting of ATM cells. Allthese operations are performed over VCs. VCs and VPs are identified by VCIs and VPIsrespectively.

Figure 12-15 shows the relationship between VC and VP.

l A VC is identified by the VCI. It is the logical connection between ATM nodes and is thechannel for transmitting ATM cells between two or more nodes. The VC is used for theinformation transmission between UEs, between networks, or between UE and network.

l A VP is a group of VCs at a given reference point. The VCs in the group have the sameVPI.



12-39

Figure 12-15 Relationship between VC and VP

12.8.2 Service TypeThe ATM services are of four types: Constant Bit Rate (CBR), Real-Time Variable Bit Rate(RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), and Unspecified Bit Rate (UBR).

Table 12-16 describes the types of service.

Table 12-16 Types of service

Type of Service Acronym Description

Constant Bit Rate CBR No error check, flow control, or other processing

Real-Time VariableBit Rate

RT-VBR Services with variable data streams and strictreal-time requirements, for example, interactivecompressed video (video telephony).

Non-Real-TimeVariable Bit Rate

NRT-VBR Used for timing transmission, where theapplication program is relatively insensitive todelivery time or delay, for example, e-mail.

Unspecified Bit Rate UBR No commitment to transmission. No feedback oncongestion. This type of service is ideal for thetransmission of IP datagrams. In the case ofcongestion, UBR cells are discarded, and nofeedback or request for slowing down the datarate is delivered to the sender.

Table 12-17 describes the features of different ATM services.

Table 12-17 Features of different ATM services

Feature CBR RT-VBR NRT-VBR UBR

Bandwidthguarantee

Yes Yes Yes No

Applicability toreal-timecommunication

Yes Yes No No




Issue 03 (2008-08-30)

Feature CBR RT-VBR NRT-VBR UBR

Applicability tobursts ofcommunication

No No Yes Yes

Feedback oncongestion

No No No No

12.8.3 Traffic ParametersTraffic parameters refer to the parameters used by each PVC for flow control. The trafficparameters include traffic rate and delay variation.

Table 12-18 describes the ATM traffic parameters.

Table 12-18 ATM traffic parameters

Parameter Name Parameter ID Description

Traffic record index TRFX Identifies a traffic record.

Service Type ST Indicates the type of service carried on theATM layer. CBR and RTVBR indicate real-time services, which are usually carried on theuser planes of the Iur, Iub, and Iu-CSinterfaces. NRTVBR and UBR indicate non-real-time services, which are usually carriedon the user plane of the Iu-PS interface.

Rate unit UT Indicates the unit of PCR, SCR, and MCR.

Peak cell rate PCR Indicates the maximum rate of transmittingATM cells.

Sustainable cell rate SCR Indicates the average rate of transmittingATM cells over a long time.

Minimum cell rate MCR Indicates the minimum rate of transmittingATM cells.

Max burst size MBS Indicates the maximum quantity of continuousATM cells.

Cell delay variationtolerance

CDVT Indicates the maximum tolerable variation.Unit: 0.1 μs

Traffic usedescription

REMARK Describes the usage of the ATM traffic record.

The traffic rate is indicated in the following ways:



12-41

l PCR: The traffic rate is PCR when Service Type is CBR, that is, the traffic rate is a constantvalue.

l PCR + SCR: The traffic rate is PCR + SCR when Service Type is RTVBR or NRTVBR.

l MCR: The traffic rate is MCR when Service Type is UBR_PLUS.

12.8.4 ATM Traffic Resource Configuration GuidelinesThis provides suggestions for configuring service types during configuration of ATM trafficresources for links on the interfaces.

Table 12-19 lists the recommended service types for links on different interfaces.

Table 12-19 Recommended service types for links on different interfaces

Link Type of Service (In Descending Order ofPriority)

NCP/CCP RTVBR, NRTVBR, CBR

AAL2 Path RTVBR, NRTVBR, CBR, UBR

IPoA PVC (user plane) UBR

IPoA PVC (management plane) UBR_PLUS, RTVBR, NRTVBR, CBR, UBR

MTP3-b Link RTVBR, NRTVBR, CBR

NOTE

l In practice, ATM traffic resources should be negotiated between the RNC and the peer equipment.

l The ATM traffic parameters of an interface, such as PCR and SCR, should be configured dependingon the traffic model in use.

l When configuring ATM traffic resources for interfaces, you should take the limits to traffic on interfaceboards of the RNC into consideration. For details, refer to 12.5.1 Specifications for Traffic on RNCBoards.

12.9 AAL2 Configuration GuidelinesThis describes AAL2 configuration guidelines in terms of the working principles of AAL2 paths,destination boards of AAL2 paths, and AAL2 routes.

12.9.1 Working Principles of AAL2 PathsAn AAL2 path is actually a PVC that has relatively high bandwidth. One AAL2 path has 256AAL2 connections among which AAL2 connections 0 to 7 are reserved for protocols and AAL2connections 8 to 255 for traffic.

12.9.2 AAL2 RouteAn AAL2 path reaches only an adjacent node, not necessarily the destination node. Byconfiguring AAL2 routes, you can set up a route from the RNC to the destination node throughadjacent nodes.




Issue 03 (2008-08-30)

12.9.1 Working Principles of AAL2 PathsAn AAL2 path is actually a PVC that has relatively high bandwidth. One AAL2 path has 256AAL2 connections among which AAL2 connections 0 to 7 are reserved for protocols and AAL2connections 8 to 255 for traffic.

During communication, the Q.AAL2 module is responsible for dynamically setting up andreleasing AAL2 connections between the RNC and the peer end. The peer end can be a NodeB,a CS CN node, or a neighboring RNC. The destination of an AAL2 path is the ATM interfaceboards AEUa, AOUa, and UOI_ATM of the RNC.

Figure 12-16 shows the relationship between an AAL2 path carried on the Iub interface andAAL2 connections.

Figure 12-16 Relationship between an AAL2 path and AAL2 connections

12.9.2 AAL2 RouteAn AAL2 path reaches only an adjacent node, not necessarily the destination node. Byconfiguring AAL2 routes, you can set up a route from the RNC to the destination node throughadjacent nodes.

Figure 12-17 shows an example of the AAL2 route.

Figure 12-17 Example of the AAL2 route

NOTE

Even if the destination node is an adjacent node, an AAL2 route is still required. In this case, the destinationnode and the adjacent node refer to the same one.

12.10 MTP3-b/M3UA Configuration GuidelinesThis describes the MTP3-b/M3UA configuration guidelines.

12.10.1 Types of and Specifications for the MTP3-b/M3UA DSPs



12-43

The RNC supports seven types of Destination Signaling Point (DSP), namely, IUCS,IUCS_ALCAP, IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different typeshave different meanings and different specifications.


12.10.3 Signaling Route Mask and Signaling Link MaskThis describes configurations and examples of the signaling route mask and signaling link mask.

12.10.4 Configuration Guidelines for MTP3-b/M3UAThis describes the guidelines for configuring MTP3-b/M3UA signaling links, MTP3-b/M3UAsignaling link sets, and MTP3-b/M3UA routes.


12.10.1 Types of and Specifications for the MTP3-b/M3UA DSPsThe RNC supports seven types of Destination Signaling Point (DSP), namely, IUCS,IUCS_ALCAP, IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different typeshave different meanings and different specifications.

Table 12-20 describes the types of and specifications for the DSPs.

Table 12-20 Types of and specifications for the DSPs

DSP Type Description Specification

IUCS R99 MSC DSP. The IUCS DSPhas the control plane functions ofboth the radio network layer andtransport network layer on the Iu-CS interface.

l Quantity of IUCS DSPs ≤ 32l Quantity of IUCS_RANAP

DSPs ≤ 32l Quantity of IUCS_ALCAP

DSPs ≤ 32l Quantity of IUCS_RANAP

DSPs + quantity of IUCSDSPs ≤ 32

l Quantity of IUCS_ALCAPDSPs + quantity of IUCSDSPs ≤ 32

IUCS_ALCAP R4 MGW DSP. TheIUCS_ALCAP DSP has thecontrol plane functions of thetransport network layer on the Iu-CS interface.

IUCS_RANAP R4 MSC server DSP. TheIUCS_RANAP DSP has thecontrol plane functions of the radionetwork layer on the Iu-CSinterface.

IUPS Signaling point on the Iu-PScontrol plane

Number of the IUPS DSPs ≤ 32

IUR Other RNC signaling points Number of the IUR DSPs ≤ 15

STP Signaling transfer point Number of the STP DSPs ≤ 2




Issue 03 (2008-08-30)

DSP Type Description Specification

AAL2SWITCH AAL2 transfer point Quantity of AAL2SWITCHDSPs ≤ 6


PrinciplesA Huawei BSC6810 supports a maximum of 119 DSPs, including the DSPs that are eitherdirectly or indirectly connected to the Originating Signaling Points (OSPs). The numbers of theMTP3-b or M3UA DSPs range from 0 to 118. Each DSP is uniquely but not necessarilyconsecutively numbered within an RNC. The number is the DSP index. For example, set thenumber of an MSC signaling point to 10 and that of the next MSC signaling point to 12.


Specify different ranges for DSPs depending on the DSP types. For example, specify the rangeof 0 to 59 for DSPs over Iu-CS, the range of 60 to 69 for DSPs over Iu-PS, the range of 70 to79 for DSPs over Iur, the range of 80 to 89 for DSPs of the STP type, and the range of 90 to 99for DSPs of the AAL2 switch type. There are three types of DSP over Iu-CS: IuCS,IuCS_RANAP, and IuCS_ALCAP.

12.10.3 Signaling Route Mask and Signaling Link MaskThis describes configurations and examples of the signaling route mask and signaling link mask.

The number of 1s in a signaling route mask (expressed with n) determines the maximum numberof routes (2n). For example, B0000 indicates that there is at most one route. B0001 or B1000indicates that there are at most two routes. A BSC6810 supports a maximum of 16 routes forload sharing for one DSP.

The number of 1s in a signaling link mask (expressed with n) determines the maximum numberof links (2n). For example, B0000 indicates that there is at most one link. B0001 or B1000indicates that there are at most two links. For a signaling link set, a BSC6810 supports amaximum of 16 links for load sharing.

The signaling link mask AND the signaling route mask must be 0, as shown in Figure 12-18.

Figure 12-18 Relation between signaling link mask and signaling route mask



12-45

12.10.4 Configuration Guidelines for MTP3-b/M3UAThis describes the guidelines for configuring MTP3-b/M3UA signaling links, MTP3-b/M3UAsignaling link sets, and MTP3-b/M3UA routes.

MTP3-b Signaling Link SetThe MTP3-b signaling link set is assigned to a neighboring DSP of the RNC. The MTP3-b linkset index uniquely identifies an MTP3-b signaling link set within an RNC. Each index is uniquewithin an RNC.

When configuring an MTP3-b link set, you should specify the MTP3-b link mask to determinethe strategy of routing between the signaling links in the link set.

MTP3-b Signaling LinkAn MTP3-b link set can have a maximum of 16 MTP3-b links. To enhance the reliability of SS7links, each signaling link set is configured with more than one MTP3-b link, if the total numberof MTP3-b links is within the limit.

MTP3-b RouteAn MTP3-b route is used to pass signaling messages from the OSP to the DSP.

The MTP3-b route should be configured regardless of whether the DSP is adjacent to the RNC.It is recommended that an indirect route be configured as redundancy for a direct route.

M3UA Signaling Link SetThe M3UA signaling link set is assigned to a neighboring destination M3UA entity of the RNC.The M3UA link set index uniquely identifies an M3UA link set within an RNC. Each index isunique within an RNC.

When configuring an M3UA link set, you should specify the M3UA link mask to determine thestrategy of routing between the signaling links in the link set.

M3UA Signaling LinkAn M3UA link set can have a maximum of 16 M3UA links. To enhance the reliability of SS7links, each signaling set is configured with more than one M3UA link, if the total number ofM3UA links is within the limit.

M3UA RouteAn M3UA route is used to pass signaling messages from the local M3UA entity to the destinationM3UA entity.

The M3UA route should be configured regardless of whether the destination entity is adjacentto the local entity. It is recommended that an indirect route be configured as redundancy for adirect route.





Issue 03 (2008-08-30)

PrinciplesIn a Huawei BSC6810, the numbers of adjacent nodes range from 0 to 1999. Each adjacent nodeis uniquely but not necessarily consecutively numbered within an RNC. For example, set thenumber of an adjacent NodeB to 10 and that of the next adjacent node to 12.


Within the range of 0 to 1999, number the Iub adjacent nodes and the Iur and Iu adjacent nodesfrom the two ends. For example, number the Iub adjacent nodes from 0 up and number the Iurand Iu adjacent nodes from 1999 down.

For Iur and Iu adjacent nodes, it is recommended that different ranges be allocated to adjacentnode numbers depending on the interfaces. For example, specify the range of 1995 to 1999 foradjacent nodes over Iu-CS, the range of 1990 to 1994 for adjacent nodes over Iu-PS, and therange of 1985 to 1989 for adjacent nodes over Iur.

12.11 Cell-Related ConceptsThis describes the cell-related concepts, such as sector, carrier, cell, local cell and logical cell,cell ID, logical cell model, and areas of logical cells.

12.11.1 Definitions of Sector, Carrier, and CellA sector is the smallest radio coverage area unit, which is covered by one or more radio carriers.Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallestserving unit for UE access.

12.11.2 Definitions of Local Cell and Logical CellIn the 3GPP, a service-providing cell is referred to as a local cell in implementation sense andas a logical cell in logical resource management sense.

12.11.3 Logical Cell ModelThis describes the logical cell model that is instructive for the configuration of logical cells.

12.11.4 Areas of Logical CellsA logical cell must exist in a Location Area (LA), a Service Area (SA), a Routing Area (RA),and a UTRAN Registration Area (URA).

12.11.5 Definition of Neighboring CellA neighboring cell is associated with a specific cell. There are three types of neighboring cellfor UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, andneighboring GSM cell.

12.11.1 Definitions of Sector, Carrier, and CellA sector is the smallest radio coverage area unit, which is covered by one or more radio carriers.Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallestserving unit for UE access.

Sectors are of two types: omnidirectional sector and directional sector. The omnidirectionalsector provides coverage for small traffic. It covers the 360º circle area with the omnidirectionalantenna in the center of the circle. As the traffic grows, the omnidirectional sector is split intothree or six directional sectors. The directional sectors are covered by directional antennas. For



12-47

a 3-sector cell, each of the three directional antennas covers a 120º sector area. For a 6-sectorcell, each of the six directional antennas covers a 60º sector area. In fact, the azimuth of theantenna is greater than the theoretical value, and therefore there is overlap between the sectors.

Number of cells supported by a NodeB = number of sectors x number of carriers in each sector.Figure 12-19 shows the typical 3 x 2 configuration. The whole circle area is split into threesectors: sector 0, sector 1, and sector 2. Each sector has two carriers, and each carrier forms acell. 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.The different downlink primary scrambling codes lower the interference between cells.

Figure 12-19 shows the relations between sector, frequency, and cell.

Figure 12-19 Relations between sector, frequency, and cell

12.11.2 Definitions of Local Cell and Logical CellIn the 3GPP, a service-providing cell is referred to as a local cell in implementation sense andas a logical cell in logical resource management sense.

Local CellA local cell is a combination of physical resources, such as hardware resources and softwareresources, in a cell of a NodeB. A local cell is related to the physical implementation of a device.

NodeBs from different vendors have different ways of providing physical resources for cells.Therefore, the concept of logical cell is proposed by the 3GPP to ensure that the RNC can control




Issue 03 (2008-08-30)

the radio resources in certain cells through the standard Iub interface. These cells are carried onNodeBs from different vendors.

Logical Cell

A logical cell is a standard logical model that helps the RNC control the radio resources in acell. The model is independent of local cell implementation and ensures that the Iub interface isan open interface. For details about the logical cell model, refer to 12.11.3 Logical CellModel.

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. Each logical cell has a one-to-onerelationship with each local cell.

12.11.3 Logical Cell ModelThis describes the logical cell model that is instructive for the configuration of logical cells.

Figure 12-20 shows the logical cell configuration model. The number above the square is thequantity of the entities that serve as lower-level nodes. The number below the square is thequantity of the entities that serve as upper-level nodes.

Figure 12-20 Logical cell configuration model

NOTE

l P-CPICH: Primary Common Pilot Channel

l PSCH: Primary Synchronization Channel

l SSCH: Secondary Synchronization Channel

l P-CCPCH: Primary Common Control Physical Channel

l PICH: Paging Indicator Channel

l S-CCPCH: Secondary Common Control Physical Channel

l PRACH: Physical Random Access Channel

l AICH: Acquisition Indication Channel

l BCH: Broadcast Channel

l PCH: Paging Channel

l FACH: Forward Access Channel

l RACH: Random Access Channel



12-49

12.11.4 Areas of Logical CellsA logical cell must exist in a Location Area (LA), a Service Area (SA), a Routing Area (RA),and a UTRAN Registration Area (URA).

NOTE

For details about the areas, refer to 12.4 Area Identifiers.

l A cell can belong to only one LA.

l A cell can belong to only one RA.

l A cell can belong to only one CS/PS SA.

l A cell can belong to only one CBS SA.

l A cell can belong to one to eight URAs.

12.11.5 Definition of Neighboring CellA neighboring cell is associated with a specific cell. There are three types of neighboring cellfor UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, andneighboring GSM cell.

l The intra-frequency neighboring cell refers to a cell that has overlapping coverage with theserving cell and uses the same carrier frequency as the serving cell.

l The inter-frequency neighboring cell refers to a cell that has overlapping coverage with theserving cell but uses a different carrier frequency from the serving cell.

l The neighboring GSM cell refers to a cell that is adjacent to the serving cell but belongs toa GSM, General Packet Radio Service (GPRS), or Enhanced Data rates for GlobalEvolution (EDGE) system.

12.12 Configurations of RAN SharingThis describes the configuration principles of the RAN sharing. The data refers to the operator-based license control, operator-based transport network layer configuration of the Iub interface,operator-based cell and NodeB configuration, and operator-based Iu interface configuration.

12.12.1 Operator-Based License ControlThis describes the operator-based license control in terms of its background, principles, andconfiguration rules.

12.12.2 Operator-Based Configuration at the Iub Transport Network LayerThis describes the operator-based configuration at the Iub transport network layer in terms ofits background, principles, and configuration rules.

12.12.3 Operator-Based Configuration of Cells and NodeBsThis describes the operator-based configuration of cells and NodeBs in terms of its background,principles, and configuration rules.

12.12.4 Operator-Based Configuration on the Iu InterfaceThis describes the operator-based configuration on the Iu interface in terms of its background,principles, and configuration rules.




Issue 03 (2008-08-30)

12.12.1 Operator-Based License ControlThis describes the operator-based license control in terms of its background, principles, andconfiguration rules.

BackgroundThe operator-based license control is a basic requirement of the RAN sharing feature. When anRNC supports the RAN sharing, multiple operators share one physical RNC but may usedifferent capacities and different optional functions, thus requiring operator-based licensecontrol on capacities and optional functions.

PrinciplesThe license configuration for the RNC under network sharing is performed by maintenancepersonnel from the primary operator. To configure the license information, perform thefollowing steps: Save the license file in BAM active workspace installation directory\FTP\License.

1. Run the ACT LICENSE command to configure the capacity and optional functions of theprimary operation and activate the license.

2. Run the ACT LICENSE command to configure the capacities and optional functions fora secondary operator.

The BAM sends the license information of the operators to the RNC host, which then controlsthe capacities and optional functions for each operator.

Configuration Restriction1. When you activate the license file and configure the license information of the primary

operator, the RNC checks according to the license file applied by the primary operator.That is, when you run the ADD RNCBASIC command to configure RNC ID and the ADDCNOPERATOR command to configure Mobile Country Code and Mobile NetworkCode of the primary operator, the settings must be consistent with the ESN (equipmentserial number of the RNC) in the license file applied for by the primary operator.

2. If the primary operator does not purchase the RAN sharing feature, the primary operatorcannot configure the capacities and optional functions of secondary operators.

3. In terms of the capacity, the total traffic of the PS and CS domains of the primary andsecondary operators cannot exceed the value specified in the license file.

4. In terms of optional functions, if a function is disabled in the license file, the primaryoperator cannot enable the function in configuring the license information of secondaryoperators.

5. When a new license file is activated, the system automatically sets Maximum UserNumber of the CS Domain of secondary operators to 0 and Maximum Traffic of the PSDomain to 0 and enables all optional functions. The configurations have certain effects onnew service access of the secondary operators. Hence, the primary operator needs toconfigure the license of secondary operators as soon as possible.



12-51

12.12.2 Operator-Based Configuration at the Iub TransportNetwork Layer

This describes the operator-based configuration at the Iub transport network layer in terms ofits background, principles, and configuration rules.

Background

The operator-based configuration at the Iub transport network layer is a higher requirement ofthe RAN sharing feature. Operators use their individual cells but share the RNC and NodeBresources. The Iub TRM allocates resources to operators according to the their applicationsequences. Hence, the reasonable transport resource allocation to operators cannot beguaranteed. After the Iub transport resource separation function is available, the Iub transportresource used by each operator can be configured independently.

Principles

To implement the operator-based configuration at the Iub transport network layer, admissioncontrol and traffic shaping at the transport network layer on the RNC side are used to separatebandwidth resources for operators. Each operator has exclusive control on its own resources.

Implement the admission control at the transport network layer by the resource management inresource group mode. The port traffic shaping can be achieved through the virtual port shapingand logic port shaping technologies.

Implement the operator-based transport resource configuration through the operator-based TRMmapping of adjacent nodes (including the operator-based activity factor setting and TRMmapping setting).

Achieve the congestion control through the operator-oriented congestion management strategy.When the resource congestion occurs to an operator, the congestion control is performed onlyfor the users of the operator .

1. Run the ADD CNOPERATOR command to add the information of an operator.

2. Run the ADD TRMMAP and ADD FACTORTABLE commands to add a TRM mappingtable and a factor table respectively.

3. Run the ADD ADJMAP command to add the TRM mapping table and factor table to beused by the operator.

4. Run the ADD VP command to add a virtual port for the operator. In this step, set ResourceManagement Mode to EXCLUSIVE.

5. Run the ADD LGCPORT command to add a logical port for the operator. In this step, setResource Management Mode to EXCLUSIVE.

6. Run the ADD RSCGRP command to add a transport resource group for the operator. Inthis step, set Resource Management Mode to EXCLUSIVE.

Configuration Restrictionl The information of the operators must be already configured.

l The separation feature of transport resources on the Iub transport network layer is subjectto the control of the license.




Issue 03 (2008-08-30)

l Transport resources of the same NodeB can only be shared by several operators orexclusively used by one operator. These resources cannot be shared and used exclusivelyat the same time.

l The AEUa, AOUa, and UOI_ATM support the virtual port and each interface boardsupports a maximum of 120 virtual ports.

l The FG2a, GOUa, and UOI_IP support the logical port and each interface board supportsa maximum of 120 logical ports.

l The PEUa and POUa do not support the logical port. To support the separation of user planeresources on the Iub interface in PEUa or POUa, you can configure the PPP link/MLPPPlink groups to realize the separation of user plane resources through the separation ofphysical ports or you can also configure the resource groups.

l Each SPUa subsystem supports a maximum of 25 NodeBs, the shared RAN supports amaximum of 4 operators, and the user plane resource separation function of the Iub interfacesupports 4 operators. However, if the resource group specification, VP number, and logicalport number are taken into consideration, the SPUa subsystem fails to support 50 NodeBsafter the transport resource separation function of the Iub interface is enabled, and multi-level PVC-based networking might also fail to support 4 operators and the maximumnumber of levels.

l When operator-oriented TRM mapping tables and factor tables are specified in nodes, theresource management modes of all the adjacent nodes carried on a physical link or portmust be set uniformly, that is, either shared or exclusive.

12.12.3 Operator-Based Configuration of Cells and NodeBsThis describes the operator-based configuration of cells and NodeBs in terms of its background,principles, and configuration rules.

BackgroundThe operator-based configuration of cells and NodeBs is a basic requirement of the RAN sharingfeature. The logical unit of RAN sharing is cell, so an operator must be specified for a cell whenthe cell is configured. In addition, if a NodeB carries cells of different operators, the NodeBmust be configured to support sharing by the operators.

PrinciplesWhen basic data is configured for the RNC, the operators that the RNC serves must beconfigured. The operators are identified by their indexes. When a cell is configured, the indexof the operator that owns the cell must be specified. This operator must be already configuredon the RNC. When a NodeB is configured, whether the NodeB is shared must be set. If theNodeB is shared, no operator index needs to be specified. If the NodeB is non-shared, the indexof the operator that owns the NodeB must be specified. To configure a cell and a NodeB for anoperator, perform the following steps:

1. Run the ADD CNOPERATOR command to configure an operator.2. Run the ADD NODEB command to configure the basic data of the NodeB. In this step,

when Sharing Support is set to NON_SHARED, configure Cn Operator Index to specifythe operator that the NodeB serves.

3. Run the ADD QUICKCELLSETUP command to quickly set up a cell. In this step,configure Cn Operator Index to specify the operator that the cell serves. If the cell iscarried on a non-shared NodeB, the cell and NodeB serve the same operator.



12-53

Configuration Restrictionl When a NodeB is configured, the information of the RNC and operators must be already

configured. When a cell is configured, the information of the NodeB that carries the cellmust be already configured.

l If a cell is carried on a non-shared NodeB, the index of the operator that owns the cell mustbe the same as the index of the operator that owns the NodeB.

l If a cell is carried on a shared NodeB, the index of the operator that owns the cell can bedifferent from the index of the operator that owns the NodeB.

12.12.4 Operator-Based Configuration on the Iu InterfaceThis describes the operator-based configuration on the Iu interface in terms of its background,principles, and configuration rules.

Background

The operator-based configuration on the Iu interface is a basic requirement of the RAN sharingfeature. Operators use their individual CNs but share a UTRAN, which covers RNCs andNodeBs. This saves network investment and facilitates quick deployment of networks with widecoverage.

Principles

The operator-based configuration on the Iu interface mainly covers the radio network layer ofthe Iu interface. Operators use their individual CNs but share RNCs and NodeBs. Operator usesthe cells of different frequencies in NodeBs and each cell includes the PLMN information of thecorresponding operator. Before basic data is configured for the Iu interface, the operators thatthe RNC serves and the global location information of the RNC must be configured. Theoperators are identified by their indexes. Hence, the operator index must be specified in thecommands of the Iu interface to identify the target operator of the commands.

1. Run the ADD RNCBASIC command to add the basic data of the RNC. In this step, setNetworking Sharing Support to specify whether the RNC supports network sharing. YESindicates that the network sharing is supported and NO indicates that network sharing isnot supported. When the parameter is set to YES, Max Cn Operator Num must be set.

2. Run the ADD CNOPERATOR command to configure the operator that the RNC serves.To configure more operators, run this command repeatedly.

To implement operator-based configuration on the Iu interface, set the operator index whenrunning the following MML commands:

l SET IUFLEX: used to set whether the CN of the specified operator supports Iu-Flex.

l ADD CNNODE: used to add a CN node for the specified operator.

l ADD CELLSETUP: used to add the basic information of the cell for the specified operator.

l ADD LAC, ADD SAC, and ADD RAC: used to set the information of a location area,service area, and routing area respectively for the specified operator.

l ADD MBMSSA: used to add an MBMS service area for the specified operator.

l ADD CBSADDR: used to add the CBS IP address for the specified operator.




Issue 03 (2008-08-30)

Configuration Restrictionl Before configuration on the Iu interface, the information of the RNC and operators must

be already configured. In addition, the RNC must support network sharing.

l If the values of Cn Operator Index specified through the ADD CNOPERATOR, SETIUFLEX, and ADD CNNODE commands are the same, you can infer that the operator-based Iu interface accesses the specified CN.

l It is recommended that Cn Operator Index in each of the previously listed Iu-related MMLcommands be set to the same value. When there are multiple operators, you need to run theIu-related MML commands for each operator, so as to implement the operator-based Iuconfiguration.

12.13 TRM Configuration GuidelinesThe Transmission Resource Management (TRM) of the RNC manages the transmissionresources of the interfaces, thus improving efficiency of resource utilization and guaranteeingthe Quality of Service (QoS). The RNC determines which type of bearer should be used forcurrent services, depending on certain conditions. These conditions are the service type, thepreset mapping between service types and transmission resources, and the utilization of thetransmission resources.

Background to TRM

Different types of service have different QoS requirements. For example, voice services requirehigh QoS but PS background services do not. Therefore, mapping services with different QoSrequirements onto different transmission resources helps achieve high efficiency of resourceutilization.

TRM Configuration Guidelines

Before the transport bearers are set up for radio links on the interfaces, the RNC applies fortransmission resources, makes admission decisions based on transmission resources, andallocates transmission resources.

Admission to transmission resources plays a role of admission decision. If the admission issuccessful, the RNC allocates transmission resources according to the TRM mapping tables. ForATM transport, the RNC applies for Connection IDs (CIDs) and AAL2 path bandwidthresources. For IP transport, the RNC applies for UDP ports and IP path bandwidth resources.

TRM Configuration Description

You can run the ADD TRMMAP command to configure the mapping between service typesand transmission resources.

A TRM mapping table is not interface-specific. One TRM mapping table can be used by multipleinterfaces. For example, if the TRM mapping table whose index is 1 and Transport Type isATM meets the requirements of Iub, Iur, and Iu-CS interfaces for transmission resources, thetable can be used by the Iub, Iur, and Iu-CS interfaces at the same time.

For the Iu-PS interface, only the mapping between the Per Hop Behavior (PHB) andDifferentiated Services Code Point (DSCP) is required.



12-55

CAUTIONThe preferred and candidate paths for a type of service must be different.

Typical TRM Configuration

The RNC can set up real-time services, such as common channels, RRC signaling, and voiceservices, over non-real-time paths when the real-time paths are faulty. This achieves the backupbetween real-time and non-real-time paths and enhances transmission reliability.

Table 12-21 and Table 12-22 describe the recommended settings of TRM mapping on the Iubinterface that is based on hybrid IP transport.

Table 12-21 Recommended PHB settings on the hybrid-IP-based Iub interface

PHB DSCP

EF 46

AF43 38

AF42 38

AF41 38

AF33 30

AF32 30

AF31 30

AF23 18

AF22 18

AF21 18

AF13 10

AF12 10

AF11 10

BE 0

Table 12-22 Recommended settings of TRM mapping on the hybrid-IP-based Iub interface

Service Type Preferred Path Candidate Path

Common channel HQ_IPRT LQ_IPRT

Signaling HQ_IPRT LQ_IPRT

AMR voice service HQ_IPRT LQ_IPRT




Issue 03 (2008-08-30)


R99 CS conversationalservice

HQ_IPRT LQ_IPRT

R99 CS streaming service HQ_IPRT LQ_IPRT

R99 PS conversationalservice

HQ_IPRT LQ_IPRT

R99 PS streaming service HQ_IPRT LQ_IPRT

R99 PS interactive service ofhigh priority

HQ_IPNRT LQ_IPNRT

R99 PS interactive service ofmedium priority

HQ_IPNRT LQ_IPNRT

R99 PS interactive service oflow priority

HQ_IPNRT LQ_IPNRT

R99 PS background service HQ_IPNRT LQ_IPNRT

HSDPA signaling HQ_IPHDRT LQ_IPHDRT

HSDPA conversationalservice

HQ_IPHDRT LQ_IPHDRT

HSDPA streaming service HQ_IPHDNRT LQ_IPHDNRT

HSDPA interactive serviceof high priority

LQ_IPHDNRT HQ_IPHDNRT

HSDPA interactive serviceof medium priority


HSDPA interactive serviceof low priority


HSDPA background service LQ_IPHDNRT HQ_IPHDNRT

HSUPA signaling HQ_IPHURT LQ_IPHURT

HSUPA conversationalservice

HQ_IPHURT LQ_IPHURT

HSUPA streaming service HQ_IPHURT LQ_IPHURT

HSUPA interactive serviceof high priority


HSUPA interactive serviceof medium priority


HSUPA interactive serviceof low priority


HSUPA background service LQ_IPHUNRT HQ_IPHUNRT



12-57

NOTE

HQ, standing for high QoS, refers to the path over private line of E1/T1. LQ, standing for low QoS, refersto the path over FE/GE.

The RNC can differentiate the admission priorities of paths of the same type. For example, ifboth options of the hybrid IP transport, that is, E1/T1 and FE/GE, carry real-time services,services are preferentially admitted to the E1/T1. When the E1/T1 is faulty, the services areadmitted to the FE/GE.

Table 12-23 and Table 12-24 describe the recommended settings of TRM mapping on the Iubinterface that is based on the ATM/IP dual stack.

Table 12-23 Recommended PHB settings on the ATM/IP-based Iub interface

PHB DSCP

EF 46

AF43 38

AF42 38

AF41 38

AF33 30

AF32 30

AF31 30

AF23 18

AF22 18

AF21 18

AF13 10

AF12 10

AF11 10

BE 0

Table 12-24 Recommended settings of TRM mapping on the ATM/IP-based Iub interface


Common channel ATMRT HQ_IPRT

Signaling ATMRT HQ_IPRT

Voice service ATMRT HQ_IPRT

R99 CS conversationalservice

ATMRT HQ_IPRT




Issue 03 (2008-08-30)


R99 CS streaming service ATMRT HQ_IPRT

R99 PS conversationalservice

ATMRT HQ_IPRT

R99 PS streaming service ATMRT HQ_IPRT

R99 PS interactive service ofhigh priority

ATMNRT HQ_IPNRT

R99 PS interactive service ofmedium priority

ATMNRT HQ_IPNRT

R99 PS interactive service oflow priority

ATMNRT HQ_IPNRT

R99 PS background service ATMNRT HQ_IPNRT

HSDPA signaling ATMHDRT HQ_IPHDRT

HSDPA conversationalservice

ATMHDRT HQ_IPHDRT

HSDPA streaming service ATMHDRT HQ_IPHDRT

HSDPA interactive serviceof high priority

HQ_IPHDNRT ATMHDNRT

HSDPA interactive serviceof medium priority

HQ_IPHDNRT ATMHDNRT

HSDPA interactive serviceof low priority

HQ_IPHDNRT ATMHDNRT

HSDPA background service HQ_IPHDNRT ATMHDNRT

HSUPA signaling ATMHURT HQ_IPHURT

HSUPA conversationalservice

ATMHURT HQ_IPHURT

HSUPA streaming service ATMHURT HQ_IPHURT

HSUPA interactive serviceof high priority

HQ_IPHUNRT ATMHUNRT

HSUPA interactive serviceof medium priority

HQ_IPHUNRT ATMHUNRT

HSUPA interactive serviceof low priority

HQ_IPHUNRT ATMHUNRT

HSUPA background service HQ_IPHUNRT ATMHUNRT



12-59

12.14 Activity Factor Configuration GuidelinesConfiguration of activity factors improves resource efficiency.

Background to and Principles of Activity FactorsServices are not always active. This sometimes leads to low efficiency of resource utilization.For the purpose of resource multiplexing, transmission resources should be reserved ascalculated by service bandwidth x activity factor when a service is initiated. The value of anactivity factor affects the quantity of services admitted.

Activity Factor Configuration Policy for Traffic TypesThe following policy for reserving the transmission resources is applicable to all interfaces:

l Signaling radio bearer: 3.4 kbit/s x activity factor

l Conversational and streaming services: MBR x activity factor. On the Iu-PS interface, theseservices are admitted at GBR x activity factor.

l Inactive and background services: GBR x activity factor

Note that MBR stands for Maximum Bit Rate and GBR stands for Guaranteed Bit Rate.

Activity Factor Application Policy for InterfacesBased on the requirements, you can run the ADD FACTORTABLE command to add an activityfactor table. The activity factor application policy for the interfaces is as follows:

l Each Iub interface is individually configured with activity factors.

l The Iu and Iur interfaces share activity factors within the RNC.

Table 12-25 describes the default settings of activity factors at the RNC.

Table 12-25 Default settings of activity factors

Service Type Activity Factor (%)

Common public channel (uplink anddownlink)

70

MBMS common channel (downlink) 100

Signaling (uplink and downlink) 15

AMR voice service (uplink and downlink) 70

R99 CS conversational service (uplink anddownlink)

100

R99 CS streaming service (uplink anddownlink)

100

R99 PS conversational service (uplink anddownlink)

70




Issue 03 (2008-08-30)

Service Type Activity Factor (%)

R99 PS streaming service (uplink anddownlink)

100

R99 PS interactive service (uplink anddownlink)

100

R99 PS background service (uplink anddownlink)

100

HSDPA signaling (downlink) 50

HSDPA conversational service (downlink) 70

HSDPA streaming service (downlink) 100

HSDPA interactive service (downlink) 100

HSDPA background service (downlink) 100

HSDPA signaling (uplink) 50

HSUPA conversational service (uplink) 70

HSUPA streaming service (uplink) 100

HSUPA interactive service (uplink) 100

HSUPA background service (uplink) 100



12-61

RNC Initial Configuration Guide

Documents

Transcript of RNC Initial Configuration Guide