RNC Initial Configuration Guide

RNC V200R011
Initial Configuration Guide

Issue Date 06 2010-09-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 06 (2010-09-20)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
RNC Initial Configuration Guide
About This Document
About This Document

Purpose
This document describes the initial configuration of Huawei Radio Network Controller (RNC).
Version
The following table lists the product version related to this document. Product Name RNC Product Model BSC6810 Version V200R011
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.
Organization
1 Changes in the RNC Initial Configuration Guide This describes the changes in the RNC Initial Configuration Guide. 2 Introduction to RNC Initial Configuration RNC initial configuration refers to a process of data configuration through MML commands for the RNC to start to work. The process consists of the composition and execution of configuration scripts. 3 Procedure of RNC Initial Configuration This describes the procedure of RNC initial configuration. After the initial configuration, a script for loading is available. 4 Data Preparation for RNC Initial Configuration
Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
About This Document
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. 5 Configuring RNC Global Data This describes how to configure RNC global data. This is an essential step in RNC initial configuration. Global data configuration takes precedence over configuration of equipment data, interface data, and cell data. 6 Configuring RNC Equipment Data This describes how to configure RNC equipment data. The data includes RNC clock-related data, RNC time, basic data of the RSS subrack, and basic data of each RBS subrack. 7 Configuring Iub Interface Data (Initial) The Iub interface is the logical interface between the RNC and the NodeB. This topic describes how to add the transport network layer data on the Iub interface on the RNC side. 8 Configuring Iu-CS Interface Data (Initial) The Iu-CS is the logical interface between the RNC and the CS domain. The RNC exchanges the CS data with the CN through the Iu-CS interface. This topic describes how to add the transport network layer data on the Iu-CS interface. 9 Configuring Iu-PS Interface Data (Initial) The Iu-PS is the logical interface between the RNC and the PS domain. The RNC exchanges the packet domain data with the CN through the Iu-PS interface. This topic describes how to add the transport network layer data on the Iu-PS interface. 10 Configuring Iur Interface Data (Initial) An Iur interface is a logical interface between RNCs. This topic describes how to add the transport network layer data on the Iur interface. 11 Configuring Iu-BC Interface Data (Initial) An Iu-BC interface is a logical interface between the RNC and CBC. This topic describes how to add the transport network layer data on the Iu-BC interface. 12 Configuring Cell Data (Initial) This describes how to configure cell data of the radio network layer. The related activities are the quick setup of cells, the addition of inter-frequency neighboring cell relationships, intrafrequency neighboring cell relationships, and inter-RAT neighboring cell relationships, and switching all subracks to the online mode after the cell data configuration is complete. 13 Related Information for RNC Initial Configuration This reference part covers the concepts, principles, rules, and conventions that should be understood before data configuration.
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows.
iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2010-09-20)
About This Document
Symbol
Description Indicates a hazard with a high level of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional. Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Issue 06 (2010-09-20)
About This Document
Convention { x | y | ... }*
Description Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2010-09-20)
vi
Contents
Contents
About This Document...................................................................................................................iii 1 Changes in the RNC Initial Configuration Guide..............................................................1-1 2 Introduction to RNC Initial Configuration...........................................................................2-1
2.1 Definition of RNC Initial Configuration.........................................................................................................2-2 2.2 RNC Initial Configuration Tool......................................................................................................................2-2 2.3 Components of the RNC Initial Configuration Script.....................................................................................2-3 2.3.1 Example: Global Data in the RNC Initial Configuration Script............................................................2-4 2.3.2 Example: Equipment Data in the RNC Initial Configuration Script......................................................2-4 2.3.3 Example: Interface Data in the RNC Initial Configuration Script.........................................................2-6 2.3.4 Example: Cell Data in the RNC Initial Configuration Script...............................................................2-16 2.4 Conventions in Parameter Relationship Diagrams........................................................................................2-17
3 Procedure of RNC Initial Configuration...............................................................................3-1 4 Data Preparation for RNC Initial Configuration.................................................................4-1
4.1 Data Preparation for Initial Configuration......................................................................................................4-2 4.2 Global Data and Equipment Data of the RNC................................................................................................4-2 4.3 Data Negotiated Between RNC and Other Network Elements.......................................................................4-4 4.3.1 Data Negotiated on the Iub Interface (over ATM).................................................................................4-5 4.3.2 Data Negotiated on the Iub Interface (over IP)......................................................................................4-8 4.3.3 Data Negotiated on the Iub Interface (over ATM and IP)...................................................................4-13 4.3.4 Data Negotiated on the Iu-CS Interface (over ATM) ..........................................................................4-21 4.3.5 Data Negotiated on the Iu-CS Interface (over IP)................................................................................4-24 4.3.6 Data Negotiated on the Iu-PS Interface (over ATM)...........................................................................4-28 4.3.7 Data Negotiated on the Iu-PS Interface (over IP)................................................................................4-31 4.3.8 Data Negotiated on the Iur Interface (over ATM)...............................................................................4-35 4.3.9 Data Negotiated on the Iur Interface (over IP).....................................................................................4-38 4.3.10 Data Negotiated on the Iu-BC Interface (over ATM)........................................................................4-41 4.3.11 Data Negotiated on the Iu-BC Interface (over IP).............................................................................4-43 4.4 Cell Data on the RNC....................................................................................................................................4-44
5 Configuring RNC Global Data................................................................................................5-1

5.1 Example: Global Data in the RNC Initial Configuration Script.....................................................................5-2 5.2 Setting the RNC to Offline Mode (Initial)......................................................................................................5-3 Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
5.3 Adding Basic Data to the RNC (Initial)..........................................................................................................5-3 5.4 Adding OSP to the RNC (Initial)....................................................................................................................5-4 5.5 Adding RNC Global Location Data (Initial)...................................................................................................5-5 5.6 Adding a Local M3UA Entity (Initial)............................................................................................................5-7
6 Configuring RNC Equipment Data........................................................................................6-1

6.1 Example: Equipment Data in the RNC Initial Configuration Script...............................................................6-3 6.2 Setting RNC Equipment Description (Initial).................................................................................................6-4 6.3 Adding Basic Data of the RSS to the RNC (Initial)........................................................................................6-4 6.4 Adding Basic Data of the RBS to the RNC (Initial).......................................................................................6-6 6.5 Adding an EMU (Initial).................................................................................................................................6-6 6.6 Configuring RNC Clock Data (Initial)............................................................................................................6-7 6.7 Setting RNC Time (Initial)..............................................................................................................................6-8 6.8 Adding the IP Address of the EMS Server (Initial)........................................................................................6-9
7 Configuring Iub Interface Data (Initial)................................................................................7-1

7.1 Example: Iub Data in the RNC Initial Configuration Script...........................................................................7-2 7.2 Data Configuration Guidelines for the Iub Interface (over ATM)..................................................................7-5 7.2.1 Protocol Structure for the Iub Interface (over ATM).............................................................................7-5 7.2.2 Links on the Iub Interface (over ATM)..................................................................................................7-6 7.2.3 OM IPoA Data Configuration on the Iub Interface (over ATM)...........................................................7-7 7.3 Adding Data on the Iub Interface (Initial, over ATM)....................................................................................7-8 7.3.1 Adding Physical Layer Data (Initial, over ATM)..................................................................................7-9 7.3.2 Adding ATM Traffic Resources (Initial).............................................................................................7-13 7.3.3 Adding Control Plane Data on the Iub Interface (Initial, over ATM)..................................................7-13 7.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)........................7-16 7.3.5 Adding User Plane Data on the Iub Interface (Initial, over ATM)......................................................7-17 7.3.6 Adding an OM Channel on the Iub Interface (Initial, over ATM).......................................................7-19 7.4 Data Configuration Guidelines for the Iub Interface (over IP).....................................................................7-21 7.4.1 Protocol Stack on the Iub Interface (over IP).......................................................................................7-21 7.4.2 Links on the Iub Interface (over IP).....................................................................................................7-22 7.4.3 IP Addresses and Routes on the Iub Interface (over IP)......................................................................7-24 7.4.4 OM Channel Configuration on the Iub Interface (over IP)..................................................................7-26 7.5 Adding Data on the Iub Interface (Initial, over IP).......................................................................................7-29 7.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................7-30 7.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP).......................................................7-36 7.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)........................7-38 7.5.4 Adding User Plane Data on the Iub Interface (Initial, over IP)............................................................7-39 7.5.5 Adding an OM Channel on the Iub Interface (Initial, over IP)............................................................7-40 7.6 Data Configuration Guidelines for the Iub Interface (over ATM and IP).....................................................7-41 7.6.1 ATM/IP Hybrid Transport on the Iub Interface...................................................................................7-42 7.6.2 ATM/IP-Based Networking on the Iub Interface.................................................................................7-43 7.6.3 Hardware Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface...................7-44 7.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface...........................7-45 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2010-09-20)
Contents
7.6.5 IP Addresses and Routes on the Iub Interface (over IP)......................................................................7-46 7.6.6 OM Channel Configuration on the Iub Interface (over IP)..................................................................7-49 7.7 Adding Data on the Iub Interface (Initial, over ATM and IP)......................................................................7-51
8 Configuring Iu-CS Interface Data (Initial)............................................................................8-1

8.1 Example: Iu-CS Data in the RNC Initial Configuration Script.......................................................................8-2 8.2 Data Configuration Guidelines for the Iu-CS Interface (over ATM)..............................................................8-4 8.2.1 Protocol Structure for the Iu-CS Interface (over ATM).........................................................................8-4 8.2.2 Links on the Iu-CS Interface (over ATM)..............................................................................................8-5 8.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6...........................................................8-7 8.3 Adding Data on the Iu-CS Interface (Initial, over ATM)..............................................................................8-10 8.3.1 Adding Physical Layer Data (Initial, over ATM)................................................................................8-11 8.3.2 Adding ATM Traffic Resources (Initial).............................................................................................8-11 8.3.3 Adding Control Plane Data on the Iu-CS Interface (Initial, over ATM).............................................8-12 8.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)........................8-15 8.3.5 Adding User Plane Data on the Iu-CS Interface (Initial, over ATM)..................................................8-16 8.4 Data Configuration Guidelines for the Iu-CS Interface (over IP).................................................................8-18 8.4.1 Protocol Structure for the Iu-CS Interface (over IP)............................................................................8-18 8.4.2 Links on the Iu-CS interface (over IP).................................................................................................8-19 8.4.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6.........................................................8-20 8.5 Adding Data on the Iu-CS Interface (Initial, over IP)...................................................................................8-23 8.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................8-24 8.5.2 Adding Control Plane Data on the Iu-CS Interface (Initial, over IP)...................................................8-24 8.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)........................8-27 8.5.4 Adding User Plane Data on the Iu-CS Interface (Initial, over IP).......................................................8-29
9 Configuring Iu-PS Interface Data (Initial)............................................................................9-1

9.1 Example: Iu-PS Data in the RNC Initial Configuration Script.......................................................................9-2 9.2 Data Configuration Guidelines for the Iu-PS Interface (over ATM)..............................................................9-4 9.2.1 Protocol Structure for the Iu-PS Interface (over ATM).........................................................................9-4 9.2.2 Links on the Iu-PS Interface (over ATM) .............................................................................................9-5 9.2.3 IPoA Data Configuration on the Iu-PS User Plane (over ATM)........................................................... 9-6 9.3 Adding Data on the Iu-PS Interface (Initial, over ATM)................................................................................9-8 9.3.1 Adding Physical Layer Data on the Interface (Initial, with UOIa)........................................................9-8 9.3.2 Adding ATM Traffic Resources (Initial)...............................................................................................9-9 9.3.3 Adding Control Plane Data on the Iu-PS Interface (Initial, over ATM)..............................................9-10 9.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)........................9-12 9.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, over ATM)...................................................9-14 9.4 Data Configuration Guidelines for the Iu-PS Interface (over IP).................................................................9-15 9.4.1 Protocol Structure for the Iu-PS Interface (over IP).............................................................................9-15 9.4.2 Links on the Iu-PS Interface (over IP) ................................................................................................9-16 9.5 Adding Data on the Iu-PS Interface (Initial, over IP)...................................................................................9-17 9.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...................................................9-18 9.5.2 Adding Control Plane Data on the Iu-PS Interface (Initial, over IP)...................................................9-19 Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
RNC Initial Configuration Guide 9.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)........................9-22 9.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, over IP)........................................................9-23
10 Configuring Iur Interface Data (Initial).............................................................................10-1

10.1 Example: Iur Data in the RNC Initial Configuration Script........................................................................10-2 10.2 Data Configuration Guidelines for the Iur Interface (over ATM)...............................................................10-4 10.2.1 Protocol Structure for the Iur Interface (over ATM)..........................................................................10-4 10.2.2 Links on the Iur Interface (over ATM) .............................................................................................10-5 10.2.3 Configuration Guidelines for Static Relocation Routes over Iur.......................................................10-7 10.3 Adding Data on the Iur Interface (Initial, over ATM)................................................................................10-7 10.3.1 Adding Physical Layer Data (Initial, over ATM)..............................................................................10-8 10.3.2 Adding ATM Traffic Resources (Initial)...........................................................................................10-9 10.3.3 Adding Control Plane Data on the Iur Interface (Initial, over ATM)................................................10-9 10.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)....................10-11 10.3.5 Adding User Plane Data on the Iur Interface (Initial, over ATM)...................................................10-13 10.3.6 Adding a Path for Static SRNS Relocation (Initial).........................................................................10-14 10.4 Data Configuration Guidelines for the Iur Interface (over IP)..................................................................10-15 10.4.1 Protocol Stack on the Iur Interface (over IP)...................................................................................10-15 10.4.2 Links on the Iur Interface (over IP)..................................................................................................10-16 10.4.3 Configuration Guidelines for Static Relocation Routes over Iur.....................................................10-18 10.5 Adding Data on the Iur Interface (Initial, over IP)....................................................................................10-18 10.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP)...............................................10-19 10.5.2 Adding Control Plane Data on the Iur Interface (Initial, over IP)....................................................10-19 10.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)....................10-22 10.5.4 Adding User Plane Data on the Iur Interface (Initial, over IP)........................................................10-23 10.5.5 Adding a Path for Static SRNS Relocation (Initial).........................................................................10-24
11 Configuring Iu-BC Interface Data (Initial).......................................................................11-1

11.1 Example: Iu-BC Data in the RNC Initial Configuration Script..................................................................11-3 11.2 Data Configuration Guidelines for the Iu-BC Interface..............................................................................11-3 11.2.1 Protocol Structure for the Iu-BC Interface.........................................................................................11-4 11.2.2 Networking on the Iu-BC Interface....................................................................................................11-4 11.2.3 Links on the Iu-BC Interface..............................................................................................................11-5 11.2.4 IPoA Data Configuration on the Iu-BC Interface..............................................................................11-6 11.3 Adding Data on the Iu-BC Interface (Initial, over ATM)...........................................................................11-6 11.3.1 Adding Physical Layer Data (Initial, over ATM)..............................................................................11-7 11.3.2 Adding ATM Traffic Resources (Initial)...........................................................................................11-7 11.3.3 Adding IPoA Data on the Iu-BC Interface (Initial)............................................................................11-8 11.3.4 Adding SABP Data (Initial).............................................................................................................11-10 11.4 Data Configuration Guidelines for the Iu-BC Interface (Initial, over IP).................................................11-11 11.4.1 Protocol Structure for the Iu-BC Interface.......................................................................................11-11 11.4.2 Networking on the Iu-BC Interface..................................................................................................11-12 11.5 Adding Data on the Iu-BC Interface (Initial, over IP)..............................................................................11-13
Issue 06 (2010-09-20)
Contents
12 Configuring Cell Data (Initial)............................................................................................12-1

12.1 Example: Cell Data in the RNC Initial Configuration Script......................................................................12-2 12.2 Quickly Setting Up a Cell (Initial)..............................................................................................................12-3 12.3 Adding an Intra-Frequency Neighboring Cell (Initial)...............................................................................12-4 12.4 Adding an Inter-Frequency Neighboring Cell (Initial)...............................................................................12-6 12.5 Adding a Neighboring GSM Cell (Initial)..................................................................................................12-8 12.6 Setting the RNC to Online Mode (Initial)...................................................................................................12-9
13 Related Information for RNC Initial Configuration.......................................................13-1

13.1 Types of RNC Optical Ports........................................................................................................................13-3 13.2 Introduction to RAN Time Synchronization...............................................................................................13-3 13.3 Numbering Schemes of the RNC................................................................................................................13-3 13.3.1 RNC ID..............................................................................................................................................13-4 13.3.2 RNC Subrack Number.......................................................................................................................13-5 13.3.3 ATM Traffic Record Index................................................................................................................13-5 13.3.4 RNC Transmission Resource Mapping Record Index.......................................................................13-6 13.3.5 RNC Activity Factor Table Index......................................................................................................13-6 13.3.6 SAAL Link Number...........................................................................................................................13-6 13.3.7 SCTP Link Number............................................................................................................................13-7 13.3.8 Adjacent Node ID...............................................................................................................................13-8 13.3.9 MTP3/M3UA DSP Index...................................................................................................................13-8 13.3.10 Signaling Link Set Index..................................................................................................................13-8 13.3.11 CN Node ID.....................................................................................................................................13-9 13.3.12 Local Cell ID..................................................................................................................................13-10 13.3.13 Logical Cell ID...............................................................................................................................13-10 13.3.14 Common Physical Channel ID.......................................................................................................13-10 13.3.15 Common Transport Channel ID.....................................................................................................13-12 13.3.16 GSM Cell ID..................................................................................................................................13-13 13.3.17 NCP and CCP Number...................................................................................................................13-13 13.3.18 NRI.................................................................................................................................................13-13 13.4 Area Identifiers..........................................................................................................................................13-14 13.4.1 PLMN ID..........................................................................................................................................13-14 13.4.2 LA Identifiers...................................................................................................................................13-15 13.4.3 SA Identifiers...................................................................................................................................13-15 13.4.4 RA Identifiers...................................................................................................................................13-16 13.4.5 URA Identifier..................................................................................................................................13-16 13.4.6 PLMN Value Tag.............................................................................................................................13-16 13.5 External Specifications for the RNC.........................................................................................................13-17 13.5.1 Specifications for Traffic on RNC Boards.......................................................................................13-18 13.5.2 RNC Capability for SAAL...............................................................................................................13-19 13.5.3 RNC Capability for SCTP................................................................................................................13-19 13.5.4 RNC Capability for NodeBs............................................................................................................13-19 13.5.5 RNC Capability for MTP3...............................................................................................................13-19 Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
RNC Initial Configuration Guide 13.5.6 RNC Capability for M3UA..............................................................................................................13-20 13.5.7 RNC Capability for AAL2 Paths and AAL2 Routes.......................................................................13-20 13.5.8 RNC Capability for IP Paths and IP Routes.....................................................................................13-20 13.5.9 RNC Capability for IPoA.................................................................................................................13-21 13.5.10 Specifications for Channels in a Cell.............................................................................................13-21 13.5.11 Specifications for Neighboring Cells.............................................................................................13-23
13.6 Physical Layer Data Configuration Guidelines.........................................................................................13-24 13.6.1 Interface Boards Applicable to Terrestrial Interfaces......................................................................13-24 13.6.2 Upper-Layer Applications Supported by Interface Boards..............................................................13-25 13.6.3 Numbering of Links Carried on AOUa Optical Ports......................................................................13-26 13.6.4 Ports on the AEUa/AOUa................................................................................................................13-29 13.6.5 Configuration Requirements for E1/T1 Links and IMA Links........................................................13-31 13.6.6 Configuration Specifications for ATM-Based Ports........................................................................13-31 13.6.7 Requirements of PPP/MLPPP Configuration..................................................................................13-32 13.7 ATM Transport.........................................................................................................................................13-33 13.7.1 UNI Mode........................................................................................................................................13-33 13.7.2 Fractional ATM................................................................................................................................13-34 13.7.3 Timeslot Cross Connection..............................................................................................................13-36 13.7.4 IMA Mode........................................................................................................................................13-37 13.8 PVC Parameters of the RNC.....................................................................................................................13-39 13.8.1 VPI and VCI.....................................................................................................................................13-39 13.8.2 Service Type.....................................................................................................................................13-40 13.8.3 Traffic Parameters............................................................................................................................13-41 13.8.4 ATM Traffic Resource Configuration Guidelines...........................................................................13-42 13.9 AAL2 Configuration Guidelines...............................................................................................................13-42 13.9.1 Working Principles of AAL2 Paths.................................................................................................13-43 13.9.2 AAL2 Route.....................................................................................................................................13-43 13.10 MTP3/M3UA Configuration Guidelines................................................................................................13-44 13.10.1 Types of and Specifications for the MTP3/M3UA DSPs..............................................................13-44 13.10.2 MTP3/M3UA DSP Index...............................................................................................................13-45 13.10.3 Signaling Route Mask and Signaling Link Mask...........................................................................13-45 13.10.4 Configuration Guidelines for MTP3/M3UA..................................................................................13-46 13.10.5 Adjacent Node ID...........................................................................................................................13-47 13.11 Cell-Related Concepts.............................................................................................................................13-47 13.11.1 Definitions of Sector, Carrier, and Cell..........................................................................................13-48 13.11.2 Definitions of Local Cell and Logical Cell....................................................................................13-49 13.11.3 Logical Cell Model.........................................................................................................................13-49 13.11.4 Areas of Logical Cells....................................................................................................................13-50 13.11.5 Definition of Neighboring Cell......................................................................................................13-50 13.12 TRM Configuration Guidelines..............................................................................................................13-50 13.13 Activity Factor Configuration Guidelines...............................................................................................13-51
xii
Issue 06 (2010-09-20)
Figures
Figures
Figure 2-1 Interface of the LMT..........................................................................................................................2-3 Figure 2-2 Example of the parameter relationship diagram...............................................................................2-17 Figure 5-1 Parameter relationship in the addition of the global location data.....................................................5-6 Figure 7-1 Protocol stack for the ATM-based Iub interface................................................................................7-5 Figure 7-2 Links on the ATM-based Iub interface...............................................................................................7-6 Figure 7-3 IPoA PVCs from the RNC to NodeBs................................................................................................7-8 Figure 7-4 Parameter relationship in the addition of the SAAL link.................................................................7-14 Figure 7-5 Parameter relationship in the addition of the adjacent node.............................................................7-15 Figure 7-6 Parameter relationship in the addition of the AAL2 path in the ATM-based interface...................7-18 Figure 7-7 Parameter relationship in the addition of the IPoA PVC..................................................................7-19 Figure 7-8 Parameter relationship in the addition of the OM IP address of the NodeB in ATM transport mode .............................................................................................................................................................................7-20 Figure 7-9 Protocol stack for IP transport on the Iub interface..........................................................................7-22 Figure 7-10 Links on the Iub interface (over IP)................................................................................................7-23 Figure 7-11 Layer 2 networking on the Iub interface.........................................................................................7-24 Figure 7-12 Layer 3 networking on the Iub interface.........................................................................................7-25 Figure 7-13 Example of routing between the M2000 and the NodeB through the RNC...................................7-27 Figure 7-14 Example of routing between the M2000 and the NodeB not through the RNC.............................7-29 Figure 7-15 Parameter relationship in the addition of the SCTP link................................................................7-36 Figure 7-16 Parameter relationship in the addition of the IP adjacent node......................................................7-36 Figure 7-17 Parameter relationship in the addition of the port data...................................................................7-37 Figure 7-18 Parameter relationship in the addition of the IP path.....................................................................7-40 Figure 7-19 ATM/IP dual stack-based networking............................................................................................7-43 Figure 7-20 Typical configuration of boards in the RSS subrack for ATM/IP hybrid transport.......................7-44 Figure 7-21 Typical configuration of boards in an RBS subrack for ATM/IP hybrid transport........................7-45 Figure 7-22 Layer 2 networking on the Iub interface.........................................................................................7-47 Figure 7-23 Layer 3 networking on the Iub interface.........................................................................................7-47 Figure 7-24 Example of routing between the M2000 and the NodeB through the RNC...................................7-49 Figure 7-25 Example of routing between the M2000 and the NodeB not through the RNC.............................7-51 Figure 8-1 Protocol stack for the ATM-based Iu-CS interface............................................................................8-5 Figure 8-2 Links on the Iu-CS Interface (over ATM)..........................................................................................8-6 Figure 8-3 Example of connections between the MSC server and the RNC.......................................................8-7 Figure 8-4 Iu-CS interface in the 3GPP R4/R5/R6..............................................................................................8-8 Figure 8-5 Example of the topology on the Iu-CS interface in the 3GPP R4/R5/R6...........................................8-8 Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Figures
RNC Initial Configuration Guide Figure 8-6 Protocol stack for the ATM-based Iu-CS interface............................................................................8-9
Figure 8-7 Protocol stack for the IP-based Iu-CS interface.................................................................................8-9 Figure 8-8 Parameter relationship in the addition of the MTP3 link................................................................. 8-13 Figure 8-9 Parameter relationship in the addition of the CN node.....................................................................8-13 Figure 8-10 Parameter relationship in the addition of the AAL2 path and the AAL2 route..............................8-17 Figure 8-11 Protocol stack for the IP-based Iu-CS interface............................................................................. 8-18 Figure 8-12 Links on the Iu-CS interface (over IP)........................................................................................... 8-19 Figure 8-13 Example of connections between the MSC server and the RNC................................................... 8-20 Figure 8-14 Iu-CS interface in the 3GPP R4/R5/R6..........................................................................................8-21 Figure 8-15 Example of the topology on the Iu-CS interface in the 3GPP R4/R5/R6.......................................8-21 Figure 8-16 Protocol stack for the ATM-based Iu-CS interface........................................................................8-22 Figure 8-17 Protocol stack for the IP-based Iu-CS interface............................................................................. 8-22 Figure 8-18 Parameter relationship in the addition of the M3UA link.............................................................. 8-25 Figure 8-19 Parameter relationship in the addition of the CN node...................................................................8-26 Figure 9-1 Protocol stack for the ATM-based Iu-PS interface.............................................................................9-5 Figure 9-2 Links on the Iu-PS interface (over ATM)...........................................................................................9-6 Figure 9-3 IPoA PVC on the Iu-PS interface.......................................................................................................9-7 Figure 9-4 Parameter relationship in the addition of the MTP3 link................................................................. 9-11 Figure 9-5 Parameter relationship in the addition of the CN node.....................................................................9-11 Figure 9-6 Parameter relationship in the addition of the IP path and IP route on the ATM-based Iu-PS interface. .............................................................................................................................................................................9-14 Figure 9-7 Protocol stack for the IP-based Iu-PS interface................................................................................9-16 Figure 9-8 Links on the Iu-PS interface (over IP)..............................................................................................9-17 Figure 9-9 Parameter relationship in the addition of the M3UA link................................................................ 9-19 Figure 9-10 Parameter relationship in the addition of the CN node...................................................................9-20 Figure 10-1 Protocol stack for the ATM-based Iur interface.............................................................................10-5 Figure 10-2 Links on the Iur interface (over ATM)...........................................................................................10-6 Figure 10-3 IP route configuration on the Iur interface..................................................................................... 10-7 Figure 10-4 Parameter relationship in the addition of the MTP3 link.............................................................10-10 Figure 10-5 Parameter relationship in the addition of the AAL2 path.............................................................10-13 Figure 10-6 Protocol stack for IP transport on the Iur interface.......................................................................10-16 Figure 10-7 Links on the Iur Interface (over IP)..............................................................................................10-17 Figure 10-8 IP route configuration on the Iur interface...................................................................................10-18 Figure 10-9 Parameter relationship in the addition of the M3UA link............................................................10-20 Figure 11-1 Protocol stack for the Iu-BC interface............................................................................................11-4 Figure 11-2 RNC-CBC networking through an SGSN......................................................................................11-5 Figure 11-3 Links on the Iu-BC interface..........................................................................................................11-5 Figure 11-4 IPoA configuration on the Iu-BC interface networked through an SGSN.....................................11-6 Figure 11-5 Parameter relationship in the addition of the IPoA PVC................................................................11-9 Figure 11-6 Parameter relationship in the addition of the SABP data.............................................................11-10 Figure 11-7 Protocol stack for the Iu-BC interface .........................................................................................11-12 Figure 11-8 IP networking based on the data network.....................................................................................11-12 Figure 12-1 Parameter relationship in the quick addition of a cell.................................................................... 12-3 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2010-09-20)
Figures
Figure 12-2 Parameter relationship in the addition of an intra-frequency neighboring cell that belongs to the local RNC.....................................................................................................................................................................12-5 Figure 12-3 Parameter relationship in the addition of an intra-frequency neighboring cell that belongs to a neighboring RNC................................................................................................................................................12-5 Figure 12-4 Parameter relationship in the addition of an inter-frequency neighboring cell that belongs to the local RNC.....................................................................................................................................................................12-7 Figure 12-5 Parameter relationship in the addition of an inter-frequency neighboring cell that belongs to a neighboring RNC................................................................................................................................................12-7 Figure 12-6 Parameter relationship in the addition of the neighboring GSM cell.............................................12-9 Figure 13-1 Numbered subracks........................................................................................................................13-5 Figure 13-2 Components of the PLMN ID......................................................................................................13-15 Figure 13-3 Components of the LAI................................................................................................................13-15 Figure 13-4 Components of the SAI................................................................................................................13-16 Figure 13-5 Components of the RAI................................................................................................................13-16 Figure 13-6 Example of planning the value ranges of PLMN value tags........................................................13-17 Figure 13-7 Relationship between the physical links configured on the AEUa and AOUa boards and the E1/T1 physical ports.....................................................................................................................................................13-30 Figure 13-8 Mapping between the ATM cell and the E1 timeslots in UNI mode...........................................13-34 Figure 13-9 Fractional ATM mode..................................................................................................................13-34 Figure 13-10 Fractional ATM function............................................................................................................13-35 Figure 13-11 Principles of timeslot cross connection......................................................................................13-36 Figure 13-12 Principles of timeslot cross connection......................................................................................13-37 Figure 13-13 Working principles of the IMA mode........................................................................................13-38 Figure 13-14 IMA frame..................................................................................................................................13-38 Figure 13-15 Relationship between VC and VP..............................................................................................13-40 Figure 13-16 Relationship between an AAL2 path and AAL2 connections....................................................13-43 Figure 13-17 Example of the AAL2 route.......................................................................................................13-43 Figure 13-18 Relation between signaling link mask and signaling route mask...............................................13-46 Figure 13-19 Relations between sector, frequency, and cell............................................................................13-48 Figure 13-20 Logical cell configuration model................................................................................................13-49
Issue 06 (2010-09-20)
xv
Tables
Tables
Table 4-1 Global data...........................................................................................................................................4-2 Table 4-2 Equipment data.....................................................................................................................................4-3 Table 4-3 MSP data..............................................................................................................................................4-4 Table 4-4 Basic data of the NodeB.......................................................................................................................4-5 Table 4-5 Data on the physical layer - 1...............................................................................................................4-5 Table 4-6 Data on the physical layer - 2...............................................................................................................4-6 Table 4-7 Data of the IMA group.........................................................................................................................4-6 Table 4-8 Data on the control plane.....................................................................................................................4-7 Table 4-9 Data on the user plane..........................................................................................................................4-7 Table 4-10 Data of the OM channel.....................................................................................................................4-8 Table 4-11 Basic data of the NodeB.....................................................................................................................4-9 Table 4-12 Data on the physical layer - 1.............................................................................................................4-9 Table 4-13 Data on the physical layer - 2.............................................................................................................4-9 Table 4-14 Data on the data link layer...............................................................................................................4-10 Table 4-15 Data on the physical layer - 3...........................................................................................................4-10 Table 4-16 Data on the control plane.................................................................................................................4-11 Table 4-17 Data on the user plane......................................................................................................................4-12 Table 4-18 Data of the OM channel...................................................................................................................4-12 Table 4-19 Iub data transmission mode planning...............................................................................................4-13 Table 4-20 Basic data of the NodeB...................................................................................................................4-14 Table 4-21 Data on the physical layer - 1...........................................................................................................4-15 Table 4-22 Data on the physical layer - 2...........................................................................................................4-15 Table 4-23 Data of the IMA group.....................................................................................................................4-15 Table 4-24 Data on the physical layer - 1...........................................................................................................4-16 Table 4-25 Data on the physical layer - 2...........................................................................................................4-16 Table 4-26 Data on the data link layer...............................................................................................................4-17 Table 4-27 Data on the physical layer - 3...........................................................................................................4-17 Table 4-28 Data on the control plane.................................................................................................................4-18 Table 4-29 Data on the control plane.................................................................................................................4-18 Table 4-30 Data on the user plane......................................................................................................................4-19 Table 4-31 Data on the user plane......................................................................................................................4-20 Table 4-32 Data of the OM channel...................................................................................................................4-20 Table 4-33 Data of the OM channel...................................................................................................................4-21 Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Tables
RNC Initial Configuration Guide Table 4-34 Basic data of the CS domain............................................................................................................4-22 Table 4-35 Data on the physical layer - 2...........................................................................................................4-22 Table 4-36 Data of the IMA group.....................................................................................................................4-23 Table 4-37 Data about timers.............................................................................................................................4-23 Table 4-38 Data on the Iu-CS control plane.......................................................................................................4-23 Table 4-39 Data on the Iu-CS user plane...........................................................................................................4-24 Table 4-40 Basic data of the CS domain............................................................................................................4-25 Table 4-41 Data on the physical layer - 2...........................................................................................................4-25 Table 4-42 Data on the data link layer...............................................................................................................4-26 Table 4-43 Data on the physical layer - 3...........................................................................................................4-26 Table 4-44 Data on the Iu-CS control plane.......................................................................................................4-27 Table 4-45 Data on the Iu-CS user plane...........................................................................................................4-28 Table 4-46 Basic data of the PS domain.............................................................................................................4-28 Table 4-47 Data on the physical layer - 2...........................................................................................................4-29 Table 4-48 Data about timers.............................................................................................................................4-30 Table 4-49 Data on the Iu-PS control plane.......................................................................................................4-30 Table 4-50 Data on the Iu-PS user plane............................................................................................................4-31 Table 4-51 Basic data of the PS domain.............................................................................................................4-31 Table 4-52 Data on the physical layer - 2...........................................................................................................4-32 Table 4-53 Data on the data link layer...............................................................................................................4-33 Table 4-54 Data on the physical layer - 3...........................................................................................................4-33 Table 4-55 Data on the Iu-PS control plane.......................................................................................................4-33 Table 4-56 Data on the Iu-PS user plane............................................................................................................4-35 Table 4-57 Basic data of the neighboring RNC.................................................................................................4-35 Table 4-58 Data on the physical layer - 2...........................................................................................................4-36 Table 4-59 Data about timers.............................................................................................................................4-36 Table 4-60 Data on the Iur control plane............................................................................................................4-37 Table 4-61 Data on the Iur user plane................................................................................................................4-37 Table 4-62 Basic data of the neighboring RNC.................................................................................................4-38 Table 4-63 Data on the physical layer - 2...........................................................................................................4-38 Table 4-64 Data on the data link layer...............................................................................................................4-39 Table 4-65 Data on the physical layer - 3...........................................................................................................4-39 Table 4-66 Data on the Iur control plane............................................................................................................4-40 Table 4-67 Data on the Iur user plane................................................................................................................4-41 Table 4-68 Data on the physical layer - 2...........................................................................................................4-41 Table 4-69 Data Negotiated on the Iu-BC Interface...........................................................................................4-42 Table 4-70 Data on the physical layer - 3...........................................................................................................4-43 Table 4-71 Data Negotiated on the Iu-BC Interface...........................................................................................4-43 Table 4-72 Data for quick addition of a cell.......................................................................................................4-44 Table 4-73 Intra-/inter-frequency neighboring cells...........................................................................................4-45 Table 4-74 Basic data of inter-/intra-frequency neighboring cells.....................................................................4-45 Table 4-75 Neighboring GSM cells....................................................................................................................4-45
xviii
Issue 06 (2010-09-20)
Tables
Table 4-76 Basic data of neighboring GSM cells...............................................................................................4-46 Table 7-1 Data carried on SAAL links of UNI type.............................................................................................7-7 Table 7-2 TRM mapping data to be negotiated and planned..............................................................................7-16 Table 7-3 Activity factor to be negotiated and planned..................................................................................... 7-17 Table 7-4 Data carried on SCTP links................................................................................................................7-23 Table 7-5 IP addresses on the Iub interface........................................................................................................7-25 Table 7-6 Route on the Iub Interface..................................................................................................................7-26 Table 7-7 Routes for the connection between the M2000 and the NodeB through the RNC............................ 7-27 Table 7-8 Routes for the connection between the M2000 and the NodeB not through the RNC......................7-29 Table 7-9 TRM mapping data to be negotiated and planned..............................................................................7-39 Table 7-10 Activity factor to be negotiated and planned................................................................................... 7-39 Table 7-11 IP addresses on the Iub interface......................................................................................................7-48 Table 7-12 Route on the Iub Interface................................................................................................................7-49 Table 7-13 Routes for the connection between the M2000 and the NodeB through the RNC.......................... 7-50 Table 7-14 Routes for the connection between the M2000 and the NodeB not through the RNC....................7-51 Table 8-1 Differences between signaling point configuration in R99 and that in R4/R5/R6.............................8-10 Table 8-2 TRM mapping data to be negotiated and planned..............................................................................8-15 Table 8-3 Activity factor to be negotiated and planned..................................................................................... 8-15 Table 8-4 Differences between signaling point configuration in R99 and that in R4/R5/R6.............................8-23 Table 8-5 TRM mapping data to be negotiated and planned..............................................................................8-28 Table 8-6 Activity factor to be negotiated and planned..................................................................................... 8-28 Table 9-1 IPoA data on the user plane of the ATM-based Iu-PS interface..........................................................9-7 Table 9-2 TRM mapping data to be negotiated and planned..............................................................................9-13 Table 9-3 Activity factor to be negotiated and planned..................................................................................... 9-13 Table 9-4 TRM mapping data to be negotiated and planned..............................................................................9-22 Table 9-5 Activity factor to be negotiated and planned..................................................................................... 9-23 Table 10-1 TRM mapping data to be negotiated and planned..........................................................................10-12 Table 10-2 Activity factor to be negotiated and planned.................................................................................10-12 Table 10-3 TRM mapping data to be negotiated and planned..........................................................................10-23 Table 10-4 Activity factor to be negotiated and planned.................................................................................10-23 Table 11-1 IPoA data on the Iu-BC interface.....................................................................................................11-6 Table 13-1 Types of RNC optical ports..............................................................................................................13-3 Table 13-2 Suggested numbering of common physical channels....................................................................13-11 Table 13-3 Suggested numbering of common transport channels...................................................................13-12 Table 13-4 Traffic specifications for physical links and ports.........................................................................13-18 Table 13-5 Specifications for the traffic on boards..........................................................................................13-19 Table 13-6 IDs of and specifications for common physical channels..............................................................13-21 Table 13-7 IDs of and specifications for common transport channels.............................................................13-22 Table 13-8 Default power specifications for cells and channels......................................................................13-23 Table 13-9 Recommended ATM interface boards...........................................................................................13-25 Table 13-10 Recommended IP interface boards...............................................................................................13-25 Table 13-11 Upper-layer applications supported by ATM interface boards....................................................13-26 Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Tables
RNC Initial Configuration Guide Table 13-12 Upper-layer applications supported by IP interface boards.........................................................13-26 Table 13-13 Relationship between link numbers of AOUa optical ports and transmission equipment numbers ...........................................................................................................................................................................13-27 Table 13-14 Restrictions on the specifications of physical links for the AEUa and AOUa boards.................13-30 Table 13-15 Methods of configuring fractional ATM links and fractional IMA links....................................13-36 Table 13-16 Types of service...........................................................................................................................13-40 Table 13-17 Features of different ATM services.............................................................................................13-40 Table 13-18 ATM traffic parameters................................................................................................................13-41 Table 13-19 Recommended service types for links on different interfaces.....................................................13-42 Table 13-20 Types of and specifications for the DSPs....................................................................................13-44
xx
Issue 06 (2010-09-20)
1 Changes in the RNC Initial Configuration Guide
Changes in the RNC Initial Configuration Guide

This describes the changes in the RNC Initial Configuration Guide.
06(2010-09-20)
This is the fifth commercial release. Compared with issue 05(2010-03-25) of V200R011, no information is added or deleted. This issue incorporates the changes described in the following table: Topic 8.5.2 Adding Control Plane Data on the IuCS Interface (Initial, over IP) 7.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP) 9.5.2 Adding Control Plane Data on the IuPS Interface (Initial, over IP) 10.5.2 Adding Control Plane Data on the Iur Interface (Initial, over IP) Change The note of MML command ADD SCTPLNK is added: If multiple SCTP links use the same source IP address and destination IP address, adhere to the following principle when configuring these SCTP links: The sum of the source port number and the destination port number of a newly configured SCTP link is eight greater than or smaller than the sum of the source port number and the destination port number of any configured SCTP link. The RINT shown in the preceding figure refers to ATM interface boards of the RNC. The UOIa (UOIa_ATM) board is recommended to be used for the ATM-based Iu-CS interface. If other interface boards need to be used, contact local Huawei office for technical support.
8.2.2 Links on the Iu-CS Interface (over ATM)
05(2010-03-25)
This is the fourth commercial release.
Issue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
Compared with issue 04(2009-10-31) of V200R011, this issue includes the following new topics: 4.1 Data Preparation for Initial Configuration Compared with issue 04(2009-10-31) of V200R011, this issue does not incorporate any change. Compared with issue 04(2009-10-31) of V200R011, this issue does not exclude any topic.
04(2009-10-31)
This is the third commercial release. Compared with issue 03 (2009-08-25) of V200R011, no information is added or deleted. This issue incorporates the changes described in the following table: Topic 9.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, over ATM) 9.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, over IP) Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with FG2a/GOUa) 7.3.2 Adding ATM Traffic Resources (Initial) Change Delete the following description: 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. Add the detailed configuration information of link aggregation. Add the note of one RNC can be configured with 500 ATM traffic records.
03(2009-08-25)
This is the second commercial release. Compared with issue 02 (2009-03-25) of V200R011, no information is added or deleted. This issue incorporates the changes described in the following table: Topic 10.3.6 Adding a Path for Static SRNS Relocation (Initial) Change The Next hop IP address needed to be set when running the ADD IPRT command is changed from the service IP address to the gateway IP address of the SGSN.
02 (2009-03-25)
This is the first commercial release. Compared with issue 01 (2009-02-10) of V200R011, no information is added or deleted. This issue incorporates the changes described in the following table:
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 06 (2010-09-20)
Topic 13.5.2 RNC Capability for SAAL
Change The IPoA PVC specifications supported by the AEUa, AOUa, and UOIa (UOIa_ATM) boards are modified. The SCTP link specifications supported by the SPUa board are modified. The MTP3 signaling link specifications supported by the BSC6810 are modified. The M3UA signaling link specifications supported by the BSC6810 are modified. The IPoA specifications supported by the AEUa, AOUa, and UOIa boards are modified.
13.5.3 RNC Capability for SCTP 13.5.5 RNC Capability for MTP3 13.5.6 RNC Capability for M3UA 13.5.9 RNC Capability for IPoA
01 (2009-02-10)
This is the field trial release. Compared with issue 04 (2008-08-30) of V200R010, this issue includes the following new topics: l l l l l 11.4 Data Configuration Guidelines for the Iu-BC Interface (Initial, over IP) 11.4.1 Protocol Structure for the Iu-BC Interface 11.4.2 Networking on the Iu-BC Interface 11.5 Adding Data on the Iu-BC Interface (Initial, over IP) 6.5 Adding an EMU (Initial)
Compared with issue 04 (2008-08-30) of V200R010, this issue excludes the following topics: Configurations of RAN Sharing Compared with issue 04 (2008-08-30) of V200R010, this issue incorporates the changes described in the following table: Topic 5.3 Adding Basic Data to the RNC (Initial) 6.3 Adding Basic Data of the RSS to the RNC (Initial) 6.4 Adding Basic Data of the RBS to the RNC (Initial) Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with FG2a/GOUa)
Issue 06 (2010-09-20)
Change The steps for configuring the operator information are modified. The steps for adding the basic data of the RSS subrack to the RNC are modified. The steps for adding the basic data of the RBS subrack to the RNC are modified. The steps for configuring the link aggregation mode are added.
1-3
Topic 7.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) 7.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) l 7.3.5 Adding User Plane Data on the Iub Interface (Initial, over ATM) l 7.5.4 Adding User Plane Data on the Iub Interface (Initial, over IP) l 8.3.5 Adding User Plane Data on the IuCS Interface (Initial, over ATM) l 8.5.4 Adding User Plane Data on the IuCS Interface (Initial, over IP) l 9.3.5 Adding User Plane Data on the IuPS Interface (Initial, over ATM) l 9.5.4 Adding User Plane Data on the IuPS Interface (Initial, over IP) l 10.3.5 Adding User Plane Data on the Iur Interface (Initial, over ATM) l 10.5.4 Adding User Plane Data on the Iur Interface (Initial, over IP) 13.12 TRM Configuration Guidelines 13.13 Activity Factor Configuration Guidelines 8.5.2 Adding Control Plane Data on the IuCS Interface (Initial, over IP) 8.4.2 Links on the Iu-CS interface (over IP) 7.3.3 Adding Control Plane Data on the Iub Interface (Initial, over ATM) 7.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP)
Change The ADD FACTORTABLE command is replaced by ADD TRMFACTOR. The steps for configuring the threshold table for loading sharing between the primary and secondary paths are added. The ADD PORTCTRLER command is deleted.
The description of the TRM configuration guidelines is modified. The description of the activity factor configuration guidelines is modified. The settings of the parameters in the ADD N7DPC command are modified. The description of the M3UA is modified. The settings of the NodeB overload congestion algorithm parameters are added. The settings of the NodeB overload congestion algorithm parameters are added.
1-4
Issue 06 (2010-09-20)
2 Introduction to RNC Initial Configuration
Introduction to RNC Initial Configuration
About This Chapter

RNC initial configuration refers to a process of data configuration through MML commands 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 hardware configuration of the RNC, network planning, and negotiation between the RNC and other equipment. 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. For details, refer to the RNC Commissioning Guide. The correct initial configuration data is a prerequisite for the RNC to start to run. Modification of data during the proper running of the RNC is not initial configuration. For details about data reconfiguration, refer to the RAN Reconfiguration Guide. 2.1 Definition of RNC Initial Configuration RNC 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. 2.2 RNC Initial Configuration Tool The RNC initial configuration tool is a text editor that creates the RNC initial configuration script through the addition, deletion, and modification of MML commands when the MML commands are available. 2.3 Components of the RNC Initial Configuration Script A complete RNC initial configuration script consists of global data, equipment data, interface data, and cell data. 2.4 Conventions in Parameter Relationship Diagrams Parameter relationship diagrams show the relationships between the parameters of MML commands.
Issue 06 (2010-09-20)
2-1
2.1 Definition of RNC Initial Configuration

RNC 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 hardware configuration of the RNC, network planning, and negotiation between the RNC and other equipment. 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. Modification of data during the proper running of the RNC is not initial configuration. For details about data reconfiguration, 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 RNC host to take effect. For details, refer to Loading RNC Software and Data Files.
2.2 RNC Initial Configuration Tool

The RNC initial configuration tool is a text editor that creates the RNC initial configuration script through the addition, deletion, and modification of MML commands when the MML commands are available. The Local Maintenance Terminal (LMT) is an RNC initial configuration tool. Figure 2-1 shows the interface of the LMT.
2-2
Issue 06 (2010-09-20)
Figure 2-1 Interface of the LMT
2.3 Components of the RNC Initial Configuration Script

A complete RNC initial configuration script consists of global data, equipment data, interface data, and cell data. 2.3.1 Example: Global Data in the RNC Initial Configuration Script This describes global data in the RNC initial configuration script. The global data includes the basic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, global location data, and data of the local M3UA entity. 2.3.2 Example: Equipment Data in the RNC Initial Configuration Script The equipment data includes the data of the RSS subrack, RBS subrack, RNC time and clock, and IP address of the EMS server. 2.3.3 Example: Interface Data in the RNC Initial Configuration Script This describes interface data in the RNC initial configuration script. The interfaces refer to Iub, Iu-CS, Iu-PS, Iu-BC, and Iur. 2.3.4 Example: Cell Data in the RNC Initial Configuration Script This describes cell data in the RNC initial configuration script. The cell data includes the data of 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 and logical cells.
Issue 06 (2010-09-20)
2-3
2.3.1 Example: Global Data in the RNC Initial Configuration Script

This describes global data in the RNC initial configuration script. The global data includes the basic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, global location 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 the debugging 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 ADD ADD ADD ADD LAC: SAC: RAC: URA: URA: CnOpIndex=0, LAC=100, PlmnValTagMin=1, PlmnValTagMax=64; CnOpIndex=0, LAC=100, SAC=100; CnOpIndex=0, LAC=100, RAC=0, PlmnValTagMin=65, PlmnValTagMax=128; URAId=0, CnOpIndex=0; 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";
2.3.2 Example: Equipment Data in the RNC Initial Configuration 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 SET RMV RMV RMV RMV RMV RMV RMV RMV RMV ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD SUBRACK: SRN=0, SRName="RSS"; CLKTYPE: CLKTYPE=GCU; BRD: SRN=0, SN=8; BRD: SRN=0, SN=9; BRD: SRN=0, SN=10; BRD: SRN=0, SN=11; BRD: SRN=0, SN=14; BRD: SRN=0, SN=16; BRD: SRN=0, SN=18; BRD: SRN=0, SN=24; BRD: SRN=0, SN=26; BRD: SRN=0, BRDTYPE=DPU, SN=8; BRD: SRN=0, BRDTYPE=DPU, SN=9; BRD: SRN=0, BRDTYPE=DPU, SN=10; BRD: SRN=0, BRDTYPE=DPU, SN=11; BRD: SRN=0, BRDTYPE=AEU, SN=14, RED=NO; BRD: SRN=0, BRDTYPE=AEU, SN=15, RED=NO; BRD: SRN=0, BRDTYPE=UOI_ATM, SN=16, RED=YES; BRD: SRN=0, BRDTYPE=GOU, SN=18, RED=YES; BRD: SRN=0, BRDTYPE=UOI_ATM, SN=24, RED=YES; BRD: SRN=0, BRDTYPE=UOI_ATM, SN=26, RED=YES;
//Add an RBS subrack.

ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD SUBRACK: SRN=1, SRName="RBS"; BRD: SRN=1, BRDTYPE=SPU, SN=8; BRD: SRN=1, BRDTYPE=SPU, SN=10; BRD: SRN=1, BRDTYPE=DPU, SN=14; BRD: SRN=1, BRDTYPE=DPU, SN=16; BRD: SRN=1, BRDTYPE=DPU, SN=18; BRD: SRN=1, BRDTYPE=AOU, SN=20, BRD: SRN=1, BRDTYPE=FG2, SN=22, BRD: SRN=1, BRDTYPE=GOU, SN=24, BRD: SRN=1, BRDTYPE=AEU, SN=26,
RED=YES; RED=YES; RED=YES; 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; ADD CLKSRC:SRCGRD=2, SRCT=LINE1_8KHZ; ADD CLKSRC:SRCGRD=3, SRCT=LINE2_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;
Issue 06 (2010-09-20)
2-5
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";
2.3.3 Example: Interface Data in the RNC Initial Configuration Script

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

This describes an example of Iub data in the RNC initial configuration script. The Iub data consists 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, set working 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 AEUa board 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: REMARK="FOR ADD ATMTRF: CDVT=1024, REMARK="FOR ADD ATMTRF: REMARK="FOR ADD ATMTRF: CDVT=1024, REMARK="FOR ADD ATMTRF: CDVT=1024, TRFX=110, ST=RTVBR, UT=CELL/S, PCR=217, SCR=170, MBS=1000, CDVT=1024, IUB NCP"; TRFX=120, ST=RTVBR, UT=CELL/S, PCR=2000, SCR=548, MBS=1000, IUB CCP"; TRFX=130, ST=RTVBR, UT=CELL/S, PCR=83, SCR=76, MBS=1000, CDVT=1024, IUB ALCAP"; TRFX=140, ST=RTVBR, UT=CELL/S, PCR=5312, SCR=4831, MBS=1000, R99 RT"; TRFX=150, ST=NRTVBR, UT=CELL/S, PCR=13154, SCR=10854, MBS=1000,
2-6
Issue 06 (2010-09-20)
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.

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

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 and the 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=2, PT=RT, CARRYT=IMA, CARRYF=0, CARRYSN=14, CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=44, 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 subnet mask is 255.255.255.0.
ADD DEVIP: SRN=0, SN=14, IPADDR="10.218.107.126", MASK="255.255.255.0";
2-8
Issue 06 (2010-09-20)
//Add an IPoA PVC. The local IP address is 10.218.107.126, the peer IP address is 10.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. The gateway 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";
Example: Iu-CS Data in the RNC Initial Configuration Script

This describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS data consists of the physical layer data, ATM traffic resource data, TRM mapping, activity factor table, 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 UOIa_ATM board in slot 18 of subrack 0.
SET OPT: SRN=0, SN=18, BT=UOIa,LGCAPPTYPE=ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16byte, J0TXVALUE="SBS 155",J0RXT=16byte, J0RXVALUE="SBS 155", J1TXT=16byte, J1TXVALUE="SBS 155", J1RXT=16byte, J1RXVALUE="SBS 155";
//Add ATM traffic records. //For the ATM traffic record on the control plane, the record index is 170, the service type is CBR, 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 TRMMAP: TMI=13, ITFT=IUCS, TRANST=ATM; ADD TRMMAP: TMI=14, ITFT=IUCS, TRANST=ATM; ADD TRMMAP: TMI=15, ITFT=IUCS, TRANST=ATM;
//Add activity factor tables for gold, silver, and copper users respectively.
ADD TRMFACTOR: FTI=11, REMARK="FOR IUCS";
//Add the Iu-CS control plane data. //Add SAAL links.

ADD SAALLNK: SRN=0, SN=0, SAALLNKN=10, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=18,
Issue 06 (2010-09-20)
2-9
CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=100, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI; ADD SAALLNK: SRN=0, SN=0, SAALLNKN=11, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=18, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=101, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI; ADD SAALLNK: SRN=0, SN=0, SAALLNKN=12, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=18, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=102, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI; ADD SAALLNK: SRN=0, SN=0, SAALLNKN=13, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=18, CARRYNCOPTN=0, CARRYVPI=10, CARRYVCI=103, TXTRFX=170, RXTRFX=170, SAALLNKT=NNI;
//Add RNC DSPs.

ADD N7DPC: NAME="TO-MGW",DPX=0, DPC=H'0008DB, SLSMASK=B0000, NEIGHBOR=YES, DPCT=IUCS, STP=OFF, BEARTYPE=MTP3;
//Add the MTP3 data.

ADD MTP3LKS: SIGLKSX=0, DPX=0, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-MGW"; ADD MTP3RT: DPX=0, SIGLKSX=0, NAME="TO-MGW"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=0, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_0"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_1"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=2, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_2"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=3, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_3"; SAALLNKN=10, PRIORITY=0,
SAALLNKN=11, PRIORITY=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, ITFT=IUCS, TMIGLD=13, TMISLV=14, TMIBRZ=15, FTI=11
//Add a CN domain and a CN node.

ADD CNDOMAIN: CNDomainId=CS_DOMAIN, T3212=10, ATT=ALLOWED, DRXCycleLenCoef=6; ADD CNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;
//Add the Iu-CS user plane data. //Add AAL2 paths.

ADD AAL2PATH: ANI=1, PATHID=1, CARRYT=NCOPT, CARRYF=0, CARRYSN=18, CARRYNCOPTN=2, RSCGRPFLAG=NO, VPI=33, VCI=55, TXTRFX=180, RXTRFX=180, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0,
2-10
Issue 06 (2010-09-20)

TIMERCU=10, AAL2PATHT=HSPA;
ADD AAL2PATH: ANI=1, PATHID=2, CARRYT=NCOPT, CARRYF=0, CARRYSN=18, CARRYNCOPTN=2, RSCGRPFLAG=NO, VPI=33, VCI=56, TXTRFX=180, RXTRFX=180, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10, AAL2PATHT=HSPA; ADD AAL2PATH: ANI=1, PATHID=3, CARRYT=NCOPT, CARRYF=0, CARRYSN=18, CARRYNCOPTN=2, RSCGRPFLAG=NO, VPI=33, VCI=57, TXTRFX=180, RXTRFX=180, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10, AAL2PATHT=HSPA;
//Add AAL2 routes.

ADD AAL2RT:NSAP="H'45000006598540056F0000000000000000000000", ANI=1, RTX=1, OWNERSHIP=YES;
Example: Iu-PS Data in the RNC Initial Configuration Script

This describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS data consists of the physical layer data, TRM mapping, activity factor table, control plane data, and user plane data. //Take the script for the IP-based Iu-PS interface as an example. //Add physical layer data of the external interface for the RNC. //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 dualhoming 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 SCTPLNK: SRN=0, SN=4, SSN=2, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, DSCP=62, 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 M3LNK: SIGLKSX=1, SIGLNKID=0, SRN=0, SN=2, SSN=2, SCTPLNKN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="LINKSGSN-01"; ADD M3LNK: SIGLKSX=1, SIGLNKID=1, SRN=0, SN=4, SSN=2, SCTPLNKN=1, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="LINKSGSN-02";
//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.
2-12
Issue 06 (2010-09-20)

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 a port controller.

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", NEXTHOP="10.218.161.1", PRIORITY=HIGH, REMARK="TO SGSN";
Example: Iur Data in the RNC Initial Configuration Script

This describes an example of Iur data in the RNC initial configuration script. The Iur data consists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table, control plane data, and user plane data. //Take the script for the ATM-based Iur interface as an example. //Add physical layer data of the external interface for the RNC. //Set the attributes of all the optical ports on the ATM-based UOIa board in slot 24 of subrack 0.
SET OPT:SRN=0, SN=24, BT=UOIa, LGCAPPTYPE=ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16BYTE, J0TXVALUE="SBS 155", J0RXT=16BYTE, J0RXVALUE="SBS 155", J1TXT=16BYTE, J1TXVALUE="SBS 155", J1RXT=16BYTE, J1RXVALUE="SBS 155";

//For the ATM traffic record on the control plane, the record index is 190, the service type is CBR, and the peak cell rate is 530 cell/s. //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 TRMMAP: TMI=19, ITFT=IUR, TRANST=ATM; ADD TRMMAP: TMI=20, ITFT=IUR, TRANST=ATM; ADD TRMMAP: TMI=21, ITFT=IUR, TRANST=ATM;
//Add an activity factor table

ADD TRMFACTOR: FTI=13, REMARK="FOR IUR";
//Add the Iur control plane data. //Add SAAL links.

ADD SAALLNK: SRN=0, SN=0, SAALLNKN=100, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=1, CARRYVPI=5, CARRYVCI=54, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI; ADD SAALLNK: SRN=0, SN=0, SAALLNKN=101, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=1, CARRYVPI=5, CARRYVCI=55, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI; ADD SAALLNK: SRN=0, SN=0, SAALLNKN=102, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=1, CARRYVPI=5, CARRYVCI=56, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI; ADD SAALLNK: SRN=0, SN=0, SAALLNKN=103, CARRYT=NCOPT, CARRYSRN=0, CARRYSN=24, CARRYNCOPTN=1, CARRYVPI=5, CARRYVCI=57, TXTRFX=190, RXTRFX=190, SAALLNKT=NNI;
//Add a destination signaling point of the RNC.

ADD N7DPC: DPX=3, DPC=H'A32, NAME="TO-RNC", DPCT=IUR, BEARTYPE=MTP3;
//Add a neighboring RNC.

ADD NRNC: NRncId=201, SHOTRIG=CS_SHO_SWTICH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1, HOTRIG=ON, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, Dpx=3, RncProtclVer=R6, TnlBearerType=ATM_TRANS;
//Add the MTP3 data

ADD MTP3LKS: SIGLKSX=2, DPX=3, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-RNC"; ADD MTP3RT: DPX=3, SIGLKSX=2, PRIORITY=0, NAME="TO-RNC"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=0, SRN=0, SN=0, SAALLNKN=100, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC1"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=1, SRN=0, SN=0, SAALLNKN=101, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC2";
2-14
Issue 06 (2010-09-20)
ADD MTP3LNK: SIGLKSX=2, SIGSLC=2, SRN=0, SN=0, SAALLNKN=102, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC3"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=3, SRN=0, SN=0, SAALLNKN=103, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC4";

ADD ADJNODE: ANI=3, NAME="TO-RNC", NODET=IUR, DPX=3, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS2;
//Set the mapping between the Iur adjacent node and transmission resources.
ADD ADJMAP: ANI=3, ITFT=IUR, TMIGLD=19, TMISLV=20, TMIBRZ=21, FTI=13;
//Add the Iur user plane data. //Add AAL2 paths.

ADD AAL2PATH: ANI=3, PATHID=110, CARRYT=NCOPT, CARRYF=0, CARRYSN=24, CARRYNCOPTN=0, RSCGRPFLAG=NO, VPI=20, VCI=101, TXTRFX=200, RXTRFX=200, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10, AAL2PATHT=HSPA; ADD AAL2PATH: ANI=3, PATHID=111, CARRYT=NCOPT, CARRYF=0, CARRYSN=24, CARRYNCOPTN=0, RSCGRPFLAG=NO, VPI=20, VCI=102, TXTRFX=200, RXTRFX=200, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10, AAL2PATHT=HSPA; ADD AAL2PATH: ANI=3, PATHID=112, CARRYT=NCOPT, CARRYF=0, CARRYSN=24, CARRYNCOPTN=0, RSCGRPFLAG=NO, VPI=20, VCI=103, TXTRFX=200, RXTRFX=200, OWNERSHIP=LOCAL, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, TIMERCU=10, AAL2PATHT=HSPA;
//Add an AAL2 route.

Example: Iu-BC Data in the RNC Initial Configuration Script

This 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 SABP data. //Take the script for the ATM-based Iu-BC interface as an example. //Add physical layer data of the external interface for the RNC. //Set attributes of all the optical ports on the UOIa_ATM board in slot 17 of subrack 0.
SET OPT: SRN=0, SN=17, BT=UOIa, LGCAPPTYPE=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";
Issue 06 (2010-09-20)
2-15

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=17, DSTIP="172.22.5.0", DSTMASK="255.255.255.0", NEXTHOP="172.22.21.254", PRIORITY=HIGH, REMARK="IP ROUTE TO CBC";
//Add SABP data.

ADD CBSADDR: SRN=0, SN=0, CnOpIndex=0, RNCIPADDR="172.22.21.50", CBCIPADDR="172.22.5.1", CBCMASK="255.255.255.0";
2.3.4 Example: Cell Data in the RNC Initial Configuration Script

This describes cell data in the RNC initial configuration script. The cell data includes the data of 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 and logical 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=1, CellName="CELL 1",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, UARFCNDownlink=10563, PScrambCode=1, TCell=CHIP256, LAC=100, SAC=100,
2-16
Issue 06 (2010-09-20)
CfgRacInd=REQUIRE, RAC=0 , SpgId=2, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=1, SupBmc=FALSE, MaxTxPower=430, PCPICHPower=330; ADD QUICKCELLSETUP: CellId=2, CellName="CELL 2",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, 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:;
2.4 Conventions in Parameter Relationship Diagrams

Parameter relationship diagrams show the relationships between the parameters of MML commands. Figure 2-2 shows an example of the parameter relationship diagram. Figure 2-2 Example of the parameter relationship diagram
The elements in the preceding diagram are explained as follows: l l l l The parameters in a box marked in solid or dotted lines belong to the command above the box. For example, parameter 3 belongs to command 2. Boxes 1 and 2 list only the parameters related to both commands. The command above box 2 in solid lines is executed to perform the current task, and the command above box 1 in dotted lines is executed to perform a related task. The parameters at both ends of the solid arrow are the same. This parameter is configured through the command at the arrowhead and invoked through the command at the arrow tail. For example, parameter 2 is configured through command 1 and invoked through command 2. The parameters at both ends of the dotted arrow are different. The parameter at the arrowhead must be predefined, and the parameter at the arrow tail must be consistent with it. For example, parameter 3 must be consistent with parameter 1.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-17
Issue 06 (2010-09-20)
The parameter marked with *, such as parameter 3, is a conditional parameter. It is configured only in certain conditions.
NOTE
The parameter relationship between the commands to add, modify, and remove a configured object is obvious. This document does not describe such relationships.
2-18
Issue 06 (2010-09-20)
3 Procedure of RNC Initial Configuration
3
Prerequisite Procedure
Procedure of RNC Initial Configuration

This describes the procedure of RNC initial configuration. After the initial configuration, a script for loading is available.
l l
You are licensed. The data negotiated between the RNC and other network elements is ready. For details, refer to 4.3 Data Negotiated Between RNC and Other Network Elements.
Step 1 Start the RNC initial configuration tool. Step 2 Create an RNC script. Step 3 Perform 5 Configuring RNC Global Data. Step 4 Perform 6 Configuring RNC Equipment Data. Step 5 Perform 7 Configuring Iub Interface Data (Initial). Step 6 Perform 8 Configuring Iu-CS Interface Data (Initial). Step 7 Perform 9 Configuring Iu-PS Interface Data (Initial). Step 8 Perform 11 Configuring Iu-BC Interface Data (Initial). Step 9 Perform 10 Configuring Iur Interface Data (Initial). Step 10 Perform 12 Configuring Cell Data (Initial). Step 11 Save the RNC initial configuration script. ----End
Postrequisite
The RNC initial configuration data is loaded during the commissioning of the RNC. For details, refer to Loading RNC Software and Data Files.
4 Data Preparation for RNC Initial Configuration
Data Preparation for RNC Initial Configuration
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. 4.1 Data Preparation for Initial Configuration In the RNC initial configuration, some data is obtained from the data sheets after negotiation with other network elements. The negotiated data includes the global data, equipment data, interface data, and cell data. 4.2 Global Data and Equipment Data of the RNC The global and equipment data configuration takes precedence over configuration of other data during RNC initial configuration. Therefore, the readiness of global data and equipment data is necessary for the RNC initial configuration. 4.3 Data Negotiated Between RNC and Other Network Elements During RNC initial configuration, some data is available on the negotiation between the RNC and other network elements. The negotiated data is necessary for RNC initial configuration. 4.4 Cell Data on the RNC This describes how to plan the cell data and neighboring cell relationship data before configuring cell data script.
Issue 06 (2010-09-20)
4-1
4.1 Data Preparation for Initial Configuration

In the RNC initial configuration, some data is obtained from the data sheets after negotiation with other network elements. The negotiated data includes the global data, equipment data, interface data, and cell data. For the data preparation for RNC initial configuration, see Data Preparation for RNC Initial Configuration.
4.2 Global Data and Equipment Data of the RNC

The global and equipment data configuration takes precedence over configuration of other data during RNC initial configuration. Therefore, the readiness of global data and equipment data is necessary for the RNC initial configuration.
Global Data
Table 4-1 lists the global data to be prepared. Table 4-1 Global data Item RNC Name RNC ID Whether to support network sharing Whether to support MOCN Number of operators supported Local basic data Whether to support Inter Plmn Ho Allowed Whether to support Inter Plmn Ho Allowed InterRat Common Plmn Using Type Source ATM address URA ID Operator index Operator name Basic information about the operator Primary operator flag Mobile country code Mobile network code
Value
Item Network ID OSP code bits OSP data OSP code SPDF SPC Location area code Location area data Minimum and maximum PLMN value tags Service area code Local M3UA entity data Local entity type Routing Context
Value
Equipment Data
Table 4-2 lists the equipment data to be prepared. Table 4-2 Equipment data Item RNC time source data Time zone Daylight saving time flag Start time of the daylight saving time End time of the daylight saving time Time offset RNC clock data Clock source level Clock source type Clock source working mode Value
If the backup of the AOUa, POUa, and UOIa is enabled, the MSP parameters must be negotiated. Table 4-3 lists the MSP data to be prepared.
Issue 06 (2010-09-20)
4-3
Table 4-3 MSP data Item Revertive type K2 mode SDSF priority Backup mode Value
4.3 Data Negotiated Between RNC and Other Network Elements

During RNC initial configuration, some data is available on the negotiation between the RNC and other network elements. The negotiated data is necessary for RNC initial configuration. 4.3.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 Iub interface is negotiated between the RNC and the NodeB. 4.3.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 Iub interface is negotiated between the RNC and the NodeB. 4.3.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 Resource Management (TRM) module of the RNC determines whether the data is transmitted on the ATM network or IP network. 4.3.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 is negotiated between the RNC and the CS domain. 4.3.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 negotiated between the RNC and the CS domain. 4.3.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 negotiated between the RNC and the SGSN. 4.3.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 negotiated between the RNC and the SGSN. 4.3.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 negotiated between the local RNC and the neighboring RNC. 4.3.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 between the local RNC and the neighboring RNC.
4.3.10 Data Negotiated on the Iu-BC Interface (over ATM) The data of the Iu-BC interface is negotiated between the RNC and the CBC. If the CBC connects to the RNC through the SGSN, the data of the Iu-BC interface is negotiated between the RNC and the SGSN. This topic describes the ATM-based Iu-BC interface data negotiated between the RNC and the CBC. 4.3.11 Data Negotiated on the Iu-BC Interface (over IP) When IP transport is applied to the Iur interface, the data of the Iur interface is negotiated between the RNC and the CBC.
4.3.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 Iub interface is negotiated between the RNC and the NodeB.
Basic Data of the NodeB

Table 4-4 lists the basic data of the NodeB. Table 4-4 Basic data of the NodeB Item NodeB ATM address NodeB type NodeB protocol version Value
CAUTION
The protocol version on the NodeB side must be later than or the same as that on the RNC side.
Data on the Physical Layer

Before configuring physical layer data, determine the type of the interface board, and then negotiate and plan the associated data. l l l Table 4-5 lists the physical layer data to be prepared when the AEUa serves as the interface board. Table 4-5 and Table 4-6 list the physical layer data to be prepared when the AOUa serves as the interface board. Table 4-6 lists the physical layer data to be prepared when the UOIa_ATM serves as the interface board.
Table 4-5 Data on the physical layer - 1 Item Working mode

Value
Item Line code Scrambling switch
Value
Table 4-6 Data on the physical layer - 2 Item Scrambling switch Standard of optical port Description The data must be negotiated only in the case of non-channelized optical port. Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are consistent with those of the RX byte at the peer end. The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment. Value
(Optional) J0 TX type, J0 TX value, expected J0 RX type, and expected J0 RX value (Optional) J1 TX type, J1 TX value, expected J1 RX type, and expected J1 RX value (Optional) J2 TX value and expected J2 RX value
Table 4-7 lists the data to be prepared when the upper-layer application of the physical layer is configured as the IMA group. Table 4-7 Data of the IMA group Item TX frame length IMA protocol version Value
Data on the Control Plane

The Iub control plane data includes data of SAAL links and basic data of the NodeB, as listed in Table 4-8.
Table 4-8 Data on the control plane Item Bearing VPI and VCI of SAAL links CCP No. Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
NOTE
When the RNC is directly connected to the NodeB, the VPI and VCI on the RNC side and those on the NodeB side must be consistent through negotiation and configured on one physical link. If the VPIs and VCIs at the two ends are negotiated but not configured on one physical link, the link fails.
Data on the User Plane

The Iub user plane data includes data of AAL2 paths, as listed in Table 4-9. Table 4-9 Data on the user plane Item AAL2 path ID Bearing VPI and VCI of AAL2 paths Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
Issue 06 (2010-09-20)
4-7

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 NodeB side.
Data of the OM Channel

The Iub OM channel data includes the data of the IPoA PVC, as listed in Table 4-10. Table 4-10 Data of the OM channel Item 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 Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
NOTE
l The gateway IP address on the RNC side is required only when layer 3 networking is applied to the Iub interface. l The local IP address of the IPoA PVC is the device IP address configured on the ATM interface board at the RNC. l The peer IP address of the IPoA PVC is the gateway IP address on the RNC side over the Iub interface in layer 3 networking or the OM IP address of the NodeB over the Iub interface in layer 2 networking.
4.3.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 Iub interface is negotiated between the RNC and the NodeB.

Table 4-11 lists the basic data of the NodeB.
4-8
Issue 06 (2010-09-20)
Table 4-11 Basic data of the NodeB Item NodeB type NodeB protocol version Value
Data on the Physical Layer and Data Link Layer

Before configuring physical layer data, determine the type of the interface board, and then negotiate and plan the associated data. l l l Table 4-12 and Table 4-14 list the physical layer data to be prepared when the PEUa serves as the interface board. Table 4-12, Table 4-13, and Table 4-14 list the physical layer data to be prepared when the POUa serves as the interface board. Table 4-13 and Table 4-14 list the physical layer data to be negotiated and planned when the UOIa_IP serves as the interface board. The UOIa_IP supports only the PPP link and does not support the MLPPP link. Table 4-15 lists the physical layer data to be negotiated and planned when the FG2a serves as the interface board. Table 4-15 lists the physical layer data to be negotiated and planned when the GOUa serves as the interface board.
l l
Table 4-12 Data on the physical layer - 1 Item Working mode Line code Scrambling switch Value
Table 4-13 Data on the physical layer - 2 Item Scrambling switch Standard of optical port Description The data must be negotiated only in the case of non-channelized optical port. Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are Value
(Optional) J0 TX type, J0 TX value, expected J0 RX type, and expected J0 RX value
Issue 06 (2010-09-20)
4-9
Item (Optional) J1 TX type, J1 TX value, expected J1 RX type, and expected J1 RX value (Optional) J2 TX value and expected J2 RX value
Description consistent with those of the RX byte at the peer end. The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment.
Value
Table 4-14 Data on the data link layer Item Local IP address and subnet mask PPP or MLPPP link data Peer IP address Bearing timeslot Value
Table 4-15 Data on the physical layer - 3 Item Device IP address of the interface board Ethernet port data Port IP address and subnet mask Maximum transmitting unit Whether to enable auto negotiation FE electrical port Transmission rate over the FE port Working mode Whether to enable flow control GE electrical port Maximum transmitting unit Maximum transmitting unit GE optical port Whether to enable auto negotiation Whether to enable flow control Value
4-10
Issue 06 (2010-09-20)

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

Table 4-16 lists the control plane data to be negotiated. Table 4-16 Data on the control plane Item Working mode Local SCTP port No. DSCP First local IP address Second local IP address First destination IP address Second destination IP address SCTP Link Destination SCTP port No. Whether to calculate checksum when transmitting messages Whether to calculate checksum when receiving messages Checksum algorithm VLAN ID setting flag VLAN ID CCP Port No. Value
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 do not need to configure VLAN ID.

The Iub user plane data includes the IP path data, as listed in Table 4-17.
Table 4-17 Data on the user plane Item IP address for the interface on the RNC side User plane IP address and subnet mask of the NodeB IP path type IP Path TX bandwidth and RX bandwidth FPMUX Flag DSCP VLAN ID setting flag VLAN ID Value

Table 4-18 lists the OM channel data to be negotiated. Table 4-18 Data of the OM channel Item IP address for the interface at the RNC IP address for the interface at the NodeB (Optional) Gateway IP address on the RNC side (Optional) Gateway IP address on the NodeB side OM IP address and subnet mask of the NodeB (Optional) Electronic serial number of the NodeB Use TRUNK or not NodeB TRUNK IP address NodeB TRUNK IP mask Whetcher binding logical port or not Logic port No. DHCP SERVER IP address Value
4-12
Issue 06 (2010-09-20)

NOTE
l The gateway IP addresses on the RNC and NodeB sides are required only when layer 3 networking is applied to the Iub interface. l The electronic serial number of the NodeB is required only when the NodeB uses DHCP.
4.3.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 Resource Management (TRM) module of the RNC determines whether the data is transmitted on the ATM network or IP network.
IP Network Planning
When data transmission on the Iub interface uses the ATM/IP dual stack, the IP network planning consists of IP networking, IP address planning, and route configuration. For IP networking, check the following information: l l l Whether to use layer 2 or layer 3 networking Whether to use the VLAN 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 4-19. Table 4-19 Iub data transmission mode planning Data Type Control plane data Description One or both of the two types can be used at a time. It is recommended that both ATM and IP transport modes be used for transmission security.
Issue 06 (2010-09-20)
4-13
Data Type User plane data
Description One or both of the two types can be used at a time. It is recommended that: l ATM transport be applied to signaling, voice services, CS conversational services, CS streaming services, PS conversational services, and PS streaming services. l IP transport be applied to PS interactive services, PS background services, HSDPA conversational services, HSDPA streaming services, HSDPA interactive services, HSDPA background services, HSUPA conversational services, HSUPA streaming services, HSUPA interactive services, and HSUPA background services.
OM channel
Only one of the two modes can be used at a time. It is recommended that IP transport be used.

Table 4-20 lists the basic data of the NodeB. Table 4-20 Basic data of the NodeB Item NodeB ATM address (required only when ATM transport is applied to the control plane) NodeB type NodeB protocol version Value
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 and IP data on the physical layer and data link layer. l l l Table 4-21 lists the physical layer data to be prepared when the AEUa serves as the interface board. Table 4-21 and Table 4-22 list the physical layer data to be prepared when the AOUa serves as the interface board. Table 4-22 lists the physical layer data to be prepared when the UOIa_ATM serves as the interface board.
4-14
Table 4-24, Table 4-25, Table 4-26, and Table 4-27 list the data to be negotiated on the physical layer and data link layer of the IP-based Iub interface.
l l l
Table 4-24 and Table 4-26 list the physical layer data to be prepared when the PEUa serves as the interface board. Table 4-24, Table 4-25, and Table 4-26 list the physical layer data to be prepared when the POUa serves as the interface board. Table 4-25 and Table 4-26 list the physical layer data to be negotiated and planned when the UOIa_IP serves as the interface board. The UOIa_IP supports only the PPP link and does not support the MLPPP link. Table 4-27 lists the physical layer data to be negotiated and planned when the FG2a serves as the interface board. Table 4-27 lists the physical layer data to be negotiated and planned when the GOUa serves as the interface board.
l l
4-16
Issue 06 (2010-09-20)
NOTE

Based on the planning result of Table 4-19, prepare data as follows: l l If ATM transport is applied to the Iub interface, negotiate and plan the control plane data listed in Table 4-28. If IP transport is applied to the Iub interface, negotiate and plan the control plane data listed in Table 4-29.
Issue 06 (2010-09-20)
4-17
Table 4-28 Data on the control plane Item Bearing VPI and VCI of SAAL links CCP No. Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
NOTE
When the RNC is directly connected to the NodeB, the VPI and VCI on the RNC side and those on the NodeB side must be consistent through negotiation and configured on one physical link. If the VPIs and VCIs at the two ends are negotiated but not configured on one physical link, the link fails.
Table 4-29 Data on the control plane Item Working mode Local SCTP port No. DSCP First local IP address Second local IP address First destination IP address SCTP Link Second destination IP address Destination SCTP port No. Whether to calculate checksum when transmitting messages Whether to calculate checksum when receiving messages Checksum algorithm VLAN ID setting flag Value
4-18
Issue 06 (2010-09-20)
Item VLAN ID CCP Port No.
Value
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 do not need to configure VLAN ID.

Based on the planning result of Table 4-19, prepare data as follows: l l If ATM transport is applied to the Iub interface, negotiate and plan the user plane data listed in Table 4-30. If IP transport is applied to the Iub interface, negotiate and plan user plane the data shown in Table 4-31.
Table 4-30 Data on the user plane Item AAL2 path ID Bearing VPI and VCI of AAL2 paths Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
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 NodeB side.
Issue 06 (2010-09-20)
4-19
Table 4-31 Data on the user plane Item IP address for the interface on the RNC side User plane IP address and subnet mask of the NodeB IP path type IP Path TX bandwidth and RX bandwidth FPMUX Flag DSCP VLAN ID setting flag VLAN ID Value

Based on the planning result of Table 4-19, prepare data as follows: l l If ATM transport is applied to the Iub interface, negotiate and plan the OM channel data listed in Table 4-32. If IP transport is applied to the Iub interface, negotiate and plan the OM channel data listed in Table 4-33.
Table 4-32 Data of the OM channel Item 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 Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
4-20
Issue 06 (2010-09-20)

NOTE
l The gateway IP address on the RNC side is required only when layer 3 networking is applied to the Iub interface. l The local IP address of the IPoA PVC is the device IP address configured on the ATM interface board at the RNC. l The peer IP address of the IPoA PVC is the gateway IP address on the RNC side over the Iub interface in layer 3 networking or the OM IP address of the NodeB over the Iub interface in layer 2 networking.
Table 4-33 Data of the OM channel Item IP address for the interface at the RNC IP address for the interface at the NodeB (Optional) Gateway IP address on the RNC side (Optional) Gateway IP address on the NodeB side OM IP address and subnet mask of the NodeB (Optional) Electronic serial number of the NodeB Use TRUNK or not NodeB TRUNK IP address NodeB TRUNK IP mask Whetcher binding logical port or not Logic port No. DHCP SERVER IP address Value
NOTE
l The gateway IP addresses on the RNC and NodeB sides are required only when layer 3 networking is applied to the Iub interface. l The electronic serial number of the NodeB is required only when the NodeB uses DHCP.
4.3.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 is negotiated 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 CS domain. Table 4-34 lists the basic data of the CS domain.
Issue 06 (2010-09-20)
4-21
Table 4-34 Basic data of the CS domain Item DSP Type DSP code Signaling route mask Adjacency flag ATM address SS7 protocol type Q.AAL2 protocol version CN protocol version CR support type Value

Table 4-35 lists the physical layer data to be prepared when the UOIa_ATM serves as the interface board. Table 4-35 Data on the physical layer - 2 Item Scrambling switch Standard of optical port Description The data must be negotiated only in the case of non-channelized optical port. Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are consistent with those of the RX byte at the peer end. The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment. Value
4-22
Issue 06 (2010-09-20)
Data About Timers

Table 4-37 lists the data to be prepared for SAAL and SCCP timers. Table 4-37 Data about timers Item Timer CC Timer POLL (Optional) SAAL (ms) Timer NO_RESPONSE Timer T1 Timer T2 Timer T3 SCCP (s) Inactive TX timer Inactive RX timer RNC MSC

Table 4-38 lists the control plane data, including data on the transport network layer control plane and that on the radio network layer control plane. Table 4-38 Data on the Iu-CS control plane Item MTP3 Signaling Link MTP3 Link set ATM traffic resources
Issue 06 (2010-09-20)
Value Signaling link code VPI/VCI Signalling link mask Service Type
4-23
Item Traffic description Peak cell rate Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance
Value

Table 4-39 lists the data on the radio network layer user plane. Table 4-39 Data on the Iu-CS user plane Item AAL2 Path AAL2 path ID VPI/VCI Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
4.3.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 negotiated 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 CS domain. Table 4-40 lists the basic data of the CS domain.
4-24
Issue 06 (2010-09-20)
Table 4-40 Basic data of the CS domain Item DSP Type DSP code Signaling route mask Adjacency flag SS7 protocol type CN protocol version CR support type Value

Before configuring physical layer data, determine the type of the interface board, and then negotiate and plan the associated data. l Table 4-41 and Table 4-42 list the physical layer data to be negotiated and planned when the UOIa_IP serves as the interface board. The UOIa_IP supports only the PPP link and does not support the MLPPP link. Table 4-43 lists the physical layer data to be negotiated and planned when the FG2a serves as the interface board. Table 4-43 lists the physical layer data to be negotiated and planned when the GOUa serves as the interface board.
l l
Table 4-41 Data on the physical layer - 2 Item Scrambling switch Standard of optical port Description The data must be negotiated only in the case of non-channelized optical port. Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are consistent with those of the RX byte at the peer end. Value
(Optional) J0 TX type, J0 TX value, expected J0 RX type, and expected J0 RX value (Optional) J1 TX type, J1 TX value, expected J1 RX type, and expected J1 RX value
Issue 06 (2010-09-20)
4-25
Item (Optional) J2 TX value and expected J2 RX value
Description The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment.
Value
NOTE
4-26
Issue 06 (2010-09-20)

Table 4-44 lists the control plane data to be negotiated. Table 4-44 Data on the Iu-CS control plane Item Working mode Local SCTP port No. First local IP address Second local IP address First destination IP address SCTP Link Second destination IP address Destination SCTP port No. Whether to calculate checksum when transmitting messages Whether to calculate checksum when receiving messages Check sum algorithm VLAN ID setting flag VLAN ID Traffic mode Working mode Local entity type M3UA Destination entity type (Optional) Routing context of the local M3UA entity (Optional) Routing context of the destination M3UA entity Signalling link mask Initial bearing traffic active tag Value
Issue 06 (2010-09-20)
4-27

NOTE
l Local SCTP port No. is required only when Signalling link mode of the SCTP link 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 do not need to configure VLAN ID. l It is not recommended to configure the routing context of the local M3UA entity. If the context needs to be configured, it must be consistent with the routing context of the destination M3UA entity at the peer through negotiation. l It is not recommended to configure the routing context of the destination M3UA entity. If the context needs to be configured, it must be consistent with the routing context of the local M3UA entity at the peer through negotiation.

The Iu-CS user plane data includes the IP path data, as listed in Table 4-45. Table 4-45 Data on the Iu-CS user plane Item IP address for the interface on the RNC side IP address and subnet mask of the MSC server TX bandwidth and RX bandwidth IP Path DSCP VLAN ID setting flag VLAN ID UDP MUX mode of the transmitter UDP MUX mode of the receiver Value
4.3.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 negotiated between the RNC and the SGSN.
Basic Data of the PS Domain

Before configuring the Iu-PS interface data, familiarize yourself with the basic data of the PS domain. Table 4-46 lists the basic data of the PS domain. Table 4-46 Basic data of the PS domain Item DSP Type DSP code
Value
Item Signaling route mask Adjacency flag ATM address SS7 protocol type CN protocol version CR support type
Value

Table 4-47 lists the physical layer data to be prepared when the UOIa_ATM serves as the interface board. Table 4-47 Data on the physical layer - 2 Item Scrambling switch Standard of optical port Description The data must be negotiated only in the case of non-channelized optical port. Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are consistent with those of the RX byte at the peer end. The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment. Value
Data About Timers

Table 4-48 lists the data to be prepared for SAAL and SCCP timers.
Issue 06 (2010-09-20)
4-29
Table 4-48 Data about timers Item Timer CC Timer POLL (Optional) SAAL (ms) Timer NO_RESPONSE Timer T1 Timer T2 Timer T3 SCCP (s) Inactive TX timer Inactive RX timer RNC SGSN

Table 4-49 lists the control plane data to be negotiated. Table 4-49 Data on the Iu-PS control plane Item MTP3 Signaling Link MTP3 Link set Signaling link code VPI/VCI Signalling link mask Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value

Table 4-50 lists the user plane data to be negotiated.
4-30
Issue 06 (2010-09-20)
Table 4-50 Data on the Iu-PS user plane Item IP address and subnet mask of the RNC IPoA PVC IP address and subnet mask of the gateway on the SGSN side VPI/VCI User plane IP address and subnet mask of the SGSN TX bandwidth and RX bandwidth IP Path DSCP VLAN ID setting flag VLAN ID Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
4.3.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 negotiated between the RNC and the SGSN.
Basic Data of the PS Domain

Before configuring the Iu-PS interface data, familiarize yourself with the basic data of the PS domain. Table 4-51 lists the basic data of the PS domain. Table 4-51 Basic data of the PS domain Item DSP Type DSP code Signaling route mask Value
Issue 06 (2010-09-20)
4-31
Item Adjacency flag SS7 protocol type CN protocol version CR support type
Value

l l
4-32
Issue 06 (2010-09-20)
NOTE

Table 4-55 lists the control plane data to be negotiated. Table 4-55 Data on the Iu-PS control plane Item SCTP Link Working mode Value
Issue 06 (2010-09-20)
4-33
Item Local SCTP port No. First local IP address Second local IP address First destination IP address Second destination IP address Destination SCTP port No. Whether to calculate checksum when transmitting messages Whether to calculate checksum when receiving messages Check sum algorithm VLAN ID setting flag VLAN ID Traffic mode Working mode Local entity type M3UA Destination entity type (Optional) Routing context of the local M3UA entity (Optional) Routing context of the destination M3UA entity Signalling link mask Initial bearing traffic active tag
Value
NOTE

The Iu-CS user plane data includes the IP path data, as listed in Table 4-56.
Table 4-56 Data on the Iu-PS user plane Item IP address and subnet mask for the interface on the RNC side IP address and subnet mask of the SGSN IP Path TX bandwidth and RX bandwidth DSCP VLAN ID setting flag VLAN ID Value
4.3.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 negotiated between the local RNC and the neighboring RNC.
Basic Data of the Neighboring RNC

Before configuring the Iur interface data, familiarize yourself with the basic data of the neighboring RNC. Table 4-57 lists the basic data of the neighboring RNC. Table 4-57 Basic data of the neighboring RNC Item DSP Type DSP code Signaling route mask ATM address Adjacency flag SS7 protocol type Protocol version of the neighboring RNC Value

Table 4-58 lists the physical layer data to be prepared when the UOIa_ATM serves as the interface board.
Issue 06 (2010-09-20)
4-35
Data About Timers

Table 4-59 lists the data to be prepared for SAAL and SCCP timers. Table 4-59 Data about timers Item Timer CC Timer POLL (Optional) SAAL (ms) Timer NO_RESPONSE Timer T1 Timer T2 Timer T3 SCCP (s) Inactive TX timer Inactive RX timer RNC Neighboring RNC

Table 4-60 lists the control plane data to be negotiated.
Table 4-60 Data on the Iur control plane Item MTP3 Signaling Link MTP3 Link set Signaling link code VPI/VCI Signalling link mask Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Q.AAL2 protocol version Value

Table 4-61 lists the user plane data to be negotiated. Table 4-61 Data on the Iur user plane Item AAL2 Path AAL2 path ID VPI/VCI Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
Issue 06 (2010-09-20)
4-37

NOTE
l When the path type is RT, HSDPA_RT, or HSUPA_RT, the type of TX traffic record index and RX traffic 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 index and RX traffic record index must be NRTVBR, UBR, or UBR+.
4.3.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 between the local RNC and the neighboring RNC.
Basic Data of the Neighboring RNC

Before configuring the Iur interface data, familiarize yourself with the basic data of the neighboring RNC. Table 4-62 lists the basic data of the neighboring RNC. Table 4-62 Basic data of the neighboring RNC Item DSP Type DSP code Signaling route mask Adjacency flag SS7 protocol type RNC protocol version Value

l l
Table 4-63 Data on the physical layer - 2 Item Scrambling switch Description The data must be negotiated only in the case of non-channelized optical port.
Issue 06 (2010-09-20)
Value
4-38
Item Standard of optical port
Description Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are consistent with those of the RX byte at the peer end. The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment.
Value
Table 4-65 Data on the physical layer - 3 Item Device IP address of the interface board Ethernet port data Port IP address and subnet mask Maximum transmitting unit Whether to enable auto negotiation FE electrical port Transmission rate over the FE port Working mode Whether to enable flow control GE electrical port GE optical port Maximum transmitting unit Maximum transmitting unit Value
Issue 06 (2010-09-20)
4-39
Item Whether to enable auto negotiation Whether to enable flow control
Value
NOTE

Table 4-66 lists the control plane data to be negotiated. Table 4-66 Data on the Iur control plane Item Working mode Local SCTP port No. Local IP address and destination IP address Destination SCTP port No. SCTP Link Whether to calculate checksum when transmitting messages Whether to calculate checksum when receiving messages Check sum algorithm VLAN ID setting flag VLAN ID Traffic mode Working mode Local entity type M3UA Destination entity type (Optional) Routing context of the local M3UA entity (Optional) Routing context of the destination M3UA entity Signalling link mask Initial bearing traffic active tag Value
4-40
Issue 06 (2010-09-20)

NOTE

The Iur user plane data includes the IP path data, as listed in Table 4-67. Table 4-67 Data on the Iur user plane Item IP address and subnet mask for the interface on the RNC side IP address and subnet mask of the neighboring RNC IP Path TX bandwidth and RX bandwidth DSCP VLAN ID setting flag VLAN ID Value
4.3.10 Data Negotiated on the Iu-BC Interface (over ATM)

The data of the Iu-BC interface is negotiated between the RNC and the CBC. If the CBC connects to the RNC through the SGSN, the data of the Iu-BC interface is negotiated between the RNC and the SGSN. This topic describes the ATM-based Iu-BC interface data negotiated between the RNC and the CBC.

Table 4-68 lists the physical layer data to be prepared when the UOIa (UOIa_ATM) serves as the interface board. Table 4-68 Data on the physical layer - 2 Item Scrambling switch Description The data must be negotiated only in the case of non-channelized optical port.
4-41
Value
Issue 06 (2010-09-20)
Item Standard of optical port
Description Optical ports comply with either of the following standards: SDH and SONET. When setting the RX and TX bytes of J0 and J1, ensure that the attributes of the TX byte at the local end are consistent with those of the RX byte at the peer end. The data must be negotiated only in the case of channelized optical port. When the RNC is connected to SDH products of other vendors, the values of these parameters should be negotiated with the peer equipment.
Value
Data on the Iu-BC Interface

Table 4-69 lists the data to be negotiated on the Iu-BC interface. Table 4-69 Data Negotiated on the Iu-BC Interface Item IP address and subnet mask for the interface on the RNC side IP address and subnet mask of the CBC Local IP address IPoA PVC Peer IP address VPI/VCI Service Type Traffic description Peak cell rate ATM traffic resources Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Value
4-42
Issue 06 (2010-09-20)
4.3.11 Data Negotiated on the Iu-BC Interface (over IP)

When IP transport is applied to the Iur interface, the data of the Iur interface is negotiated between the RNC and the CBC.

Table 4-70 lists the physical layer data to be negotiated and planned when the FG2a serves as the interface board. Table 4-70 lists the physical layer data to be negotiated and planned when the GOUa serves as the interface board. Table 4-70 Data on the physical layer - 3 Item Device IP address of the interface board Ethernet port data Port IP address and subnet mask Maximum transmitting unit Whether to enable auto negotiation FE electrical port Transmission rate over the FE port Working mode Whether to enable flow control GE electrical port Maximum transmitting unit Maximum transmitting unit GE optical port Whether to enable auto negotiation Whether to enable flow control Value
Data on the Iu-BC Interface

Table 4-71 lists the data to be negotiated on the Iu-BC interface. Table 4-71 Data Negotiated on the Iu-BC Interface Item IP address and subnet mask of the CBS RNC IP address and subnet mask of the CBC Value
Issue 06 (2010-09-20)
4-43
4.4 Cell Data on the RNC

This describes how to plan the cell data and neighboring cell relationship data before configuring cell data script.
Data for Quick Addition of a Cell on the RNC

Table 4-72 lists the data to be prepared before you quickly set up a cell on the RNC. Table 4-72 Data for quick addition of a cell Item Cell ID Cell name NodeB name Local cell ID Operator index Operator group 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 Value
Data for Addition of an Intra- or Inter-Frequency Neighboring Cell

Table 4-73 and Table 4-74 list the data to be prepared before you add an intra- or inter-frequency neighboring cell.
4-44
Issue 06 (2010-09-20)
Table 4-73 Intra-/inter-frequency neighboring cells Item Cell ID ID of the RNC that controls the neighboring cell Neighboring cell ID Value
Table 4-74 Basic data of inter-/intra-frequency neighboring cells Item 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 Value
Data for Addition of a Neighboring GSM Cell

Table 4-75 and Table 4-76 list the data to be prepared before you add a neighboring GSM cell. Table 4-75 Neighboring GSM cells Item Cell ID GSM Cell Index Value
Issue 06 (2010-09-20)
4-45
Table 4-76 Basic data of neighboring GSM cells Item 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 Value
4-46
Issue 06 (2010-09-20)
5 Configuring RNC Global Data
5
About This Chapter
1.
Configuring RNC Global Data
This describes how to configure RNC global data. This is an essential step in RNC initial configuration. Global data configuration takes precedence over configuration of equipment data, interface data, and cell data. 5.1 Example: Global Data in the RNC Initial Configuration Script This describes global data in the RNC initial configuration script. The global data includes the basic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, global location data, and data of the local M3UA entity. 5.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 the RNC initial configuration. 5.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 listening ports, and whether to enable the RAN sharing and inter-operator handover. 5.4 Adding OSP to the RNC (Initial) This describes how to add the Originating Signaling Point (OSP) data to the RNC. The data includes 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. 5.5 Adding RNC Global Location Data (Initial) This describes how to add global location data, including LA data (such as LAC and PLMN value tag range of the LA), RA data (such as RAC and PLMN value tag range of RA), CS SA data, PS SA data, and URA data. 5.6 Adding a Local M3UA Entity (Initial) This describes how to add a local M3UA entity on the IP-based Iu or Iur interface.
2.
3.
4.
5.
6.
Issue 06 (2010-09-20)
5-1
5.1 Example: Global Data in the RNC Initial Configuration Script

This describes global data in the RNC initial configuration script. The global data includes the basic data of the RNC, operator ID, Iu-Flex data, OSP data, numbers of internal subnets, global location 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 the debugging 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 ADD ADD ADD ADD LAC: SAC: RAC: URA: URA: CnOpIndex=0, LAC=100, PlmnValTagMin=1, PlmnValTagMax=64; CnOpIndex=0, LAC=100, SAC=100; CnOpIndex=0, LAC=100, RAC=0, PlmnValTagMin=65, PlmnValTagMax=128; URAId=0, CnOpIndex=0; 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";
5-2
Issue 06 (2010-09-20)
5.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 the RNC initial configuration. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Prerequisite
None.
Preparation
None.
Procedure
Step 1 Run the SET OFFLINE command to set the RNC to offline mode. ----End
5.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 listening ports, and whether to enable the RAN sharing and inter-operator handover. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Prerequisite
CAUTION
l This task takes precedence over any other initial configuration task. l The RNC must be configured with a minimum of one operator and have one primary operator, regardless of whether the RNC supports RAN sharing or not. l l
Issue 06 (2010-09-20)
All the RNC subracks are switched to the offline mode. The basic data is not configured to the RNC.
For the data to be negotiated and planned before you add basic data to the RNC (initial), refer to 4.2 Global Data and Equipment Data of the RNC.
Preparation
For the data to be negotiated and planned before you add OPC data to the RNC (initial), refer to 4.2 Global Data and Equipment Data of the RNC.
Procedure
Step 1 Run the ADD RNCBASIC command to add basic data to the RNC.
CAUTION
The data added through the ADD RNCBASIC command can be modified or queried but cannot be deleted. Step 2 (Optional) Run the SET OPERATORSHARINGMODE command to set whether to support the RAN sharing and MOCN functions. Step 3 Run the ADD CNOPERATOR command to add a primary operator. Set Primary Operator Flag to YES. Step 4 If you need to add a secondary operator, external operator, and common operator, run the ADD CNOPERATOR command repeatedly. Set Operator Type as required. Step 5 Run the ADD CNOPERGROUP command to add an operator group. To add more operator groups, run this command repeatedly. Step 6 (Optional Perform this step only when Iu-Flex and MOCN functions are enabled as required.) Run the SET OPERATORCFGPARA command to set the parameters of the operator. Step 7 (Optional. Perform this step only when the internal and external subnet numbers of the RNC conflict.) Run the SET SUBNET command to set the subnet number to the specified value.
NOTE
The internal subnet number of the RNC consists of the system subnet number and the debugging subnet number. By default, the system subnet number is 80, and the debugging subnet number is 192.
Step 8 (Optional. Perform this step only when the RNC acts as an SCTP server.) Run the SET SCTPSRVPORT command to set the service listening ports on the SCTP server. ----End
5.4 Adding OSP to the RNC (Initial)

This describes how to add the Originating Signaling Point (OSP) data to the RNC. The data includes 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. Scenario
5-4
RNC initial configuration

Mandatory/ Optional
NOTE
Mandatory
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.
Prerequisite
l l All the RNC subracks are switched to the offline mode. The basic data of the RNC is configured. For details, refer to 5.3 Adding Basic Data to the RNC (Initial).
Preparation
For the data to be negotiated and planned before you add OSP data to the RNC (initial), refer to 4.2 Global Data and Equipment Data of the RNC.
Procedure
Step 1 Run the ADD OPC command to add OSP to the RNC. ----End
5.5 Adding RNC Global Location Data (Initial)

This describes how to add global location data, including LA data (such as LAC and PLMN value tag range of the LA), RA data (such as RAC and PLMN value tag range of RA), CS SA data, PS SA data, and URA data. Scenario Mandatory/ Optional RNC initial configuration Mandatory
CAUTION
Only the global location data that is configured by this task can be used by cells. Figure 5-1 shows the parameter relationship in the addition of the global location data.
Issue 06 (2010-09-20)
5-5
Figure 5-1 Parameter relationship in the addition of the global location data
Prerequisite
The basic data of the RNC is configured. For details, refer to 5.3 Adding Basic Data to the RNC (Initial).
Preparation
For the data to be negotiated and planned before you add the RNC global location data (initial), refer to 4.2 Global Data and Equipment Data of the RNC.
Procedure
Step 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 command repeatedly. Step 4 Run the ADD URA command to add a URA ID. To add more URA IDs, run this command repeatedly.
Step 5 (Optional) Run the ADD CZ command to set an SA to be a classified zone. To add more classified zones, run this command repeatedly. ----End
5.6 Adding a Local M3UA Entity (Initial)

This describes how to add a local M3UA entity on the IP-based Iu or Iur interface. Scenario Mandatory/ Optional RNC initial configuration Optional. This task is mandatory only for the IP-based Iu or Iur interface.
CAUTION
The OSP data must be configured before a local M3UA entity is configured.
Prerequisite
l l The basic data of the RNC is configured. For details, refer to 5.3 Adding Basic Data to the RNC (Initial). The OSP data of the RNC is configured. For details, refer to 5.4 Adding OSP to the RNC (Initial).
Preparation
For the data to be negotiated and planned before you add a local M3UA entity, refer to 4.3 Data Negotiated Between RNC and Other Network Elements. Prepare the related data for the interface as required.
Procedure
Step 1 Run the ADD M3LE command to add a local M3UA entity.
CAUTION
An RNC supports a maximum of two local M3UA entities. For local entities of the M3UA_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
Issue 06 (2010-09-20)
5-7
6 Configuring RNC Equipment Data
6
1. 2.
Configuring RNC Equipment Data
About This Chapter

This describes how to configure RNC equipment data. The data includes RNC clock-related data, RNC time, basic data of the RSS subrack, and basic data of each RBS subrack. 6.1 Example: Equipment Data in the RNC Initial Configuration Script The equipment data includes the data of the RSS subrack, RBS subrack, RNC time and clock, and IP address of the EMS server. 6.2 Setting RNC Equipment Description (Initial) This describes how to set basic equipment attributes of the RNC. The data includes the system description, system ID, contact information of the vendor, system location, and system services. 6.3 Adding Basic Data of the RSS to the RNC (Initial) This describes how to add the basic data of the RSS to the RNC. The related activities include changing the RSS subrack number, setting the clock board type, adding a board, and setting the MSP attributes. 6.4 Adding Basic Data of the RBS to the RNC (Initial) This describes how to add an RNC Business Subrack (RBS) to the RNC. To add an RBS subrack, you need to add the data of the subrack and the boards. During the initial configuration, the data of each physically configured RBS subrack must be added to the RNC. 6.5 Adding an EMU (Initial) This describes how to add an EMU. 6.6 Configuring RNC Clock Data (Initial) This describes the configuration of the RNC clock data. The data refers to the clock source of the interface board, clock source of the system, and working modes of the clocks. 6.7 Setting RNC Time (Initial) This describes how to set RNC time. The related activities are the setting of the time zone that the RNC is in, whether the daylight saving time (DST) is used, and the DST information. If the RNC obtains the time information from the CN by connecting to the Simple Network Time Protocol (SNTP) server, you must also set the information of the SNTP server. 6.8 Adding the IP Address of the EMS Server (Initial)
3.
4.
5. 6.
7.
8.
Issue 06 (2010-09-20)
This describes how to add the IP address of the Element Management System (EMS) server that is used to perform OM on the NodeB through the RNC.
6-2
Issue 06 (2010-09-20)
6.1 Example: Equipment Data in the RNC Initial Configuration 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 SET RMV RMV RMV RMV RMV RMV RMV RMV RMV ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD SUBRACK: SRN=0, SRName="RSS"; CLKTYPE: CLKTYPE=GCU; BRD: SRN=0, SN=8; BRD: SRN=0, SN=9; BRD: SRN=0, SN=10; BRD: SRN=0, SN=11; BRD: SRN=0, SN=14; BRD: SRN=0, SN=16; BRD: SRN=0, SN=18; BRD: SRN=0, SN=24; BRD: SRN=0, SN=26; BRD: SRN=0, BRDTYPE=DPU, SN=8; BRD: SRN=0, BRDTYPE=DPU, SN=9; BRD: SRN=0, BRDTYPE=DPU, SN=10; BRD: SRN=0, BRDTYPE=DPU, SN=11; BRD: SRN=0, BRDTYPE=AEU, SN=14, RED=NO; BRD: SRN=0, BRDTYPE=AEU, SN=15, RED=NO; BRD: SRN=0, BRDTYPE=UOI_ATM, SN=16, RED=YES; BRD: SRN=0, BRDTYPE=GOU, SN=18, RED=YES; BRD: SRN=0, BRDTYPE=UOI_ATM, SN=24, RED=YES; BRD: SRN=0, BRDTYPE=UOI_ATM, SN=26, RED=YES;
//Add an RBS subrack.

ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD SUBRACK: SRN=1, SRName="RBS"; BRD: SRN=1, BRDTYPE=SPU, SN=8; BRD: SRN=1, BRDTYPE=SPU, SN=10; BRD: SRN=1, BRDTYPE=DPU, SN=14; BRD: SRN=1, BRDTYPE=DPU, SN=16; BRD: SRN=1, BRDTYPE=DPU, SN=18; BRD: SRN=1, BRDTYPE=AOU, SN=20, BRD: SRN=1, BRDTYPE=FG2, SN=22, BRD: SRN=1, BRDTYPE=GOU, SN=24, BRD: SRN=1, BRDTYPE=AEU, SN=26,
RED=YES; RED=YES; RED=YES; 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; ADD CLKSRC:SRCGRD=2, SRCT=LINE1_8KHZ; ADD CLKSRC:SRCGRD=3, SRCT=LINE2_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";
6.2 Setting RNC Equipment Description (Initial)

This describes how to set basic equipment attributes of the RNC. The data includes the system description, system ID, contact information of the vendor, system location, and system services. Scenario Mandatory/ Optional RNC initial configuration Optional. During the initialization of the RNC, the default RNC equipment description is automatically generated in the BAM database. You can modify it as required.
NOTE
The RNC equipment description is stored only in the BAM database, instead of being sent to the host.
Prerequisite
Preparation
None.
Procedure
Step 1 Run the SET SYS command to configure the RNC system description data. ----End
6.3 Adding Basic Data of the RSS to the RNC (Initial)

This describes how to add the basic data of the RSS to the RNC. The related activities include changing the RSS subrack number, setting the clock board type, adding a board, and setting the MSP attributes.
Scenario Mandatory/ Optional

NOTE
RNC initial configuration Mandatory.
For the restrictions on slot numbers of the boards in the RSS subrack, refer to Boards in the RNC Subrack.
Prerequisite
Preparation
Prepare the data based on the actual hardware configuration of the RSS subrack.
Procedure
Step 1 Run the LST SUBRACK command to query the RSS subrack name and the type of the clock board. Step 2 Perform the operations described in the following table according to the hardware planning. Item Change the name of the RSS subrack. Description Run the MOD SUBRACK command, set Subrack No. to 0, and enter the new name in the Subrack name box. Run the SET CLKTYPE command and set Clock board type to the new type.
Change the type of clock board.
Step 3 Run the ADD BRD command to add a board as required.

NOTE
l The INT interface boards refer to the interface boards AEUa, AOUa, UOIa, PEUa, POUa, FG2a, and GOUa. l The DPU boards refer to the DPUb. l The XPU boards refer to the SPUa.
Step 4 (Optional. Perform this step only when the AOUa, UOIa, or POUa boards are configured in board backup mode.) Run the SET MSP command to set the MSP attributes. The MSP attributes refer to Revertive type, WTR Time (required only when Revertive type is set to REVERTIVE), K2 Mode, SDSF Priority, and Backup mode. The settings of these parameters must be consistent with those at the peer end through negotiation. ----End
Issue 06 (2010-09-20)
6-5
6.4 Adding Basic Data of the RBS to the RNC (Initial)

This describes how to add an RNC Business Subrack (RBS) to the RNC. To add an RBS subrack, you need to add the data of the subrack and the boards. During the initial configuration, the data of each physically configured RBS subrack must be added to the RNC. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Optional. Perform this task when an RBS subrack needs to be added to the RNC.
l The types of interface boards physically positioned in the subrack must be consistent with the types of interface boards configured. l For the restrictions on slot numbers of the boards in the RBS subrack, refer to Boards in the RNC Subrack.
Prerequisite
l l The basic data of the RNC is configured. For details, refer to 5.3 Adding Basic Data to the RNC (Initial). The active and standby SCUa boards in the new RBS subrack are correctly connected to the active and standby SCUa boards in the RSS subrack through Ethernet cables.
Preparation
Prepare the data based on the actual hardware configuration of the RBS subrack.
Procedure
Step 1 Run the ADD SUBRACK command to add an RBS subrack. Set the subrack number and name. Step 2 Run the ADD BRD command to add a board as required.
NOTE
l The INT interface boards refer to the interface boards AEUa, AOUa, UOIa, PEUa, POUa, FG2a, and GOUa. l The DPU boars refer to the DPUb. l The XPU boars refer to the SPUa.
Step 3 (Optional. Perform this step only when the AOUa, UOIa, or POUa boards are configured in board backup mode.) Run the SET MSP command to set the MSP attributes. The MSP attributes refer to Revertive type, WTR Time (required only when Revertive type is set to REVERTIVE), K2 Mode, SDSF Priority, and Backup mode. The settings of these parameters must be consistent with those at the peer end through negotiation. ----End
6.5 Adding an EMU (Initial)

This describes how to add an EMU.

NOTE
RNC initial configuration Optional. Perform this task when the BSC6810 needs to collect the Boolean value, analog value, and alarm threshold information.
l The EMU gathers Boolean values, analog values, and alarm threshold information and reports them to the LMT. l One cabinet can be configured only one EMU.
Prerequisite
Preparation
The subrack for holding the EMU is already configured.
Procedure
Step 1 Run the ADD EMU command on the MML client to add an EMU. ----End
6.6 Configuring RNC Clock Data (Initial)

This describes the configuration of the RNC clock data. The data refers to the clock source of the interface board, clock source of the system, and working modes of the clocks. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the settings of the clock source of the interface board, clock source of the system, working modes of the clock are inconsistent 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 boards available for extracting timing signals, it is recommended that two interface board clock sources be configured. 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.
Prerequisite
Preparation
Determine the clock source in the interface board of the RSS or RBS subrack, clock source of the 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 RBS subrack. 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 subrack extracts the clock from the CN domain and sends it to the GCUa/GCGa board through the 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 subrack extracts the clock from the CN domain and sends it to the GCUa/GCGa board through the backplane channel in the RSS subrack, set Clock source type to LINE1_8KHZ or INE2_8KHZ. If the external BITS equipment provides the clock source, set Clock source type to BITS1-2MBPS, BITS2-2MBPS,, BITS1-T1BPS, or BITS2-T1BPS. If the clock source is the synchronous clock supplied by the GPS satellite and the GCGa serves 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 is unavailable, the system automatically switches to the clock source of the highest priority.
----End
6.7 Setting RNC Time (Initial)

This describes how to set RNC time. The related activities are the setting of the time zone that the RNC is in, whether the daylight saving time (DST) is used, and the DST information. If the RNC obtains the time information from the CN by connecting to the Simple Network Time Protocol (SNTP) server, you must also set the information of the SNTP server. Scenario Mandatory/ Optional RNC initial configuration Optional. During the initialization of the RNC, the time information of the RNC is automatically set. You can use default settings or modify them as required.
Prerequisite
l l The basic data of the RNC is configured. For details, refer to 5.3 Adding Basic Data to the RNC (Initial). If the time source of the RNC is a SNTP server, the connection between the SNTP server and the OMUa board must work properly.
Preparation
None.
Procedure
l l 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. Run the ADD SNTPSRVINFO command to add SNTP server information for SNTP client.
----End
6.8 Adding the IP Address of the EMS Server (Initial)

This describes how to add the IP address of the Element Management System (EMS) server that is used to perform OM on the NodeB through the RNC. Scenario Mandatory/ Optional RNC initial configuration Mandatory.
Prerequisite
None.
Preparation
For the data to be negotiated and planned before you add the IP address of the EMS server (initial), refer to 4.2 Global Data and Equipment Data of the RNC.
Procedure
Step 1 Run 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 External Network Virtual IP parameter.
----End
Issue 06 (2010-09-20)
6-9
7 Configuring Iub Interface Data (Initial)
Configuring Iub Interface Data (Initial)
About This Chapter

The Iub interface is the logical interface between the RNC and the NodeB. This topic describes how to add the transport network layer data on the Iub interface on the RNC side. 7.1 Example: Iub Data in the RNC Initial Configuration Script This describes an example of Iub data in the RNC initial configuration script. The Iub data consists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table, control plane data, user plane data, and OM channel data. 7.2 Data Configuration Guidelines for the Iub Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iub interface. Such information refers to the protocol stack, links on the Iub interface, and OM channel configuration guidelines. 7.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. 7.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 route configuration, and OM channel configuration guidelines. 7.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. 7.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-based networking, hardware configuration guidelines, data configuration guidelines, IP addresses and routes configuration, and OM channel configuration guidelines. 7.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 Iub interface.
Issue 06 (2010-09-20)
7-1
7.1 Example: Iub Data in the RNC Initial Configuration Script

This describes an example of Iub data in the RNC initial configuration script. The Iub data consists 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, set working 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 AEUa board 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: REMARK="FOR ADD ATMTRF: CDVT=1024, REMARK="FOR ADD ATMTRF: REMARK="FOR ADD ATMTRF: CDVT=1024, REMARK="FOR ADD ATMTRF: CDVT=1024, REMARK="FOR ADD ATMTRF: TRFX=110, ST=RTVBR, UT=CELL/S, PCR=217, SCR=170, MBS=1000, CDVT=1024, IUB NCP"; TRFX=120, ST=RTVBR, UT=CELL/S, PCR=2000, SCR=548, MBS=1000, IUB CCP"; TRFX=130, ST=RTVBR, UT=CELL/S, PCR=83, SCR=76, MBS=1000, CDVT=1024, IUB ALCAP"; TRFX=140, ST=RTVBR, UT=CELL/S, PCR=5312, SCR=4831, MBS=1000, R99 RT"; TRFX=150, ST=NRTVBR, UT=CELL/S, PCR=13154, SCR=10854, MBS=1000, R99 NRT"; TRFX=160, ST=UBR, CDVT=1024, REMARK="IUB FOR IPOA";
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 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 at subsystem 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 a port controller.

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;
Issue 06 (2010-09-20)
7-3
//Add an adjacent node over the Iub interface, that is, NODEB1. The adjacent node ID is 0 and the 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=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=2, PT=RT, CARRYT=IMA, CARRYF=0, CARRYSN=14, CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=44, 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 subnet mask is 255.255.255.0.
//Add an IPoA PVC. The local IP address is 10.218.107.126, the peer IP address is 10.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. The gateway 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";
7-4
Issue 06 (2010-09-20)
7.2 Data Configuration Guidelines for the Iub Interface (over ATM)
Related information is required for performing data configuration on the ATM-based Iub interface. Such information refers to the protocol stack, links on the Iub interface, and OM channel configuration guidelines. 7.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 7.2.2 Links on the Iub Interface (over ATM) This describes the links on the ATM-based Iub interface. 7.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.
7.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 7-1 shows the protocol stack for the ATM-based Iub interface. Figure 7-1 Protocol stack for the ATM-based Iub interface
Issue 06 (2010-09-20)
7-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 user plane (area C). l l Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areas can be carried on common physical links. 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 are carried in area B. In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is the ATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set up or released for the transmission of upper-layer services. Therefore, each AAL2 path must have its corresponding controlling Q.AAL2.
7.2.2 Links on the Iub Interface (over ATM)

This describes the links on the ATM-based Iub interface.
Links on the Iub Interface

The links on the ATM-based Iub interface are of three types: SAAL link of User-Network Interface (UNI) type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carry NCP, CCP, and ALCAP, as shown in Figure 7-2. Figure 7-2 Links on the ATM-based Iub interface
7-6
Issue 06 (2010-09-20)

NOTE
l The links in the NodeB are not shown in Figure 7-2 because the data configuration does not involve the internal information of the NodeB. l The RINT shown in Figure 7-2 refers to ATM interface boards UOIa (UOIa_ATM), AOUa, and AEUa.
SAAL Link of UNI Type

An SAAL link of UNI type carries signaling messages on the Iub interface. The signaling messages carried on the SAAL links are classified into NCP, CCP, and ALCAP, as described in Table 7-1. Table 7-1 Data carried on SAAL links of UNI type Data Type NCP CCP Description The NCP carries common process messages of NBAP over the Iub interface. An Iub interface has only one NCP. A CCP carries dedicated process messages of NBAP over the Iub interface. An Iub interface may have multiple CCPs. The number of CCPs depends on network planning. ALCAP is also called Q.AAL2. Typically, an Iub interface has one ALCAP.
ALCAP
An SAAL link of UNI type is carried on a PVC. The PVC identifier (VPI/VCI) and other attributes of the PVC must be negotiated between the RNC and the NodeB.
AAL2 Paths
An AAL2 path is a group of connections between the RNC and the NodeB. An Iub interface has at least one 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 the PVC 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.
7.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 7-3 shows the IPoA PVCs from the RNC to NodeBs.
Issue 06 (2010-09-20)
7-7
Figure 7-3 IPoA PVCs from the RNC to NodeBs
NOTE
The RINT shown in Figure 7-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 l 80.168.3.0 segment (with address mask of 255.0.0.0) between the OMUa board and the ATM interface board. This network segment is set before delivery of the RNC. 12.13.1.0 segment (with address mask of 255.255.255.0) between the ATM interface board and the NodeBs. When setting this network segment, you should take field conditions into consideration.
7.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. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Optional. Perform this task when the RNC connects to the NodeB in ATM transport mode.
l This task configures only the transport network layer data on the Iub interface. To enable cells controlled by 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 Iub interface, refer to 13.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 into consideration. For details, refer to 13.5 External Specifications for the RNC. l All the data of a NodeB, including data of cells and links, should be controlled by one SPU 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.
Prerequisite
The OSP data of the RNC is configured. For details, refer to 5.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, over ATM), refer to 4.3.1 Data Negotiated on the Iub Interface (over ATM).
Procedure
----End 1. 7.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. The types of interface boards should be determined before the related configuration. 7.3.2 Adding ATM Traffic Resources (Initial) This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links. 7.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 related activities are the addition of SAAL links, basic data and algorithm parameters of the NodeB, an adjacent node, and the NCP and CCPs. 7.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 7.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. Related activities are addition of the virtual port and the AAL2 path. 7.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 related activities are the setting of the device IP address of an interface board, the addition of an IPoA PVC between the RNC and the NodeB, and the setting of the OM IP address of the NodeB in ATM transport mode.
2.
3.
4.
5.
6.
7.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. The types of interface boards should be determined before the related configuration.
NOTE
For the recommended interface board types for different interfaces, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
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 the interface 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.
RNC initial configuration Optional. Perform this task only when the AEUa serves as the interface board.
CAUTION
l To configure the upper-layer application for the ATM physical port, adhere to the principles listed in 13.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 13.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 AEUa), refer to 4.3 Data Negotiated Between RNC and Other Network Elements. 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 in the 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 settings the same as those in E1 mode.
Step 2 Determine the E1/T1 application type and perform the corresponding configuration. Note that the E1/T1 application type can be only one of IMA, UNI, fractional IMA, fractional ATM, and timeslot cross connection. If the E1/T1 link carries... IMA link UNI link Fractional IMA link Fractional ATM link Timeslot cross connection Then... Go to Step 3. Go to Step 4. Go to Step 5. Go to Step 6. Go to Step 7.
7-10
Issue 06 (2010-09-20)
Step 3 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, perform this step repeatedly. 1. 2. Run the ADD IMAGRP command to add an IMA group. Run the ADD IMALNK command to add an IMA link to the IMA group. To add more IMA links, run this command repeatedly. End this task.
Step 4 Run the ADD UNILNK command to add a UNI link. Run this command repeatedly if multiple UNI links are required. End this task. Step 5 Add fractional IMA links by performing the following steps: 1. 2. Run the ADD IMAGRP command to add a fractional IMA group. 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 this command repeatedly. End this task.
Step 6 Run the ADD FRALNK command to add a fractional ATM link. Set Fractional link type to FRAATM. To add more fractional ATM links, run this command repeatedly. End this task. Step 7 If the source and destination timeslots are not used, run the ADD TSCROSS command to add a timeslot cross connection. End this task. ----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 as the interface board. The associated type of application on E1/T1 links may be of the following types: IMA link and UNI link. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the AOUa serves as the interface board.
CAUTION
For the configuration restrictions on each type of upper-layer link carried on the AOUa board, refer to 13.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 4.3 Data Negotiated Between RNC and Other Network Elements. 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 in the 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 in the database.) Run the SET OPT command to set the parameters of the optical ports on the AOUa board. Step 3 (Optional. Perform this step only when the RNC needs to interwork with equipment from another vendor.) Run the SET COPTLNK command to set the parameters of a channelized optical port on the AOUa board. Step 4 Determine the E1/T1 application type and perform the corresponding configuration. Note that the E1/T1 application type can be either IMA or UNI, not both. If the E1/T1 link carries... IMA link UNI link Then... Go to Step 5. Go to Step 6.
Step 5 Add an IMA group and add IMA links to the IMA group. To add more IMA groups, perform this step repeatedly. 1. 2. Run the ADD IMAGRP command to add an IMA group. 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 6 Run the ADD UNILNK command to add a UNI link. To add more UNI links, run this command repeatedly. This task is complete. ----End
Adding Physical Layer Data on the Interface (Initial, with UOIa)

This describes how to add physical layer data on an interface when the UOIa serves as the interface board. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the UOIa serves as the interface board.
Prerequisite
Preparation
For the data to be negotiated and planned before you add the physical layer data on the interface (initial, with UOIa), refer to 4.3 Data Negotiated Between RNC and Other Network Elements. Prepare the related data for the interface as required.
Procedure
Step 1 Optional: If the planned data is inconsistent with the default data in the database, run the SET OPT command to set the proprieties of the optical port on the UOIa with the Logic function type as ATM. ----End
7.3.2 Adding ATM Traffic Resources (Initial)

This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Mandatory
l When adding the RNC ATM traffic resources, observe 13.5.1 Specifications for Traffic on RNC Boards. l For types of service, traffic parameters, and configuration guidelines of ATM traffic resources, refer to 13.8 PVC Parameters of the RNC.
Prerequisite
Preparation
For the data to be negotiated and planned before you add ATM traffic resources, refer to 4.3 Data Negotiated Between RNC and Other Network Elements. Prepare the related data for the interface as required.
Procedure
Step 1 Run the ADD ATMTRF command to add an ATM traffic record. To add more ATM traffic records, run this command repeatedly.
NOTE
One RNC can be configured with 500 ATM traffic records.
----End
7.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 related activities are the addition of SAAL links, basic data and algorithm parameters of the NodeB, an adjacent node, and the NCP and CCPs.
CAUTION
l The Iub interface needs to be configured with at least three SAAL UNI links. One SAAL UNI link is used for one NCP; at least one SAAL UNI link is used for one CCP; one SAAL UNI link is used to carry an ALCAP link, that is, a Q.AAL2 signaling link. l Between an RNC and a NodeB, only one NCP can be configured, but multiple CCPs are allowed. Figure 7-4 shows the parameter relationship in the addition of the SAAL link. Figure 7-4 Parameter relationship in the addition of the SAAL link
Figure 7-5 shows the parameter relationship in the addition of the adjacent node.
7-14
Issue 06 (2010-09-20)
Figure 7-5 Parameter relationship in the addition of the adjacent node
Prerequisite
l l The physical layer data on the external interface of the RNC is configured. For details, refer to 7.3.1 Adding Physical Layer Data (Initial, over ATM). Traffic resources at the ATM layer are configured. For details, refer to 7.3.2 Adding ATM Traffic Resources (Initial).
Preparation
For the data to be negotiated and planned before you configure the Iub control plane on the RNC (initial, over ATM), refer to 4.3.1 Data Negotiated on the Iub Interface (over ATM).
Procedure
Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to UNI. To add more 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: Set IUB trans bearer type to ATM_TRANS. 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 the NodeB. Step 5 Run the ADD NODEBOLC command to add overload congestion algorithm parameters for the NodeB. Step 6 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUB. l Set Transport Type to ATM.
Step 7 Run the ADD NCP command to add an NCP. Set Bearing link type to SAAL. Step 8 Run the ADD CCP command to add a CCP. Set Bearing link type to SAAL. To add more CCPs, run this command repeatedly. ----End
7.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial)
This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. Scenario Mandatory/ Optional
NOTE
l For the guidelines for configuring the TRM mapping between service types and transmission resources, refer to 13.12 TRM Configuration Guidelines. l For the guidelines for configuring the activity factor table, refer to 13.13 Activity Factor Configuration Guidelines.
Prerequisite
Preparation
Table 7-2 describes the data to be negotiated and planned before you configure the TRM mapping. Table 7-2 TRM mapping data to be negotiated and planned Item Mapping between service types and transmission resources Description Based on the requirements, configure the preferred path and candidate path for each type of service on Iub, Iu, and Iur interfaces. Data Source Data planning in the RNC
Table 7-3 describes the data to be negotiated and planned before you add the activity factor table.
7-16
Issue 06 (2010-09-20)
Table 7-3 Activity factor to be negotiated and planned Item Activity factors for services Description Activity factor used by each type of service Data Source Data planning in the RNC
Procedure
Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, run this command repeatedly. Step 2 Run the ADD TRMFACTOR command to add an activity factor table. Step 3 (Optional. This command is run only when the Iub interface uses the dual stack or hybrid IP transmission mode.) Run the ADD LOADEQ command to add a threshold table of loading balancing between the active and standby boards. Step 4 Run the ADD ADJMAP command to configure the TRM mapping tables for users of specific priorities and the activity factor table. ----End
7.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. Related activities are addition of the virtual port and the AAL2 path. Scenario Mandatory/ Optional
NOTE
When adding the Iub user plane data to the RNC, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.7 RNC Capability for AAL2 Paths and AAL2 Routes.
Figure 7-6 shows the parameter relationship in the addition of the AAL2 path.
Issue 06 (2010-09-20)
7-17
Figure 7-6 Parameter relationship in the addition of the AAL2 path in the ATM-based interface
Prerequisite
The control plane data for the Iub interface in ATM transport is successfully configured. For details, refer to 7.3.3 Adding Control Plane Data on the Iub Interface (Initial, over ATM).
Preparation
For the data to be negotiated and planned before you configure the Iub user plane on the RNC (initial, over ATM), refer to 4.3.1 Data Negotiated on the Iub Interface (over ATM).
Procedure
Step 1 (Optional. Perform this step when the ATM traffic shaping and congestion control functions are enabled) Run the ADD ATMLOGICPORT command to add an ATM virtual port.
NOTE
If the RAN sharing function is used and the user plane resources are separated by operators, set Resource Management Mode to EXCLUSIVE and set Cn Operator Index.
Step 2 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, run this command repeatedly.
NOTE
If the ATM traffic shaping and congestion control functions or the user plane resource separation by operators in RAM sharing is already enabled by running the ADD ATMLOGICPORT command, set The bearing type of the virtual port to ATMLOGICPORT, which indicates that the AAL2 path is used to carry the user plan resources of the specified operator.
7-18
Issue 06 (2010-09-20)
Step 3 Run the ADD AAL2RT command to add an AAL2 route. ----End
7.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 related activities are the setting of the device IP address of an interface board, the addition of an IPoA PVC between the RNC and the NodeB, and the setting of the OM IP address of the NodeB in ATM transport mode. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Figure 7-7 shows the parameter relationship in the addition of the IPoA PVC. Figure 7-7 Parameter relationship in the addition of the IPoA PVC
Figure 7-8 shows how to add parameter relationship in the addition of the OM IP address of the NodeB in ATM transport mode.
Figure 7-8 Parameter relationship in the addition of the OM IP address of the NodeB in ATM transport mode
Prerequisite
l l l The Iub control plane data is configured. For details, refer to 7.3.3 Adding Control Plane Data on the Iub Interface (Initial, over ATM). The Iub user plane data is configured. For details, refer to 7.3.5 Adding User Plane Data on the Iub Interface (Initial, over ATM). The IP address of the Element Management System (EMS) is configured. For details, refer to 6.8 Adding the IP Address of the EMS Server (Initial).
Preparation
For the data to be negotiated and planned before you add the OM channel on the Iub interface (initial, over ATM), refer to 4.3.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. Set Peer type to IUB. Step 3 Run the ADD NODEBIP command to add the IP address of the NodeB. The details are as follows: l Set NodeB TransType to ATMTRANS_IP. l Set NodeB ATM_TRANS IP address and NodeB ATM_TRANS IP Mask to the OM IP address and mask of the NodeB in ATM transport mode. ----End
7-20
Issue 06 (2010-09-20)
7.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 route configuration, and OM channel configuration guidelines. 7.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 should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 7.4.2 Links on the Iub Interface (over IP) This describes the links on the IP-based Iub interface. 7.4.3 IP Addresses and Routes on the Iub Interface (over IP) On the IP-based or ATM/IP dual stackbased Iub interface, IP addresses and routes are required. 7.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. They are routing between the M2000 and the NodeB through the RNC and routing between the M2000 and the NodeB not through the RNC.
7.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 should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 7-9 shows the protocol stack for IP transport on the Iub interface.
Issue 06 (2010-09-20)
7-21
Figure 7-9 Protocol stack for IP transport on the Iub interface
7.4.2 Links on the Iub Interface (over IP)

This describes the links on the IP-based Iub interface.
Links on the Iub Interface

The IP-based Iub interface has two types of links, that is, the SCTP link and IP path. The SCTP link is used to carry NCP and CCP, as shown in Figure 7-10.
7-22
Issue 06 (2010-09-20)
Figure 7-10 Links on the Iub interface (over IP)
NOTE
l The links in the NodeB are not shown in Figure 7-10 because the data configuration does not involve the internal information of the NodeB. l The RINT shown in Figure 7-10 refers to IP interface boards PEUa, POUa, UOIa (UOIa_IP), FG2a, and GOUa.
SCTP Links
An SCTP link carries signaling messages on the Iub interface. The signaling messages carried on the SCTP links are classified into NCP and CCP, as described in Table 7-4. Table 7-4 Data carried on SCTP links Data Type NCP CCP Description The NCP carries common process messages of NBAP over the Iub interface. An Iub interface has only one NCP. A CCP carries dedicated process messages of NBAP over the Iub interface. An Iub interface may have multiple CCPs. The number of CCPs depends on network planning.
The SCTP link can work in two modes, SERVER and CLIENT, on the RNC and the NodeB sides. On the RNC side, the differences between the two working modes are as follows: l SERVER: The local end enables only the listening port and the peer end sends the initialization request.
Issue 06 (2010-09-20)
In SERVER mode, all SCTP links use the listening port as a local port. The listening port also becomes the local port of NCP or CCP on the control plane. On the NodeB side, a port number is added to each new NCP and CCP. l CLIENT: The local end sends the initialization request during the setup of a link. In CLIENT mode, each SCTP link must be configured with a local port, which means that a local port number is added to each NCP and CCP. On the NodeB side, only one port number needs to be configured. It is recommended that the working mode of the RNC be set to SERVER when you configure an SCTP link.
IP Paths
An IP path is a group of connections between the RNC and the NodeB. An Iub interface has at least one AAL2 path. It is recommended that two or more AAL2 paths be planned.
7.4.3 IP Addresses and Routes on the Iub Interface (over IP)

On the IP-based or ATM/IP dual stackbased Iub interface, IP addresses and routes are required.
Networking on the Iub Interface

There are two types of networking on the Iub interface, namely, layer 2 networking and layer 3 networking. Compared with layer 3 networking, layer 2 networking is simpler. That is because the port IP addresses of the RNC and NodeB are located on the same network segment and no route is required. Figure 7-11 shows an example of layer 2 networking on the Iub interface. Figure 7-11 Layer 2 networking on the Iub interface
7-24
Issue 06 (2010-09-20)

NOTE
IP 1 and IP 2 are port IP addresses.
Figure 7-12 shows an example of layer 3 networking on the Iub interface. Figure 7-12 Layer 3 networking on the Iub interface
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 the IP interface board. IP 5 and IP 6 are gateway IP addresses on the RNC side. IP 7 is the gateway IP address on the NodeB side. IP 8 is the IP address of the NodeB.
IP Addresses on the Iub Interface

As shown in Figure 7-11 and Figure 7-12, the Iub IP addresses at the RNC consist of IP addresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP groups, and device IP addresses. Table 7-5 describes these IP addresses. Table 7-5 IP addresses on the Iub interface IP Address IP address of an Ethernet port Configuration Scenario Required when the FG2a or GOUa serves as the interface board Configuration Restriction l Each Ethernet port can be configured with only one primary IP address and 5 secondary addresses. l The IP address of an Ethernet port and the internal IP address of the BAM must be located on different network segments. For these network segments, one cannot cover another. l In the RNC, the IP addresses of different Ethernet ports must be located on different network segments. For these network segments, one cannot cover another.
IP Address Local IP address of a PPP link Local IP address of an MLPPP group Device IP address
Configuration Scenario Required when the PEUa, POUa, or UOI_IP serves as the interface board Required when the PEUa or POUa serves as the interface board Required in layer 3 networking
Configuration Restriction Each PPP link can be configured with only one local IP address. Each MLPPP group can be configured with only one local IP address. l Each interface board can be configured with a maximum of five device IP addresses. l The IP addresses of any two different devices must be located on different subnets.
Route on the Iub Interface

On the Iub interface where layer 2 networking is applied, no route is required. On the Iub interface where layer 3 networking is applied, you should configure the route described in Table 7-6 on the RNC. Table 7-6 Route on the Iub Interface Device IP interface board Route Description The route travels from the RNC to the network segment where the NodeB is located. 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 the NodeB is located, and Next Hop Address is the gateway IP address on the RNC side, for example, IP 5 or IP 6.
7.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. They are routing between the M2000 and the NodeB through the RNC and routing between the M2000 and the NodeB not through the RNC.
Routing Between the M2000 and the NodeB Through the RNC
Figure 7-13 shows an example of routing between the M2000 and the NodeB through the RNC. Table 7-7 describes the routes.
7-26
Issue 06 (2010-09-20)
Figure 7-13 Example of routing between the M2000 and the NodeB through the RNC
NOTE
l Figure 7-13 takes layer 2 networking on the Iub interface for an example. When layer 3 networking is applied to the Iub interface, the IP interface board and the NodeB communicate through a router. l The RINT shown in Figure 7-13 refers to IP interface boards PEUa, POUa, UOI_IP, FG2a, and GOUa.
Table 7-7 Routes for the connection between the M2000 and the NodeB through the RNC Equipment M2000 Forward Route From the M2000 to the NodeB OM network segment 19.19.19.X, with the next hop to be the external virtual IP address of the BAM, that is, 172.121.139.200 From the OMUa board to the NodeB OM network segment 19.19.19.X, with the next hop to be the internal IP address of the IP interface board at the RNC, that is, 80.168.3.66 Reverse Route -
RNC
From the IP interface board of the RNC to the M2000 IP network segment 172.121.139.X You can run the ADD EMSIP command on the RNC to configure the route. When you run this command, set EMS IP Address to the IP address of the M2000, set Subnet mask to the subnet mask of the M2000, and specify the values of BAM External Network Virtual IP and BAM External Network Mask. In this example, EMS IP Address is 172.121.139.56, and BAM External Network Virtual IP is 172.121.139.200.
Issue 06 (2010-09-20)
7-27
Equipment
Forward Route From the IP interface board of the RNC to the NodeB OM network segment 19.19.19.X l If layer 2 networking is applied to the Iub interface, the next hop is the IP address of the interface board at the NodeB, that is, 16.16.16.2. l If layer 3 networking is applied to the Iub interface, the next hop is the gateway IP address on the RNC side. You can run the ADD NODEBIP command on the RNC to configure the route. IP address is the OM IP address of the NodeB. l If layer 2 networking is applied to the Iub interface, Gateway IP address is the IP address of the interface board at the NodeB. l If layer 3 networking is applied to the Iub interface, Gateway IP address is the gateway IP address on the RNC side.
Reverse Route
NodeB
From the NodeB to the M2000 IP network segment 172.121.139.X l If layer 2 networking is applied to the Iub interface, the next hop is the IP address of the IP interface board at the RNC, that is, 16.16.16.1. l If layer 3 networking is applied to the Iub interface, the next hop is the gateway IP address on the NodeB side.
Routing Between the M2000 and the NodeB Not Through the RNC
If the OM subnet where the M2000 is located is connected to the IP network that covers the NodeB, routes can be configured between the M2000 and the NodeB not through the RNC. Figure 7-14 shows an example of routing between the M2000 and the NodeB not through the RNC. Table 7-8 describes the routes.
7-28
Issue 06 (2010-09-20)
Figure 7-14 Example of routing between the M2000 and the NodeB not through the RNC
Table 7-8 Routes for the connection between the M2000 and the NodeB not through the RNC Equipment M2000 Forward Route From the M2000 to the NodeB OM network segment 19.19.19.X, with the next hop to be the port IP address of router 1, that is, 10.161.215.200 From router 1 to the NodeB OM network segment 19.19.19.X, with the next hop to be the port IP address of router 2, that is, 172.16.16.10 From router 2 to the NodeB OM network segment 19.19.19.X, with the next hop to be the IP address of the IP interface board at the NodeB, that is, 16.16.16.2 Reverse Route -
Router 1
Router 2
From router 2 to the M2000 network segment 10.161.215.100, with the next hop to be the port IP address of router 1, that is, 172.16.16.9 From the NodeB to the M2000 network segment 10.161.215.100, with the next hop to be the port IP address of router 2, that is, 16.16.16.20
NodeB
7.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. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task when the RNC connects to the NodeB in IP transport mode.
Issue 06 (2010-09-20)
7-29

NOTE
l This task configures only the transport network layer data on the Iub interface. To enable cells controlled by 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 Iub interface, refer to 13.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 into consideration. For details, refer to 13.5 External Specifications for the RNC. l All the data of a NodeB, including data of cells and links, should be controlled by one SPU 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.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iub interface (initial, over IP), refer to 4.3.2 Data Negotiated on the Iub Interface (over IP). 1. 7.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 configuration of 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 the corresponding physical layer and data link layer data according to the interface board type. 7.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 related activities are the addition of SCTP signaling links, basic data and algorithm parameters of the NodeB, an adjacent node, and the NCP and CCPs. 7.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 7.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 activities include addition of the IP path, IP route, and transmission resource group. 7.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 activities are the setting of the OM IP address of the NodeB and the addition of the electronic serial number of the NodeB that uses DHCP.
2.
3.
4.
5.
7.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 configuration of 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 the corresponding physical layer and data link layer data according to the interface board type.
7-30
Issue 06 (2010-09-20)

NOTE
For the recommended interface board types of different interfaces, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
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 when the FG2a or GOUa serves as the IP interface board. The related activities are setting the properties of the Ethernet port, adding the primary and secondary IP addresses for the Ethernet port, adding a link aggregation group, adding a sublink to the aggregation group, and setting the primary and secondary IP addresses for the link aggregation group. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the FG2a/GOUa serves as the interface board.
Prerequisite
Preparation
For the data to be negotiated and planned before you add the physical layer and data link layer data on the interface (initial, with FG2a/GOUa), refer to 4.3 Data Negotiated Between RNC and Other Network Elements. Prepare the related data for the interface as required.
Procedure
Step 1 Check whether the link aggregation function is required and then perform the corresponding step. If... Link non-aggregation mode Link aggregation mode Step 2 Link non-aggregation mode 1. 2. 3. Run the SET ETHPORT command to set the properties of the Ethernet port. Run the ADD ETHIP command to add the IP address of the Ethernet port. (Optional. Perform this step when multiple VLAN gateways need to be configured). Run the ADD ETHIP command to add the secondary IP for the Ethernet port. Run the SET ETHPORT command to set the properties of the Ethernet port. The Ethernet ports need to be used in link aggregation must work in full duplex mode, and the FE port speed must be set consistent.
Then... Go to Step 2. Go to Step 3.
Step 3 Link aggregation mode 1.
Issue 06 (2010-09-20)
2.
Run the ADD ETHTRK command to add a link aggregation group.

NOTE
Run the DSP ETHTRK command to query the status of trunk group.
3.
Run the ADD ETHTRKLNK command to add a sublink to the link aggregation group. To add more sublink to the link aggregation group, run this command repeatedly.
NOTE
l Run the DSP ETHTRKLNK command to query the status of trunk link. l The links of the same link aggregation group can be distributed on discontinuous ports. l The ports bound with links cannot work with the ports on other boards in backup or load sharing relation. l If one link is faulty, the system removes it automatically. After the link restores to the normal state, the port carrying the link negotiates with the peer end automatically. If the negotiation succeeds, the link is added to the link aggregation group automatically.
4. 5.
Run the ADD ETHTRKIP command to add primary IP address for the link aggregation group. (Optional. Perform this step when multiple VLAN gateways need to be configured). Run the ETHTRKIP command to add the secondary IP for the link aggregation group.
Step 4 (Optional. Perform this step only when using layer 3 networking.) Run the ADD DEVIP command 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 when the PEUa serves as the IP interface board. At least one of the PPP link data and MLPPP link data must be configured. Scenario Mandatory/ Optional RNC initial configuration 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 layer data on the external interface (initial, with PEUa) of the RNC, refer to 4.3 Data Negotiated Between RNC and Other Network Elements. 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 in the database.) Run the SET E1T1 command to set the parameters of E1/T1 links.

NOTE
In T1 mode, use the SET E1T1 command to set the link to the required T1 type and keep other settings the same as those in E1 mode.
Step 2 Determine the type of the upper-layer application in E1/T1 (PPP link or MLPPP groups) and then perform the associated step as described in the following table. If... PPP links need to be configured MLPPP groups need to be configured Step 3 Add the PPP link data. 1. Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. Then... Go to Step 3. Go to Step 4.
Step 4 Add the MLPPP group data. 1. 2. Run the ADD MPGRP command to add an MLPPP group. Run the ADD MPLNK command to add an MLPPP link.
CAUTION
l 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 a board. l Slot 0 is beyond the value range of Bearing time slot. The values of bearing timeslot for the same Digital Signaling level 1 (DS1) must be consecutive. Timeslot 16 on an E1 link is optional. That is, timeslots 15, 16, and 17 are regarded as consecutive, and the same is true for timeslots 15 and 17. A timeslot on an E1/T1 link can be used by only 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 the RNC when the POUa serves as the IP interface board. The related activities are the setting of E1/T1 attributes, optical port attributes, and channel attributes of the channelized optical port, and the addition of PPP links or MLPPP groups. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the POUa serves as the interface board.
Issue 06 (2010-09-20)
7-33
Prerequisite
Preparation
For the data to be negotiated and planned before you add the physical layer and data link layer data on the interface (initial, with POUa), refer to 4.3 Data Negotiated Between RNC and Other 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 TX Value, 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 then perform the associated step as described in the following table. If... PPP links need to be configured MLPPP link groups need to be configured Then... Go to Step 5. Go to Step 6.
Step 5 Run the ADD PPPLNK command to add a PPP link. To add more PPP links, run this command repeatedly. Step 6 To add an MLPPP link group, perform the following steps: 1. 2. Run the ADD MPGRP command to add an MLPPP group. Run the ADD MPLNK command to add an MLPPP link.
7-34
Issue 06 (2010-09-20)
CAUTION
l 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 a board. l Slot 0 is beyond the value range of Bearing time slot. The values of bearing timeslot for the same Digital Signaling level 1 (DS1) must be consecutive. Timeslot 16 on an E1 link is optional. That is, timeslots 15, 16, and 17 are regarded as consecutive, and the same is true for timeslots 15 and 17. A timeslot on an E1/T1 link can be used by only one PPP or MLPPP link. ----End
Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with UOIa)
This describes how to add the physical layer and data link layer data on the interfaces of the RNC when the UOIa (UOIa_IP) serves as the IP interface board. The related activities are the configuration of optical port attributes and the addition of PPP links. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the UOIa serves as the interface board.
Prerequisite
Preparation
For the data to be negotiated and planned before you add the physical layer and data link layer data on the interface (initial, with UOIa), refer to 4.3 Data Negotiated Between RNC and Other Network Elements. Prepare the related data for the interface as required.
Procedure
Step 1 Run the SET OPT command to set properties of the optical port on the UOIa interface with the Logic function type as IP.
NOTE
J0 TX Type, J0 TX Value, Expected J0 RX Type, Expected J0 RX Value, J1 TX Type, J1 TX Value, 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 command repeatedly. ----End
7.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 related activities are the addition of SCTP signaling links, basic data and algorithm parameters of the NodeB, an adjacent node, and the NCP and CCPs. Scenario Mandatory/ Optional
NOTE
l The IP-based Iub interface needs to be configured with at least two SCTP links: one for the NCP and the 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/T1 share 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 RNC processing capability into consideration. For details, refer to 13.5.3 RNC Capability for SCTP.
Figure 7-15 shows the parameter relationship in the addition of the SCTP link. Figure 7-15 Parameter relationship in the addition of the SCTP link
Figure 7-16 shows the parameter relationship in the addition of the IP adjacent node. Figure 7-16 Parameter relationship in the addition of the IP adjacent node
7-36
Issue 06 (2010-09-20)
Figure 7-17 shows the parameter relationship in the addition of the port data. Figure 7-17 Parameter relationship in the addition of the port data
Prerequisite
The data of the physical layer and data link layer for IP transport is configured. For details, refer to 7.5.1 Adding Physical Layer and Data Link Layer Data (Initial, over IP).
Preparation
For the data to be negotiated and planned before you configure the Iub control plane on the RNC (initial, over IP), refer to 4.3.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 this command repeatedly. The details are as follows: l Set Signalling link model to SERVER. l Set Application type to NBAP.
NOTE
If multiple SCTP links use the same source IP address and destination IP address, adhere to the following principle when configuring these SCTP links: The sum of the source port number and the destination port number of a newly configured SCTP link is eight greater than or smaller than the sum of the source port number and the destination port number of any configured SCTP link.
Step 2 Run the ADD NODEB command to add the basic data of a NodeB. Set IUB trans bearer type to IP_TRANS.

NOTE
When satellite-based networking is applied to the Iub interface, set Satellite Trans Ind to TRUE and IUB Trans 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. Step 4 Run the ADD NODEBLDR command to add load reshuffling algorithm parameters for the NodeB. Step 5 Run the ADD NODEBOLC command to add overload congestion algorithm parameters for the NodeB. Step 6 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUB. l Set Transport Type to IP. Step 7 Run the ADD NCP command to add an NCP. Set Bearing link type to SCTP. Step 8 Run the ADD CCP command to add a CCP. Set Bearing link type to SCTP. To add more CCPs, run this command repeatedly. ----End
NOTE
Prerequisite
Preparation
Table 7-9 describes the data to be negotiated and planned before you configure the TRM mapping.
Table 7-9 TRM mapping data to be negotiated and planned Item Mapping between service types and transmission resources Description Based on the requirements, configure the preferred path and candidate path for each type of service on Iub, Iu, and Iur interfaces. Data Source Data planning in the RNC
Table 7-10 describes the data to be negotiated and planned before you add the activity factor table. Table 7-10 Activity factor to be negotiated and planned Item Activity factors for services Description Activity factor used by each type of service Data Source Data planning in the RNC
Procedure
7.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 activities include addition of the IP path, IP route, and transmission resource group. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Figure 7-18 shows the parameter relationship in the addition of the IP path.
Figure 7-18 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 7.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 4.3.2 Data Negotiated on the Iub Interface (over IP).
Procedure
Step 1 (Optional. Perform this step when the RAN sharing function is used) Run the ADD IPLOGICPORT command to add a logical port.
NOTE
If the user plane resources on the Iub interface are separated by operators, set Resource Management Mode to EXCLUSIVE and set Cn Operator Index.
Step 2 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly.
NOTE
The Iub interface supports the FP MUX function. To enable the FP MUX function, set FPMUX Enable to YES, and configure Maximum Subframe Length, Maximum Multiplexing Packet Number, and Maximum Multiplexing Delay.
Step 3 (Optional. Perform this step only when the Iub interface uses layer 3 networking.) Run the ADD IPRT command to add an IP route. ----End
7.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 activities are the setting of the OM IP address of the NodeB and the addition of the electronic serial number of the NodeB that uses DHCP.
Prerequisite
l The control plane data for the Iub interface in IP transport is successfully configured. For details, refer to 7.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP). The IP address of the Element Management System (EMS) is configured. For details, refer to 6.8 Adding the IP Address of the EMS Server (Initial).
Preparation
For the data to be negotiated and planned before you add the OM channel on the Iub interface (initial, over IP), refer to 4.3.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 as follows: l Set NodeB TransType to IPTRANS_IP. l Set NodeB IP_TRANS IP address and NodeB IP_TRANS IP Mask to the OM IP address and mask in IP transport mode. l When L3 networking is used between the RNC and the NodeB, set NodeB IP_TRANS Next hop IP address to the IP address of the RNC gateway. When L2 networking is used between the RNC and the NodeB, set NodeB IP_TRANS Next hop IP address to the IP address of the NodeB interface board. Step 2 If the peer NodeB uses the DHCP, perform the following steps: 1. 2. Run the ADD NODEBESN command to add the electronic serial number of the NodeB. (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 the NodeB detecting function. With this function, the NodeB can obtain the VLAN ID of the RNC broadcast from the network when the NodeB is set up or faulty. Hence, the NodeB can start up normally and the local maintenance is avoided.
----End
7.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-based networking, hardware configuration guidelines, data configuration guidelines, IP addresses and routes configuration, and OM channel configuration guidelines. 7.6.1 ATM/IP Hybrid Transport on the Iub Interface
With 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 on ATM over E1, however, causes high cost. Data services produce a decreasing efficiency for operators. Therefore, the operators require a low-cost Iub transmission solution. In such a situation, ATM/IP hybrid transport, which is based on the ATM/IP dual stack, is introduced. In addition to the guarantee of services, this transport reduces costs of data transmission on the Iub interface. 7.6.2 ATM/IP-Based Networking on the Iub Interface The ATM/IP-based networking on the Iub interface refers to the case where the ATM/IP dual stack is used between the RNC and the NodeB. 7.6.3 Hardware Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface This describes the hardware configuration guidelines for ATM/IP hybrid transport on the Iub interface in terms of board configuration, cable connections, and hardware-related precautions. 7.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface This describes the data configuration guidelines for ATM/IP hybrid transport on the Iub interface in terms of VLAN planning, transmission resource allocation, and traffic distribution. 7.6.5 IP Addresses and Routes on the Iub Interface (over IP) On the IP-based or ATM/IP dual stackbased Iub interface, IP addresses and routes are required. 7.6.6 OM Channel Configuration on the Iub Interface (over IP) Two ways are available for configuring routes for the OM channel on the Iub interface. They are routing between the M2000 and the NodeB through the RNC and routing between the M2000 and the NodeB not through the RNC.
7.6.1 ATM/IP Hybrid Transport on the Iub Interface

With 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 on ATM over E1, however, causes high cost. Data services produce a decreasing efficiency for operators. Therefore, the operators require a low-cost Iub transmission solution. In such a situation, ATM/IP hybrid transport, which is based on the ATM/IP dual stack, is introduced. In addition to the guarantee of services, this transport reduces costs of data transmission on the Iub interface. Based on the Quality of Service (QoS) and bandwidth requirements, ATM/IP hybrid transport implements 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 ATM networks. BE services and HSDPA/HSUPA services have a relatively high requirement for the bandwidth 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 impact of IP transport on the ATM networks, and meets the requirements of operators for highly efficient and low-cost networks and for flexible networking.
7-42
Issue 06 (2010-09-20)
7.6.2 ATM/IP-Based Networking on the Iub Interface

The ATM/IP-based networking on the Iub interface refers to the case where the ATM/IP dual stack is used between the RNC and the NodeB. With the development of data services, especially the introduction of High Speed Downlink Packet Access (HSDPA) and High Speed Uplink Packet Access (HSUPA), the Iub interface has an increasing demand for the bandwidth. A pure ATM network is expensive to operate. The IP technology 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 different QoS 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 QoS requirements. 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, such as HSDPA and HSUPA services, are transmitted on the IP network. Figure 7-19 shows the ATM/IP-based networking. Figure 7-19 ATM/IP dual stack-based networking
An RSS or RBS in the RNC is configured with the ATM interface board and the IP interface board at the same time. l l The ATM interface board can be an AEUa, AOUa, or UOIa board. It is connected to the ATM network through the E1/T1 port, channelized STM-1 port, or OC-3C port. The IP interface board can be an FG2a, GOUa, PEUa, POUa, or UOIa board. It is connected to the IP network through the E1/T1 port, channelized STM-1 port, or OC-3C port.
The NodeB is connected to the ATM and IP networks through the corresponding ATM and IP interface boards respectively.
Advantages
l
Issue 06 (2010-09-20)
The ATM network ensures the QoS.

The IP network saves the transmission cost and meets the requirement for high bandwidth on the Iub interface.
Disadvantages
When the ATM/IP-based networking is applied, maintenance is required for both ATM network and IP network. Thus increasing the difficulty in and cost of maintaining the networks.
7.6.3 Hardware Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface
This describes the hardware configuration guidelines for ATM/IP hybrid transport on the Iub interface in terms of board configuration, cable connections, and hardware-related precautions.
Hardware Configuration Guidelines for ATM/IP Hybrid Transport

When implementing ATM/IP hybrid transport, insert ATM and IP interface boards into the slots of the RSS and RBS subracks. That is, an ATM/IP dual stackbased NodeB can be connected to an ATM interface board and an IP interface board at the same time. The two interface boards can be positioned in different subracks.
NOTE
Though the RNC ATM and IP interface boards for one NodeB can be positioned in different subracks, it is recommended that the interface boards be positioned in one subrack if possible.
Interface Board Configuration for ATM/IP Hybrid Transport

All ATM and IP interface boards are available for ATM/IP hybrid transport. The recommended interface boards are as follows: l l ATM interface board: UOIa (UOIa_ATM), AOUa, and AEUa IP interface board: GOUa, FG2a, POUa, PEUa, and UOIa (UOIa_IP)
Figure 7-20 and Figure 7-21 show the typical configurations of interface boards for ATM/IP hybrid transport. As shown in the figures, the AOUa serves as the ATM interface board and the GOUa serves as the IP interface board. Figure 7-20 Typical configuration of boards in the RSS subrack for ATM/IP hybrid transport
7-44
Issue 06 (2010-09-20)
Figure 7-21 Typical configuration of boards in an RBS subrack for ATM/IP hybrid transport
Cable Connections
When ATM/IP hybrid transport is applied, the ATM interface at the RNC connects to the NodeB through an ATM network, and the IP interface at the RNC connects to the NodeB through an IP network.
7.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface
This describes the data configuration guidelines for ATM/IP hybrid transport on the Iub interface in terms of VLAN planning, transmission resource allocation, and traffic distribution.
VLAN Planning
Virtual Local Area Network (VLAN) helps shield the RNC from network storms and improve the security of layer 2 networking. The priorities in VLAN tags are used for service differentiation. The specifications for VLANs in ATM/IP hybrid transport are the same as those in IP transport on the Iub interface. The VLAN can be planned as VLAN setting in layer 2 networking and as VLAN setting in layer 3 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, it is recommended that an identical VLAN ID be allocated to the NodeBs whose traffic is converged to the same layer 2 transmission device LAN switch. If the layer 2 transmission device supports the setting of VLAN priorities, the priorities of services need to be mapped onto those of VLANs. If the layer 2 transmission device identifies the priorities based on the VLAN IDs, the priorities of services need to be mapped onto VLAN IDs based on the service types, so as to implement differentiated services. l
Issue 06 (2010-09-20)
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. If the RNC connects to a layer 3 transmission device through a layer 2 network that supports configuration of VLAN priorities, the interface board at the RNC can map the priorities of services either onto the priorities of VLANs or, based on the service types, onto the VLAN IDs. In layer 3 networking, the VLANs configured at the RNC apply to the RNC and the layer 3 transmission device only. Therefore, the typical practice is to set VLAN IDs and priorities based on the service types, rather than to set them based on the NodeB.
Transmission Resource Allocation

When you allocate resources for ATM/IP hybrid transport on the Iub interface, take the following suggestions into consideration: ATM transport, IP transport, or ATM/IP hybrid transport is applicable to control plane data. It is recommended that ATM/IP hybrid transport be applied to control plane data for security. In other words, the SAAL and SCTP links carry the NCP or a CCP at the same time, and the active link is the SAAL link. ATM transport, IP transport, or ATM/IP hybrid transport is applicable to user plane data. It is recommended that: l l ATM transport be applied to signaling, voice services, CS conversational services, CS streaming services, PS conversational services, and PS streaming services. IP transport be applied to PS interactive services, PS background services, HSDPA conversational services, HSDPA streaming services, HSDPA interactive services, HSDPA background 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 IP transport be applied.
Traffic Distribution
For ATM traffic distribution principles and the correlation between ATM traffic description and service type, refer to 13.8.4 ATM Traffic Resource Configuration Guidelines.
7.6.5 IP Addresses and Routes on the Iub Interface (over IP)

On the IP-based or ATM/IP dual stackbased Iub interface, IP addresses and routes are required.
Networking on the Iub Interface

There are two types of networking on the Iub interface, namely, layer 2 networking and layer 3 networking. Compared with layer 3 networking, layer 2 networking is simpler. That is because the port IP addresses of the RNC and NodeB are located on the same network segment and no route is required. Figure 7-22 shows an example of layer 2 networking on the Iub interface.
7-46
Issue 06 (2010-09-20)
Figure 7-22 Layer 2 networking on the Iub interface
NOTE
IP 1 and IP 2 are port IP addresses.
Figure 7-23 shows an example of layer 3 networking on the Iub interface. Figure 7-23 Layer 3 networking on the Iub interface
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 the IP interface board. IP 5 and IP 6 are gateway IP addresses on the RNC side. IP 7 is the gateway IP address on the NodeB side. IP 8 is the IP address of the NodeB.
Issue 06 (2010-09-20)
7-47
IP Addresses on the Iub Interface

As shown in Figure 7-22 and Figure 7-23, the Iub IP addresses at the RNC consist of IP addresses of Ethernet ports, local IP addresses of PPP links, local IP addresses of MLPPP groups, and device IP addresses. Table 7-11 describes these IP addresses. Table 7-11 IP addresses on the Iub interface IP Address IP address of an Ethernet port Configuration Scenario Required when the FG2a or GOUa serves as the interface board Configuration Restriction l Each Ethernet port can be configured with only one primary IP address and 5 secondary addresses. l The IP address of an Ethernet port and the internal IP address of the BAM must be located on different network segments. For these network segments, one cannot cover another. l In the RNC, the IP addresses of different Ethernet ports must be located on different network segments. For these network segments, one cannot cover another. Local IP address of a PPP link Local IP address of an MLPPP group Device IP address Required when the PEUa, POUa, or UOI_IP serves as the interface board Required when the PEUa or POUa serves as the interface board Required in layer 3 networking Each PPP link can be configured with only one local IP address. Each MLPPP group can be configured with only one local IP address. l Each interface board can be configured with a maximum of five device IP addresses. l The IP addresses of any two different devices must be located on different subnets.
Route on the Iub Interface

On the Iub interface where layer 2 networking is applied, no route is required. On the Iub interface where layer 3 networking is applied, you should configure the route described in Table 7-12 on the RNC.
7-48
Issue 06 (2010-09-20)
Table 7-12 Route on the Iub Interface Device IP interface board Route Description The route travels from the RNC to the network segment where the NodeB is located. 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 the NodeB is located, and Next Hop Address is the gateway IP address on the RNC side, for example, IP 5 or IP 6.
7.6.6 OM Channel Configuration on the Iub Interface (over IP)

Two ways are available for configuring routes for the OM channel on the Iub interface. They are routing between the M2000 and the NodeB through the RNC and routing between the M2000 and the NodeB not through the RNC.
Routing Between the M2000 and the NodeB Through the RNC
Figure 7-24 shows an example of routing between the M2000 and the NodeB through the RNC. Table 7-13 describes the routes. Figure 7-24 Example of routing between the M2000 and the NodeB through the RNC
NOTE
l Figure 7-24 takes layer 2 networking on the Iub interface for an example. When layer 3 networking is applied to the Iub interface, the IP interface board and the NodeB communicate through a router. l The RINT shown in Figure 7-24 refers to IP interface boards PEUa, POUa, UOI_IP, FG2a, and GOUa.
Issue 06 (2010-09-20)
7-49
Table 7-13 Routes for the connection between the M2000 and the NodeB through the RNC Equipment M2000 Forward Route From the M2000 to the NodeB OM network segment 19.19.19.X, with the next hop to be the external virtual IP address of the BAM, that is, 172.121.139.200 From the OMUa board to the NodeB OM network segment 19.19.19.X, with the next hop to be the internal IP address of the IP interface board at the RNC, that is, 80.168.3.66 From the IP interface board of the RNC to the NodeB OM network segment 19.19.19.X l If layer 2 networking is applied to the Iub interface, the next hop is the IP address of the interface board at the NodeB, that is, 16.16.16.2. l If layer 3 networking is applied to the Iub interface, the next hop is the gateway IP address on the RNC side. You can run the ADD NODEBIP command on the RNC to configure the route. IP address is the OM IP address of the NodeB. l If layer 2 networking is applied to the Iub interface, Gateway IP address is the IP address of the interface board at the NodeB. l If layer 3 networking is applied to the Iub interface, Gateway IP address is the gateway IP address on the RNC side. NodeB From the NodeB to the M2000 IP network segment 172.121.139.X l If layer 2 networking is applied to the Iub interface, the next hop is the IP address of the IP interface board at the RNC, that is, 16.16.16.1. l If layer 3 networking is applied to the Iub interface, the next hop is the gateway IP address on the NodeB side. Reverse Route -
RNC
From the IP interface board of the RNC to the M2000 IP network segment 172.121.139.X You can run the ADD EMSIP command on the RNC to configure the route. When you run this command, set EMS IP Address to the IP address of the M2000, set Subnet mask to the subnet mask of the M2000, and specify the values of BAM External Network Virtual IP and BAM External Network Mask. In this example, EMS IP Address is 172.121.139.56, and BAM External Network Virtual IP is 172.121.139.200.
7-50
Issue 06 (2010-09-20)
Routing Between the M2000 and the NodeB Not Through the RNC
If the OM subnet where the M2000 is located is connected to the IP network that covers the NodeB, routes can be configured between the M2000 and the NodeB not through the RNC. Figure 7-25 shows an example of routing between the M2000 and the NodeB not through the RNC. Table 7-14 describes the routes. Figure 7-25 Example of routing between the M2000 and the NodeB not through the RNC
Table 7-14 Routes for the connection between the M2000 and the NodeB not through the RNC Equipment M2000 Forward Route From the M2000 to the NodeB OM network segment 19.19.19.X, with the next hop to be the port IP address of router 1, that is, 10.161.215.200 From router 1 to the NodeB OM network segment 19.19.19.X, with the next hop to be the port IP address of router 2, that is, 172.16.16.10 From router 2 to the NodeB OM network segment 19.19.19.X, with the next hop to be the IP address of the IP interface board at the NodeB, that is, 16.16.16.2 Reverse Route -
Router 1
Router 2
From router 2 to the M2000 network segment 10.161.215.100, with the next hop to be the port IP address of router 1, that is, 172.16.16.9 From the NodeB to the M2000 network segment 10.161.215.100, with the next hop to be the port IP address of router 2, that is, 16.16.16.20
NodeB
7.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 Iub interface.

NOTE
RNC initial configuration Optional. Perform this task for each ATM and IP dual stack-based Iub interface.
l This task configures only the transport network layer data on the Iub interface. To enable cells controlled by 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 Iub interface, refer to 13.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 into consideration. For details, refer to 13.5 External Specifications for the RNC. l All the data of a NodeB, including data of cells and links, should be controlled by one SPU 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 the Iub interface, refer to 7.6.4 Data Configuration Guidelines for ATM/IP Hybrid Transport on the Iub Interface.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iub interface (over ATM and IP), refer to 4.3.3 Data Negotiated on the Iub Interface (over ATM and IP).
Procedure
Step 1 Add the physical layer data and ATM layer traffic resource data in the ATM transport: 1. 2. For details about adding the physical layer data in the ATM transport, refer to 7.3.1 Adding Physical Layer Data (Initial, over ATM). For details about adding the ATM layer traffic resource, refer to 7.3.2 Adding ATM Traffic Resources (Initial).
Step 2 Add the physical layer data and data link layer data in the IP transport. For details, refer to 7.5.1 Adding 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 7.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 7.5.2 Adding Control Plane Data on the Iub Interface (Initial, over IP).
7-52
Issue 06 (2010-09-20)

NOTE
l Run the ADD NODEB command and set IUB trans bearer type to ATMANDIP_TRANS(ATM&IP transmission). l Run the ADD ADJNODE command and set Node Type to IUB and Trans Type to ATM_IP. l The NCP/CCP supports the SAAL and SCTP dual link bearer to improve the security. To implement this function, configure the NCP/CCP as follows: Run the ADD NCP and ADD CCP commands and set Bearing Link Type to SAAL-SCTP and input the bearing SAAL link No. and SCTP link No.. The recommended Main link type is SAAL.
Step 4 Add the TRM mapping of adjacent nodes. For details, refer to 7.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial). When you run the ADD TRMMAP command to add the TRM mapping of the dual stack-based NodeB: l Set Interface Type to IUB. 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 7.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 7.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 ADD DEVIP and ADD IPOAPVC commands to set up an IPoA PVC, which is used as the OM channel between the RNC and the NodeB. Run the ADD NODEBIP command to add the OM IP address of the NodeB in ATM/IP dual-stack mode. Set NodeB TransType to ATMANDIPTRANS_IP. For ATM stackbased OM channel parameters for the NodeB, refer to 7.3.6 Adding an OM Channel on the Iub Interface (Initial, over ATM). For IP stack-based OM channel parameters for the NodeB, refer to 7.5.5 Adding an OM Channel on the Iub Interface (Initial, over IP). l If ATM transport is applied to the OM channel, add related data by referring to 7.3.6 Adding an 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 7.5.5 Adding an OM Channel on the Iub Interface (Initial, over IP). ----End
Issue 06 (2010-09-20)
7-53
8 Configuring Iu-CS Interface Data (Initial)
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 exchanges the CS data with the CN through the Iu-CS interface. This topic describes how to add the transport network layer data on the Iu-CS interface. 8.1 Example: Iu-CS Data in the RNC Initial Configuration Script This describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS data consists of the physical layer data, ATM traffic resource data, TRM mapping, activity factor table, control plane data, and user plane data. 8.2 Data Configuration Guidelines for the Iu-CS Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iu-CS interface. Such information refers to the protocol stack, links on the Iu-CS interface, and the differences between R99 and R4/R5/R6/R7. 8.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. 8.4 Data Configuration Guidelines for the Iu-CS Interface (over IP) Related information is required for performing data configuration on the IP-based Iu-CS interface. Such information refers to the protocol structure, links on the Iu-CS interface, and the differences between R99 and R4/R5/R6. 8.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.
Issue 06 (2010-09-20)
8-1
8.1 Example: Iu-CS Data in the RNC Initial Configuration Script

This describes an example of Iu-CS data in the RNC initial configuration script. The Iu-CS data consists of the physical layer data, ATM traffic resource data, TRM mapping, activity factor table, 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 UOIa_ATM board in slot 18 of subrack 0.
SET OPT: SRN=0, SN=18, BT=UOIa,LGCAPPTYPE=ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16byte, J0TXVALUE="SBS 155",J0RXT=16byte, J0RXVALUE="SBS 155", J1TXT=16byte, J1TXVALUE="SBS 155", J1RXT=16byte, J1RXVALUE="SBS 155";
//Add ATM traffic records. //For the ATM traffic record on the control plane, the record index is 170, the service type is CBR, 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 TRMMAP: TMI=13, ITFT=IUCS, TRANST=ATM; ADD TRMMAP: TMI=14, ITFT=IUCS, TRANST=ATM; ADD TRMMAP: TMI=15, ITFT=IUCS, TRANST=ATM;
//Add activity factor tables for gold, silver, and copper users respectively.
ADD TRMFACTOR: FTI=11, REMARK="FOR IUCS";
//Add the Iu-CS control plane data. //Add SAAL links.

//Add RNC DSPs.

ADD N7DPC: NAME="TO-MGW",DPX=0, DPC=H'0008DB, SLSMASK=B0000, NEIGHBOR=YES, DPCT=IUCS, STP=OFF, BEARTYPE=MTP3;
//Add the MTP3 data.

ADD MTP3LKS: SIGLKSX=0, DPX=0, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-MGW"; ADD MTP3RT: DPX=0, SIGLKSX=0, NAME="TO-MGW"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=0, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_0"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_1"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=2, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_2"; ADD MTP3LNK: SIGLKSX=0, SIGSLC=3, SRN=0, SN=0, TCLEN=10, TC=170, NAME="TO_MGW_3"; SAALLNKN=10, PRIORITY=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, ITFT=IUCS, TMIGLD=13, TMISLV=14, TMIBRZ=15, FTI=11

ADD CNDOMAIN: CNDomainId=CS_DOMAIN, T3212=10, ATT=ALLOWED, DRXCycleLenCoef=6; ADD CNNODE: CnOpIndex=0, CNId=0, CNDomainId=CS_DOMAIN, Dpx=0, CNProtclVer=R6, CNLoadStatus=NORMAL, AvailCap=65535, TnlBearerType=ATM_TRANS, Switch3GPP25415CR0125=OFF;
//Add the Iu-CS user plane data. //Add AAL2 paths.

Issue 06 (2010-09-20)
8-3
//Add AAL2 routes.

8.2 Data Configuration Guidelines for the Iu-CS Interface (over ATM)
Related information is required for performing data configuration on the ATM-based Iu-CS interface. Such information refers to the protocol stack, links on the Iu-CS interface, and the differences between R99 and R4/R5/R6/R7. 8.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 8.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 and AAL2 path. 8.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6 In the 3GPP R99, the MSC connects to the RNC as one entity. In the 3GPP R4/R5/R6, the MSC connects to the RNC after being split into two entities, namely, MSC server and MGW.
8.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 8-1 shows the protocol stack for the Iu-CS interface.
8-4
Issue 06 (2010-09-20)
Figure 8-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 l l Transport network layer user plane (area A) Transport network layer control plane (area B) 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 areas can be carried on common physical links.
8.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 and AAL2 path.
Links on the ATM-based Iu-CS Interface

Figure 8-2 shows the links on the ATM-based Iu-CS interface.
Issue 06 (2010-09-20)
8-5
Figure 8-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. The UOIa (UOIa_ATM) board is recommended to be used for the ATM-based Iu-CS interface. If other interface boards need to be used for the ATM-based Iu-CS interface, contact local Huawei office for technical support.
MTP3 Links
MTP3 links are contained in an MTP3 link set. The number of MTP3 links ranges from 0 to 15. At least one MTP3 link should be configured between the RNC and the MGW. Configuration of two or more MTP3 links is recommended. The configuration of MTP3 links between the RNC and MSC server depends on the networking between the MSC server and the RNC: l If the MSC server is directly connected to the RNC, at least one MTP3 link is required for the MSC server (IUCS_RANAP signaling point). It is recommended that two or more one MTP3 link be planned. If the MSC server is connected to the RNC through the MGW, the MSC server (IUCS_RANAP signaling point) does not require any MTP3 link. If the MSC server and the RNC are directly connected and connected through the MGW at the same time, as shown in Figure 8-3, the MSC server (IUCS-RANAP) requires at least one MTP3 link. It is recommended that two or more MTP3 links be configured.
l l
8-6
Issue 06 (2010-09-20)
Figure 8-3 Example of connections between the MSC server and the RNC
MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type. It is recommended that the SAAL links of NNI type be evenly distributed to the SPU subsystems in the RSS subrack or an RBS subrack so that the signaling exchange can be reduced between the SPU subsystems. An SAAL link of NNI type is carried on an ATM PVC. The PVC identifier (VPI/VCI) and other attributes of the PVC must be negotiated between the RNC and the peer.
AAL2 Paths
An AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to 4294967295. An Iu-CS interface has at least one AAL2 path. It is recommended that two or more AAL2 paths be configured. An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVC attributes must be negotiated between the RNC and the peer.
8.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6

In the 3GPP R99, the MSC connects to the RNC as one entity. In the 3GPP R4/R5/R6, the MSC connects to the RNC after being split into two entities, namely, MSC server and MGW.
Iu-CS Interface Defined in the 3GPP R4/R5/R6

Figure 8-4 shows the Iu-CS interface in the 3GPP R4/R5/R6.
Issue 06 (2010-09-20)
8-7
Figure 8-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 forwarded between the MSC server and the RNC through the routes configured on the MGW. Figure 8-5 shows an example topology on the Iu-CS interface in the 3GPP R4/R5/R6. Figure 8-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 MGW

Figure 8-6 and Figure 8-7 show the protocol stacks for the ATM- and IP-based Iu-CS interfaces respectively.
8-8
Issue 06 (2010-09-20)
Figure 8-7 Protocol stack for the IP-based Iu-CS interface
Issue 06 (2010-09-20)
8-9
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: l l The MSC server implements the functions in area A. On the ATM-based Iu-CS interface, the MGW implements the functions in areas B and C shown in Figure 8-6. On the IP-based Iu-CS interface, the MGW implements the functions in area C shown in Figure 8-7.
Data Configuration on the RNC

In 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-CS signaling point: l l MSC server (also called Iu-CS RANAP signaling point) MGW (also called Iu-CS ALCAP signaling point)
Table 8-1 describes the differences between signaling point configuration in R99 and that in R4/R5/R6. Table 8-1 Differences between signaling point configuration in R99 and that in R4/R5/R6 Item Type Quantity R4/R5/R6 Iu-CS RANAP signaling point and Iu-CS ALCAP signaling point More than one R99 Iu-CS signaling point One
8.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. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Mandatory. Perform this task once on each Iu-CS interface when the RNC connects to multiple CS CN nodes over ATM.
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 IuCS interface, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iu-CS interface (initial, over ATM), refer to 4.3.4 Data Negotiated on the Iu-CS Interface (over ATM) . 1. 8.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. The types of interface boards should be determined before the related configuration. 8.3.2 Adding ATM Traffic Resources (Initial) This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links. 8.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 related activities are the addition of the SAAL links, Destination Signaling Point (DSP), MTP3 data, adjacent node, and CN node. 8.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 8.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 related activities are adding the AAL2 path and AAL2 route.
2.
3.
4.
5.

NOTE

NOTE
Issue 06 (2010-09-20)
8-11
Prerequisite
Preparation
Procedure
NOTE
----End
8.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 related activities are the addition of the SAAL links, Destination Signaling Point (DSP), MTP3 data, adjacent node, and CN node. Scenario Mandatory/ Optional
NOTE
l When you configure a DSP code, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the strategy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0. For the method and example of configuring the signaling route mask and the signaling link mask, refer to 13.10.3 Signaling Route Mask and Signaling Link Mask. l When adding the MTP3 data, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.5 RNC Capability for MTP3. l When adding the CS CN node, pay attention to 13.3.11 CN Node ID.
Figure 8-8 shows the parameter relationship in the addition of the MTP3 link.
8-12
Issue 06 (2010-09-20)
Figure 8-8 Parameter relationship in the addition of the MTP3 link
Figure 8-9 shows the parameter relationship in the addition of the CN node. Figure 8-9 Parameter relationship in the addition of the CN node
Prerequisite
l l l The OSP data of the RNC is configured. For details, refer to 5.4 Adding OSP to the RNC (Initial). The physical layer data for ATM transport is configured. For details, refer to 8.3.1 Adding Physical Layer Data (Initial, over ATM). Traffic resources at the ATM layer are configured. For details, refer to 8.3.2 Adding ATM Traffic Resources (Initial).
Issue 06 (2010-09-20)
Preparation
For the data to be negotiated and planned before you configure the Iu-CS control plane on the RNC (initial, over ATM), refer to 4.3.4 Data Negotiated on the Iu-CS Interface (over ATM) .
Procedure
Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To add more 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 configure a Media Gateway as the DSP, set Adjacent flag to YES, and set DSP type to IUCS-ALCAP. This configuration indicates that the DSP has the function of transport network layer control plane on the Iu-CS interface. l When you configure an MSC server as the DSP, set Adjacent flag to NO, and set DSP type to IUCS-RANAP. This configuration indicates that the DSP has the functionality of radio network layer control plane on the Iu-CS interface.
CAUTION
Each DSP code must be unique and be different from any Originating Signaling Point (OSP) code. Step 3 Run the ADD MTP3LKS command to add an MTP3 signaling link set. To enable load sharing between the MTP3 signaling links, it is recommended that Signalling route mask be set to B1111. Step 4 Run the ADD MTP3RT command to add an MTP3 route. To add more MTP3 routes, run this command repeatedly. Step 5 Run the ADD MTP3LNK command to add an MTP3 signaling link. To add more MTP3 signaling links, run this command repeatedly. Step 6 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUCS. l Set Transport Type to ATM. Step 7 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID to CS_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
NOTE
Prerequisite
Preparation
Issue 06 (2010-09-20)
8-15
Procedure
8.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 related activities are adding the AAL2 path and AAL2 route. Scenario Mandatory/ Optional
NOTE
The AAL2 path capability of the Iu-CS adjacent node must comply with those stipulated in 13.5.7 RNC Capability for AAL2 Paths and AAL2 Routes.
Figure 8-10 shows the parameter relationship in the addition of the AAL2 path and AAL2 route.
8-16
Issue 06 (2010-09-20)
Figure 8-10 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 to 8.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 4.3.4 Data Negotiated on the Iu-CS Interface (over ATM) .
Procedure
Step 1 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, run this command repeatedly. Step 2 Run the ADD AAL2RT command to add an AAL2 route. ----End
Issue 06 (2010-09-20)
8-17
8.4 Data Configuration Guidelines for the Iu-CS Interface (over IP)
Related information is required for performing data configuration on the IP-based Iu-CS interface. Such information refers to the protocol structure, links on the Iu-CS interface, and the differences between R99 and R4/R5/R6. 8.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 8.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 IP path. 8.4.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6 In the 3GPP R99, the MSC connects to the RNC as one entity. In the 3GPP R4/R5/R6, the MSC connects to the RNC after being split into two entities, namely, MSC server and MGW.
8.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 8-11 shows the protocol stack for the Iu-CS interface. Figure 8-11 Protocol stack for the IP-based Iu-CS interface
8-18
Issue 06 (2010-09-20)
8.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 IP path.
Links on the Iu-CS Interface

Figure 8-12 shows the links on the IP-based Iu-CS interface. Figure 8-12 Links on the Iu-CS interface (over IP)
NOTE
The RINT shown in the preceding figure refers to IP interface boards GOUa, FG2a, and UOIa (UOIa_IP).
M3UA Links
M3UA links are contained in an M3UA link set. The number of M3UA links ranges from 0 to 15. The configuration of M3UA links depends on the networking between the MSC server and the RNC. l If the MSC server is directly connected to the RNC, at least one M3UA link is required for the MSC server (IUCS_RANAP signaling point). It is recommended that more than one M3UA link be configured. If the MSC server and the RNC are connected through the MGW, you need to configure only the M3UA link between the RNC and the MGW. The MGW is responsible for
Issue 06 (2010-09-20)
signaling transfer to the MSC server. It is recommended that two or more M3UA links be configured. l If the MSC server and the RNC are directly connected and connected through the MGW at the same time, as shown in Figure 8-13, you can configure the M3UA link between the RNC and the MSC server (IUCS_RANAP), configure the M3UA between the RNC and the MGW, which is responsible for the signaling transfer to the MSC server, or configure the M3UA link between the RNC and the MSC server and the M3UA link between the RNC and the MGW at the same time. It is recommended two or more M3UA links be configured.
Figure 8-13 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 evenly distributed to the SPU subsystems in the RSS subrack or an RBS subrack so that the signaling exchange can be reduced between the SPU subsystems.
IP Paths
An IP path is a group of connections to the adjacent node. The path ID ranges from 0 to 65535. An Iu-CS interface has at least one IP path. It is recommended that two or more AAL2 paths be configured.
8.4.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6

In the 3GPP R99, the MSC connects to the RNC as one entity. In the 3GPP R4/R5/R6, the MSC connects to the RNC after being split into two entities, namely, MSC server and MGW.
Iu-CS Interface Defined in the 3GPP R4/R5/R6

Figure 8-14 shows the Iu-CS interface in the 3GPP R4/R5/R6.
8-20
Issue 06 (2010-09-20)
Figure 8-14 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 forwarded between the MSC server and the RNC through the routes configured on the MGW. Figure 8-15 shows an example topology on the Iu-CS interface in the 3GPP R4/R5/R6. Figure 8-15 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 MGW

Figure 8-16 and Figure 8-17 show the protocol stacks for the ATM- and IP-based Iu-CS interfaces respectively.
Issue 06 (2010-09-20)
8-21
Figure 8-17 Protocol stack for the IP-based Iu-CS interface
8-22
Issue 06 (2010-09-20)
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: l l The MSC server implements the functions in area A. On the ATM-based Iu-CS interface, the MGW implements the functions in areas B and C shown in Figure 8-16. On the IP-based Iu-CS interface, the MGW implements the functions in area C shown in Figure 8-17.
Data Configuration on the RNC

In 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-CS signaling point: l l MSC server (also called Iu-CS RANAP signaling point) MGW (also called Iu-CS ALCAP signaling point)
Table 8-4 describes the differences between signaling point configuration in R99 and that in R4/R5/R6. Table 8-4 Differences between signaling point configuration in R99 and that in R4/R5/R6 Item Type Quantity R4/R5/R6 Iu-CS RANAP signaling point and Iu-CS ALCAP signaling point More than one R99 Iu-CS signaling point One
8.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. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Mandatory. Perform this task once on each Iu-CS interface when the RNC connects to multiple CS CN nodes over IP.
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-CS interface, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iu-CS interface (initial, over IP), refer to 4.3.5 Data Negotiated on the Iu-CS Interface (over IP). 1. 8.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 configuration of 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 the corresponding physical layer and data link layer data according to the interface board type. 8.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UA data, adjacent node, CN domain data, and CN node data. 8.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 8.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 related activities are adding the IP path and the IP route.
2.
3.
4.
NOTE
8.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UA data, adjacent node, CN domain data, and CN node data. Scenario Mandatory/ Optional RNC initial configuration Mandatory
8-24
Issue 06 (2010-09-20)

NOTE
l When you configure a DSP code, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the strategy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0. For the method and example of configuring the signaling route mask and the signaling link mask, refer to 13.10.3 Signaling Route Mask and Signaling Link Mask. l When adding the M3UA data, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.6 RNC Capability for M3UA. l When adding the CS CN node, pay attention to 13.3.11 CN Node ID.
Figure 8-18 shows the parameter relationship in the addition of the M3UA link. Figure 8-18 Parameter relationship in the addition of the M3UA link
Figure 8-19 shows the parameter relationship in the addition of the CN node.
Issue 06 (2010-09-20)
8-25
Figure 8-19 Parameter relationship in the addition of the CN node
Prerequisite
l l The OSP data of the RNC is configured. For details, refer to 5.4 Adding OSP to the RNC (Initial). The physical layer data for IP transport is configured. For details, refer to Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with FG2a/ GOUa). The data on the data link layer for IP transport is configured. For details, refer to Adding 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 the RNC (initial, over IP), refer to 4.3.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 this command repeatedly. The details are as follows: l Set Signalling link model to CLIENT. l Set Application type to M3UA.
NOTE
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 configure a media gateway as the DSP, set Adjacent flag to YES, and set DSP type to STP. l When you configure an MSC server as the DSP, set Adjacent flag to NO, and set DSP type to IUCS-RANAP. This configuration indicates that the DSP has the functionality of radio network layer control plane on the Iu-CS interface.
CAUTION
Each DSP code must be unique and be different from any Originating Signaling Point (OSP) code. 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 to M3UA_SS7SP, the DSP that this destination M3UA entity corresponds to cannot be adjacent to the local RNC, that is, you must set Adjacent flag to NO when running the ADD N7DPC command to add that DSP. l When Local entity type is set to M3UA_IPSP, Destination entity type must be set to M3UA_IPSP. 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 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 the M3UA link set must be set to M3UA_ASP if the destination entity type is either of the other two values. l To enable load sharing between M3UA links, it is recommended that Signalling link mask 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 this command repeatedly. Step 7 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUCS. l Set Transport Type to IP. Step 8 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID to CS_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
This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table.

NOTE
Prerequisite
Preparation
Procedure
Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, run this command repeatedly. Step 2 Run the ADD TRMFACTOR command to add an activity factor table.
Step 3 (Optional. This command is run only when the Iub interface uses the dual stack or hybrid IP transmission mode.) Run the ADD LOADEQ command to add a threshold table of loading balancing between the active and standby boards. Step 4 Run the ADD ADJMAP command to configure the TRM mapping tables for users of specific priorities and the activity factor table. ----End
8.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 related activities are adding the IP path and the IP route. Scenario Mandatory/ Optional
NOTE
When adding IP paths, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.8 RNC Capability for IP Paths and IP Routes.
Prerequisite
The control plane data of the IP-based Iu-CS interface is configured. For details, refer to 8.5.2 Adding Control Plane Data on the Iu-CS Interface (Initial, over IP).
Preparation
For the data to be negotiated and planned before you configure the Iu-CS user plane on the RNC (initial, over IP), refer to 4.3.5 Data Negotiated on the Iu-CS Interface (over IP).
Procedure
Step 1 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly.
NOTE
The IP path on the Iu-CS interface supports the UDP MUX function. If IP path on the Iu-CS interface is enabled with the UDP MUX function, the RTCP must be enabled on its corresponding node on the CN side. Otherwise, the UDP MUX function is invalid. Step 2 (Optional. Perform this step only when the Iu-CS interface uses layer 3 networking.) Run the ADD IPRT command to add an IP route. ----End
Issue 06 (2010-09-20)
8-29
9 Configuring Iu-PS Interface Data (Initial)
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 exchanges the packet domain data with the CN through the Iu-PS interface. This topic describes how to add the transport network layer data on the Iu-PS interface. 9.1 Example: Iu-PS Data in the RNC Initial Configuration Script This describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS data consists of the physical layer data, TRM mapping, activity factor table, control plane data, and user plane data. 9.2 Data Configuration Guidelines for the Iu-PS Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iu-PS interface. Such information refers to the protocol structure, links on the ATM-based Iu-PS interface, and IPoA configuration principle on the user plane. 9.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. 9.4 Data Configuration Guidelines for the Iu-PS Interface (over IP) Related information is required for performing data configuration on the IP-based Iu-PS interface. Such information refers to the protocol structure and links on the IP-based Iu-PS interface. 9.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.
Issue 06 (2010-09-20)
9-1
9.1 Example: Iu-PS Data in the RNC Initial Configuration Script

This describes an example of Iu-PS data in the RNC initial configuration script. The Iu-PS data consists of the physical layer data, TRM mapping, activity factor table, control plane data, and user plane data. //Take the script for the IP-based Iu-PS interface as an example. //Add physical layer data of the external interface for the RNC. //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 dualhoming 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 SCTPLNK: SRN=0, SN=4, SSN=2, SCTPLNKN=1, MODE=CLIENT, APP=M3UA, DSCP=62,
9-2
Issue 06 (2010-09-20)
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 M3LNK: SIGLKSX=1, SIGLNKID=0, SRN=0, SN=2, SSN=2, SCTPLNKN=0, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="LINKSGSN-01"; ADD M3LNK: SIGLKSX=1, SIGLNKID=1, SRN=0, SN=4, SSN=2, SCTPLNKN=1, PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="LINKSGSN-02";

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 a port controller.

ADD PORTCTRLER: SRN=0, SN=18, PT=ETHER, CARRYEN=0, CTRLSN=2, CTRLSSN=2,
Issue 06 (2010-09-20)
9-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";
9.2 Data Configuration Guidelines for the Iu-PS Interface (over ATM)
Related information is required for performing data configuration on the ATM-based Iu-PS interface. Such information refers to the protocol structure, links on the ATM-based Iu-PS interface, and IPoA configuration principle on the user plane. 9.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 9.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 two types: MTP3-b link and IPoA PVC. 9.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.
9.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 9-1 shows the protocol stack for the Iu-PS interface.
9-4
Issue 06 (2010-09-20)
Figure 9-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 user plane (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 can be carried on common physical links.
9.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 two types: MTP3-b link and IPoA PVC.
Links on the Iu-PS Interface

Figure 9-2 shows the links on the Iu-PS interface.
Issue 06 (2010-09-20)
9-5
Figure 9-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 from 0 to 15. An Iu-PS interface requires at least one MTP3-b link. It is recommended that more than one MTP3-b link be planned. MTP3-b links are carried on the SAAL links of Network-to-Network Interface (NNI) type. It is recommended that the SAAL links of NNI type be evenly distributed to the SPUa subsystems in the RSS subrack or an RBS subrack so that the signaling exchange can be reduced between the SPUa subsystems. An SAAL link of NNI type is carried on a PVC. The PVC identifier (VPI/VCI) and other attributes 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 IPoA PVC be planned.
9.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.
IPoA PVC on the Iu-PS User Plane

Figure 9-3 shows the IPoA PVC on the Iu-PS user plane. Figure 9-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 9-1 describes the IPoA data to be configured on the user plane of the ATM-based Iu-PS interface. Table 9-1 IPoA data on the user plane of the ATM-based Iu-PS interface Item Local IP address of the IPoA PVC Peer IP address of the IPoA PVC PVC between the interface board carrying the IPoA and the peer gateway on the SGSN side Route between the interface board carrying the IPoA and each destination network segment of the connected SGSN Description Device IP address on the ATM interface board of the RNC IP address of the gateway on the SGSN side -
If the IP address of the interface board carrying the IPoA and the IP address of the SGSN are located on different subnets, routes to the destination IP address should be configured at the RNC. Destination IP address is the IP address of the SGSN, and Forward route address is the IP address of the gateway on the SGSN side.
CAUTION
On the Iu-PS interface, a route to the network segment to which the IP address of the RNC interface board belongs must be configured at the SGSN. The next hop is the gateway on the RNC side connected to the SGSN. Otherwise, PS services cannot be provided.
Issue 06 (2010-09-20)
9-7
9.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. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Mandatory. Perform this task once on each Iu-PS interface when the RNC connects to multiple PS CN nodes over ATM.
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 IuPS interface, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iu-PS interface (initial, over ATM), refer to 4.3.6 Data Negotiated on the Iu-PS Interface (over ATM). 1. 9.3.1 Adding Physical Layer Data on the Interface (Initial, with UOIa) This describes how to add physical layer data on an interface when the UOIa serves as the interface board. 9.3.2 Adding ATM Traffic Resources (Initial) This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links. 9.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), MTP3 signaling link, adjacent node, and CN node. 9.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 9.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 related activities are adding the device IP address, IPoA PVC, IP path, and IP route.
2.
3.
4.
5.
9.3.1 Adding Physical Layer Data on the Interface (Initial, with UOIa)
This describes how to add physical layer data on an interface when the UOIa serves as the interface board.
RNC initial configuration Optional. Perform this task only when the UOIa serves as the interface board.
Prerequisite
Preparation
For the data to be negotiated and planned before you add the physical layer data on the interface (initial, with UOIa), refer to 4.3 Data Negotiated Between RNC and Other Network Elements. Prepare the related data for the interface as required.
Procedure
Step 1 Optional: If the planned data is inconsistent with the default data in the database, run the SET OPT command to set the proprieties of the optical port on the UOIa with the Logic function type as ATM. ----End

NOTE
Prerequisite
Preparation
Procedure
NOTE
----End
9.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), MTP3 signaling link, adjacent node, and CN node. Scenario Mandatory/ Optional
NOTE
l When you configure a DSP code, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the strategy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0. For the method and example of configuring the signaling route mask and the signaling link mask, refer to 13.10.3 Signaling Route Mask and Signaling Link Mask. l When adding the MTP3 data, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.5 RNC Capability for MTP3. l When adding the PS CN node, pay attention to 13.3.11 CN Node ID.
Figure 9-4 shows the parameter relationship in the addition of the MTP3 link.
9-10
Issue 06 (2010-09-20)
Figure 9-4 Parameter relationship in the addition of the MTP3 link
Prerequisite
l l l The OSP data of the RNC is configured. For details, refer to 5.4 Adding OSP to the RNC (Initial). The physical layer data for ATM transport is configured. For details, refer to 8.3.1 Adding Physical Layer Data (Initial, over ATM). Traffic resources at the ATM layer are configured. For details, refer to 9.3.2 Adding ATM Traffic Resources (Initial).
Issue 06 (2010-09-20)
Preparation
For the data to be negotiated and planned before you configure the Iu-PS control plane on the RNC (initial, over ATM), refer to 4.3.6 Data Negotiated on the Iu-PS Interface (over ATM).
Procedure
Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To add more 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. The details are as follows: l You are advised to set Signalling route mask to B0000. l Set DSP type to IUPS.
CAUTION
Each DSP code must be unique and be different from any Originating Signaling Point (OSP) code. Step 3 Run the ADD MTP3LKS command to add an MTP3 signaling link set. To enable load sharing between the signaling links, it is recommended that Signalling route mask be set to B1111. Step 4 Run the ADD MTP3RT command to add an MTP3 route. To add more MTP3 routes, run this command repeatedly. Step 5 Run the ADD MTP3LNK command to add an MTP3 signaling link. To add more MTP3 signaling links, run this command repeatedly. Step 6 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUPS. l Set Transport Type to ATM. Step 7 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID to PS_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
This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table.

NOTE
Prerequisite
Preparation
Procedure
Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, run this command repeatedly. Step 2 Run the ADD TRMFACTOR command to add an activity factor table.
Step 3 (Optional. This command is run only when the Iub interface uses the dual stack or hybrid IP transmission mode.) Run the ADD LOADEQ command to add a threshold table of loading balancing between the active and standby boards. Step 4 Run the ADD ADJMAP command to configure the TRM mapping tables for users of specific priorities and the activity factor table. ----End
9.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 related activities are adding the device IP address, IPoA PVC, IP path, and IP route. Scenario Mandatory/ Optional
NOTE
Figure 9-6 shows the parameter relationship in the addition of the IP path and IP route on the ATM-based Iu-PS interface. Figure 9-6 Parameter relationship in the addition of the IP path and IP route on the ATM-based Iu-PS interface.
Prerequisite
The control plane data of the ATM-based Iu-PS interface is configured. For details, refer to 9.3.3 Adding 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 4.3.6 Data Negotiated on the Iu-PS Interface (over ATM).
Procedure
Step 1 Run the ADD DEVIP command to add the device IP address to the interface board that carries the user plane data. Step 2 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 IU-PS. Step 3 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly.
CAUTION
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. Step 4 (Optional. Perform this step only when the Iu-PS interface uses layer 3 networking.) Run the ADD IPRT command to add an IP route. ----End
9.4 Data Configuration Guidelines for the Iu-PS Interface (over IP)
Related information is required for performing data configuration on the IP-based Iu-PS interface. Such information refers to the protocol structure and links on the IP-based Iu-PS interface. 9.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 9.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 IP path.
9.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 data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 9-7 shows the protocol stack for the Iu-PS interface.
Figure 9-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 user plane (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 areas can be carried on common physical links.
9.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 IP path.
Links on the Iu-PS Interface

Figure 9-8 shows the links on the IP-based Iu-PS interface.
9-16
Issue 06 (2010-09-20)
Figure 9-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
M3UA links are contained in an M3UA link set. The numbers of M3UA links range from 0 to 63. An Iu-PS interface requires at least one M3UA link. It is recommended that more than one M3UA link be planned. M3UA links are carried on SCTP links. It is recommended that the SCTP links are evenly distributed to the SPUa subsystems in the RSS subrack or an RBS subrack so that the signaling exchange can be reduced between the SPUa subsystems.
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 be planned.
9.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. Scenario
Issue 06 (2010-09-20)

Mandatory/ Optional
NOTE
Mandatory. Perform this task once on each Iu-PS interface when the RNC connects to multiple PS CN nodes over IP.
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-PS interface, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
Prerequisite
l l You are licensed to apply IP transport to the Iu interface. The OSP data of the RNC is configured. For details, refer to 5.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 4.3.7 Data Negotiated on the Iu-PS Interface (over IP). 1. 9.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 configuration of 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 the corresponding physical layer and data link layer data according to the interface board type. 9.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UA link set, adjacent node, CN domain data, and CN node data. 9.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 9.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 related activities are adding the IP path and the IP route.
2.
3.
4.
NOTE
9-18
Issue 06 (2010-09-20)
9.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), M3UA link set, adjacent node, CN domain data, and CN node data. Scenario Mandatory/ Optional
NOTE
l When you configure a DSP code, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the strategy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0. For the method and example of configuring the signaling route mask and the signaling link mask, refer to 13.10.3 Signaling Route Mask and Signaling Link Mask. l When adding the M3UA data, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.6 RNC Capability for M3UA. l When adding the PS CN node, pay attention to 13.3.11 CN Node ID.
Figure 9-9 shows the parameter relationship in the addition of the M3UA link on the IP-based Iu-PS interface. Figure 9-9 Parameter relationship in the addition of the M3UA link
Issue 06 (2010-09-20)
9-19
Prerequisite
l l The OSP data of the RNC is configured. For details, refer to 5.4 Adding OSP to the RNC (Initial). The physical layer data for IP transport is configured. For details, refer to Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with FG2a/ GOUa). The data on the data link layer for IP transport is configured. For details, refer to Adding 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-PS control plane on the RNC (initial, over IP), refer to 4.3.7 Data Negotiated on the Iu-PS Interface (over IP).
Procedure
Step 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 model to CLIENT. l Set Application type to M3UA.
9-20
Issue 06 (2010-09-20)
CAUTION
l Each DSP code must be unique and be different from any Originating Signaling Point (OSP) code. l If multiple SCTP links use the same source IP address and destination IP address, adhere to the following principle when configuring these SCTP links: The sum of the source port number and the destination port number of a newly configured SCTP link is eight greater than or smaller than the sum of the source port number and the destination port number of any configured SCTP link. 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 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 M3UA_SS7SP, the DSP that this destination M3UA entity corresponds to cannot be adjacent to the local RNC, that is, you must set Adjacent flag to NO when running the ADD N7DPC command to add that DSP. l When Local entity type is set to M3UA_IPSP, Destination entity type must be set to M3UA_IPSP. 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 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 the M3UA link set must be set to M3UA_ASP if the destination entity type is either of the other two values. l To enable load sharing between M3UA links, it is recommended that Signalling link mask 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. Step 7 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUPS. l Set Transport Type to IP. Step 8 Run the ADD CNDOMAIN command to add a CN domain. Set CN domain ID to PS_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
NOTE
Prerequisite
Preparation
Table 9-5 describes the data to be negotiated and planned before you add the activity factor table.
9-22
Issue 06 (2010-09-20)
Table 9-5 Activity factor to be negotiated and planned Item Activity factors for services Description Activity factor used by each type of service Data Source Data planning in the RNC
Procedure
9.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 related activities are adding the IP path and the IP route. Scenario Mandatory/ Optional
NOTE
Prerequisite
The control plane data of the IP-based Iu-PS interface is configured. For details, refer to 9.5.2 Adding 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 4.3.7 Data Negotiated on the Iu-PS Interface (over IP).
Issue 06 (2010-09-20)
9-23
Procedure
Step 1 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly. Step 2 (Optional. Perform this step only when the Iu-PS interface uses layer 3 networking.) Run the ADD IPRT command to add an IP route. ----End
9-24
Issue 06 (2010-09-20)
10 Configuring Iur Interface Data (Initial)
10
Configuring Iur Interface Data (Initial)
About This Chapter

An Iur interface is a logical interface between RNCs. This topic describes how to add the transport network layer data on the Iur interface. 10.1 Example: Iur Data in the RNC Initial Configuration Script This describes an example of Iur data in the RNC initial configuration script. The Iur data consists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table, control plane data, and user plane data. 10.2 Data Configuration Guidelines for the Iur Interface (over ATM) Related information is required for performing data configuration on the ATM-based Iur interface. Such information refers to the protocol structure, links on the ATM-based Iur interface, and configuration of paths for static SRNS reallocation. 10.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. 10.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, and configuration of paths for static SRNS relocation. 10.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.
Issue 06 (2010-09-20)
10-1
10.1 Example: Iur Data in the RNC Initial Configuration Script

This describes an example of Iur data in the RNC initial configuration script. The Iur data consists of the physical layer data, ATM traffic resources, TRM mapping, activity factor table, control plane data, and user plane data. //Take the script for the ATM-based Iur interface as an example. //Add physical layer data of the external interface for the RNC. //Set the attributes of all the optical ports on the ATM-based UOIa board in slot 24 of subrack 0.
SET OPT:SRN=0, SN=24, BT=UOIa, LGCAPPTYPE=ATM, PS=ALL, SCRAMBLESW=ON, OPTM=SDH, J0TXT=16BYTE, J0TXVALUE="SBS 155", J0RXT=16BYTE, J0RXVALUE="SBS 155", J1TXT=16BYTE, J1TXVALUE="SBS 155", J1RXT=16BYTE, J1RXVALUE="SBS 155";
//Add ATM traffic records. //For the ATM traffic record on the control plane, the record index is 190, the service type is CBR, and the peak cell rate is 530 cell/s. //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 TRMMAP: TMI=19, ITFT=IUR, TRANST=ATM; ADD TRMMAP: TMI=20, ITFT=IUR, TRANST=ATM; ADD TRMMAP: TMI=21, ITFT=IUR, TRANST=ATM;
//Add an activity factor table

ADD TRMFACTOR: FTI=13, REMARK="FOR IUR";
//Add the Iur control plane data. //Add SAAL links.

//Add a destination signaling point of the RNC.

ADD N7DPC: DPX=3, DPC=H'A32, NAME="TO-RNC", DPCT=IUR, BEARTYPE=MTP3;
//Add a neighboring RNC.

ADD NRNC: NRncId=201, SHOTRIG=CS_SHO_SWTICH-1&HSPA_SHO_SWITCH-1&NON_HSPA_SHO_SWITCH-1, HOTRIG=ON, ServiceInd=SUPPORT_CS_AND_PS, IurExistInd=TRUE, Dpx=3, RncProtclVer=R6, TnlBearerType=ATM_TRANS;
//Add the MTP3 data

ADD MTP3LKS: SIGLKSX=2, DPX=3, LNKSLSMASK=B1111, EMERGENCY=OFF, NAME="TO-RNC"; ADD MTP3RT: DPX=3, SIGLKSX=2, PRIORITY=0, NAME="TO-RNC"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=0, SRN=0, SN=0, SAALLNKN=100, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC1"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=1, SRN=0, SN=0, SAALLNKN=101, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC2"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=2, SRN=0, SN=0, SAALLNKN=102, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC3"; ADD MTP3LNK: SIGLKSX=2, SIGSLC=3, SRN=0, SN=0, SAALLNKN=103, PRIORITY=0, TCLEN=10, TC=170, NAME="TO-RNC4";

ADD ADJNODE: ANI=3, NAME="TO-RNC", NODET=IUR, DPX=3, TRANST=ATM, IsROOTNODE=YES, QAAL2VER=CS2;
//Set the mapping between the Iur adjacent node and transmission resources.
ADD ADJMAP: ANI=3, ITFT=IUR, TMIGLD=19, TMISLV=20, TMIBRZ=21, FTI=13;
//Add the Iur user plane data. //Add AAL2 paths.

Issue 06 (2010-09-20)
10-3
//Add an AAL2 route.

10.2 Data Configuration Guidelines for the Iur Interface (over ATM)
Related information is required for performing data configuration on the ATM-based Iur interface. Such information refers to the protocol structure, links on the ATM-based Iur interface, and configuration of paths for static SRNS reallocation. 10.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 should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 10.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 link and AAL2 path. 10.2.3 Configuration Guidelines for Static Relocation Routes over Iur The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites to configuration of IP routes on the Iur interface are that the IP paths between the local RNC and the SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC) and the Drift RNC (DRNC) are configured.
10.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 should be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 10-1 shows the protocol stack for the Iur interface.
10-4
Issue 06 (2010-09-20)
Figure 10-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 l l Transport network layer user plane (area A) Transport network layer control plane (area B) Transport network layer user plane (area C)
10.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 link and AAL2 path.
Links on the Iur Interface

Figure 10-2 shows the links on the ATM-based Iur interface.
Issue 06 (2010-09-20)
10-5
Figure 10-2 Links on the Iur interface (over ATM)
NOTE
The RINT shown in the preceding figure refers to ATM interface boards UOIa_ATM, AOUa, and AEUa.
MTP3 Link
MTP3 links are contained in an MTP3 link set. The numbers of MTP3 links range from 0 to 15. The configuration of MTP3 links depends on the networking between the RNC and the neighboring RNC. See specifics as follows: l l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at least one MTP3 link. It is recommended that more than one MTP3 link be planned. If the RNC is connected to the neighboring RNC through a Signaling Transfer Point (STP), no MTP3 link is required.
MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type. It is recommended that the SAAL links of NNI type be evenly distributed to the SPUa subsystems in the RSS subrack or an RBS subrack so that the signaling exchange can be reduced between the SPUa subsystems. An SAAL link of NNI type is carried on an ATM PVC. The PVC identifier (VPI/VCI) and other attributes of the PVC must be negotiated between the RNC and the peer.
AAL2 Path
An AAL2 path is a group of connections to the adjacent node. The path IDs range from 1 to 4294967295. An Iub interface has at least one AAL2 path. It is recommended that more than one AAL2 path be planned.
An AAL2 path is carried over an ATM PVC. The PVC identifier (VPI/VCI) and other PVC attributes must be negotiated between the RNC and the peer.
10.2.3 Configuration Guidelines for Static Relocation Routes over Iur

The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites to configuration of IP routes on the Iur interface are that the IP paths between the local RNC and the SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC) and the Drift RNC (DRNC) are configured. Figure 10-3 shows the configuration of IP routes on the Iur interface. The IP routes configured in multiple subsystems are similar. Figure 10-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, and GOUa.
10.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. Scenario Mandatory/ Optional RNC initial configuration Mandatory. Perform this task once on each Iur interface when the RNC connects to multiple neighboring RNCs over ATM.
Issue 06 (2010-09-20)
10-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 Iur interface, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iur interface (initial, over ATM), refer to 4.3.8 Data Negotiated on the Iur Interface (over ATM). 1. 10.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. The types of interface boards should be determined before the related configuration. 10.3.2 Adding ATM Traffic Resources (Initial) This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links. 10.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 related activities are the addition of the SAAL links, Destination Signaling Point (DSP), basic data of the neighboring RNC, MTP3 data, and adjacent node. 10.3.4 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 10.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 related activities are adding the AAL2 path and AAL2 route. 10.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 path for static SRNS relocation.
2.
3.
4.
5.
6.

NOTE
10-8
Issue 06 (2010-09-20)

NOTE
Prerequisite
Preparation
Procedure
NOTE
----End
10.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 related activities are the addition of the SAAL links, Destination Signaling Point (DSP), basic data of the neighboring RNC, MTP3 data, and adjacent node. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Issue 06 (2010-09-20)
10-9

NOTE
l When you configure a DSP code, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the strategy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0. For the method and example of configuring the signaling route mask and the signaling link mask, refer to 13.10.3 Signaling Route Mask and Signaling Link Mask. l When adding the MTP3 data, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.5 RNC Capability for MTP3.
Figure 10-4 shows the parameter relationship in the addition of the MTP3 link. Figure 10-4 Parameter relationship in the addition of the MTP3 link
Prerequisite
l l The physical layer data for ATM transport is configured. For details, refer to 10.3.1 Adding Physical Layer Data (Initial, over ATM). Traffic resources at the ATM layer are configured. For details, refer to 10.3.2 Adding ATM Traffic Resources (Initial).
Preparation
For the data to be planned and negotiated before you configure the Iur control plane on the RNC (initial, over ATM), refer to 4.3.8 Data Negotiated on the Iur Interface (over ATM).
10-10
Issue 06 (2010-09-20)
Procedure
Step 1 Run the ADD SAALLNK command to add an SAAL link. Set Interface type to NNI. To add more 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. The details are as follows: l You are advised to set Signalling route mask to B0000. l Set DSP type to IUR. l Set DSP bear type to MTP3.
CAUTION
Each DSP code must be unique and be different from any Originating Signaling Point (OSP) code. Step 3 Run the ADD NRNC command to add the basic data of the neighboring RNC. The details are as follows: l Set Iur Interface Existing Indication to TRUE. l Set IUR trans bearer type to ATM_TRANS. Step 4 Run the ADD MTP3LKS command to add an MTP3 signaling link set. To enable load sharing between the signaling links, it is recommended that Signalling route mask be set to B1111. Step 5 Run the ADD MTP3RT command to add an MTP3 route. To add more MTP3 routes, run this command repeatedly. Step 6 Run the ADD MTP3LNK command to add an MTP3 signaling link. To add more MTP3 signaling links, run this command repeatedly. Step 7 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUR. l Set Transport Type to ATM. ----End
This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Issue 06 (2010-09-20)
10-11

NOTE
Prerequisite
Preparation
Procedure
Step 1 Run the ADD TRMMAP command to add a TRM mapping table. To add more TRM mapping tables, run this command repeatedly. Step 2 Run the ADD TRMFACTOR command to add an activity factor table. Step 3 (Optional. This command is run only when the Iub interface uses the dual stack or hybrid IP transmission mode.) Run the ADD LOADEQ command to add a threshold table of loading balancing between the active and standby boards.
Step 4 Run the ADD ADJMAP command to configure the TRM mapping tables for users of specific priorities and the activity factor table. ----End
10.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 related activities are adding the AAL2 path and AAL2 route. Scenario Mandatory/ Optional
NOTE
When adding the AAL2 path to the Iur adjacent node, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.7 RNC Capability for AAL2 Paths and AAL2 Routes.
Figure 10-5 shows the parameter relationship in the addition of the AAL2 path. Figure 10-5 Parameter relationship in the addition of the AAL2 path
Prerequisite
The control plane data of the ATM-based Iur interface is configured. For details, refer to 10.3.3 Adding 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 4.3.8 Data Negotiated on the Iur Interface (over ATM).
Procedure
Step 1 Run the ADD AAL2PATH command to add an AAL2 path. To add more AAL2 paths, run this command repeatedly. Step 2 Run the ADD AAL2RT command to add an AAL2 route. ----End
10.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 path for static SRNS relocation. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the setting for static SRNS relocation is required.
Prerequisite
The IP path on the Iu-PS user plane is configured. For details, refer to 9.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, over ATM) or 9.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, over IP).
Preparation
For the data to be negotiated and planned before you add a path for static SRNS relocation (initial), refer to 4.3.6 Data Negotiated on the Iu-PS Interface (over ATM) and 4.3.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 Destination IP address to the user plane IP address of the DRNC. l Set Next hop IP address to the gateway IP address of the SGSN. Step 2 Run the ADD IPPATH command to add an IP path for static SRNS relocation. The details are as 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.
10-14
Issue 06 (2010-09-20)
CAUTION
For the IP interface boards configured with Iu-PS user plane data, it is recommended that each board be configured with an IP route and IP path towards the DRNC. If multiple destination IP network segments exist at the DRNC, it is also recommended that each board be configured with IP routes and IP paths towards each of the network segments. This facilitates load sharing between Iu-PS and Iur interfaces. ----End
10.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, and configuration of paths for static SRNS relocation. 10.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 be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. 10.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. 10.4.3 Configuration Guidelines for Static Relocation Routes over Iur The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites to configuration of IP routes on the Iur interface are that the IP paths between the local RNC and the SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC) and the Drift RNC (DRNC) are configured.
10.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 be consistent with the protocol structure, that is, from the lowest layer to the highest layer and from the control plane to the user plane. Figure 10-6 shows the protocol stack for the Iur interface.
Issue 06 (2010-09-20)
10-15
Figure 10-6 Protocol stack for IP transport on the Iur interface
The transport network layer of the IP-based Iur interface consists of the transport network layer user plane (area A) and the transport network layer user plane (area C).
10.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.
Links on the Iur Interface

Figure 10-7 shows the links on the Iur interface.
10-16
Issue 06 (2010-09-20)
Figure 10-7 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
M3UA links are contained in an M3UA link set. The numbers of M3UA links range from 0 to 63. The configuration of M3UA links depends on the networking between the RNC and the neighboring RNC. See specifics as follows: l l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at least one M3UA link. It is recommended that more than one M3UA link be planned. If the RNC is connected to the neighboring RNC through a Signaling Transfer Point (STP), no M3UA link is required.
M3UA links are carried on SCTP links. It is recommended that the SCTP links are evenly distributed to the SPUa subsystems in the RSS subrack or an RBS subrack so that the signaling exchange can be reduced between the SPUa subsystems.
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.
Issue 06 (2010-09-20)
10-17
10.4.3 Configuration Guidelines for Static Relocation Routes over Iur

The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local RNC to the SGSN and then to the neighboring RNC. Therefore, the prerequisites to configuration of IP routes on the Iur interface are that the IP paths between the local RNC and the SGSN, between the neighboring RNC and the SGSN, and between the Service RNC (SRNC) and the Drift RNC (DRNC) are configured. Figure 10-8 shows the configuration of IP routes on the Iur interface. The IP routes configured in multiple subsystems are similar. Figure 10-8 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, and GOUa.
10.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. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Mandatory . Perform this task once on each Iur interface when the RNC connects to multiple neighboring RNCs over IP.
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 Iur interface, refer to 13.6.1 Interface Boards Applicable to Terrestrial Interfaces.
10-18
Issue 06 (2010-09-20)
Prerequisite
Preparation
For the data to be negotiated and planned before you add data to the Iur interface (initial, over IP), refer to 4.3.9 Data Negotiated on the Iur Interface (over IP). 1. 10.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 configuration of 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 the corresponding physical layer and data link layer data according to the interface board type. 10.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), basic data of the neighboring RNC, M3UA data, and adjacent node. 10.5.3 Setting the Mapping Between Adjacent Nodes and Transmission Resources (Initial) This describes how to set the mapping between adjacent nodes and transmission resources by configuring the TRM mapping for users of specific priorities and configuring the activity factor table. 10.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 activities are adding the IP path and the IP route. 10.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 path for static SRNS relocation.
2.
3.
4.
5.
NOTE
10.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 related activities are the addition of the SCTP links, Destination Signaling Point (DSP), basic data of the neighboring RNC, M3UA data, and adjacent node. Scenario
Issue 06 (2010-09-20)

Mandatory/ Optional
NOTE
Mandatory
l When you configure a DSP code, specify the signaling route mask for load sharing. When you configure a signaling link set, specify the signaling link mask to determine the strategy of routing between signaling links within that signaling link set. The result of the signaling route mask AND the signaling link mask should be 0. For the method and example of configuring the signaling route mask and the signaling link mask, refer to 13.10.3 Signaling Route Mask and Signaling Link Mask. l When adding the M3UA data, take the constraints on the RNC processing capability into consideration. For details, refer to 13.5.6 RNC Capability for M3UA.
Figure 10-9 shows the parameter relationship in the addition of the M3UA link. Figure 10-9 Parameter relationship in the addition of the M3UA link
Prerequisite
l The physical layer data for IP transport is configured. For details, refer to Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with FG2a/ GOUa).
10-20
Issue 06 (2010-09-20)
The data on the data link layer for IP transport is configured. For details, refer to Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with UOIa).
Preparation
For the data to be planned and negotiated before you configure the Iur control plane on the RNC (initial, over ATM), refer to 4.3.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 this command repeatedly. Set Application type to M3UA.
NOTE
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 IUR. l Set DSP bear type to M3UA.
CAUTION
Each DSP code must be unique and be different from any Originating Signaling Point (OSP) code. Step 3 Run the ADD NRNC command to add the basic data of the neighboring RNC. The details are as 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 to M3UA_SS7SP, the DSP that this destination M3UA entity corresponds to cannot be adjacent to the local RNC, that is, you must set Adjacent flag to NO when running the ADD N7DPC command to add that DSP. l When Local entity type is set to M3UA_IPSP, Destination entity type must be set to M3UA_IPSP. Step 5 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 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 the
M3UA link set must be set to M3UA_ASP if the destination entity type is either of the other two values. l To enable load sharing between M3UA links, it is recommended that Signalling link mask be set to B1111. Step 6 Run the ADD M3RT command to add an M3UA route. Step 7 Run the ADD M3LNK command to add an M3UA link. To add more M3UA links, run this command repeatedly. Step 8 Run the ADD ADJNODE command to add the basic data of an adjacent node and set appropriate TRM mapping and activity factor tables for users of different priorities. The details are as follows: l Set Adjacent Node Type to IUR. l Set Transport Type to IP. ----End
NOTE
Prerequisite
Preparation
Table 10-3 describes the data to be negotiated and planned before you configure the TRM mapping.
10-22
Issue 06 (2010-09-20)
Table 10-3 TRM mapping data to be negotiated and planned Item Mapping between service types and transmission resources Description Based on the requirements, configure the preferred path and candidate path for each type of service on Iub, Iu, and Iur interfaces. Data Source Data planning in the RNC
Procedure
10.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 activities are adding the IP path and the IP route. Scenario Mandatory/ Optional
NOTE
The IP path capability of the Iur adjacent node must comply with those stipulated in 13.5.8 RNC Capability for IP Paths and IP Routes.
Issue 06 (2010-09-20)
10-23
Prerequisite
The control plane data of the IP-based Iur interface is configured. For details, refer to 10.5.2 Adding Control Plane Data on the Iur Interface (Initial, over IP).
Preparation
For the data to be planned and negotiated before you configure the Iur user plane on the RNC (initial, over IP), refer to 4.3.9 Data Negotiated on the Iur Interface (over IP).
Procedure
Step 1 Run the ADD IPPATH command to add an IP path. To add more IP paths, run this command repeatedly. Step 2 (Optional. Perform this step only when the Iur interface uses layer 3 networking.) Run the ADD IPRT command to add an IP route. ----End
10.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 path for static SRNS relocation. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task only when the setting for static SRNS relocation is required.
Prerequisite
The IP path on the Iu-PS user plane is configured. For details, refer to 9.3.5 Adding User Plane Data on the Iu-PS Interface (Initial, over ATM) or 9.5.4 Adding User Plane Data on the Iu-PS Interface (Initial, over IP).
Preparation
For the data to be negotiated and planned before you add a path for static SRNS relocation (initial), refer to 4.3.6 Data Negotiated on the Iu-PS Interface (over ATM) and 4.3.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 Destination IP address to the user plane IP address of the DRNC. l Set Next hop IP address to the gateway IP address of the SGSN. Step 2 Run the ADD IPPATH command to add an IP path for static SRNS relocation. The details are as 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.
CAUTION
For the IP interface boards configured with Iu-PS user plane data, it is recommended that each board be configured with an IP route and IP path towards the DRNC. If multiple destination IP network segments exist at the DRNC, it is also recommended that each board be configured with IP routes and IP paths towards each of the network segments. This facilitates load sharing between Iu-PS and Iur interfaces. ----End
Issue 06 (2010-09-20)
10-25
11 Configuring Iu-BC Interface Data (Initial)
11
NOTE
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 how to add the transport network layer data on the Iu-BC interface. RNC initial configuration Optional. Perform this task only when the RNC is connected to the CBC.
This task configures only the transport network layer of the Iu-BC interface. To enable the RNC to provide the Cell Broadcast Service (CBS), you also need to configure CBS data. For details, refer to the RAN Feature Description.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iu-BC interface, refer to 4.3.10 Data Negotiated on the Iu-BC Interface (over ATM). 1. 11.1 Example: Iu-BC Data in the RNC Initial Configuration Script This describes an example of Iu-BC data in the RNC initial configuration script. The IuBC data consists of the physical layer data, ATM traffic records, IPoA data, and SABP data. 11.2 Data Configuration Guidelines for the Iu-BC Interface Related 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.
2.
Issue 06 (2010-09-20)
3. 4.
11.3 Adding Data on the Iu-BC Interface (Initial, over ATM) This describes how to add transport network layer data on the ATM-based Iu-BC interface. 11.4 Data Configuration Guidelines for the Iu-BC Interface (Initial, over IP) Related information is required for performing data configuration on the IP-based Iu-BC interface. Such information refers to the protocol structure and networking on the Iu-BC interface. 11.5 Adding Data on the Iu-BC Interface (Initial, over IP) This describes how to add transport network layer data on the IP-based Iu-BC interface.
5.
11-2
Issue 06 (2010-09-20)
11.1 Example: Iu-BC Data in the RNC Initial Configuration Script

This 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 SABP data. //Take the script for the ATM-based Iu-BC interface as an example. //Add physical layer data of the external interface for the RNC. //Set attributes of all the optical ports on the UOIa_ATM board in slot 17 of subrack 0.
SET OPT: SRN=0, SN=17, BT=UOIa, LGCAPPTYPE=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=17, DSTIP="172.22.5.0", DSTMASK="255.255.255.0", NEXTHOP="172.22.21.254", PRIORITY=HIGH, REMARK="IP ROUTE TO CBC";
//Add SABP data.

ADD CBSADDR: SRN=0, SN=0, CnOpIndex=0, RNCIPADDR="172.22.21.50", CBCIPADDR="172.22.5.1", CBCMASK="255.255.255.0";
11.2 Data Configuration Guidelines for the Iu-BC Interface

Related 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. 11.2.1 Protocol Structure for the Iu-BC Interface
The Iu-BC interface is the logical interface between the RNC and the CBC. The sequence of adding Iu-BC interface data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer. 11.2.2 Networking on the Iu-BC Interface The RNC connects to the CBC through an SGSN. 11.2.3 Links on the Iu-BC Interface The Iu-BC interface has only one type of link, that is, IPoA PVC. 11.2.4 IPoA Data Configuration on the Iu-BC Interface The IPoA PVC configured on the Iu-BC interface enables the RNC to indirectly connect to the CBC.
11.2.1 Protocol Structure for the Iu-BC Interface

The Iu-BC interface is the logical interface between the RNC and the CBC. The sequence of adding Iu-BC interface data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer. Figure 11-1 shows the protocol stack of the Iu-BC interface. Figure 11-1 Protocol stack for the Iu-BC interface
11.2.2 Networking on the Iu-BC Interface

The RNC connects to the CBC through an SGSN. The connection of the RNC and CBC through an SGSN can make full use of the physical transport resources on the Iu-PS interface. Figure 11-2 shows the networking on the Iu-BC interface.
Figure 11-2 RNC-CBC networking through an SGSN
11.2.3 Links on the Iu-BC Interface

The Iu-BC interface has only one type of link, that is, IPoA PVC.
Links on the Iu-BC Interface

Figure 11-3 shows the links on the Iu-BC interface. Figure 11-3 Links on the Iu-BC interface
NOTE
The RINT shown in the preceding figure refers to ATM interface boards UOI_ATM, AOUa, and AEUa.
IPoA PVC
Because the CBC connects to the RNC through an SGSN, an IPoA PVC must be configured on the Iu-BC interface for connecting the RNC and SGSN gateway. In this case, the data on the IuIssue 06 (2010-09-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 11-5
BC interface is transmitted to the SGSN through the IPoA PVC and then routed to the CBC by the SGSN.
11.2.4 IPoA Data Configuration on the Iu-BC Interface

The IPoA PVC configured on the Iu-BC interface enables the RNC to indirectly connect to the CBC.
IPoA PVC for the Iu-BC Interface

On the Iu-BC interface, the RNC connects to the CBC through an SGSN, as shown in Figure 11-4. Figure 11-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 11-1 describes the IPoA data to be configured on the Iu-BC interface. Table 11-1 IPoA data on the Iu-BC interface Item Local IP address of the IPoA PVC Peer IP address of the IPoA PVC PVC between the interface board carrying the IPoA and the peer gateway on the SGSN side Route between the interface board carrying the IPoA and each destination network segment of the connected SGSN Description Device IP address on the ATM interface board of the RNC IP address of the gateway on the SGSN side If the IP address of the interface board carrying the IPoA and the destination IP addresses are located on different subnets, routes to the destination IP addresses must be configured on the RNC.
11.3 Adding Data on the Iu-BC Interface (Initial, over ATM)

This describes how to add transport network layer data on the ATM-based Iu-BC interface.

NOTE
RNC initial configuration Perform this task only when the RNC is directly connected to the CBC.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iu-BC interface (initial, over ATM), refer to 4.3.10 Data Negotiated on the Iu-BC Interface (over ATM). 11.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. The types of interface boards should be determined before the related configuration. 11.3.2 Adding ATM Traffic Resources (Initial) This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links. 11.3.3 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. 11.3.4 Adding SABP Data (Initial) This describes how to add the Service Area Broadcast Protocol (SABP) data, that is, to add the radio network layer data of the CBS.

NOTE

This describes how to add ATM traffic records at the RNC based on the traffic models of SAAL links, AAL2 paths, IPoA PVCs on the interfaces. Thus, the records can be directly used through their indexes during the configuration of these links.

NOTE
Prerequisite
Preparation
Procedure
NOTE
----End
11.3.3 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. Scenario Mandatory/ Optional
NOTE
For details about guidelines for IPoA configuration on the Iu-BC interface, refer to 11.2.4 IPoA Data Configuration on the Iu-BC Interface.
Figure 11-5 shows the parameter relationship in the addition of the IPoA data on the Iu-BC interface.
11-8
Issue 06 (2010-09-20)
Figure 11-5 Parameter relationship in the addition of the IPoA PVC
Prerequisite
l 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 11.3.1 Adding Physical Layer Data (Initial, over ATM). The ATM traffic resources of the IPoA PVC are configured. For details, refer to 11.3.2 Adding ATM Traffic Resources (Initial).
Preparation
For the data to be negotiated and planned before you add the IPoA data on the Iu-BC interface (initial), refer to 4.3.10 Data Negotiated on the Iu-BC Interface (over ATM).
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 06 (2010-09-20)
11-9
Step 2 Run the ADD IPOAPVC command to establish an IPoA PVC between the RNC and the SGSN gateway. 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 the ADD IPRT command to add a route from the RNC to the CBC. ----End
11.3.4 Adding SABP Data (Initial)

This describes how to add the Service Area Broadcast Protocol (SABP) data, that is, to add the radio network layer data of the CBS. Scenario Mandatory/ Optional RNC initial configuration Mandatory
Figure 11-6 shows the parameter relationship in the addition of SABP data. Figure 11-6 Parameter relationship in the addition of the SABP data
11-10
Issue 06 (2010-09-20)
Prerequisite
The IPoA data is configured for the Iu-BC interface. For details, refer to 11.3.3 Adding IPoA Data on the Iu-BC Interface (Initial).
Preparation
For the data to be negotiated and planned before you add SABP data (initial), refer to 4.3.10 Data Negotiated on the Iu-BC Interface (over ATM).
Procedure
Step 1 Run the ADD CBSADDR command to add the CBS address. ----End
11.4 Data Configuration Guidelines for the Iu-BC Interface (Initial, over IP)
Related information is required for performing data configuration on the IP-based Iu-BC interface. Such information refers to the protocol structure and networking on the Iu-BC interface. 11.4.1 Protocol Structure for the Iu-BC Interface If IP transport is applied to the Iu-BC interface, the sequence of adding Iu-BC interface data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer. 11.4.2 Networking on the Iu-BC Interface IThis describes the IP networking between the RNC and the CBC.
11.4.1 Protocol Structure for the Iu-BC Interface

If IP transport is applied to the Iu-BC interface, the sequence of adding Iu-BC interface data should be consistent with the protocol structure, that is, from the lowest layer to the highest layer. Figure 11-7 shows the protocol stack of the Iu-BC interface.
Issue 06 (2010-09-20)
11-11
Figure 11-7 Protocol stack for the Iu-BC interface
11.4.2 Networking on the Iu-BC Interface

IThis describes the IP networking between the RNC and the CBC.
Scenario
RThe RNC can communicate with the CBC through the data network.
Description
In IP networking mode, the RNC uses FG2a or GOUa as the Iu-BC interface board. The RNC supports redundancy configuration of FG2a/GOUa and FE/GE ports. Figure 11-8shows the IP networking based on the data network. IP transport is applied on the FE/GE ports. Figure 11-8 IP networking based on the data network
11-12
Issue 06 (2010-09-20)
When IP networking is applied to the Iu interface, the RNC and the CBC can directly access the IP bearer network, which enables connections over the Iu-BC interface. Physically, an Iu-BC interface can share an FE/GE port at the RNC with an Iu interface, because of the low traffic on the Iu-BC interface.
11.5 Adding Data on the Iu-BC Interface (Initial, over IP)

This describes how to add transport network layer data on the IP-based Iu-BC interface. Scenario Mandatory/ Optional
NOTE
RNC initial configuration Optional. Perform this task only when the RNC is directly connected to the CBC.
Prerequisite
Preparation
For the data to be negotiated and planned before you add data on the Iu-BC interface (initial, over IP), refer to 4.3.11 Data Negotiated on the Iu-BC Interface (over IP).
Procedure
Step 1 When the FG2a or GOUa serves as the IP interface board for the Iu-BC interface, add the physical layer data by referring to Adding Physical Layer and Data Link Layer Data on Interfaces of the RNC (Initial, with FG2a/GOUa). Step 2 Run the ADD CBSADDR command to add the CBS address. ----End
Issue 06 (2010-09-20)
11-13
12 Configuring Cell Data (Initial)
12
About This Chapter
1.
Configuring Cell Data (Initial)
This describes how to configure cell data of the radio network layer. The related activities are the quick setup of cells, the addition of inter-frequency neighboring cell relationships, intrafrequency neighboring cell relationships, and inter-RAT neighboring cell relationships, and switching all subracks to the online mode after the cell data configuration is complete. 12.2 Quickly Setting Up a Cell (Initial) This describes how to quickly set up a cell on the RNC. You need to manually configure some of the parameters while keeping default settings for other parameters. 12.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 belong to either one RNC or two RNCs. 12.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 belong to either one RNC or two RNCs. 12.5 Adding a Neighboring GSM Cell (Initial) This describes how to add a neighboring GSM cell to a cell. 12.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.
2.
3.
4. 5.
Issue 06 (2010-09-20)
12-1
12.1 Example: Cell Data in the RNC Initial Configuration Script

This describes cell data in the RNC initial configuration script. The cell data includes the data of 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 and logical 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=1, CellName="CELL 1",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, UARFCNDownlink=10563, PScrambCode=1, TCell=CHIP256, LAC=100, SAC=100, CfgRacInd=REQUIRE, RAC=0 , SpgId=2, URANUM=D2, URA1=0, URA2=1, NodeBName="NODEB1", LoCell=1, SupBmc=FALSE, MaxTxPower=430, PCPICHPower=330; ADD QUICKCELLSETUP: CellId=2, CellName="CELL 2",CnOpIndex=0, BandInd=Band1, UARFCNUplink=9613, 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:;
12-2
Issue 06 (2010-09-20)
12.2 Quickly Setting Up a Cell (Initial)

This describes how to quickly set up a cell on the RNC. You need to manually configure some of the parameters while keeping default settings for other parameters. Scenario Mandatory/ Optional RNC initial configuration 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 SPU subsystem. l For the cell-related concepts, refer to 13.11 Cell-Related Concepts.
Figure 12-1 shows the parameter relationship in the quick addition of a cell. Figure 12-1 Parameter relationship in the quick addition of a cell
Issue 06 (2010-09-20)
12-3

NOTE
The parameter Routing area code of the ADD QUICKCELLSETUP command is optional. When the Non Access Stratum (NAS) data of the PS domain is configured on the RNC through the ADD CNDOMAIN command, the parameter Routing area code must be configured for the cell.
Prerequisite
l l l The transport layer data of the RNC is configured. The data of the areas that the cell is located in is configured as global location data of the RNC. For details, refer to 5.5 Adding RNC Global Location Data (Initial). The equipment data of the RNC is configured. For details, refer to 6 Configuring RNC Equipment Data.
Preparation
For the data to be planned and negotiated before you quickly set up a cell on the RNC (initial), refer to 4.4 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 services 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
12.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 belong to either one RNC or two RNCs. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task when intra-frequency neighboring cells are planned for a cell in the local RNC.
CAUTION
Each intra-frequency neighboring cell of a cell must have a unique primary scrambling code.
12-4
Issue 06 (2010-09-20)

NOTE
l In the sense of neighboring relations, the concept of local cell is relative to the concept of neighboring cell. 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 an intra-frequency neighboring cell of cell A, check whether cell A should also be an intra-frequency neighboring cell of cell B. If so, configure cell A as an intra-frequency neighboring cell of cell B on the 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 13.5.11 Specifications for Neighboring Cells.
Figure 12-2 shows the parameter relationship in the addition of an intra-frequency neighboring cell that belongs to the local RNC. Figure 12-2 Parameter relationship in the addition of an intra-frequency neighboring cell that belongs to the local RNC
Figure 12-3 shows the parameter relationship in the addition of an intra-frequency neighboring cell that belongs to a neighboring RNC. Figure 12-3 Parameter relationship in the addition of an intra-frequency neighboring cell that belongs to a neighboring RNC
Issue 06 (2010-09-20)
12-5
Prerequisite
When the intra-frequency neighboring cell belongs to a neighboring RNC, the data of the neighboring RNC and that of the Iur interface are configured. For details, refer to 10 Configuring Iur Interface Data (Initial).
Preparation
For the data to be negotiated and planned before you add an intra-frequency neighboring cell (initial), refer to 4.4 Cell Data on the RNC.
Procedure
l If the target cell and the local cell belong to the same RNC, perform the following step: 1. l Run the ADD INTRAFREQNCELL command to set the target cell as an intrafrequency neighboring cell of the local cell. Run the ADD NRNCCELL command to add the basic information of the target cell. If the URA information is not configured for the neighboring RNC, run the ADD NRNCURA command to add the information.
If the target cell and the local cell belong to different RNCs, perform the following steps: 1. 2.
CAUTION
The URA ID in the ADD NRNCURA command must have been added through the ADD URA command. 3. ----End Run the ADD INTRAFREQNCELL command to set the target cell as an intrafrequency neighboring cell of the local cell.
12.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 belong to either one RNC or two RNCs. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task when inter-frequency neighboring cells are planned for a cell in the local RNC.
CAUTION
Each inter-frequency neighboring cell of a cell must have a unique combination of uplink frequency, downlink frequency, and scrambling code.
12-6
Issue 06 (2010-09-20)

NOTE
l In the sense of neighboring relations, the concept of local cell is relative to the concept of neighboring cell. 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 an inter-frequency neighboring cell of cell A, check whether cell A should also be an inter-frequency neighboring cell of cell B. If so, configure cell A as an inter-frequency neighboring cell of cell B on the 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 13.5.11 Specifications for Neighboring Cells.
Figure 12-4 shows the parameter relationship in the addition of an inter-frequency neighboring cell that belongs to the local RNC. Figure 12-4 Parameter relationship in the addition of an inter-frequency neighboring cell that belongs to the local RNC
Figure 12-5 shows the parameter relationship in the addition of an inter-frequency neighboring cell that belongs to a neighboring RNC. Figure 12-5 Parameter relationship in the addition of an inter-frequency neighboring cell that belongs to a neighboring RNC
Issue 06 (2010-09-20)
12-7
Prerequisite
When the inter-frequency neighboring cell belongs to a neighboring RNC, the data of the neighboring RNC and that of the Iur interface are configured. For details, refer to 10 Configuring Iur Interface Data (Initial).
Preparation
For the data to be negotiated and planned before you add an inter-frequency neighboring cell (initial), refer to 4.4 Cell Data on the RNC.
Procedure
l If the target cell and the local cell belong to the same RNC, perform the following step: 1. l Run the ADD INTERFREQNCELL command to set the target cell as an interfrequency neighboring cell of the local cell. Run the ADD NRNCCELL command to add the basic information of the target cell. If the homing URA information is not configured for the neighboring RNC that controls the target cell, run the ADD NRNCURA command to add the information.
If the target cell and the local cell belong to different RNCs, perform the following steps: 1. 2.
CAUTION
The URA ID in the ADD NRNCURA command must have been added through the ADD URA command. 3. ----End Run the ADD INTERFREQNCELL command to set the target cell as an interfrequency neighboring cell of the local cell.
12.5 Adding a Neighboring GSM Cell (Initial)

This describes how to add a neighboring GSM cell to a cell. Scenario Mandatory/ Optional RNC initial configuration Optional. Perform this task when neighboring GSM cells are planned for a cell in the local RNC.
CAUTION
Each neighboring GSM cell of a cell must have a unique combination of BS color code, network color code, frequency number, and frequency band.
12-8
Issue 06 (2010-09-20)

NOTE
l In the sense of neighboring relations, the concept of local cell is relative to the concept of neighboring cell. l In the RNC, the cell neighboring relationship is unidirectional. Therefore, after the configuration by this task, GSM cell B becomes a neighboring cell of WCDMA cell A in the local RNC, but WCDMA cell 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 13.5.11 Specifications for Neighboring Cells.
Figure 12-6 shows the parameter relationship in the addition of the neighboring GSM cell. Figure 12-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) in a 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), refer to 4.4 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 WCDMA cell. ----End
12.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. Scenario
Issue 06 (2010-09-20)

Mandatory/ Optional
NOTE
Mandatory
This is the last task of initial configuration.
Prerequisite
None.
Preparation
None.
Procedure
Step 1 Run the SET ONLINE command to set the RNC to online mode. ----End
12-10
Issue 06 (2010-09-20)
13 Related Information for RNC Initial Configuration
13
Related Information for RNC Initial Configuration
About This Chapter

This reference part covers the concepts, principles, rules, and conventions that should be understood before data configuration. 13.1 Types of RNC Optical Ports This describes the types of RNC optical ports. 13.2 Introduction to RAN Time Synchronization The time synchronization function enables the time at the nodes of the RAN system to be synchronized. 13.3 Numbering Schemes of the RNC This describes the schemes of numbering the RNC hardware components and applications on the transport network layer and radio network layer. 13.4 Area Identifiers This describes the principles of and suggestions for numbering PLMNs, LAs, SAs, RAs, and URAs. 13.5 External Specifications for the RNC This describes the capability specifications of the RNC for boards, links, and cells. The configuration of interface data and cell data must conform to the external specifications for the RNC. 13.6 Physical Layer Data Configuration Guidelines This describes the guidelines for configuring physical layer data. 13.7 ATM Transport ATM transport has four modes: UNI, fractional ATM, timeslot cross connection, and IMA. 13.8 PVC Parameters of the RNC During the setting of PVC attributes of the ATM layer at Huawei BSC6810, the associated parameters of the ATM Adaptation Layer (AAL) are also configured. Thus, you need to take the associated AAL parameters into consideration when setting the PVC attributes. 13.9 AAL2 Configuration Guidelines
This describes AAL2 configuration guidelines in terms of the working principles of AAL2 paths, destination boards of AAL2 paths, and AAL2 routes. 13.10 MTP3/M3UA Configuration Guidelines This describes the MTP3/M3UA configuration guidelines. 13.11 Cell-Related Concepts This 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. 13.12 TRM Configuration Guidelines The Transmission Resource Management (TRM) of the RNC manages the transmission resources of the interfaces, thus improving efficiency of resource utilization and guaranteeing the Quality of Service (QoS). The RNC determines which type of bearer should be used for current services, depending on certain conditions. These conditions are the service type, the preset mapping between service types and transmission resources, and the utilization of the transmission resources. 13.13 Activity Factor Configuration Guidelines Configuration of activity factors improves efficiency of resource utilization.
13-2
Issue 06 (2010-09-20)
13.1 Types of RNC Optical Ports

This describes the types of RNC optical ports. Table 13-1 describes the types of RNC optical ports. Table 13-1 Types of RNC optical ports Type Channelized optical port Unchannelized optical port GE optical port Board AOUa POUa UOIa GOUa Transport Mode ATM IP ATM/IP IP Applicable Interfaces Iub Iub Iub, Iu-CS, Iu-PS, Iur, and Iu-BC Iub, Iu-CS, Iu-PS, Iur, and Iu-BC
13.2 Introduction to RAN Time Synchronization

The time synchronization function enables the time at the nodes of the RAN system to be synchronized. Synchronization is critical for identifying faults. For example, if the E1 link between the RNC and the NodeB is broken, time synchronization between the RNC and the NodeB ensures that the 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 of Huawei RAN system. SNTP serves the time synchronization between a server and multiple clients. Therefore, an SNTP server must be configured in the RAN system. The SNTP server broadcasts time synchronization information to the SNTP clients. Either the RNC or the M2000 can serve as an SNTP server. You can configure an SNTP server by taking the field condition into consideration. SNTP works on the basis of the Greenwich Mean Time (GMT). Therefore, when setting the time at different nodes, you should set the time zone where the node is located and decide whether to set the Daylight Saving Time (DST). If the DST is set, you need to configure the start time and end time of the DST and the time offset.
13.3 Numbering Schemes of the RNC

This describes the schemes of numbering the RNC hardware components and applications on the transport network layer and radio network layer. 13.3.1 RNC ID The RNC ID is a 12-bit binary code, ranging from 0 to 4095. 13.3.2 RNC Subrack Number
This describes the principles of and suggestions for numbering RNC subracks. 13.3.3 ATM Traffic Record Index This describes the principles of and suggestions for numbering ATM traffic records. 13.3.4 RNC Transmission Resource Mapping Record Index This describes the principles of and suggestions for numbering RNC transmission resource mapping records. 13.3.5 RNC Activity Factor Table Index This describes the principle of numbering RNC activity factor tables. 13.3.6 SAAL Link Number This describes the principles of and suggestions for numbering SAAL links. 13.3.7 SCTP Link Number This describes the principles of and suggestions for numbering SCTP links. 13.3.8 Adjacent Node ID This describes the principles of and suggestions for numbering all adjacent nodes. 13.3.9 MTP3/M3UA DSP Index This describes the principles of and suggestions for numbering MTP3/M3UA Destination Signaling Points (DSPs). 13.3.10 Signaling Link Set Index This describes the principles of and suggestions for numbering signaling link sets. The signaling link set can be the MTP3 signaling link set or the M3UA signaling link set. 13.3.11 CN Node ID This describes the principles of and suggestions for numbering CN nodes. 13.3.12 Local Cell ID This describes the principles of and suggestions for numbering local cells. 13.3.13 Logical Cell ID This describes the principles of and suggestions for numbering logical cells. 13.3.14 Common Physical Channel ID This describes the principles of and suggestions for numbering common physical channels. 13.3.15 Common Transport Channel ID This describes the principles of and suggestions for numbering common transport channels. 13.3.16 GSM Cell ID This describes the principles of numbering GSM cells. 13.3.17 NCP and CCP Number This describes the principle of numbering the NodeB Control Port (NCP) and Communication Control Ports (CCPs). 13.3.18 NRI This describes the principles of setting a Network Resource Identifier (NRI). NRI uniquely identifies a CN node that serves a pool area.
13.3.1 RNC ID
The 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 PLMN ID, the RNC ID can uniquely identify an RNC node worldwide. Being used either independently
or jointly with the PLMN ID, the RNC ID can identify an RNC on the Iub, Iur, and Iu interfaces of the UTRAN.
13.3.2 RNC Subrack Number

This describes the principles of and suggestions for numbering RNC subracks.
Principles
A cabinet of Huawei BSC6810, which supports a maximum of six subracks, has two types of subrack: RSS and RBS. Each subrack is uniquely but not necessarily consecutively numbered within an RNC. l l The mandatory RSS subrack is the switching subrack whose number is always set to 0. The optional RBS subrack is the business subrack whose number is set within the range 1 to 5. The numbering of RBS subracks depends on the traffic requirement.
Figure 13-1 shows the numbered subracks. Figure 13-1 Numbered subracks
Suggestions
It is recommended that the RBS subracks are numbered in ascending order in the directions from left to right and from bottom to top, seen from the front.
13.3.3 ATM Traffic Record Index

This describes the principles of and suggestions for numbering ATM traffic records.
Principles
ATM traffic record indexes are used by the upper layers of the ATM layer. The upper layers of the 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 uniquely identifies an ATM traffic record within the RNC. An ATM traffic record index is set within the range 100 to 1999 (1 to 99 are reserved for internal use). The numbering is not necessarily consecutive.
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 range of 200 to 299 for ATM traffic record indexes over the Iur interface, the range of 300 to 399 for ATM traffic record indexes over the Iu-CS interface, and the range of 400 to 499 for ATM traffic record indexes over the Iu-PS interface. Specify different ranges of ATM traffic record indexes based on the different links over an interface. For example, on the Iub interface, specify the range of 100 to 149 for ATM traffic record indexes of SAAL links, the range of 150 to 179 for ATM traffic record indexes of AAL2 paths, 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. For example, some networks may have detailed planning for various links, which thus requires a large quantity of ATM traffic record indexes. In this case, the allocated ranges in the previous suggestions may need to be extended.
13.3.4 RNC Transmission Resource Mapping Record Index

This describes the principles of and suggestions for numbering RNC transmission resource mapping records.
Principles
A Huawei BSC6810 supports a maximum of 32 transmission resource mapping records. The numbers of such records range from 9 to 163.
13.3.5 RNC Activity Factor Table Index

This describes the principle of numbering RNC activity factor tables.
Principles
A Huawei BSC6810 supports a maximum of 34 activity factor tables. The numbers of such tables range from 0 to 33.
13.3.6 SAAL Link Number

This describes the principles of and suggestions for numbering SAAL links.
Principles
In a Huawei BSC6810, the numbers of SAAL links range from 0 to 699. The SAAL links are numbered within an SPUa board. The numbering for SAAL links of the same type can be discontinuous. The methods used by companies or organizations for numbering
transmission equipment are as follows: For example, specify an SAAL UNI link on one Iub interface to 10 and number an SAAL UNI link another Iub interface to 12.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Number the SAAL UNI and SAAL NNI links from 0 up or 699 down. The methods used by companies or organizations for numbering transmission equipment are as follows: For example, number the SAAL UNI links from 0 up and SAAL NNI links from 174 down. The SAAL NNI links are easy to identify because there are a small number of SAAL NNI links. l SAAL UNI links It is recommended that the SAAL UNI links of the same NodeB be numbered consecutively. The methods used by companies or organizations for numbering transmission equipment are as follows: For example, number the SAAL UNI links of NodeB 1 from 0 through 2 and those of NodeB 2 from 3 through 5. If there are sufficient SAAL UNI links, it is recommended that some numbers be reserved for each NodeB. The methods used by companies or organizations for numbering transmission equipment are as follows: For example, number the SAAL UNI links of NodeB 1 from 0 through 2 and those of NodeB 2 from 4 through 6. Therefore, when an SAAL UNI link is added to NodeB 1, the number 3 can be used. l SAAL NNI links It is recommended that different ranges of numbers be allocated to the SAAL NNI links depending on the interfaces. The methods used by companies or organizations for numbering transmission equipment are as follows: For example, specify the range of 620 to 699 for SAAL NNI links over Iu-CS, the range of 540 to 619 for SAAL NNI links over Iu-PS, and the range of 460 to 539 for SAAL NNI links over Iur.
13.3.7 SCTP Link Number

This describes the principles of and suggestions for numbering SCTP links.
Principles
In a Huawei BSC6810, the numbers of SCTP links range from 0 to 599. The SCTP links are numbered within an SPUa board. The numbering for SCTP links of the same type can be discontinuous. The methods used by companies or organizations for numbering transmission equipment are as follows: For example, specify an SCTP link on one Iub interface to the number 10 and an SCTP link on another Iub interface to the number 12.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Specify different ranges of SCTP link numbers based on different interfaces. The methods used by companies or organizations for numbering transmission equipment are as follows: For example, specify the range of 0 to 239 for SCTP links over Iub, the range of 240 to 359 for SCTP links over Iur, the range of 360 to 479 for SCTP links over Iu-CS, and the range of 480 to 599 for SCTP links over Iu-PS.
13.3.8 Adjacent Node ID

This describes the principles of and suggestions for numbering all adjacent nodes.
Principles
In a Huawei BSC6810, the numbers of adjacent nodes range from 0 to 1999. Each adjacent node is uniquely but not necessarily consecutively numbered within an RNC. For example, set the number of an adjacent NodeB to 10 and that of the next adjacent node to 12.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Within the range of 0 to 1999, number the Iub adjacent nodes and the Iur and Iu adjacent nodes from the two ends. For example, number the Iub adjacent nodes from 0 up and number the Iur and Iu adjacent nodes from 1999 down. For Iur and Iu adjacent nodes, it is recommended that different ranges be allocated to adjacent node numbers depending on the interfaces. For example, specify the range of 1995 to 1999 for adjacent nodes over Iu-CS, the range of 1990 to 1994 for adjacent nodes over Iu-PS, and the range of 1985 to 1989 for adjacent nodes over Iur.
13.3.9 MTP3/M3UA DSP Index

This describes the principles of and suggestions for numbering MTP3/M3UA Destination Signaling Points (DSPs).
Principles
A Huawei BSC6810 supports a maximum of 118 DSPs, including the DSPs that are either directly or indirectly connected to the Originating Signaling Points (OSPs). The number of the MTP3 or M3UA DSP ranges from 0 to 150. Each DSP is uniquely but not necessarily consecutively numbered within an RNC. The number is the DSP index. For example: Set the number of an MSC signaling point to 10 and the number of another MSC signaling point to 12.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Specify different ranges for DSPs depending on the DSP types. For example: Specify the range of 0 to 59 for DSPs over Iu-CS, the range of 60 to 69 for DSPs over Iu-PS, the range of 70 to 79 for DSPs over Iur, the range of 80 to 89 for DSPs of the STP type, and the range of 90 to 99 for DSPs of the AAL2 switch type. There are three types of DSP over Iu-CS: IuCS, IuCS_RANAP, and IuCS_ALCAP.
13.3.10 Signaling Link Set Index

This describes the principles of and suggestions for numbering signaling link sets. The signaling link set can be the MTP3 signaling link set or the M3UA signaling link set.
Principles of Numbering MTP3 Signaling Link Sets

In a Huawei BSC6810, the number of the MTP3 link ranges from 0 to 118. Each MTP3 signaling link set is uniquely but not necessarily consecutively numbered within an RNC. The number is
the signaling link set index. For example: Set the number of an MTP3 signaling link set towards a neighboring MGW to 10 and the number of an MTP3 signaling link set towards another neighboring MGW to 12.
Suggestions for Numbering MTP3 Signaling Link Sets

For 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 signaling link sets over Iu-PS, the range of 80 to 99 for signaling link sets over Iur, the range of 100 to 109 for signaling link sets of the STP type, and the range of 110 to 118 for signaling link sets of 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 Sets

In a Huawei BSC6810, the numbers of M3UA links range from 0 to 118. Each M3UA signaling link set is uniquely but not necessarily consecutively numbered within an RNC. The number is the signaling link set index. For example: Set the number of an M3UA signaling link set towards a neighboring MGW to 11 and the number of an M3UA signaling link set towards another neighboring MGW to 13.
Suggestions for Numbering M3UA Signaling Link Sets

For 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 signaling link sets over Iu-PS, the range of 80 to 99 for signaling link sets over Iur, and the range of 100 to 109 for signaling link sets of the STP type. There are three types of signaling link set over IuCS: IuCS, IuCS_RANAP, and IuCS_ALCAP.
13.3.11 CN Node ID
This describes the principles of and suggestions for numbering CN nodes.
Principles
When the Iu-Flex feature is enabled, a maximum of 32 CN nodes can be configured in each CN domain, either CS domain or PS domain. Each CN node is uniquely but not necessarily consecutively numbered within an RNC. For example, set the number of an MSC to 0 and that of 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.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Specify different ranges for CN nodes in different domains. For example, specify the range of 0 to 31 for CN nodes in the CS domain and the range of 32 to 63 for CN nodes in the PS domain.
13.3.12 Local Cell ID

This describes the principles of and suggestions for numbering local cells.
Principles
The local cell ID uniquely identifies a local cell in a NodeB. The ID of a local cell is required to be unique in a NodeB. In addition, for easy management, this ID should also be unique in the UTRAN. A Huawei BSC6810 supports a maximum of 5,100 local cells. Each local cell is uniquely but not necessarily consecutively numbered within the UTRAN. For example, set the number of a cell to 0 and that of the next cell to 2.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Specify different ranges for local cells depending on the subracks. For example, specify the range of 0 to 899 for the local cells in subrack 0 (the RSS subrack) and the range of 900 to 1799 for the local cells in subrack 1 (an RBS subrack).
13.3.13 Logical Cell ID

This describes the principles of and suggestions for numbering logical cells.
Principles
The 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 during the cell setup procedure. The correlations between logical cell IDs and local cell IDs are configured on the RNC. A Huawei BSC6810 supports a maximum of 5,100 logical cells. Each logical cell is uniquely but not necessarily consecutively numbered within an RNC. For example, set the number of a cell 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 and informs the NodeB of the local cell ID and the logical cell ID. The NodeB then acquires the correlation between the cell IDs. After the logical cell is set up, the cell is identified only through the logical cell ID over the Iub interface. l Though logical cell IDs range from 0 to 65535, a maximum of 5,100 logical cells can be configured.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Specify different ranges for logical cells depending on the subracks. For example, specify the range of 0 to 899 for the logical cells in subrack 0 (the RSS subrack) and the range of 900 to 1799 for the logical cells in subrack 1 (an RBS subrack).
13.3.14 Common Physical Channel ID

This describes the principles of and suggestions for numbering common physical channels.
Principles
The ID of a common physical channel is used to identify the channel in a cell. Each common physical channel is uniquely numbered within a cell. The IDs of common physical channels should be planned before the channels are configured for the cell.
Suggestions
Table 13-2 shows the suggested numbering of common physical channels at the RNC. Table 13-2 Suggested numbering of common physical channels Number 0 Common Physical Channel PSCH Full Spelling Primary Synchronization Channel Secondary Synchronization Channel Primary Common Pilot Channel Primary Common Control Physical Channel Description One cell has one and only one PSCH. One cell has one and only one SSCH. One cell has one and only one P-CPICH. One cell has one and only one P-CCPCH. One cell can be configured with one or two PRACHs. It is recommended that one PRACH be configured. AICHs and PRACHs have a one-to-one mapping. One cell can be configured with one to eight S-CCPCHs. It is recommended that one S-CCPCH be configured. One cell has one and only one PICH. The PICH has a one-to-one relationship with the Paging Channel (PCH).
SSCH
2 3
P-CPICH P-CCPCH
4 5
PRACH 1 PRACH 2 Physical Random Access Channel
6 7 8 9
AICH 1 AICH 2 S-CCPCH 1 S-CCPCH 2
Acquisition Indicator Channel
Secondary Common Control Physical Channel
10
PICH
Paging Indicator Channel
Issue 06 (2010-09-20)
13-11
Number 11 12
Common Physical Channel S-CCPCH 3 S-CCPCH 4
Full Spelling Secondary Common Control Physical Channel
Description One cell can be configured with one to eight S-CCPCHs.
13.3.15 Common Transport Channel ID

This describes the principles of and suggestions for numbering common transport channels.
Principles
The ID of a common transport channel is used to identify the channel in a cell. Each common transport channel is uniquely numbered within a cell. The IDs of common transport channels should be planned before the channels are configured for the cell.
Suggestions
Table 13-3 shows the suggested numbering of common transport channels. Table 13-3 Suggested numbering of common transport channels Number 0 Common Transport Channel BCH Full Spelling Broadcast Channel Description One cell has one and only one BCH. The BCH is carried by the P-CCPCH.
1 2 3
RACH 1 (carried by PRACH 1) RACH 2 (carried by PRACH 2) PCH (carried by SCCPCH 1)
Random Access Channel
One PRACH carries one RACH.
Paging Channel
One cell has one and only one PCH. It is carried on the S-CCPCH of the minimum ID.
4 5 6
FACH 1 (carried by S-CCPCH 1) FACH 2 (carried by S-CCPCH 1) FACH 3 (carried by S-CCPCH 2) Forward Access Channel
One cell has at least one FACH. One S-CCPCH carries zero to two FACHs.
13-12
Issue 06 (2010-09-20)
Number 7 8 9 10 11
Common Transport Channel FACH 4 (carried by S-CCPCH 2) FACH 5 (carried by S-CCPCH 3) FACH 6 (carried by S-CCPCH 3) FACH 7 (carried by S-CCPCH 4) FACH 8 (carried by S-CCPCH 4)
Full Spelling
Description
13.3.16 GSM Cell ID

This 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 maximum of 9,600 GSM cells. Each GSM cell is uniquely but not necessarily consecutively numbered within an RNC. For example, set the number of a GSM cell to 0 and that of the next GSM cell to 3.
13.3.17 NCP and CCP Number

This describes the principle of numbering the NodeB Control Port (NCP) and Communication Control 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 CCPs should be negotiated between the RNC and the NodeB.
13.3.18 NRI
This describes the principles of setting a Network Resource Identifier (NRI). NRI uniquely identifies 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 and expansion requirements. The maximum number of NRIs is 1,024. For example, a CS domain has a maximum of 16 nodes. If Length of CS NRI in bits is set to 4, an NRI is represented by four binary digits. Then, the value range of NRI is 0 to 15. Because of the independence between the CS domain and the PS domain, the NRIs of the CS domain 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 each domain. For example, if NullNRI is 10, both the NullNRIs in the CS and PS domains are 10.

NOTE
You can use the SET OPERATORCFGPARA command to set Length of NRI in bits and NullNRI.
13.4 Area Identifiers

This describes the principles of and suggestions for numbering PLMNs, LAs, SAs, RAs, and URAs. 13.4.1 PLMN ID This defines the PLMN ID, describes the components of the PLMN ID, and provides principles of and suggestions for numbering PLMNs. 13.4.2 LA Identifiers The identifiers related to the Location Area (LA) consist of Location Area Code (LAC) and Location Area Identification (LAI). 13.4.3 SA Identifiers The identifiers related to the Service Area (SA) consist of Service Area Code (SAC) and Service Area Identification (SAI). 13.4.4 RA Identifiers The identifiers related to the Routing Area (RA) consist of Routing Area Code (RAC) and Routing Area Identification (RAI). 13.4.5 URA Identifier The UTRAN Registration Area (URA) is an area covered by a number of cells. In this area, a UE in URA_PCH state does not have to frequently perform cell update. One cell may belong to multiple URAs. The RNC identifies a URA by URA ID. Each URA ID is uniquely numbered within an RNC. The URA IDs range from 0 to 65535. 13.4.6 PLMN Value Tag As 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 upon an SIB1 update. After detecting the change in the PLMN value tag, the UE automatically reads the new SIB1.
13.4.1 PLMN ID
This defines the PLMN ID, describes the components of the PLMN ID, and provides principles of and suggestions for numbering PLMNs.
PLMN
Public Land Mobile Networks (PLMNs), which are established and operated by executive branches or recognized private carriers, are networks that provide public land mobile radio telecommunication services. PLMNs identify different mobile communication carriers of different countries. PLMNs of different carriers have different PLMN IDs.
PLMN ID
The PLMN ID is used to uniquely identify a PLMN worldwide.
The PLMN ID consists of two parts: MCC and MNC. Figure 13-2 shows the components of the PLMN ID. Figure 13-2 Components of the PLMN ID
l l
Mobile Country Code (MCC) is used to identify different countries or regions. Mobile Network Code (MNC) is used to identify different network carriers.
13.4.2 LA Identifiers
The identifiers related to the Location Area (LA) consist of Location Area Code (LAC) and Location Area Identification (LAI).
LAC
The 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 FFFE are reserved. The LAC is presented in the format of h'X1X2X3X4 or H'X1X2X3X4. h' and H' are the hexadecimal symbols.
LAI
The LAI is used to uniquely identify an LA worldwide. The LAI consists of three parts: MCC, MNC, and LAC. Figure 13-3 shows the components of the LAI. Figure 13-3 Components of the LAI
13.4.3 SA Identifiers
The identifiers related to the Service Area (SA) consist of Service Area Code (SAC) and Service Area Identification (SAI).
SAC
The SAC is a 2-byte hexadecimal code. It is used to uniquely identify an SA within an LA.
SAI
The 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 13-4 shows the components of the SAI. Figure 13-4 Components of the SAI
13.4.4 RA Identifiers
The identifiers related to the Routing Area (RA) consist of Routing Area Code (RAC) and Routing Area Identification (RAI).
RAC
The RAC is a 1-byte hexadecimal code. It is used to uniquely identify a routing area within a LA.
RAI
The 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 13-5 shows the components of the RAI. Figure 13-5 Components of the RAI
13.4.5 URA Identifier

The UTRAN Registration Area (URA) is an area covered by a number of cells. In this area, a UE in URA_PCH state does not have to frequently perform cell update. One cell may belong to multiple URAs. The RNC identifies a URA by URA ID. Each URA ID is uniquely numbered within an RNC. The URA IDs range from 0 to 65535.
13.4.6 PLMN Value Tag

As 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 upon
an SIB1 update. After detecting the change in the PLMN value tag, the UE automatically reads the new SIB1. When a UE moves between two neighboring cells that belong to different LAs or RAs, the UE needs to read the SIB1 of the destination cell to initiate the location update process, which requires that the two cells have different PLMN value tags. Therefore, during network planning, different value ranges should be allocated to the PLMN value tags of any two geographically neighboring areas (including the case where one area is part 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 be assigned to any neighboring areas after negotiation. There is no overlap between the value ranges. The area can be a LA or an RA. The PLMN value tags of LAs or RAs vary within the specified range. As a result, a UE can always read different PLMN value tags when moving across 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 value range of the RA to which the cell belongs. If a cell does not support PS services, the PLMN value tag of the cell varies within the specified value range of the LA to which the cell belongs.
Figure 13-6 shows an example of planning the value ranges of PLMN value tags. Figure 13-6 Example of planning the value ranges of PLMN value tags
13.5 External Specifications for the RNC

This describes the capability specifications of the RNC for boards, links, and cells. The configuration of interface data and cell data must conform to the external specifications for the RNC. 13.5.1 Specifications for Traffic on RNC Boards The RNC has ATM traffic specifications for physical links, ports, and upper-layer applications. 13.5.2 RNC Capability for SAAL The RNC has capability specifications for SAAL. 13.5.3 RNC Capability for SCTP The RNC has capability specifications for SCTP links. 13.5.4 RNC Capability for NodeBs The RNC has capability specifications for NodeBs. 13.5.5 RNC Capability for MTP3 The RNC has capability specifications for MTP3.
13.5.6 RNC Capability for M3UA The RNC has capability specifications for M3UA. 13.5.7 RNC Capability for AAL2 Paths and AAL2 Routes The RNC has capability specifications for AAL2 paths and AAL2 routes. 13.5.8 RNC Capability for IP Paths and IP Routes The RNC has capability specifications for AAL2 paths and AAL2 routes. 13.5.9 RNC Capability for IPoA The RNC has capability specifications for IPoA. 13.5.10 Specifications for Channels in a Cell This describes the IDs, specifications, default configuration, and full configuration of common transport channels and common physical channels and the default power specifications for cells. 13.5.11 Specifications for Neighboring Cells This describes the specifications for neighboring cells at an RNC.
13.5.1 Specifications for Traffic on RNC Boards

The RNC has ATM traffic specifications for physical links, ports, and upper-layer applications.
Traffic Specifications for Physical Links and Ports

When configuring the ATM traffic for SAAL links, AAL2 paths, or IPoA PVCs, adhere to the principle that the sum of the average traffic values of all links carried on a physical link or port cannot be larger than the maximum traffic bandwidth of the physical link or port. Table 13-4 describes the traffic specifications for physical links and ports. Table 13-4 Traffic specifications for physical links and ports Physical Link or Port E1 link Link Carried UNI link IMA link T1 link UNI link IMA link UOIa board (UOIa_ATM) in STM-1 mode Maximum Traffic 4528 cell/s, namely 1.92 Mbit/s 4507 cell/s, namely 1.91 Mbit/s 3622 cell/s, namely 1.54 Mbit/s 3606 cell/s, namely 1.53 Mbit/s 353207 cell/s, namely 149.76 Mbit/s
The conversion between units of kbit/s and cell/s are as follows: l l 1 KBIT/S = ((1*1000)/(53*8))CELL/S 1 CELL/S = ((1*53*8)/1000)KBIT/S
Traffic Specifications for Upper-Layer Links

The peak cell rate of each single upper-layer link carried on or terminated at different boards must comply with the specifications in terms of maximum and minimum traffic. Table 13-5 lists the specifications for the traffic on associated boards.
Table 13-5 Specifications for the traffic on boards Link SAAL link AAL2 path IPoA PVC Board Carrying or Terminating the Link SPUa l AEUa l AOUa l UOIa (UOIa_ATM) Minimum Traffic (cell/s) 71 71 71 Maximum Traffic (cell/s) 353207 353207 353207
13.5.2 RNC Capability for SAAL

The RNC has capability specifications for SAAL. The RNC capability for supporting SAAL is as follows: l l An SPUa board supports a maximum of 500 SAAL links of UNI type and 200 SAAL links of NNI type. An AEUa AOUa board and UOIa (UOIa_ATM) supports a maximum of 1,500 SAAL links or 1,600 AAL2 paths or 500 IPoA PVCs. The total number of the three types of link cannot exceed 2,000.
13.5.3 RNC Capability for SCTP

The RNC has capability specifications for SCTP links. The RNC capability for supporting SCTP links is as follows: l l For an IP-based Iub Iu or Iur interface, an SPUa board supports a maximum of 600 SCTP links. A PEUa, FG2a, or GOUa board supports a maximum of 1,200 SCTP links.
13.5.4 RNC Capability for NodeBs

The RNC has capability specifications for NodeBs. The RNC capability for supporting NodeBs is as follows: l l The RSS subrack supports a maximum of 200 NodeBs and 600 cells. An RBS subrack supports a maximum of 300 NodeBs and 900 cells.
13.5.5 RNC Capability for MTP3

The RNC has capability specifications for MTP3. The RNC capability for supporting MTP3 is as follows: l l
Issue 06 (2010-09-20)
A Huawei BSC6810 supports a maximum of 119 MTP3 signaling link sets. A Huawei BSC6810 supports a maximum of 119 MTP3 destination signaling points.
l l l l
An MTP3 signaling link set supports a maximum of 16 MTP3 signaling links. An SPU subsystem supports a maximum of 50 MTP3 signaling links. A Huawei BSC6810 supports a maximum of 2,416 MTP3 signaling links. A Huawei BSC6810 supports a maximum of 366 MTP3 signaling routes.
13.5.6 RNC Capability for M3UA

The RNC has capability specifications for M3UA. The RNC capability for supporting M3UA is as follows: l l l l l A Huawei BSC6810 supports a maximum of 2 local M3UA entities and 119 destination M3UA entities. A Huawei BSC6810 supports a maximum of 119 M3UA link sets. A Huawei BSC6810 supports a maximum of 2,416 M3UA links. An SPUa board supports a maximum of 200 M3UA links. A Huawei BSC6810 supports a maximum of 366 M3UA routes.
13.5.7 RNC Capability for AAL2 Paths and AAL2 Routes

The RNC has capability specifications for AAL2 paths and AAL2 routes. The RNC capability for supporting AAL2 paths is as follows: l l A Huawei BSC6810 supports a maximum of 13,000 AAL2 paths. The total number of AAL2 paths and IP paths, however, cannot exceed 13,000. 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. The ATM interface board refers to the AEUa, AOUa, or UOIa. For adjacent nodes of Iu-CS, Iur, or NNI_AAL2SWITCH type, the RNC supports a maximum of 210 AAL2 paths towards each adjacent node. The total number of AAL2 paths and IP paths, however, cannot exceed 210. For adjacent nodes of Iub or UNI_AAL2SWITCH type, the RNC supports a maximum of 36 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 l A Huawei BSC6810 supports a maximum of 160 AAL2 routes. For the Iu-CS/Iur interface, the RNC supports a maximum of five AAL2 routes towards each adjacent node.
13.5.8 RNC Capability for IP Paths and IP Routes

The RNC has capability specifications for AAL2 paths and AAL2 routes. The RNC capability for supporting IP paths is as follows: l l A Huawei BSC6810 supports a maximum of 12,000 IP paths. The total number of AAL2 paths and IP paths, however, cannot exceed 12,000. An IP interface board of a Huawei BSC6810 supports a maximum of 1,800 IP paths. The IP interface board refers to the PEUa, POUa, UOIa (UOIa_IP), FG2a, or GOUa.
13-20
For adjacent nodes of Iu-CS or Iur type, the RNC supports a maximum of 210 IP paths towards each adjacent node. The total number of AAL2 paths and IP paths, however, cannot exceed 210. For adjacent nodes of Iub type, the RNC supports a maximum of 36 IP paths towards each adjacent node. The total number of AAL2 paths and IP paths, however, cannot exceed 36. For adjacent nodes of Iu-PS type, the RNC supports a maximum of 32 IP paths towards each adjacent node.
l l
The RNC capability for supporting IP routes is as follows: An interface board of Huawei BSC6810 supports a maximum of 512 IP routes, among which a maximum of 128 IP routes can reach network segments instead of hosts. The interface board refers to the PEUa, POUa, UOIa (UOIa_IP), FG2a, or GOUa.
13.5.9 RNC Capability for IPoA

The RNC has capability specifications for IPoA. The RNC capability for supporting IPoA is as follows: An AEUa board an AOUa board or a UOIa board supports a maximum of 500 IPoA PVCs. The total number of AAL2 paths, SAAL links, and IPoA PVCs, however, cannot exceed 2,000.
13.5.10 Specifications for Channels in a Cell

This describes the IDs, specifications, default configuration, and full configuration of common transport channels and common physical channels and the default power specifications for cells.
IDs of and Specifications for Common Physical Channels

Table 13-6 describes the IDs of and specifications for common physical channels that are supported by Huawei BSC6810. Table 13-6 IDs of and specifications for common physical channels Comm on Physic al Chann el IDs 0 1 2 3 4 6 Defau lt Confi gurati on 1 1 1 1 1 1 Full Confi gurati on 1 1 1 1 2 2
Channel
Specification
PSCH SSCH P-CPICH P-CCPCH PRACH AICH
One cell has one and only one PSCH. One cell has one and only one SSCH. One cell has one and only one P-CPICH. One cell has one and only one P-CCPCH. One cell can be configured with one or two PRACHs. AICHs and PRACHs have a one-to-one relationship.
Issue 06 (2010-09-20)
13-21
Comm on Physic al Chann el IDs 8
Channel
Specification
Defau lt Confi gurati on 1
Full Confi gurati on 16
S-CCPCH
One cell can be configured with one to 16 SCCPCHs. 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, the S-CCPCH that carries the MBMS service must be configured. A maximum of 15 SCCPCHs can be configured. It is recommended that the S-CCPCHs be numbered from 11.
10
PICH
One cell has one and only one PICH. The PICH corresponds to the PCH.
IDs of and Specifications for Common Transport Channels

Table 13-7 describes the common transport channel IDs and specifications supported by the Huawei BSC6810. Table 13-7 IDs of and specifications for common transport channels Commo n Transp ort Channe l IDs 0 Type and ID of the Carried Common Physical Channel P-CCPCH (3) PRACH (4) Defa ult Conf igura tion 1 Full Conf igur ation 1
Channel
Specification
BCH
One cell has one and only one BCH. The BCH is carried by the P-CCPCH. One cell can be configured with one to two RACHs. One PRACH can carry only one RACH.
RACH
PCH
S-CCPCH (8)
One cell has one and only one PCH. The PCH is carried by the S-CCPCH of the minimum ID.
13-22
Issue 06 (2010-09-20)
Commo n Transp ort Channe l IDs 4 5
Channel
Type and ID of the Carried Common Physical Channel
Specification
Defa ult Conf igura tion
Full Conf igur ation
FACH (signaling) FACH (traffic)
One cell has at least one FACH. l One S-CCPCH that carries non-MBMS services can carry zero to two FACHs. l One S-CCPCH that carries the MBMS service can carry one or two FACHs.
32
Default Power Specifications

Table 13-8 lists the default power specifications for cells and channels of the RNC. Table 13-8 Default power specifications for cells and channels Item Maximum TX power of a cell P-CPICH TX power PSCH power SSCH power AICH power offset PICH power offset BCH power PCH power Maximum TX power of the FACH Default Value 430 dBm 330 dBm -50 dB -50 dB -6 dB -7 dB -20 dB -20 dB 10 dB Power offset from the P-CPICH TX power Description Absolute power Absolute power
13.5.11 Specifications for Neighboring Cells

This describes the specifications for neighboring cells at an RNC. The RNC capabilities for supporting neighboring cells are as follows: l l
Issue 06 (2010-09-20)
A cell can be configured with a maximum of 32 intra-frequency neighboring cells, including the cell itself. A cell can be configured with a maximum of 64 inter-frequency neighboring cells.
l l l l l l l l
A cell can be configured with a maximum of 32 neighboring GSM/GPRS/EDGE cells. The neighboring cells of a cell can be distributed in a maximum of 16 RNCs, including the local RNC and 15 neighboring RNCs. An RNC can be configured with a maximum of 5,100 cells, including intra- and interfrequency cells, in the local RNC. An RNC can be configured with a maximum of 7,680 cells, including intra- and interfrequency cells, in neighboring RNCs. An RNC can be configured with a maximum of 9,600 GSM cells. The total number of intra-frequency neighboring cells that can be configured for an RNC cannot exceed 163,200. The total number of inter-frequency neighboring cells that can be configured for an RNC cannot exceed 326400. The total number of neighboring GSM cells that can be configured for an RNC cannot exceed 163,200.
13.6 Physical Layer Data Configuration Guidelines

This describes the guidelines for configuring physical layer data. 13.6.1 Interface Boards Applicable to Terrestrial Interfaces Before planning the configuration data, you need to select the appropriate interface boards based on the features of terrestrial interfaces. 13.6.2 Upper-Layer Applications Supported by Interface Boards Related information is required for the data configuration of the physical layer and data link layer data. The information refers to the upper-layer applications supported by each interface board. 13.6.3 Numbering of Links Carried on AOUa Optical Ports The numbering of links carried on the optical ports of the AOUa board is different from that of common SDH transmission equipment. 13.6.4 Ports on the AEUa/AOUa This describes the relationship between the physical links configured on the AEUa and AOUa boards and the E1/T1 physical ports. 13.6.5 Configuration Requirements for E1/T1 Links and IMA Links This describes the configuration requirements of the RNC for E1/T1 links and IMA links. 13.6.6 Configuration Specifications for ATM-Based Ports This describes the guidelines for configuring upper-layer applications for ATM-based physical ports. The ATM-based physical ports consist of E1/T1 ports and optical ports. 13.6.7 Requirements of PPP/MLPPP Configuration This describes the requirements of and specifications for PPP and MLPPP configuration.
13.6.1 Interface Boards Applicable to Terrestrial Interfaces

Before planning the configuration data, you need to select the appropriate interface boards based on the features of terrestrial interfaces.
13-24
Issue 06 (2010-09-20)
ATM Interface Boards

Table 13-9 lists the recommended interface boards for ATM-based interfaces. Table 13-9 Recommended ATM interface boards Interface Iub Iu-CS Iu-PS Iur Iu-BC Recommended ATM Interface Board AOUa, UOIa (UOIa_ATM), and AEUa UOIa (UOIa_ATM) UOIa (UOIa_ATM) UOIa (UOIa_ATM) UOIa (UOIa_ATM)
NOTE
The Iu-BC interface can share physical transmission resources with the Iu-PS interface. In this networking, if the physical layer data of the Iu-PS interface exists, the physical layer configuration is not necessary for the Iu-BC interface.
IP Interface Boards
Table 13-10 lists the recommended interface boards for IP-based interfaces. Table 13-10 Recommended IP interface boards Interface Iub Iu-CS Iu-PS Iur Iu-BC Recommended IP Interface Board POUa, UOIa (UOIa_IP), GOUa, FG2a, and PEUa GOUa, FG2a, and UOIa (UOIa_IP) GOUa, FG2a, and UOIa (UOIa_IP) GOUa, FG2a, and UOIa (UOIa_IP) GOUa, FG2a, and UOIa (UOIa_IP)
13.6.2 Upper-Layer Applications Supported by Interface Boards

Related information is required for the data configuration of the physical layer and data link layer data. The information refers to the upper-layer applications supported by each interface board.
Upper-Layer Applications Supported by ATM Interface Boards

Table 13-11 shows the upper-layer applications supported by ATM interface boards.
Table 13-11 Upper-layer applications supported by ATM interface boards ATM Interface Board AEUa AOUa UOIa Upper-Layer Applications IMA, UNI, fractional ATM, fractional IMA, and timeslot cross connection IMA and UNI Optical port transmission
Upper-Layer Applications Supported by IP Interface Boards

Table 13-12 shows the upper-layer applications supported by IP interface boards. Table 13-12 Upper-layer applications supported by IP interface boards IP Interface Board PEUa POUa UOIa FG2a GOUa Upper-Layer Applications PPP link and MLPPP link group PPP link and MLPPP link group PPP link Ethernet transmission Ethernet transmission
13.6.3 Numbering of Links Carried on AOUa Optical Ports

The numbering of links carried on the optical ports of the AOUa board is different from that of common SDH transmission equipment. The methods used by companies or organizations for numbering transmission equipment are as follows: l l l Huawei: TUG3 + (TUG2 - 1) x 3 + (TU12 - 1) x 21 Lucent: TU12 + (TUG2 - 1) x 3 + (TUG3 - 1) x 21 ITU-T: TUG2 + (TU12 - 1) x 7 + (TUG3 - 1) x 21
Table 13-13 describes the relationship between link numbers of optical ports on the AOUa board and transmission equipment numbers.
13-26
Issue 06 (2010-09-20)
Table 13-13 Relationship between link numbers of AOUa optical ports and transmission equipment numbers Number of TUG3 Blocks 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 Number of TUG2 Columns 1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5 Number of TU12 Lines 1 1 1 1 1 1 1 2 2 2 2 2 2 2 3 3 3 3 3 3 3 1 1 1 1 1 Huawei Transmissi on Equipment 1 4 7 10 13 16 19 22 25 28 31 34 37 40 43 46 49 52 55 58 61 2 5 8 11 14 Lucent Transmissi on Equipment 1 4 7 10 13 16 19 2 5 8 11 14 17 20 3 6 9 12 15 18 21 22 25 28 31 34 Link Number of AOUa Optical Ports 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
ITU-T Standard
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
Issue 06 (2010-09-20)
13-27
Number of TUG3 Blocks 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3

13-28
Number of TUG2 Columns 6 7 1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5 6 7 1 2 3 4 5
Number of TU12 Lines 1 1 2 2 2 2 2 2 2 3 3 3 3 3 3 3 1 1 1 1 1 1 1 2 2 2 2 2
Huawei Transmissi on Equipment 17 20 23 26 29 32 35 38 41 44 47 50 53 56 59 62 3 6 9 12 15 18 21 24 27 30 33 36
Lucent Transmissi on Equipment 37 40 23 26 29 32 35 38 41 24 27 30 33 36 39 42 43 46 49 52 55 58 61 44 47 50 53 56
ITU-T Standard
Link Number of AOUa Optical Ports 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54
Issue 06 (2010-09-20)
Number of TUG3 Blocks 3 3 3 3 3 3 3 3 3
Number of TUG2 Columns 6 7 1 2 3 4 5 6 7
Number of TU12 Lines 2 2 3 3 3 3 3 3 3
Huawei Transmissi on Equipment 39 42 45 48 51 54 57 60 63
Lucent Transmissi on Equipment 59 62 45 48 51 54 57 60 63
ITU-T Standard
Link Number of AOUa Optical Ports 54 55 56 57 58 59 60 61 62
55 56 57 58 59 60 61 62 63
13.6.4 Ports on the AEUa/AOUa

This describes the relationship between the physical links configured on the AEUa and AOUa boards and the E1/T1 physical ports. Figure 13-7 shows the relationship between the physical links configured on the AEUa and AOUa boards and the E1/T1 physical ports.
Issue 06 (2010-09-20)
13-29
Figure 13-7 Relationship between the physical links configured on the AEUa and AOUa boards and the E1/T1 physical ports
Table 13-14 describes the restrictions on the specifications of physical links for the AEUa and AOUa boards. Table 13-14 Restrictions on the specifications of physical links for the AEUa and AOUa boards Board Restrictions Quantity of IMA Groups AEUa 32 Quantity of IMA Links 32 Other Restrictions
l Quantity of IMA groups + quantity of UNI links + quantity of fractional links 32 l Quantity of IMA links + quantity of UNI links + quantity of fractional links 32
AOUa
84
126 (E1)
l Quantity of IMA groups + quantity of UNI links 126 l Quantity of IMA links + quantity of UNI links 126
13-30
Issue 06 (2010-09-20)
Board
Restrictions Quantity of IMA Groups Quantity of IMA Links 168 (T1) Other Restrictions
l Quantity of IMA groups + quantity of UNI links 168 l Quantity of IMA links + quantity of UNI links 168
13.6.5 Configuration Requirements for E1/T1 Links and IMA Links

This 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 l l l l The physical layer applications of E1/T1 links include IMA links, UNI links, fractional ATM links, and fractional IMA links. For a single link or links carried on a single port, the link type cannot be changed from E1 to T1 or from T1 to E1. All the links must be set to the T1 or E1 type uniformly. An E1/T1 link can serve only one application, such as the IMA link or UNI link. It cannot work as an IMA link and a UNI link at the same time. If an E1/T1 link serves multiple fractional ATM links or fractional IMA links, the fractional ATM or IMA links must be carried on different timeslots. 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 IMA link. The configurations of frame structure, line code, and scrambling switch must be identical at both ends of an E1/T1 link.
Configuration requirements of the RNC for IMA links are as follows: l l l l All links in an IMA group must be of the same type, either E1 or T1. The configurations of scrambling switches of all E1/T1 links in an IMA group must be identical. All IMA links in an IMA group must be of the same type, either common IMA link or fractional IMA link. For a fractional IMA group, the quantities of timeslots that carry the fractional IMA links must be identical. A fractional IMA group refers to the IMA group that contains only fractional IMA links. The E1/T1 links whose link numbers are congruent modulo 32 cannot be in the same IMA group. Links carried on different optical ports of the AOUa board cannot be gathered in the same IMA group.
l l
13.6.6 Configuration Specifications for ATM-Based Ports

This describes the guidelines for configuring upper-layer applications for ATM-based physical ports. 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 they occupy different timeslots.
Timeslot Compatibility
At one time point, a timeslot can be occupied by only one upper-layer application. Take an AEUa board for example: If a timeslot is occupied by a fractional ATM link, the timeslot cannot be used by any fractional IMA link or timeslot cross connection.
Application Compatibility
If 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 added to the group. In a fractional IMA group, each fractional IMA link occupies the same quantity of idle 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.
13.6.7 Requirements of PPP/MLPPP Configuration

This describes the requirements of and specifications for PPP and MLPPP configuration.
Requirements of PPP/MLPPP Configuration

l l l l l l The number of each PPP link and that of each MLPPP link must be unique within each PEUa. Timeslot 0 is unavailable for configuration. In addition, one timeslot cannot carry both PPP and MLPPP links at the same time. During configuration, the slot number must be that of an active board. For a PPP link or an MLPPP group, the local and peer IP addresses must be on the same network segment and unique across the network. Neither the local IP address nor the peer IP address can be set to 0.0.0.0. If the IP address set on the RNC side is inconsistent with that set on the NodeB side, the IP address set on the RNC side applies.
Configuration Specifications for PPP/MLPPP

l l l l l A PEUa board supports a maximum of 128 PPP and MLPPP links in total. The total number of PPP and MLPPP links configured in each POUa cannot exceed 126 in E1 mode or 168 in T1 mode. Each UOIa supports a maximum of four PPP links. A PEUa board supports a maximum of 64 MLPPP groups. Each MLPPP group supports a maximum of eight MLPPP links. The total number of MLPPP links configured in each POUa cannot exceed 42 in E1 mode or 64 in T1 mode.
13-32
13.7 ATM Transport

ATM transport has four modes: UNI, fractional ATM, timeslot cross connection, and IMA. 13.7.1 UNI Mode The UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of the physical layer. 13.7.2 Fractional ATM Fractional ATM is a transport application at the Transmission Convergence (TC) sublayer of the physical layer. This describes the principles and functions of fractional ATM, introduces the two implementation modes (that is, fractional IMA and fractional ATM), and provides the guidelines for configuring fractional IMA links and fractional ATM links. 13.7.3 Timeslot Cross Connection The timeslot cross function implements cross connections between timeslots on two E1/T1s at the PM sublayer of the physical layer. This describes the principles and functions of timeslot cross connection. 13.7.4 IMA Mode The Inverse Multiplexing on ATM (IMA) mode is a transport application at the Transmission Convergence (TC) sublayer of the physical layer. This topic describes the IMA mode in terms of its working principles, clock modes, and features.
13.7.1 UNI Mode

The UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of the physical layer. In UNI mode, an ATM cell is directly carried on an E1/T1 and the bits of the ATM cell are sequentially mapped to the valid timeslots on the E1/T1. Figure 13-8 shows the mapping between the ATM cell and the E1 timeslots in UNI mode. The 53 octets of the ATM cell are sequentially carried on E1 timeslots. Each E1 provides 31 timeslots (with slot 0 unavailable) for carrying the ATM cell.
Issue 06 (2010-09-20)
13-33
Figure 13-8 Mapping between the ATM cell and the E1 timeslots in UNI mode
13.7.2 Fractional ATM

Fractional ATM is a transport application at the Transmission Convergence (TC) sublayer of the physical layer. This describes the principles and functions of fractional ATM, introduces the two implementation modes (that is, fractional IMA and fractional ATM), and provides the guidelines for configuring fractional IMA links and fractional ATM links.
Principles of Fractional ATM

For fractional ATM, multiple timeslots out of the 32 timeslots on an E1/T1 are used to transmit an ATM cell. At the TX end, an ATM cell is mapped to multiple timeslots among the 31 timeslots on an E1/T1. At the RX end, the ATM cell is restored from the associated timeslots on the E1/ T1. Figure 13-9 shows the fractional ATM mode. An E1 frame has timeslots numbered from 0 to 31. All the timeslots except timeslot 0 are available for service data transmission. A T1 frame has 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 13-9 Fractional ATM mode
13-34
Issue 06 (2010-09-20)
If multiple E1/T1 trunks exist between the TX end and the RX end and work in IMA mode, such an IMA mode is called fractional IMA. In fractional IMA mode, an IMA group contains multiple fractional ATM links.
Function of Fractional ATM

After the fractional ATM function is enabled, the ATM cells of a 3G network can be transmitted over an existing 2G network, as shown in Figure 13-10. Figure 13-10 Fractional ATM function
Two Modes of the Fractional ATM Function

There are the following two modes of the fractional ATM function: l Fractional ATM In fractional ATM mode, multiple idle timeslots can be used for transmission. The fractional ATM mode is applicable to only the AEUa board. l Fractional IMA In fractional IMA mode, multiple fractional IMA links are logically gathered into a group with 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 Links

Table 13-15 describes the methods of configuring fractional ATM links and fractional IMA links.
Table 13-15 Methods of configuring fractional ATM links and fractional IMA links Link Fractional ATM link Fractional IMA link Method Use the ADD FRALNK command. The timeslot that carries the FRA ATM link should be specified during the configuration. The timeslot number stays within the range of 1 to 31 and cannot be 0. 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 this command repeatedly.
NOTE Within the IMA group, the fractional IMA links must carry the same quantity of timeslots.
13.7.3 Timeslot Cross Connection

The timeslot cross function implements cross connections between timeslots on two E1/T1s at the PM sublayer of the physical layer. This describes the principles and functions of timeslot cross connection.
Principles of Timeslot Cross Connection

Figure 13-11 shows an example of timeslot cross connection. The timeslot cross connection device cross-connects the timeslots on one E1/T1 to the timeslots on another E1/T1. In the example shown in the following figure, the device cross-connects slots 2 and 3 on one E1/T1 to slots 4 and 8 on another E1/T1 respectively. Figure 13-11 Principles of timeslot cross connection
Function of Timeslot Cross Connection

The AEUa board supports timeslot cross connection. Through the configured timeslot cross connection, the E1 data in timeslot A of the source port is transmitted to timeslot B of the target
port. Thus, the timeslot cross connection helps provide a transparent data transmission channel for the 2G equipment or NodeB monitoring equipment. Figure 13-12 shows implementation of timeslot cross connection. Figure 13-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 other modes, 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 UNI link. The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.
13.7.4 IMA Mode

The Inverse Multiplexing on ATM (IMA) mode is a transport application at the Transmission Convergence (TC) sublayer of the physical layer. This topic describes the IMA mode in terms of its working principles, clock modes, and features.
Working Principles
Figure 13-13 shows the working principles of the IMA mode based on the assumption that each IMA group contains three E1/T1 links. l l At the TX end, the IMA group receives the ATM cell stream from the ATM layer and distributes the cells among the E1/T1 links. At the RX end, the IMA group reassembles the cells to restore the ATM cell stream to the original 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 ATM layer.
Issue 06 (2010-09-20)
13-37
Figure 13-13 Working principles of the IMA mode
In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells build up an IMA frame to implement necessary controlling functions. The length of an IMA frame, m, is defined during the setup of an IMA group. Figure 13-14 shows an IMA frame. The mapping between the ATM cell and the physical link (E1/T1) is similar to that in UNI mode. Figure 13-14 IMA frame
Clock Modes
The clock mode of an IMA group is defined from the perspective of an IMA group rather than a 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 one clock source. The clock source may be extracted from the same external clock or from a link.
13-38
Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within an IMA group are derived from at least two clock sources. The loopback clock mode is a special case of the ITC mode.
Features
The IMA mode has the following features: l l The clock modes at the two ends of the IMA group should be identical. All E1/T1s within an IMA group are simultaneously scrambled or none of them is scrambled. In other words, the states of the scrambling switches at both ends of E1/T1s must be identical. All IMA links within an IMA group must be of the same type. In other words, within an IMA group, either all links are common IMA links or all links are fractional IMA links. If an IMA group is made up of fractional IMA links, the quantities of timeslots on the fractional IMA links must be identical. The same is true for the numbers of each timeslots on the fractional IMA links.
l l
13.8 PVC Parameters of the RNC

During the setting of PVC attributes of the ATM layer at Huawei BSC6810, the associated parameters of the ATM Adaptation Layer (AAL) are also configured. Thus, you need to take the associated AAL parameters into consideration when setting the PVC attributes. 13.8.1 VPI and VCI The ATM technologies features multiplexing, switching, and transmitting of ATM cells. All these operations are performed over VCs. VCs and VPs are identified by VCIs and VPIs respectively. 13.8.2 Service Type The 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). 13.8.3 Traffic Parameters Traffic parameters refer to the parameters used by each PVC for flow control. The traffic parameters include traffic rate and delay variation. 13.8.4 ATM Traffic Resource Configuration Guidelines This provides suggestions for configuring service types during configuration of ATM traffic resources for links on the interfaces.
13.8.1 VPI and VCI

The ATM technologies features multiplexing, switching, and transmitting of ATM cells. All these operations are performed over VCs. VCs and VPs are identified by VCIs and VPIs respectively. Figure 13-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 the channel for transmitting ATM cells between two or more nodes. The VC is used for the information transmission between UEs, between networks, or between UE and network.
Issue 06 (2010-09-20)
A VP is a group of VCs at a given reference point. The VCs in the group have the same VPI.
Figure 13-15 Relationship between VC and VP
13.8.2 Service Type

The 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 13-16 describes the types of service. Table 13-16 Types of service Type of Service Constant Bit Rate Real-Time Variable Bit Rate Non-Real-Time Variable Bit Rate Unspecified Bit Rate Acronym CBR RT-VBR Description No error check, flow control, or other processing Services with variable data streams and strict real-time requirements, for example, interactive compressed video (video telephony). Used for timing transmission, where the application program is relatively insensitive to delivery time or delay, for example, e-mail. No commitment to transmission. No feedback on congestion. This type of service is ideal for the transmission of IP datagrams. In the case of congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the sender.
NRT-VBR
UBR
Table 13-17 describes the features of different ATM services. Table 13-17 Features of different ATM services Feature Bandwidth guarantee
13-40
CBR Yes
RT-VBR Yes
NRT-VBR Yes
UBR No
Issue 06 (2010-09-20)
Feature Applicability to real-time communication Applicability to bursts of communication Feedback on congestion
CBR Yes
RT-VBR Yes
NRT-VBR No
UBR No
No
No
Yes
Yes
No
No
No
No
13.8.3 Traffic Parameters

Traffic parameters refer to the parameters used by each PVC for flow control. The traffic parameters include traffic rate and delay variation. Table 13-18 describes the ATM traffic parameters. Table 13-18 ATM traffic parameters Parameter Name Traffic record index Service Type Parameter ID TRFX ST Description Identifies a traffic record. Indicates the type of service carried on the ATM layer. CBR and RTVBR indicate realtime services, which are usually carried on the user planes of the Iur, Iub, and Iu-CS interfaces. NRTVBR and UBR indicate nonreal-time services, which are usually carried on the user plane of the Iu-PS interface. Indicates the unit of PCR, SCR, and MCR. Indicates the maximum rate of transmitting ATM cells. Indicates the average rate of transmitting ATM cells over a long time. Indicates the minimum rate of transmitting ATM cells. Indicates the maximum quantity of continuous ATM cells. Indicates the maximum tolerable variation. Unit: 0.1 s Describes the usage of the ATM traffic record.
Rate unit Peak cell rate Sustainable cell rate Minimum cell rate Max burst size Cell delay variation tolerance Traffic use description
UT PCR SCR MCR MBS CDVT REMARK
Issue 06 (2010-09-20)
13-41
The traffic rate is indicated in the following ways: l l l PCR: The traffic rate is PCR when Service Type is CBR, that is, the traffic rate is a constant value. PCR + SCR: The traffic rate is PCR + SCR when Service Type is RTVBR or NRTVBR. MCR: The traffic rate is MCR when Service Type is UBR_PLUS.
13.8.4 ATM Traffic Resource Configuration Guidelines

This provides suggestions for configuring service types during configuration of ATM traffic resources for links on the interfaces. Table 13-19 lists the recommended service types for links on different interfaces. Table 13-19 Recommended service types for links on different interfaces Link NCP/CCP AAL2 path IPoA PVC (user plane) IPoA PVC (management plane) MTP3 link Type of Service (In Descending Order by Priority) RTVBR, NRTVBR, CBR RTVBR, NRTVBR, CBR, UBR UBR UBR_PLUS, RTVBR, NRTVBR, CBR, UBR 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 depending on the traffic model in use. l When configuring ATM traffic resources for interfaces, you should take the limits to traffic on interface boards of the RNC into consideration. For details, refer to 13.5.1 Specifications for Traffic on RNC Boards.
13.9 AAL2 Configuration Guidelines

This describes AAL2 configuration guidelines in terms of the working principles of AAL2 paths, destination boards of AAL2 paths, and AAL2 routes. 13.9.1 Working Principles of AAL2 Paths An AAL2 path is actually a PVC that has relatively high bandwidth. One AAL2 path has 256 AAL2 connections among which AAL2 connections 0 to 7 are reserved for protocols and AAL2 connections 8 to 255 for traffic. 13.9.2 AAL2 Route An AAL2 path reaches only an adjacent node, not necessarily the destination node. By configuring AAL2 routes, you can set up a route from the RNC to the destination node through adjacent nodes.
13.9.1 Working Principles of AAL2 Paths

An AAL2 path is actually a PVC that has relatively high bandwidth. One AAL2 path has 256 AAL2 connections among which AAL2 connections 0 to 7 are reserved for protocols and AAL2 connections 8 to 255 for traffic. During communication, the Q.AAL2 module is responsible for dynamically setting up and releasing 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 interface boards AEUa, AOUa, and UOIa (UOIa_ATM) of the RNC. Figure 13-16 shows the relationship between an AAL2 path carried on the Iub interface and AAL2 connections. Figure 13-16 Relationship between an AAL2 path and AAL2 connections
13.9.2 AAL2 Route

An AAL2 path reaches only an adjacent node, not necessarily the destination node. By configuring AAL2 routes, you can set up a route from the RNC to the destination node through adjacent nodes. Figure 13-17 shows an example of the AAL2 route. Figure 13-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 destination node and the adjacent node refer to the same one.
Issue 06 (2010-09-20)
13-43
13.10 MTP3/M3UA Configuration Guidelines

This describes the MTP3/M3UA configuration guidelines. 13.10.1 Types of and Specifications for the MTP3/M3UA DSPs The RNC supports seven types of Destination Signaling Point (DSP): IUCS, IUCS_ALCAP, IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different types have different meanings and different specifications. 13.10.2 MTP3/M3UA DSP Index This describes the principles of and suggestions for numbering MTP3/M3UA Destination Signaling Points (DSPs). 13.10.3 Signaling Route Mask and Signaling Link Mask This describes configurations and examples of the signaling route mask and signaling link mask. 13.10.4 Configuration Guidelines for MTP3/M3UA This describes the guidelines for configuring MTP3/M3UA signaling links, MTP3/M3UA signaling link sets, and MTP3/M3UA routes. 13.10.5 Adjacent Node ID This describes the principles of and suggestions for numbering all adjacent nodes.
13.10.1 Types of and Specifications for the MTP3/M3UA DSPs

The RNC supports seven types of Destination Signaling Point (DSP): IUCS, IUCS_ALCAP, IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different types have different meanings and different specifications. Table 13-20 describes the types of and specifications for the DSPs. Table 13-20 Types of and specifications for the DSPs DSP Type IUCS Description R99 MSC DSP. The IUCS DSP has the control plane functions of both radio network layer and transport network layer on the IuCS interface. R4 MGW DSP. The IUCS_ALCAP DSP has the control plane functions of the transport network layer on the IuCS interface. R4 MSC server DSP. The IUCS_RANAP DSP has the control plane functions of the radio network layer on the Iu-CS interface. Specification l Quantity of IUCS DSPs 32 l Quantity of IUCS_RANAP DSPs 32 l Quantity of IUCS_ALCAP DSPs 32 l Quantity of IUCS_RANAP DSPs + quantity of IUCS DSPs 32 l Quantity of IUCS_ALCAP DSPs + quantity of IUCS DSPs 32
IUCS_ALCAP
IUCS_RANAP
13-44
Issue 06 (2010-09-20)
DSP Type IUPS IUR STP AAL2SWITCH
Description Signaling point on the Iu-PS control plane Other RNC signaling points Signaling transfer point AAL2 transfer point
Specification Number of the IUPS DSPs 32 Number of the IUR DSPs 15 Number of the STP DSPs 2 Quantity of AAL2SWITCH DSPs 6
13.10.2 MTP3/M3UA DSP Index

This describes the principles of and suggestions for numbering MTP3/M3UA Destination Signaling Points (DSPs).
Principles
A Huawei BSC6810 supports a maximum of 118 DSPs, including the DSPs that are either directly or indirectly connected to the Originating Signaling Points (OSPs). The number of the MTP3 or M3UA DSP ranges from 0 to 150. Each DSP is uniquely but not necessarily consecutively numbered within an RNC. The number is the DSP index. For example: Set the number of an MSC signaling point to 10 and the number of another MSC signaling point to 12.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Specify different ranges for DSPs depending on the DSP types. For example: Specify the range of 0 to 59 for DSPs over Iu-CS, the range of 60 to 69 for DSPs over Iu-PS, the range of 70 to 79 for DSPs over Iur, the range of 80 to 89 for DSPs of the STP type, and the range of 90 to 99 for DSPs of the AAL2 switch type. There are three types of DSP over Iu-CS: IuCS, IuCS_RANAP, and IuCS_ALCAP.
13.10.3 Signaling Route Mask and Signaling Link Mask

This 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 number of routes (2n). For example, B0000 indicates that there is at most one route. B0001 or B1000 indicates that there are at most two routes. A BSC6810 supports a maximum of 16 routes for load sharing for one DSP. The number of 1s in a signaling link mask (expressed with n) determines the maximum number of links (2n). For example, B0000 indicates that there is at most one link. B0001 or B1000 indicates that there are at most two links. For a signaling link set, a BSC6810 supports a maximum of 16 links for load sharing. The signaling link mask AND the signaling route mask must be 0, as shown in Figure 13-18.
Issue 06 (2010-09-20)
13-45
Figure 13-18 Relation between signaling link mask and signaling route mask
13.10.4 Configuration Guidelines for MTP3/M3UA

This describes the guidelines for configuring MTP3/M3UA signaling links, MTP3/M3UA signaling link sets, and MTP3/M3UA routes.
MTP3 Signaling Link Set

The MTP3 signaling link set is assigned to a neighboring DSP of the RNC. The MTP3 link set index uniquely identifies an MTP3 link set within an RNC. Each index is unique within an RNC. When configuring an MTP3 link set, you should specify the MTP3 link mask to determine the strategy of routing between the signaling links in the link set.
MTP3 Signaling Link

An MTP3 link set can have a maximum of 16 MTP3 links. To enhance the reliability of SS7 links, each signaling set is configured with two or more MTP3 links, if the total number of MTP3 links is within the limit.
MTP3 Route
An MTP3 route is used to pass signaling messages from the OSP to the DSP. The MTP3 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 Set

The 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 is unique within an RNC. When configuring an M3UA link set, you should specify the M3UA link mask to determine the strategy of routing between the signaling links in the link set.
M3UA Signaling Link

An M3UA link set can have a maximum of 16 M3UA links. To enhance the reliability of SS7 links, each signaling set is configured with more than one M3UA link, if the total number of M3UA links is within the limit.
M3UA Route
An M3UA route is used to pass signaling messages from the local M3UA entity to the destination M3UA entity. The M3UA route should be configured regardless of whether the destination entity is adjacent to the local entity. It is recommended that an indirect route be configured as redundancy for a direct route.
13.10.5 Adjacent Node ID

This describes the principles of and suggestions for numbering all adjacent nodes.
Principles
In a Huawei BSC6810, the numbers of adjacent nodes range from 0 to 1999. Each adjacent node is uniquely but not necessarily consecutively numbered within an RNC. For example, set the number of an adjacent NodeB to 10 and that of the next adjacent node to 12.
Suggestions
For clear numbering and easy identification, the following suggestions are provided: Within the range of 0 to 1999, number the Iub adjacent nodes and the Iur and Iu adjacent nodes from the two ends. For example, number the Iub adjacent nodes from 0 up and number the Iur and Iu adjacent nodes from 1999 down. For Iur and Iu adjacent nodes, it is recommended that different ranges be allocated to adjacent node numbers depending on the interfaces. For example, specify the range of 1995 to 1999 for adjacent nodes over Iu-CS, the range of 1990 to 1994 for adjacent nodes over Iu-PS, and the range of 1985 to 1989 for adjacent nodes over Iur.
13.11 Cell-Related Concepts

This 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. 13.11.1 Definitions of Sector, Carrier, and Cell A sector is the smallest radio coverage area unit, which is covered by one or more radio carriers. Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallest serving unit for UE access. 13.11.2 Definitions of Local Cell and Logical Cell In the 3GPP, a service-providing cell is referred to as a local cell in implementation sense and as a logical cell in logical resource management sense. 13.11.3 Logical Cell Model This describes the logical cell model that is instructive for the configuration of logical cells. 13.11.4 Areas of Logical Cells A logical cell must exist in a Location Area (LA), a Service Area (SA), a Routing Area (RA), and a UTRAN Registration Area (URA). 13.11.5 Definition of Neighboring Cell
A neighboring cell is associated with a specific cell. There are three types of neighboring cell for UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, and neighboring GSM cell.
13.11.1 Definitions of Sector, Carrier, and Cell

A sector is the smallest radio coverage area unit, which is covered by one or more radio carriers. Each radio carrier occupies a frequency. A sector and a carrier form a cell that is the smallest serving unit for UE access. Sectors are of two types: omnidirectional sector and directional sector. The omnidirectional sector provides coverage for small traffic. It covers the 360 circle area with the omnidirectional antenna in the center of the circle. As the traffic grows, the omnidirectional sector is split into three or six directional sectors. The directional sectors are covered by directional antennas. For a 3-sector cell, each of the three directional antennas covers a 120 sector area. For a 6-sector cell, each of the six directional antennas covers a 60 sector area. In fact, the azimuth of the antenna is greater than the theoretical value, and therefore there is overlap between the sectors. Number of cells supported by a NodeB = number of sectors x number of carriers in each sector. Figure 13-19 shows the typical 3 x 2 configuration. The whole circle area is split into three sectors: sector 0, sector 1, and sector 2. Each sector has two carriers, and each carrier forms a cell. There are six cells in total. Frequency multiplexing is allowed in a WCDMA system if different downlink primary scrambling codes are used in neighboring cells of different sectors that use the same frequency. The different downlink primary scrambling codes lower the interference between cells. Figure 13-19 shows the relations between sector, frequency, and cell. Figure 13-19 Relations between sector, frequency, and cell
13-48
Issue 06 (2010-09-20)
13.11.2 Definitions of Local Cell and Logical Cell

In the 3GPP, a service-providing cell is referred to as a local cell in implementation sense and as a logical cell in logical resource management sense.
Local Cell
A local cell is a combination of physical resources, such as hardware resources and software resources, in a cell of a NodeB. A local cell is related to the physical implementation of a device. NodeBs from different vendors have different ways of providing physical resources for cells. Therefore, the concept of logical cell is proposed by the 3GPP to ensure that the RNC can control the radio resources in certain cells through the standard Iub interface. These cells are carried on NodeBs from different vendors.
Logical Cell
A logical cell is a standard logical model that helps the RNC control the radio resources in a cell. The model is independent of local cell implementation and ensures that the Iub interface is an open interface. For details about the logical cell model, refer to 13.11.3 Logical Cell Model. The parameters of a local cell are configured at and managed by the NodeB. The parameters of a logical cell are configured at and managed by the RNC. Each logical cell has a one-to-one relationship with each local cell.
13.11.3 Logical Cell Model

This describes the logical cell model that is instructive for the configuration of logical cells. Figure 13-20 shows the logical cell configuration model. The number above the square is the quantity of the entities that serve as lower-level nodes. The number below the square is the quantity of the entities that serve as upper-level nodes. Figure 13-20 Logical cell configuration model
Issue 06 (2010-09-20)
13-49

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
13.11.4 Areas of Logical Cells

A 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 13.4 Area Identifiers.
l l l l l
A cell can belong to only one LA. A cell can belong to only one RA. A cell can belong to only one CS/PS SA. A cell can belong to only one CBS SA. A cell can belong to one to eight URAs.
13.11.5 Definition of Neighboring Cell

A neighboring cell is associated with a specific cell. There are three types of neighboring cell for UMTS cells: intra-frequency neighboring cell, inter-frequency neighboring cell, and neighboring GSM cell. l l l The intra-frequency neighboring cell refers to a cell that has overlapping coverage with the serving cell and uses the same carrier frequency as the serving cell. The inter-frequency neighboring cell refers to a cell that has overlapping coverage with the serving cell but uses a different carrier frequency from the serving cell. The neighboring GSM cell refers to a cell that is adjacent to the serving cell but belongs to a GSM, General Packet Radio Service (GPRS), or Enhanced Data rates for Global Evolution (EDGE) system.
13.12 TRM Configuration Guidelines

The Transmission Resource Management (TRM) of the RNC manages the transmission resources of the interfaces, thus improving efficiency of resource utilization and guaranteeing the Quality of Service (QoS). The RNC determines which type of bearer should be used for current services, depending on certain conditions. These conditions are the service type, the preset mapping between service types and transmission resources, and the utilization of the transmission resources.
Background to TRM
Different types of service have different QoS requirements. For example, voice services require high QoS but PS background services do not. Therefore, mapping services with different QoS requirements onto different transmission resources helps achieve high efficiency of resource utilization.
TRM Configuration Guidelines

Before the transport bearers are set up for radio links on the interfaces, the RNC applies for transmission resources, makes admission decisions based on transmission resources, and allocates transmission resources. Admission to transmission resources plays a role of admission decision. If the admission is successful, the RNC allocates transmission resources according to the TRM mapping tables. For ATM transport, the RNC applies for Connection IDs (CIDs) and AAL2 path bandwidth resources. 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 types and transmission resources. A TRM mapping table is not interface-specific. One TRM mapping table can be used by multiple interfaces. For example: If the TRM mapping table whose index is 1 and Transport Type is ATM meets the requirements of Iub, Iur, and Iu-CS interfaces for transmission resources, the table 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 IP path and the Per Hop Behavior (PHB) is required.
CAUTION
The primary and secondary paths for a type of service must be different.
13.13 Activity Factor Configuration Guidelines

Configuration of activity factors improves efficiency of resource utilization.
Background to and Principles of Activity Factors

Services are not always active. This sometimes leads to low efficiency of resource utilization. For the purpose of resource multiplexing, transmission resources should be reserved as calculated by service bandwidth x activity factor when a service is initiated. The value of an activity factor affects the quantity of services admitted.
Activity Factor Configuration Policy for Traffic Types

For all interfaces, the following transmission resource reservation policy applies: l
Issue 06 (2010-09-20)
Signaling radio bearer: 3.4 kbit/s x activity factor

l l
Conversational and streaming services: MBR x activity factor. On the Iu-PS interface, these services are admitted at GBR x activity factor. 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 Interfaces

Based on the requirements, you can run the ADD TRMFACTOR command to add an activity factor. The activity factor application policy for the interfaces is as follows: l l Each Iub interface is individually configured with activity factors. The Iu and Iur interfaces share activity factors within the RNC.
13-52
Issue 06 (2010-09-20)

RNC Initial Configuration Guide - (V200R011 - 06)

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RNC Initial Configuration Guide - (V200R011 - 06)

Transféré par

Droits d'auteur :

Formats disponibles

RNC V200R011

Initial Configuration Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

About This Document

About This Document