SJ-20100603155704-024-ZXWR RNC (V3.09.30) Ground Configuration Operation Guide

ZXWR RNC
Radio Network Controller
Ground Configuration Operation Guide

Version: V3.09.30
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R3.0
2011-08-31
Third Edition (V3.09.30.12)

The following sections have been modified:
1. About This Manual
2. 1 Configuration Overview
3. 2 Public Resource Configuration
4. 3 Hardware Resource Configuration
5. 4.1 Overview
R2.0
2011-02-28
Second Edition (V3.09.30.09)

1. About This Manual
2. 1.1 Functions of Configuration Management
3. 1.3 General RNC Configuration Process
4. 1.5 Common Operations of Data Configuration
5. 2.1 Creating UTRAN SubNetwork
6. 2.2 Viewing UTRAN SubNetwork
7. 2.3 Modifying UTRAN SubNetwork
8. 2.4 Deleting UTRAN SubNetwork
9. 2.5 Creating RNC Managed Element
10. 2.6 Creating RNC Config Set
11. 3.3 Creating RNC Ground Resource Management
Revision No.
Revision Date
Revision Reason
12. 4.1 Creating Rack
13. 4.2 Creating Shelf
14. 4.7 Performing Optical Port APS Protection
15. 4.11 Creating Unit Connection
16. 5.1.1 Creating Local Office (ATM)
17. 6.1.1 Creating Local Office (IP)
R1.3
2010-11-22

1. 5.2.8 Creating Signaling Link Configuration of Adjacent RNC
Office (ATM)
2. 5.2.10 Creating Office Route of Adjacent RNC Office (ATM)
3. 5.3.2 Creating MGW Office (ATM)
4. 5.3.7 Creating MGW Adjacent Office Signaling Point
Configuration (ATM)
5. 5.3.8 Creating MGW Signaling Link Configuration (ATM)
6. 5.3.10 Creating MGW Office Route (ATM)
7. 5.4.1 Creating MSC Office (ATM)
8. 5.4.2 Creating MSC Adjacent Office Signaling Point
Configuration (ATM)
9. 5.4.3 Creating MSC Office Route (ATM)
10. 5.5.1 Creating SGSN Office (ATM)
11. 5.5.3 Creating SGSN Adjacent Office Signaling Point
Configuration (ATM)
12. 5.5.4 Creating SGSN Signaling Link Configuration
13. 5.5.6 Creating SGSN Office Route (ATM)
14. 5.6.9 Creating Node B Signaling Link Configuration (ATM)
15. 6.3.2 Creating MSC Office (IP)
16. 6.3.4 Creating MSC Adjacent Office Signaling Point
Configuration (IP)
17. 6.4.2 Creating SGSN Office (IP)
18. 6.4.4 Creating SGSN Adjacent Office Signaling Point
Configuration (IP)
R1.2
2010-09-30
The following topics have been modified:

1. Creating AAL2 Path Configuration of Adjacent RNC Office
(ATM)
2. Creating Adjacent Office Signaling Point Configuration (ATM)
3. Creating Adjacent Office Signaling Point Configuration (IP)
Revision No.
Revision Date
Revision Reason
R1.1
2010-09-06
The following sections have been added:

1. 1.4 Opening Configuration Management Interface
2. 1.4.1 Starting NetNumen M31 Client
3. 1.4.2 Creating an NE Agent
4. 1.4.3 Starting an NE Agent
5. 1.4.4 Synchronizing Configurations
6. 1.4.5 Starting NE Management
7. 1.4.6 Opening Configuration Management Interface
The following sections have been deleted:
1. 1.4 Entering Configuration Management Interface
2. 1.5 Introduction to Configuration Management Interface
1. Preface
2. 1.1 Configuration Management Functions
3. 1.3 RNC Overall Configuration Flow
4. 1.5 Common Operations of Data Configuration
5. 2.1 Creating UTRAN SubNetwork
6. 2.3 Modifying UTRAN SubNetwork
7. 3.1 Overview to RNC Ground Resource Configuration
8. 4.3 Creating Board
9. 4.4 Showing Board Properties
10. 4.11 Creating Unit Connection
11. 5.4.1 Creating MSC Office (ATM)
12. 5.5.1 Creating SGSN Office (ATM)
13. 5.5.8 Creating PVC Configuration (ATM)
14. 5.6.4 Creating Node B Office (ATM)
15. 5.6.7 Creating Node B Path Configuration (ATM)
16. 6.1.1 Creating Local Office (IP)
17. 6.2.2 Creating Adjacent RNC Office (IP)
18. 6.3.2 Creating MSC Office (IP)
19. 6.4.2 Creating SGSN Office (IP)
20. 6.5.2 Creating SCTP Association Configuration (IP)
21. 6.6.2 Creating Node B Office (IP)
The titles of the following chapters have been modified:
1. Chapter 2 Configure Static Data for RNC Global
2. Chapter 3 Configure Static Data for Ground Global Resource
Management
3. Chapter 4 Configure Static Data for Hardware
4. Chapter 5 Configure Static Data for NE information (ATM)
5. Chapter 6 Configure Static Data for NE information (IP)
Revision No.
Revision Date
Revision Reason
6. Chapter 7 Configure Static Data for Qos
R1.0
2010-07-12
Serial Number: SJ-20100603155704-024

Publishing Date: 2011-08-31 (R3.0)
First Edition (V3.09.30.03)
Contents
About This Manual ......................................................................................... I
Chapter 1 Configuration Overview ........................................................... 1-1
1.1 Introduction........................................................................................................ 1-1
1.2 Prerequisites...................................................................................................... 1-1
1.3 Ground Resource Configuration Flow .................................................................. 1-2
Chapter 2 Public Resource Configuration ............................................... 2-1

2.1 Introduction........................................................................................................ 2-1
2.2 Creating a UTRAN Subnetwork Node .................................................................. 2-2
2.3 Creating an RNC Managed Element.................................................................... 2-3
2.4 Creating an RNC configuration Set...................................................................... 2-4
2.5 Creating a RNC Ground Resource Management Node ......................................... 2-5
2.6 Creating Global Supplemented Configuration....................................................... 2-7
Chapter 3 Hardware Resource Configuration.......................................... 3-1

3.1 Introduction........................................................................................................ 3-1
3.2 Creating a Rack ................................................................................................. 3-2
3.3 Creating a Shelf ................................................................................................. 3-4
3.4 Creating a Board ................................................................................................ 3-6
3.5 Creating a Unit Connection ................................................................................. 3-9
3.6 Configuring an Interface.................................................................................... 3-13
3.7 Creating Service IP Addresses for a DSP Path................................................... 3-15
Chapter 4 Configuring NE Information (ATM).......................................... 4-1

4.1 Overview ........................................................................................................... 4-1
4.2 Local Office........................................................................................................ 4-2
4.2.1 Creating Local Office (ATM) ...................................................................... 4-2
4.2.2 Modifying Local Office .............................................................................. 4-8
4.2.3 Creating RNC ATM Office (ATM) ............................................................. 4-12
4.2.4 Creating No. 7 Signaling (ATM)............................................................... 4-15
4.2.5 Creating RNC Local Office Signaling Point (ATM)..................................... 4-17
4.2.6 Creating RNC Local Office Subsystem No. (ATM) .................................... 4-19
4.3 Adjacent RNC Office ........................................................................................ 4-21
4.3.1 Creating Adjacent RNC Path Group (ATM)............................................... 4-21
4.3.2 Creating Adjacent RNC Office (ATM) ....................................................... 4-25
4.3.3 Modifying Adjacent RNC Office (ATM) ..................................................... 4-31
I
4.3.4 Creating ATM Office of Adjacent RNC Office (ATM) .................................. 4-34
4.3.5 Creating Path of Adjacent Office (ATM).................................................... 4-36
4.3.6 Creating AAL2 Path of Adjacent RNC Office (ATM) .................................. 4-38
4.3.7 Creating Adjacent Office Signaling Point (ATM) ........................................ 4-42
4.3.8 Creating Signaling Link of Adjacent RNC Office (ATM).............................. 4-44
4.3.9 Creating Adjacent RNC NE - RNC Signaling Link Route (ATM) ................. 4-46
4.3.10 Creating Office Route of Adjacent RNC Office (ATM) .............................. 4-48
4.3.11 Creating Adjacent Office Subsystem No. (ATM)...................................... 4-50
4.4 MGW............................................................................................................... 4-52
4.4.1 Creating MGW Path Group (ATM) ........................................................... 4-52
4.4.2 Creating MGW Office (ATM).................................................................... 4-56
4.4.3 Modifying MGW Office ............................................................................ 4-62
4.4.4 Creating MGW ATM Office (ATM) ............................................................ 4-65
4.4.5 Creating MGW Path (ATM) ..................................................................... 4-67
4.4.6 Creating MGW AAL2 Path Configuration (ATM)........................................ 4-69
4.4.7 Creating MGW Adjacent Office Signaling Point (ATM)............................... 4-72
4.4.8 Creating MGW Signaling Link (ATM) ....................................................... 4-74
4.4.9 Creating MGW Signaling Bearer - RNC Signaling Link Route (ATM) .......... 4-76
4.4.10 Creating MGW Office Route (ATM) ........................................................ 4-78
4.4.11 Creating Adjacent Office Subsystem No. (ATM)...................................... 4-80
4.5 MSC................................................................................................................ 4-82
4.5.1 Creating MSC Office (ATM)..................................................................... 4-82
4.5.2 Creating MSC Adjacent Office Signaling Point (ATM)................................ 4-88
4.5.3 Creating MSC Office Route (ATM) ........................................................... 4-90
4.5.4 Creating MSC Adjacent Office Subsystem No. (ATM) ............................... 4-92
4.6 SGSN.............................................................................................................. 4-94
4.6.1 Creating SGSN Office (ATM)................................................................... 4-94
4.6.2 Creating SGSN ATM Office (ATM) ..........................................................4-100
4.6.3 Creating SGSN Adjacent Office Signaling Point (ATM).............................4-102
4.6.4 Creating SGSN Signaling Link ...............................................................4-104
4.6.5 Creating SGSN Signaling Bearer - RNC Signaling Link Route (ATM) ........4-106
4.6.6 Creating SGSN Office Route (ATM)........................................................4-109
4.6.7 Creating SGSN Adjacent Office Subsystem No. (ATM) ............................ 4-111
4.6.8 Creating PVC Configuration (ATM) ......................................................... 4-113
4.6.9 Creating ATM and IP Binding Relation (ATM) .......................................... 4-118
4.6.10 Creating Static Route (ATM).................................................................4-120
4.7 Node B ...........................................................................................................4-123
II
4.7.1 Creating IMA Group (ATM).....................................................................4-123

4.7.2 Creating IMA Link (ATM)........................................................................4-126
4.7.3 Creating Node B Path Group (ATM)........................................................4-128
4.7.4 Creating Node B Office (ATM) ................................................................4-132
4.7.5 Modifying Node B Office (ATM) ..............................................................4-138
4.7.6 Creating Node B ATM Office (ATM) ........................................................4-140
4.7.7 Creating Node B Path (ATM)..................................................................4-142
4.7.8 Creating Node B AAL2 Path (ATM).........................................................4-144
4.7.9 Creating Node B Signaling Link (ATM) ....................................................4-146
4.7.10 Creating Node B Port (ATM).................................................................4-149
Chapter 5 Configuring NE Information (IP) .............................................. 5-1

5.1 Local Office........................................................................................................ 5-1
5.1.1 Creating Local Office (IP).......................................................................... 5-1
5.1.2 Creating RNC ATM Office (IP)................................................................... 5-7
5.1.3 Creating No. 7 Signaling (IP) .................................................................. 5-10
5.1.4 Configuring RNC Local Office Signaling Point (IP) .................................... 5-12
5.1.5 Creating RNC Local Office Subsystem No. (IP)........................................ 5-14
5.2 Adjacent RNC Office ........................................................................................ 5-16
5.2.1 Creating Adjacent RNC Path Group (IP) .................................................. 5-16
5.2.2 Creating Adjacent RNC Office (IP)........................................................... 5-20
5.2.3 Creating Path of Adjacent Office (IP) ....................................................... 5-26
5.2.4 Creating Adjacent Office Signaling Point (IP)............................................ 5-28
5.2.5 Creating Adjacent Office Subsystem No. (IP) ........................................... 5-30
5.3 MSC................................................................................................................ 5-32
5.3.1 Creating MSC Path Group (IP) ................................................................ 5-32
5.3.2 Creating MSC Office (IP) ........................................................................ 5-36
5.3.3 Creating MSC Path (IP) .......................................................................... 5-42
5.3.4 Creating MSC Adjacent Office Signaling Point (IP) ................................... 5-44
5.3.5 Creating MSC Adjacent Office Subsystem No. (IP)................................... 5-46
5.4 SGSN.............................................................................................................. 5-48
5.4.1 Creating SGSN Path Group (IP) .............................................................. 5-48
5.4.2 Creating SGSN Office (IP) ...................................................................... 5-52
5.4.3 Creating SGSN Path (IP) ........................................................................ 5-58
5.4.4 Creating SGSN Adjacent Office Signaling Point (IP) ................................. 5-60
5.4.5 Creating SGSN Adjacent Office Subsystem No. (IP)................................. 5-62
5.5 Sigtran............................................................................................................. 5-64
5.5.1 Creating Sigtran (IP)............................................................................... 5-64
III
5.5.2 Creating SCTP Association (IP) .............................................................. 5-67

5.5.3 Creating ASP Configuration Information (IP) ............................................ 5-72
5.5.4 Creating AS Static Information (IP) .......................................................... 5-74
5.5.5 Creating Static Route Information of M3UA (IP)........................................ 5-78
5.5.6 Creating Route Information of M3UA Multi-RK (IP) ................................... 5-80
5.6 Node B ............................................................................................................ 5-82
5.6.1 Creating Node B Path Group (IP) ............................................................ 5-82
5.6.2 Creating Node B Office (IP)..................................................................... 5-86
5.6.3 Configuring Node B Path (IP) .................................................................. 5-92
5.6.4 Configuring SCTP Resource Relation (IP)................................................ 5-94
5.6.5 Creating Node B Port (IP) ....................................................................... 5-96
5.7 Creating Static Route (IP) ................................................................................. 5-99
Chapter 6 Configuring QoS ....................................................................... 6-1

6.1 Creating QoS Configuration ................................................................................ 6-1
6.2 Editing QoS Configuration................................................................................... 6-3
6.3 Modifying Priority and Rate Segment Related QoS Configuration Parameter.......... 6-4
6.4 Modifying Basic Priority Configuration Information Advanced Parameter ................ 6-6
6.5 Modifying Scheduling Priority Configuration Information Advanced Parameter........ 6-7
6.6 Modifying Application Priority Configuration Information Advanced Parameter...... 6-10
6.7 Modifying Basic Priority Transport Bearer Type Advanced Parameter ...................6-11
6.8 Modifying Basic Priority Transport Reserved Bandwidth Advanced Parameter
(Interactive/Background Class) ........................................................................ 6-13
6.9 Modifying Access Control related to Basic Priority .............................................. 6-14
Chapter 7 Setting Alarm Parameters ........................................................ 7-1

7.1 Creating CLKG Board Alarm Parameters ............................................................. 7-1
7.2 Creating CLKG (ICM) Board Alarm Parameters.................................................... 7-4
7.3 Creating Power Board Alarm Parameters............................................................. 7-7
7.4 Creating MPX86/2 Alarm Parameters ................................................................ 7-13
Appendix A Common Configuration Management Operations ............ A-1

A.1 Starting the NetNumen M31 Client................................................................... A-1
A.2 Creating an NE Agent ........................................................................................ A-3
A.3 Starting an NE Agent ......................................................................................... A-5
A.4 Synchronizing the Configuration Data.................................................................. A-7
A.5 Starting the NE Management.............................................................................. A-9
A.6 Opening the Configuration Management View ................................................... A-10
Figures............................................................................................................. I
Tables ..........................................................................................................XIII
IV
Glossary ...................................................................................................... XV
VI
About This Manual

Purpose
This manual describes Ground Resource Configuration for the ZXWR RNC basic services.
The parameters should be configured according to the data planning and configuration
solution.
The manual describes the configurations in ATM transportation mode and IP transportation
mode.
Intended Audience
The audience for this book knows about the following knowledge.
l
l
l
l
Network management basics

RNC hardware structure
RNC data planning
RNC debugging
What is in This Manual

This manual consists of the following chapters:
Chapter
Chapter 1, Configuration Overview
Summary
Describes the prerequisites of RNC Data Configuration and the procedure of RNC Ground Resource
Configuration.
Chapter 2, Public Resource Configuration
Describes the details of the Public Resource Configuration.
Chapter 3, Hardware Resource Configuration
Describes the configuration of racks, shelves and

boards.
Chapter 4, NE Information (ATM)
Describes the configuration of NE information in ATM

network mode.
Chapter 5, NE Information (IP)
Describes the configuration of NE information in IP

network mode.
Chapter 6, QoS Configuration
Describes the QoS Configuration.
Chapter 7, Alarm Notification
Describes the configuration of alarm notification.
Appendix A, Common Configuration Manage-
Describes the common operations for the Configura-
ment Operations
tion Management.
II
Chapter 1
Configuration Overview
Table of Contents
Introduction ................................................................................................................1-1
Prerequisites ..............................................................................................................1-1
Ground Resource Configuration Flow.........................................................................1-2
1.1 Introduction
The purpose of Radio Network Controller (RNC) configuration management is to manage
various resource data of RNCs. The data configuration of an RNC determines the
operation mode and status of the RNC.
A connection is established between the network management system and the RNC
Network Element (NE) after the data configuration is completed. Through this connection,
users can set parameters of Managed Objects (MOs) in the RNC via the user interface of
the network management system.
1.2 Prerequisites
Tools
The following are required for RNC data configuration:
l
l
An EMS server and an OMM server are available, and they are connected to the RNC.
An EMS client is available.
Conditions
The following conditions must be met before RNC data configuration:
l
l
l
l
You have the user name and password for logging in to the network element
management system.
The hardware configuration list, engineering design document, interconnection data
for connecting peer devices, and configuration solution of the RNC are prepared.
You are authorized to configure the RNC.
The Configuration Management view is opened. For how to open the Configuration
Management window, refer to Appendix A, Common Configuration Management
Operations.
You have obtained the mutex right on the RNC Managed Element. For how to
apply for the mutex right, refer to ZXWR RNC (V3.09.30) Radio Network Controller
Configuration Tool Operation Guide.
1-1
SJ-20100603155704-024|2011-08-31 (R3.0)
ZTE Proprietary and Confidential
ZXWR RNC Ground Configuration Operation Guide
1.3 Ground Resource Configuration Flow

Figure 1-1 shows the general flow for RNC Ground Resource Configuration.
Figure 1-1 Flow for RNC Ground Resource Configuration
After the data configuration is completed, the configuration data must be synchronized
from the database of the network management server to network elements. For how
to synchronize the configuration data, refer to ZXWR RNC (V3.09.30) Radio Network
Controller Configuration Tool Operation Guide.
1-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 2
Public Resource
Configuration
Table of Contents
Introduction ................................................................................................................2-1
Creating a UTRAN Subnetwork Node.........................................................................2-2
Creating an RNC Managed Element ..........................................................................2-3
Creating an RNC configuration Set.............................................................................2-4
Creating a RNC Ground Resource Management Node ..............................................2-5
Creating Global Supplemented Configuration .............................................................2-7
2.1 Introduction
Figure 2-1 shows the general flow for the Public Resource Configuration.
2-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 2-1 Flow for the Public Resource Configuration
2.2 Creating a UTRAN Subnetwork Node

Abstract
This section describes how to create a UTRAN Subnetwork node under Configuration
Resource Tree.
Prerequisites
l
l
The Network Management System (NMS) is operating properly.

The Configuration Management view is opened.
Steps
1. In the Configuration Resource Tree, right-click the root node, and then select Create
> UTRAN Subnetwork.
2-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 2 Public Resource Configuration
The UTRAN Subnetwork dialog box opens, as shown in Figure 2-2.

Figure 2-2 UTRAN Subnetwork
2. Set the Alias and Subnetwork ID parameters.

3. Click OK.
End of Steps
2.3 Creating an RNC Managed Element

Steps
1. In the Configuration Resource Tree, right-click the UTRAN Subnetwork node, and
then select Create > RNC Managed Element.
The RNC Managed Element dialog box opens, as shown in Figure 2-3.
Figure 2-3 RNC Managed Element
2-3
SJ-20100603155704-024|2011-08-31 (R3.0)
2.
3. Set necessary parameters according to the planning data.
4. Click OK.
End of Steps
2.4 Creating an RNC configuration Set

Abstract
After an RNC Managed Element is created, the system generates an RNC Config Set
automatically. You can also create an RNC Config Set under a Managed Element node.
This section describes how to create a standby RNC Config Set.
Note:
An RNC Managed Element can have one master configuration set and multiple standby
configuration sets. They can be switched over between each other.
indicates the
master configuration set, and

indicates the slave set. For how to perform switch-over
between configuration sets, refer to ZXWR RNC (V3.09.30) Radio Network Controller
Configuration Tool Operation Guide.
Prerequisites
1. The Network Management System is operating properly.
2. You have the mutex right.
Steps
1. In the Configuration Resource Tree, right-click the RNC Managed Element node,
and then select Create > RNC Config Set.
The RNC Config Set dialog box opens, as shown in Figure 2-4.
2-4
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 2-4 RNC Config Set

3. Click OK.
End of Steps
2.5 Creating a RNC Ground Resource Management

Node
Abstract
This section describes how to create an RNC Ground Resource Management node. The
Ground Resource Management objects are created under this node.
Prerequisites
1. The Configuration Management view is opened.
Steps
1. In the Configuration Resource Tree, right-click RNC Config Set node, and then
select Create > RNC Ground Resource Management.
The RNC Ground Resource Management dialog box pops up, as shown in Figure
2-5.
2-5
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 2-5 RNC Ground Resource Management

3. Click OK.
End of Steps
Result
After RNC Ground Resource Management is created successfully, the Configuration
Resource Tree adds the RNC Ground Resource Management node and its subnodes,
as shown in Figure 2-6.
2-6
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 2-6 The RNC Ground Resource Management Node and the Subnodes
Follow-Up Action
Table 2-1 describes the icons of the shortcut menu on the RNC Ground Resource
Management tab.
Table 2-1 SHORTCUT MENU ON THE RNC GROUND RESOURCE MANAGEMENT TAB
Icon on the Shortcut Menu
Note
Modify
Cancel
Save
Close
Close All
Help
RNC Reset
Iu Port Reset
Synchronize NE Clock
Get NTP Time
2.6 Creating Global Supplemented Configuration

Abstract
This section describes how to create the Global Supplemented Configuration node.
2-7
SJ-20100603155704-024|2011-08-31 (R3.0)
Prerequisites
1. The Configuration Management view is opened.
Steps
1. In the Configuration Resource Tree, right-click the RNC Config Set node, and then
select Create > Global Supplemented Configuration.
The Global Supplemented Configuration dialog box opens, as shown in Figure 2-7.
Figure 2-7 Global Supplemented Configuration

3. Click OK.
End of Steps
2-8
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 3
Hardware Resource
Configuration
Table of Contents
Introduction ................................................................................................................3-1
Creating a Rack .........................................................................................................3-2
Creating a Shelf .........................................................................................................3-4
Creating a Board ........................................................................................................3-6
Creating a Unit Connection ........................................................................................3-9
Configuring an Interface ...........................................................................................3-13
Creating Service IP Addresses for a DSP Path.........................................................3-15
3.1 Introduction
Figure 3-1 shows the general flow for the Hardware Resource Configuration.
3-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-1 Flow for the Hardware Resource Configuration
3.2 Creating a Rack

Abstract
This section describes how to create a rack and configure it.
Prerequisites
1. The RNC Ground Resource Management node is created.
Steps
1. In the Configuration Resource Tree, right-click RNC Ground Resource
Management node, and then select Create > Rack.
3-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 3 Hardware Resource Configuration
The Rack dialog box opens, as shown in Figure 3-2.

Figure 3-2 Rack

3. Click OK.
End of Steps
Result
Double-click the Rack node in the Configuration Resource Tree. The Rack tab appears,
3-3
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-3 The Created Rack
3.3 Creating a Shelf

Abstract
This section describes how to create a shelf.
Prerequisites
1.
2.
3.
4.
The UTRAN Subnetwork node is created.

The RNC Managed Element node is created.
The RNC Config Set node is created.
The RNC Ground Resource Management node is created.
3-4
SJ-20100603155704-024|2011-08-31 (R3.0)
5. The Rack node is created.

6. The number and types of shelves are planned.
Steps
1. In the Rack tab, right-click on the rack diagram, and then select Create > Shelf, as
shown in Figure 3-4.
Figure 3-4 Creating a Shelf
The Shelf dialog box opens, as shown in Figure 3-5.

Figure 3-5 Shelf
The following four types of shelves can be created in a rack:

l
l
Control Shelf
Switch Shelf
3-5
SJ-20100603155704-024|2011-08-31 (R3.0)
l
l
Resource Shelf
1000 M Resource Shelf

3. Click OK.
End of Steps
3.4 Creating a Board

Abstract
This section describes how to create a board on a shelf.
Follow this sequence to create the boards: ROMB > UIMC > UIMU > Other boards.
Prerequisites
1.
2.
3.
4.
5.
6.
7.

The Rack node is created.
The Shelf is created.
The number and types of boards are planned.
Steps
1. In the Rack tab, right-click on the target shelf, and then select Create > Board, as
Figure 3-6 Creating a Board
The Board dialog box opens, as shown in Figure 3-7.
3-6
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-7 Board
2. From the Available Board list, select a board to be created.

3. Click OK.
3-7
SJ-20100603155704-024|2011-08-31 (R3.0)
Note:
If a RUB board is created, the system will prompt you to configure the IP addresses
and the UDP port.
For how to configure the IP addresses and UDP port, refer to Section 3.7, Creating
Service IPs for DSP.
End of Steps
Example
An example of board configuration is shown in Figure 3-8.
3-8
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-8 An Example of Board Configuration
3.5 Creating a Unit Connection

Abstract
This section describes how to create a unit connection between multiple resource shelves.
If there is only one resource shelf, you do not need to create a unit connection.
3-9
SJ-20100603155704-024|2011-08-31 (R3.0)
The Unit Connection falls into the following two types:

1. The UIMU/GUIM board on a resource shelf is connected to another UIMU/GUIM board
through a GE cable.
2. The UIMU/GUIM board on a resource shelf is connected to the GLI board on a switch
shelf through a GE cable.
Prerequisites
1.
2.
3.
4.
5.

The rack, shelves and boards are created.
Steps
l
For the type 1 connection, you shall open the the UIMU/GUIM board property pages
from both resource shelves and create unit connections. For example, the two
resource shelves are assumed to be installed on the first layer and third layer of the
rack.
a. On the Rack tab, right-click the UIMU/GUIM board on the first-layer resource shelf
(either the master board or the standby board), and then select Show Board
Properties Page.
The Board dialog box opens, as shown in Figure 3-9.
3-10
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-9 Board
b. Click Unit Connection.

c. Click Create. The Unit Connection dialog box opens, as shown in Figure 3-10.
3-11
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-10 Unit Connection
d. Set necessary parameters according to the planning data, and then click OK.
e. Right-click the UIMU/GUIM board on the third-layer resource shelf (either the
master board or the standby board) and repeat step 1 through 4 to create the unit
connection to the first-layer resource shelf.
l
For the type 2 connection, you shall open the GLI board property page from the switch
shelf and create the unit connection. For example, the switch shelf is assumed to be
installed on the fourth layer of the rack.
a. On the Rack tab, right-click the GLI board on the fourth-layer switch shelf and then
select Show Board Properties Page, as shown in Figure 3-11.
Figure 3-11 Show Board Properties Page
b. Click Unit Connection.

c. Click Create. The Unit Connection dialog box opens, as shown in Figure 3-12.
3-12
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-12 Unit Connection
d. Set necessary parameters according to the planning data, and then click OK.
End of Steps
3.6 Configuring an Interface

Abstract
This section describes how to configure the routing information for the interface board,
such as the IP address and the MAC address.
1. Two types of interface board at the Iur port:
l APBE board. If this board is connected to the adjacent RNC in STM-1 mode, you
do not need to configure the interface.
l GIPI board. If this board is connected to the adjacent RNC in IP mode, you need
to configure the interface.
2. Two types of interface board at the IU port:
l APBE board. If this board is connected to the Core Network (CN) in STM-1 mode,
the IuPS interface applies the IPoA mode. You need to configure the interface.
l GIPI board. If this board is connected to the Core Network (CN) in IP mode, you
need to configure the interface.
3. Six types of interface board at the Iub port:
l APBE board
l GIPI board
l EIPI board
l SDTB board
3-13
SJ-20100603155704-024|2011-08-31 (R3.0)
l IMAB board
l SDTA board
4. The IP addresses in the interface configuration must meet the following requirements:
a. An IP address of the interface board shall be in a different network segment with
the IP address configured for another interface board (An IP address and a mask
shall be unique).
b. Each interface board can be configured with four IP addresses.
Prerequisites
1. The interface board is created.
Steps
1. In the Configuration Resource Tree, right-click RNC Config Set > RNC
Ground Resource Management > Transmission Configuration > IP Protocol
Configuration > Interface Configuration, and then select Create > Interface
Configuration.
The Choice of Interface Information dialog box appears, as shown in Figure 3-13.
Figure 3-13 Choice of Interface Information
2. Select the board type and the unit location (subsystem: module: unit: subunit).
Note:
The subsystem No. is the same as the shelf No. for the resource shelf. The subsystem
No. for a control shelf is 255.
3. Click Next. The Interface Configuration dialog box appears, as shown in Figure
3-14.
3-14
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-14 Interface Configuration
4. Set the IP address and subnet mask according to the planning data.
5. Click OK.
End of Steps
3.7 Creating Service IP Addresses for a DSP Path

Abstract
This section describes how to configure the IP addresses for the Digital Signal Processing
(DSP) on a RUB board.
The service IP addresses for a DSP path are used to map the DSP path to the local service
IP and the UDP port. Each DSP path must be configured with an IP address and UDP
port No.
3-15
SJ-20100603155704-024|2011-08-31 (R3.0)
Tip:
There can at most 5 RUB boards (VICD) on each resource shelf, and each RUB board
has 14 DSP paths. A DSP path occupies 800 UDP ports. An IP address occupies 60000
UDP ports and can be used for 75 DSP paths in the configuration.
Each resource shelf can have at most 10 RUB2 (VTCD_2) boards. Each RUB2 (VTCD_2)
board can have 15 DSP paths. A DSP path occupies 1600 UDP ports. An IP address
occupies 60000 UDP ports and can be used for 37 DSP paths in the configuration.
Prerequisites
1. The RUB board is created.
Steps
1. On the Rack tab, right-click an RUB board, and then select Service IP for DSP.
A Wanring message pops up, as shown in Figure 3-15.
Figure 3-15 Warning
2. Click OK. The Service IP for DSP dialog box opens, as shown in Figure 3-16.
3-16
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-16 Service IP for DSP
3. Click Batch Create. The Choose Service IP dialog box opens, as shown in Figure
3-17.
3-17
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-17 Choose Service IP
4. Select the service IP addresses according to the data plan.

5. Click OK. The Service IP for DSP dialog box opens, showing the batch create
operation is successful, as shown in Figure 3-18.
3-18
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 3-18 The Batch Create is Successful
6. Click Close.
End of Steps
3-19
SJ-20100603155704-024|2011-08-31 (R3.0)
This page intentionally left blank.
3-20
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 4
Configuring NE Information
(ATM)
Table of Contents
Overview ....................................................................................................................4-1
Local Office ................................................................................................................4-2
Adjacent RNC Office ................................................................................................4-21
MGW........................................................................................................................4-52
MSC.........................................................................................................................4-82
SGSN.......................................................................................................................4-94
Node B...................................................................................................................4-123
4.1 Overview
This chapter describes how to configure the information of an RNC network element using
the ATM transmission mode. The RNC connects to the other network elements via different
transmission interfaces, as illustrated in Figure 4-1.
Figure 4-1 Transmission Interfaces Between RNC and Other NEs
The following describes the transmission modes that can be used by three types of
interfaces between the RNC and other network elements.
4-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Interface
Purpose
Supported Transmission
Configuration Reference
Mode
Iur
Iu
Iub
Connects the RNC
ATM and IP transmission
to an adjacent RNC
modes
Connects the RNC
Configuring an MGW
to the CN
modes
Configuring an MSC
Configuring an SGSN
Connects the RNC
to a Node B
modes
Configuring an Adjacent RNC
Configuring a Node B
Note:
RNC = Radio Network Controller; CN = Core Network; ATM = Asynchronous Transfer Mode; IP =
Internet Protocol; MGW = Media GateWay; MSC = Mobile Switching Center; SGSN = Service GPRS
Supporting Node
The Iur and Iu interfaces can use only one transmission mode; while the Iub interface
may use two transmission modes at the same time because IP connections and ATM
connections may coexist between the RNC and a Node B.
4.2 Local Office

4.2.1 Creating Local Office (ATM)
Abstract
This section describes how to create the basic configuration information for the ZXWR
RNC local office.
Prerequisites
1.
2.
3.
4.
5.
UTRAN Subnetwork has been created.

RNC Managed Element has been created.
RNC Config Set has been created.
RNC Ground Resource Management has been created.
Rack, Shelf, and Board have been created.
Steps
1. On Configuration Resource Tree, right-click and choose NE Information
Configuration > Create > Local Office, as shown in Figure 4-2.
4-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 4 Configuring NE Information (ATM)
Figure 4-2 Selecting Create Local Office
2. Local Office dialog box pops up, as shown in Figure 4-3~Figure 4-10.
4-3
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-3 Local Office Dialog Box (Basic Configuration Tab)
Figure 4-4 Local Office Dialog Box (Basic Config-1 Tab)
4-4
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-5 Local Office Dialog Box (Node B Config tab)
Figure 4-6 Local Office Dialog Box (CN/RNC Common Config Tab)
4-5
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-7 Local Office Dialog Box (RNC Config Tab)
Figure 4-8 Local Office Dialog Box (CN Config-1 Tab)
4-6
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-10 Local Office Dialog Box (BSC Config Tab)
3. Set parameters and click OK. The system has created the Local Office.
4-7
SJ-20100603155704-024|2011-08-31 (R3.0)
Note:
To delete the Local Office, make sure that no RNC radio resources are configured in
the current RNC configuration set.
End of Steps
Follow-Up Action
The shortcut menu on Local Office dialog box is as shown in Table 4-1.
Table 4-1 Shortcut Menu on Local Office Dialog Box
Shortcut Menu
Description
Modify
Cancel
Close
Close All
Help
4.2.2 Modifying Local Office

Steps
1. On Configuration Resource Tree, the created Local Office appears under NE
Information Configuration, as shown in Figure 4-11.
4-8
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-11 Created Local Office
2. Double-click Local Office and its information box pops up on the right, as shown in
Figure 4-12.
4-9
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-12 Local Office Information Page
3. Click
on the shortcut menu and the Local Office tab becomes editable.
4. Select one piece of information on MO Records column to modify the related

information on Local Office tab, as shown in Figure 4-13.
4-10
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-13 Modifying Information on Local Office Dialog Box
5. Click Modify Commit to modify the information, as shown in Figure 4-14.
4-11
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-14 Modified Local Office
End of Steps
4.2.3 Creating RNC ATM Office (ATM)

Abstract
This section describes how to configure the information ofAAL2 office, including ATM
address code plan, ATM address, whether the Q2630.2 protocol is supported, etc.
Prerequisites
1.
2.
3.
4.
5.
6.

Local Office has been created.
Steps
1. On Local Office interface, click ATM Office Configuration tab, as shown in Figure
4-15.
4-12
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-15 ATM Office Configuration Tab
2. Set parameters on the ATM Office Configuration tab, as shown in Figure 4-16.
Figure 4-16 Setting Parameters on the ATM Office Configuration Tab
3. Click Create Commit and one piece of configuration information appears in MO

Records column, as shown in Figure 4-17.
4-13
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-17 Created ATM Office Configuration
The button of Create Commit contains two states:

l
l
Create Commit: In this state, the user can create a new object.
Switch to Create: In this state, the user can not create a new object.
The button of Modify also contains two states:

l
l
Modify: In this state, the user can modify the information of the object.
Switch to Modify: In this state, the user can not modify the information of the
object.
The buttons of Create Commit and Modify can not exist in the same state. When the
user click the Create Commit button and it turns into the Create Commit state, the
button of Modify turns into the Switch to Modify automatically. Vice versa.
Note:
On NE Information Configuration, the relations of Create Commit and Modify
buttons of all nodes are same. Therefore, the manual does not describe any more.
4. Select one piece of configuration information on MO Records column.

Click Switch to Modify to modify the piece of information.
Click Delete to delete the piece of information from the MO Records column.
End of Steps
4-14
SJ-20100603155704-024|2011-08-31 (R3.0)
4.2.4 Creating No. 7 Signaling (ATM)

Abstract
This section describes how to configure the signal point type (STP/SEP/STEP) and link
test code of the local office.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click No.7 Signaling Configuration tab, as shown in
Figure 4-18.
Figure 4-18 No. 7 Signaling Configuration Tab
4-15
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the No.7 Signaling Configuration tab, as shown in Figure 4-19.
Figure 4-19 Setting Parameters on the No.7 Signaling Configuration Tab

Figure 4-20 Created No.7 Signaling Configuration

4-16
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
4.2.5 Creating RNC Local Office Signaling Point (ATM)

Abstract
This section describes how to configure the signaling point code of the local office, including
24-digit signaling point code and 14-digit signaling point code.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click Local Office Signaling Point Configuration tab, as
Figure 4-21 Local Office Signaling Point Configuration Tab
4-17
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Local Office Signaling Point Configuration tab, as shown in
Figure 4-22.
Figure 4-22 Setting Parameters on the Local Office Signaling Point Configuration
Tab

Figure 4-23 Created Local Office Signaling Point Configuration

4-18
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
4.2.6 Creating RNC Local Office Subsystem No. (ATM)

Abstract
This section describes how to configure the subsystem ID for the local office. The system
generates the ID automatically and the user does not need to create manually. If the ID is
deleted manually, configure as below.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click Local Office Subsystem No. tab, as shown in Figure
4-24.
Figure 4-24 Local Office Subsystem No. Tab
4-19
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Local Office Subsystem No. tab, as shown in Figure 4-25.
Figure 4-25 Setting Parameters on the Local Office Subsystem No. Tab

Figure 4-26 Created Local Office Subsystem No.
Local Office Subsystem No. is unique in the office.

4-20
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
4.3 Adjacent RNC Office

4.3.1 Creating Adjacent RNC Path Group (ATM)
Abstract
The ZXWR RNC performs the level-2 bandwidth access and flow control on the user data
through configuring the bandwidth for the path and path group.
Note:
Path and path group is used to perform the bandwidth access and flow control on the user
data. They are not related to the signaling data.
Prerequisites
1.
2.
3.
4.
5.
6.

Transmission Configuration has been created.
Steps
1. On Configuration Resource Tree, right-click and choose Path Group Configuration
> Create > Path Group Configuration, as shown in Figure 4-27.
4-21
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-27 Selecting Create Path Group Configuration
2. Path Group Configuration dialog box pops up, as shown in Figure 4-28. Fill in Path
Group ID (unique in the NE), Forward bandwidth, and Backward bandwidth according
to the actual cases.
Figure 4-28 Path Group Configuration Dialogue Box
3. Click OK and the system has created Path Group Configuration.

End of Steps
4-22
SJ-20100603155704-024|2011-08-31 (R3.0)
Example
Here is an example to describe what is transport path and path group. For example, one
company contains ten departments. The outlay of each department is within RMB 10,000
yuan and the outlay of the whole company is within RMB 80,000 yuan. The R&D outlay
limit of each department is equal to the path bandwidth limit and the R&D outlay limit of the
whole company is equal to the path group bandwidth limit. It implements the level-2 outlay
control. The path group bandwidth is less than the bandwidth sum inside the path group.
Note:
Path belongs to one target office, numbered independently in one office. Path group are
numbered uniformly.
The example for Path Group Configuration is as shown in Table 4-2.

Table 4-2 Example for Path Group Configuration
Path Group ID
Forward Bandwidth (bps)
Backward Bandwidth (bps)
1000000
1000000
1000000
1000000
1000000
1000000
1000000
1000000
Follow-Up Action
1. Transport path
The transport path can be defined as several forms, as shown in Figure 4-29.
4-23
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-29 Transmission Form and Path Definition
a. The local ZXWR RNC is configured with one IMA group port. All services coming
out of this port belong to the same transport path.
b. The local ZXWR RNC is configured with one STM-1 port. All services coming out
of this port belong to the same transport path.
c.
There is one combination of IP network address and mask. When the target
address belongs to this network, all services to this target address belong to the
same transport path. Only in the IP mode, one physical port can include several
paths.
2. Transport path group

The transport path group is the combination of several transport paths to the same
office, or the combination of several transport paths of different offices.
The multiple transport paths in the transmission path group have one common
feature: All services on these transport paths will pass the same section of the
physical transmission before arriving at the target office. This section of the physical
transmission may not be connected with ZXWR RNC.
Transport path group can help to control the service traffic on several transport paths.
3. Transport path bandwidth
The transport path bandwidth refers to the bandwidth that can be allocated for the
service data transmission on a specific transport path. It is the virtual bandwidth.
4-24
SJ-20100603155704-024|2011-08-31 (R3.0)
The transport path bandwidth is less than the physical channel (IMA group, STM-1
interface, GE interface, FE interface) bandwidth where the physical path locates.
4. Transport path group bandwidth
The transport path group bandwidth refers to the max service data traffic allowed on
the transmission path group. It is the virtual bandwidth.
The shortcut menu on Path Group Configuration dialog box is as shown in Table 4-3.
Table 4-3 Shortcut Menu on Path Group Configuration Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
4.3.2 Creating Adjacent RNC Office (ATM)

Abstract
This sections describes how to create the basic information for the adjacent ZXWR RNC,
including ATM address, target signal point, office route, and signaling link.
Prerequisites
1.
2.
3.
4.
5.

Steps
Configuration > Create > Adjacent RNC Office, as shown in Figure 4-30.
4-25
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-30 Selecting Create Adjacent RNC Office
2. Adjacent RNC Office dialog box pops up, as shown in Figure 4-31~Figure 4-38.
4-26
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-31 Adjacent RNC office Dialog Box (Basic Configuration Tab)
When the value of Net Element Type is CN or RNC, the value of No.7 Office ID can
not be 0.
Figure 4-32 Adjacent RNC Office Dialog Box (Basic Config-1 Tab
4-27
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-33 Adjacent RNC Office Dialog Box (Node B Config Tab)
Figure 4-34 Adjacent RNC Office Dialog Box (CN/RNC Common Config Tab)
4-28
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-35 Adjacent RNC Office Dialog Box (RNC Config Tab)
Figure 4-36 Adjacent RNC Office Dialog Box (CN Config-1 Tab)
4-29
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-38 Adjacent RNC Office Dialog Box (BSC Config Tab)
3. Set parameters and click OK. The system has created the Adjacent RNC Office.
End of Steps
4-30
SJ-20100603155704-024|2011-08-31 (R3.0)
Follow-Up Action
The shortcut menu on Adjacent RNC Office dialog box is as shown in Table 4-4.
Table 4-4 Shortcut Menu on Adjacent RNC Office Dialog Box
Shortcut Menu
Description
Modify
Cancel
Close
Close All
Help
4.3.3 Modifying Adjacent RNC Office (ATM)

Steps
1. On Configuration Resource Tree, the created Adjacent RNC Office appears under
NE Information Configuration, as shown in Figure 4-39.
4-31
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-39 Created Adjacent RNC Office
2. Double-click Adjacent RNC Office and its information box pops up on the right, as
4-32
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-40 Adjacent RNC Office Information Page
3. Click
on the shortcut menu and the Adjacent RNC Office tab becomes editable.

information on Adjacent RNC Office tab, as shown in Figure 4-41.
Figure 4-41 Modifying Information on Adjacent RNC Office Dialog Box
4-33
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-42 Modified Adjacent RNC Office
End of Steps
4.3.4 Creating ATM Office of Adjacent RNC Office (ATM)

Abstract
This section describes how to configure the information of AAL2 adjacent office, including
ATM address coding plan, ATM address, whether the adjacent office connects with the
local office directly, and whether Q2630.2 protocol is supported.
Prerequisites
1.
2.
3.
4.
5.
6.

Adjacent RNC Office has been created.
Steps
1. On Adjacent RNC Office interface, click ATM Office Configuration tab, as shown in
Figure 4-43.
4-34
SJ-20100603155704-024|2011-08-31 (R3.0)
ATM address is unique in all network elements.

4-35
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.3.5 Creating Path of Adjacent Office (ATM)

Abstract
This sections describes how to configure the information of the transport path. It includes
the transport path bear type, transport path ID, transport path group ID, and path
bandwidth.
Prerequisites
1.
2.
3.
4.
5.
6.

4-36
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On Adjacent RNC Office interface, click Path Configuration tab, as shown in Figure
4-46.
Figure 4-46 Path Configuration Tab
2. Set parameters on the Path Configuration tab, as shown in Figure 4-47.
Figure 4-47 Setting Parameters on the Path Configuration Tab
The value range of Path ID is [0, 127].
4-37
SJ-20100603155704-024|2011-08-31 (R3.0)
l
l
If the value of Transportation Path Bear Type is ATM, the value range of Path
ID is [31, 127].
If the value of Transportation Path Bear Type is not ATM, the value range of
Path ID is [0, 31].
Under the NE Information Configuration node, Path Configuration with same Path
Group ID have same Home Module No.
Figure 4-48 Created Path Configuration

End of Steps
4.3.6 Creating AAL2 Path of Adjacent RNC Office (ATM)

Abstract
This sections describes how to configure AAL2 PATH information of the user data.
It includes the AAL2 Path ID, transport Path ID that AAL2 path belongs to, Service type
that AAL2 path bears, etc.
4-38
SJ-20100603155704-024|2011-08-31 (R3.0)
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Adjacent RNC Office interface, click AAL2 Path Configuration tab, as shown in
Figure 4-49.
Figure 4-49 AAL2 Path Configuration Tab
2. Set parameters on the AAL2 Path Configuration tab, as shown in Figure 4-50.
4-39
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-50 Setting Parameters on the AAL2 Path Configuration Tab
The values of CVCI and CVPI on the AAL2 Path Configuration dialog box (PVC
Configuration subtab) must be unique.
Figure 4-51 Created AAL2 Path Configuration

4-40
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
Follow-Up Action
Right-click the information in the AAL2 Path Configuration list and the menu pops up, as
Figure 4-52 Shortcut Menu of AAL Path Configuration
On the pop-up shortcut menu, users can choose to perform different dynamic data
operations. For details, refer to ZXWR RNC (V3.09.30) Radio Network Controller
Dynamic Data Management Operation Guide.
Note:
PVC and AAL2 Path Configuration on the Adjacent RNC Office, Node B Office, and
CN Office interface all contain the shortcut menu. Therefore, they will not be described in
the following section.
4-41
SJ-20100603155704-024|2011-08-31 (R3.0)
4.3.7 Creating Adjacent Office Signaling Point (ATM)

Abstract
This sections describes how to configure the signaling point code, signaling point coding
format, signaling point type of adjacent offices, and the connection mode of the local office.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Adjacent RNC Office interface, click Adjacent Office Signaling Point
Configuration tab, as shown in Figure 4-53.
Figure 4-53 Adjacent Office Signaling Point Configuration Tab
2. Set parameters on the Adjacent Office Signaling Point Configuration tab, as shown
in Figure 4-54.
4-42
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-54 Setting Parameters on the Adjacent Office Signaling Point

Configuration Tab

Figure 4-55 Created Adjacent Office Signaling Point Configuration

End of Steps
4-43
SJ-20100603155704-024|2011-08-31 (R3.0)
4.3.8 Creating Signaling Link of Adjacent RNC Office (ATM)

Abstract
This sections describes how to configure the signaling link of adjacent RNCs, including
signaling link and No. 7 link.
Signaling link configuration includes the configuration of link type, module that the link
belongs to, basic parameters, timer, and transmission delay.
No.7 link configuration includes the configuration of SLC and the module that the No.7 link
belongs to.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On the Adjacent RNC Office interface, click the Signaling Link Configuration tab,
Figure 4-56 Signaling Link Configuration Tab
4-44
SJ-20100603155704-024|2011-08-31 (R3.0)
For RNC, Application Type is MTP3B.

2. Set parameters on the Signaling Link Configuration tab, as shown in Figure 4-57.
Figure 4-57 Setting Parameters on the Signaling Link Configuration Tab
3. Click Create Commit and one piece of configuration information appears in the MO
Records pane, as shown in Figure 4-58.
Figure 4-58 Created Signaling Link Configuration
4. Select one piece of configuration information in the MO Records pane.

Click Switch to Modify to modify the information.
4-45
SJ-20100603155704-024|2011-08-31 (R3.0)
Click Delete to delete the information from the MO Records pane.

End of Steps
4.3.9 Creating Adjacent RNC NE - RNC Signaling Link Route (ATM)

Abstract
This sections describes how to configure one or several signaling routes for the local office,
and the relation between the signaling route and the signaling link that forms the singling
route.
Prerequisites
1.
2.
3.
4.
5.
6.
7.

No. 7 Local Office Signaling Configuration has been created.
Steps
1. On Local Office interface, click Signaling Route tab, as shown in Figure 4-59.
Figure 4-59 Signaling Link Route Tab
4-46
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Signaling Route tab, as shown in Figure 4-60.
Figure 4-60 Setting Parameters on the Signaling Link Route Tab

Figure 4-61 Created Signaling Link Route

4-47
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
4.3.10 Creating Office Route of Adjacent RNC Office (ATM)

Abstract
This sections describes how to configure the office route information of adjacent RNCs.
The office route consists of normal route and alternate route. Generally, the normal route
is used.
Prerequisites
1.
2.
3.
4.
5.
6.
7.

Signaling Link Configuration has been created.
Steps
1. On Adjacent RNC Office interface, click the Office Route tab, as shown in Figure
4-62.
4-48
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-62 Office Route Tab
2. Set parameters on the Office Route tab, as shown in Figure 4-63.
Figure 4-63 Setting Parameters on the Office Route Tab
4-49
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-64 Created Office Route

End of Steps
4.3.11 Creating Adjacent Office Subsystem No. (ATM)

Abstract
This sections describes how to configure the information of the adjacent office subsystem.
The system generates the ID automatically and the user does not need to create manually.
If the ID is deleted manually, configure as below.
Prerequisites
1.
2.
3.
4.
5.
6.

4-50
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On Adjacent RNC Office interface, click Adjacent Office Subsystem No. tab, as
Figure 4-65 Adjacent Office Subsystem No. Tab
2. Set parameters on the Adjacent Office Subsystem tab, as shown in Figure 4-66.
Figure 4-66 Setting Parameters on the Adjacent Office Subsystem No. Tab

4-51
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-67 Created Adjacent Office Subsystem No.
Adjacent Office Subsystem No. is unique in the office.

End of Steps
4.4 MGW
4.4.1 Creating MGW Path Group (ATM)
Abstract
Note:
4-52
SJ-20100603155704-024|2011-08-31 (R3.0)
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
4-53
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
Example
Note:
numbered uniformly.

Path Group ID
1000000
1000000
1000000
1000000
1000000
1000000
1000000
1000000
Follow-Up Action
1. Transport path
4-54
SJ-20100603155704-024|2011-08-31 (R3.0)
c.
paths.

4-55
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
4.4.2 Creating MGW Office (ATM)

Abstract
This sections describes how to create the basic information for the CN.
Prerequisites
1.
2.
3.
4.
5.

Steps
Configuration > Create > CN Office, as shown in Figure 4-71.
4-56
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-71 Selecting Create CN Office
2. The CN Office dialog box pops up, as shown in Figure 4-72~Figure 4-79.
Figure 4-72 CN Office Dialog Box (Basic Configuration Tab)
not be 0.
4-57
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-73 CN Office Dialog Box (Basic Config-1 Tab)
Figure 4-74 CN Office Dialog Box (Node B Config Tab)
4-58
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-75 CN Office Dialog Box (CN/RNC Common Config Tab)
Figure 4-76 CN Office Dialog Box (RNC Config Tab)
4-59
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-77 CN Office Dialog Box (CN Config-1 Tab)
4-60
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-79 CN Office Dialog Box (BSC Config Tab)
If the first selection of Net Element Type is the combination with MSCServer, the
value of Default Office Flag in CS Domain must be Yes and Yes only for this time.
If the first selection of Net Element Type is the combination with SGSN, the value of
Default Office Flag in CS Domain must be Yes and Yes only for this time.
If there is only one CS office, the office is configured as the default office and the NE
ID must be 0.
3. Set parameters and click OK. The system has created CN Office.
End of Steps
Follow-Up Action
The shortcut menu on CN Office dialog box is as shown in Table 4-7.
Table 4-7 Shortcut Menu on CN Office Dialog Box
Shortcut Menu
Description
Modify
Cancel
Close
Close All
4-61
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
4.4.3 Modifying MGW Office

Steps
1. On Configuration Resource Tree, the created CN Office appears under NE
Figure 4-80 Created CN Office
4-62
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Double-click CN Office and its information box pops up on the right, as shown in Figure
4-81
Figure 4-81 CN Office Information Page
3. Click
on the shortcut menu and the CN Office tab becomes editable.

information on CN Office tab, as shown in Figure 4-82.
4-63
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-82 Modifying Information on CN Office Dialog Box
Figure 4-83 Modified CN Office
End of Steps
4-64
SJ-20100603155704-024|2011-08-31 (R3.0)
4.4.4 Creating MGW ATM Office (ATM)

Abstract
This sections describes how to configure the information of AAL2 adjacent office, including
Prerequisites
1.
2.
3.
4.
5.
6.

CN Office has been created.
Steps
1. On CN Office interface, click ATM Office Configuration tab, as shown in Figure 4-84.
4-65
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
4-66
SJ-20100603155704-024|2011-08-31 (R3.0)
4.4.5 Creating MGW Path (ATM)

Abstract
This sections describes how to configure the information of the transport path.
It includes the transport path bear type, transport path ID, transport path group ID, and
path bandwidth, etc.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On CN Office interface, click Path Configuration tab, as shown in Figure 4-87.
4-67
SJ-20100603155704-024|2011-08-31 (R3.0)

l
l
ID is [31, 127].
Path ID is [0, 31].
4-68
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.4.6 Creating MGW AAL2 Path Configuration (ATM)

Abstract
This sections describes how to configure AAL2 path information of the user data.
It includes the AAL2 Path ID, transport path ID that AAL2 path belongs to, and service type
that AAL2 path bears.
Prerequisites
1.
2.
3.
4.
5.
6.

4-69
SJ-20100603155704-024|2011-08-31 (R3.0)
Note:
This step is only necessary when the CN type is MGW.
Steps
1. On CN Office interface, click AAL2 Path Configuration tab, as shown in Figure 4-90.
If NE Type is MSCSERVER, the AAL2 Path Configuration can not be created.

4-70
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
4-71
SJ-20100603155704-024|2011-08-31 (R3.0)
4.4.7 Creating MGW Adjacent Office Signaling Point (ATM)

Abstract
This sections describes how to configure the signaling point code and signaling point type
to adjacent offices.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On the CN Office interface, click the Adjacent Office Signaling Point Configuration
tab, as shown in Figure 4-93.
in Figure 4-94.
4-72
SJ-20100603155704-024|2011-08-31 (R3.0)

Configuration Tab
Net Type No. and Main Signaling Point Code are unique in the office.

End of Steps
4-73
SJ-20100603155704-024|2011-08-31 (R3.0)
4.4.8 Creating MGW Signaling Link (ATM)

Abstract
This section describes how to configure MGW signaling links, including signaling link and
No.7 link.
belongs to.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On the CN Office interface, click the Signaling Link Configuration tab, as shown in
Figure 4-96.
4-74
SJ-20100603155704-024|2011-08-31 (R3.0)
]
For the CN office, the value of Link Type is MTP3B.

4-75
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.4.9 Creating MGW Signaling Bearer - RNC Signaling Link Route

(ATM)
Abstract
This section describes how to configure one or several signaling routes for the local office,
and the relation between the signaling route and the signaling link that forms the signaling
route.
Prerequisites
1.
2.
3.
4.
5.
6.
7.

No. 7 Local Office Signaling Configuration has been created.
Steps
1. On Local Office interface, click Signaling Link Route tab, as shown in Figure 4-99.
4-76
SJ-20100603155704-024|2011-08-31 (R3.0)

4-77
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.4.10 Creating MGW Office Route (ATM)

Abstract
This section describes how to configure MGW office routes, including normal route and
alternative route. Generally, the normal route is used.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On the CN Office interface, click the Office Route tab, as shown in Figure 4-102.
4-78
SJ-20100603155704-024|2011-08-31 (R3.0)
4-79
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.4.11 Creating Adjacent Office Subsystem No. (ATM)

Abstract
This section describes how to configure the information of the adjacent office subsystem.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On CN Office interface, click Adjacent Office Subsystem No. tab, as shown in
Figure 4-105.
4-80
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Adjacent Office Subsystem No. tab, as shown in Figure
4-106.

4-81
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.5 MSC
4.5.1 Creating MSC Office (ATM)
Abstract
This section describes how to create the basic information for the CN.
Prerequisites
1.
2.
3.
4.
5.

4-82
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
not be 0.
4-83
SJ-20100603155704-024|2011-08-31 (R3.0)
4-84
SJ-20100603155704-024|2011-08-31 (R3.0)
4-85
SJ-20100603155704-024|2011-08-31 (R3.0)
4-86
SJ-20100603155704-024|2011-08-31 (R3.0)
Default Office Flag in PS Domain must be Yes and Yes only for this time.
ID must be 0.
End of Steps
Follow-Up Action
Shortcut Menu
Description
Modify
Cancel
Close
Close All
4-87
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
4.5.2 Creating MSC Adjacent Office Signaling Point (ATM)

Abstract
This section describes how to configure the signaling point code and signaling point type
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
4-88
SJ-20100603155704-024|2011-08-31 (R3.0)
in Figure 4-118.

Configuration Tab
4-89
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.5.3 Creating MSC Office Route (ATM)

Abstract
This section describes how to configure MSC office routes, including normal route and
alternative route. Generally, the normal route is used.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
4-90
SJ-20100603155704-024|2011-08-31 (R3.0)
4-91
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.5.4 Creating MSC Adjacent Office Subsystem No. (ATM)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
Figure 4-123.
4-92
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Adjacent Office Subsystem No. tab, as shown in Figure
4-124.

4-93
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.6 SGSN
4.6.1 Creating SGSN Office (ATM)
Abstract
Prerequisites
1.
2.
3.
4.
5.

4-94
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
not be 0.
4-95
SJ-20100603155704-024|2011-08-31 (R3.0)
4-96
SJ-20100603155704-024|2011-08-31 (R3.0)
4-97
SJ-20100603155704-024|2011-08-31 (R3.0)
4-98
SJ-20100603155704-024|2011-08-31 (R3.0)
ID must be 0.
End of Steps
Follow-Up Action
Shortcut Menu
Description
Modify
Cancel
Close
Close All
4-99
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
4.6.2 Creating SGSN ATM Office (ATM)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On CN Office interface, click ATM Office Configuration tab, as shown in Figure
4-135.
4-100
SJ-20100603155704-024|2011-08-31 (R3.0)

4-101
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.6.3 Creating SGSN Adjacent Office Signaling Point (ATM)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
4-102
SJ-20100603155704-024|2011-08-31 (R3.0)
in Figure 4-139.

Configuration Tab
4-103
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.6.4 Creating SGSN Signaling Link

Abstract
This section describes how to configure SGSN signaling links, including signaling link and
No. 7 link.
belongs to.
Prerequisites
1.
2.
3.
4.
5.
6.

4-104
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On the CN Office interface, click the Signaling Link Configuration tab, as shown in
Figure 4-141.
For the CN office, the value of Link Type is MTP3B.

4-105
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.6.5 Creating SGSN Signaling Bearer - RNC Signaling Link Route

(ATM)
Abstract
This section describes how to configure one or several signaling routes for the local office,
and the relation between the signaling route and the signaling link that forms the signaling
route.
Prerequisites
1.
2.
3.
4.

4-106
SJ-20100603155704-024|2011-08-31 (R3.0)
5. Rack, Shelf, and Board have been created.

6. Local Office has been created.
7. No. 7 Local Office Signaling Configuration has been created.
Steps
1. On Local Office interface, click Signaling Route tab, as shown in Figure 4-144.
4-107
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
4-108
SJ-20100603155704-024|2011-08-31 (R3.0)
4.6.6 Creating SGSN Office Route (ATM)

Abstract
This section describes how to configure SGSN office routes, including normal route and
alternate route. Generally, the normal route is used.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
4-109
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4-110
SJ-20100603155704-024|2011-08-31 (R3.0)
4.6.7 Creating SGSN Adjacent Office Subsystem No. (ATM)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On CN Office interface, click Adjacent Office Subsystem tab, as shown in Figure
4-150.
4-111
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
4-112
SJ-20100603155704-024|2011-08-31 (R3.0)
4.6.8 Creating PVC Configuration (ATM)

Abstract
This section describes how to create the PVC link between the local RNC and the ATM
office that the local RNC connects. PVC Configuration at RNC side covers APBE,
APBE_2, and IMAB interface board. In the IPOA mode, PVC is required to be configured
for the Iu-PS processing interface board and OMCB processing interface board.
Prerequisites
1.
2.
3.
4.
5.

Steps
1. On Configuration Resource Tree, right-click and choose PVC Configuration >
Create > PVC Configuration, as shown in Figure 4-153.
4-113
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-153 Selecting Create PVC Configuration
2. PVC Configuration dialog box pops up, as shown in Figure 4-154, Figure 4-155, and
Figure 4-156
4-114
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-154 PVC Configuration Dialog Box (Basic Configuration Tab)
4-115
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-155 PVC Configuration Dialog Box (PVC Config-1 Tab)
4-116
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-156 PVC Configuration Dialog Box (PVC Config-2 Tab)
3. Set parameters and click OK. The system has created PVC Configuration.
End of Steps
Follow-Up Action
The shortcut menu on PVC Configuration dialog box is as shown in Table 4-10.
Table 4-10 Shortcut Menu on PVC Configuration Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
4-117
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Close
Close All
Help
Observer
Unobserver
Get Status
4.6.9 Creating ATM and IP Binding Relation (ATM)

Abstract
This section describes how to configure the destination IP address corresponding to Iu-PS
interface.
Prerequisites
1.
2.
3.
4.
5.
6.

PVC Configuration to SGSN has been created.
Steps
1. On Configuration Resource Tree, right-click and choose ATM and IP Binding
Relation > Create > ATM and IP Binding Relation, as shown in Figure 4-157.
4-118
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-157 Selecting Create ATM and IP Binding Relation
2. ATM and IP Binding Relation dialogue box pops up, as shown in Figure 4-158.
Figure 4-158 ATM and IP Binding Relation Dialogue Box
4-119
SJ-20100603155704-024|2011-08-31 (R3.0)
3. Set parameters and click OK. The system has created ATM and IP Binding Relation.
End of Steps
Example
The example for configuring ATM and IP Binding Relation is as shown in Table 4-11.
Table 4-11 Example for ATM and IP Binding Relation
PVC ID
Destination IP Address
Address Mask
2101
10.8.47.2
255.255.255.255
Follow-Up Action
The shortcut menu on ATM and IP Binding Relation dialog box is as shown in Table 4-12.
Table 4-12 Shortcut Menu on ATM and IP Binding Relation Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
4.6.10 Creating Static Route (ATM)

Abstract
l
l
Configure the static route (the next hop type is IP) when the target IP and the interface
IP are not in the same network segment.
Configure the static route (the next hop type is Interface) when sending the data
through the interface without IP configurations.
Prerequisites
1. UTRAN Subnetwork has been created.
2. RNC Managed Element has been created.
4-120
SJ-20100603155704-024|2011-08-31 (R3.0)
3.
4.
5.
6.

Interface Configuration has been created.
Steps
1. On Configuration Resource Tree, right-click and choose Static Route > Create >
Static Route, as shown in Figure 4-159.
Figure 4-159 Selecting Create Static Route
2. Static Route dialog box pops up, as shown in Figure 4-160.
4-121
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-160 Static Route Dialog Box
The drop-down menu of Is next hop IP or interface include two options, IP and
Interface.
l
l
When the user selects IP, create Interface Configuration first.

When the user selects Interface, create Point to Point Port Configuration first.
3. Click OK and the system has created Static Route.

End of Steps
Follow-Up Action
The shortcut menu on Static Route dialog box is as shown in Table 4-13.
Table 4-13 Shortcut Menu on Static Route Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
4-122
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Close All
Help
4.7 Node B
4.7.1 Creating IMA Group (ATM)
Abstract
l
When connecting ATM office in E1 mode on IMAB/APBI+DTB, configure IMA/TC

group information on IMAP. With these configurations, IMA process creates IMA
group and TC group.
When connecting ATM office in CSTM-1 mode on IMAB+SDTB When connecting ATM
office in CSTM-1 mode on IMAB/APBI+SDTB, configure IMA/TC group information on
IMAP processor. With these configurations, IMA process creates IMA group and TC
group. IMA group and TC group bear over CSTM-1.
Prerequisites
1.
2.
3.
4.
5.
6.

Rack, Shelf, and Board (IMA) have been created.
Steps
1. On Configuration Resource Tree, right-click and choose IMA Group Configuration
> Create > IMA Group Configuration, as shown in Figure 4-161.
4-123
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-161 Selecting Create IMA Group Configuration
2. IMA Group Configuration dialog box pops up, as shown in Figure 4-162 and Figure
4-163.
Figure 4-162 IMA Group Configuration Dialog Box (Basic Configuration Tab)
4-124
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-163 IMA Group Configuration Dialog Box (IMA Set -1 Tab)
Note:
After Create Continually is selected, the system does not close IMA Group
Configuration dialog box immediately after IMA Group Configuration is created.
Users can create a new IMA Group Configuration on IMA Group Configuration
dialog box.
3. Set parameters and click OK. The system has created IMA Group Configuration.
End of Steps
Follow-Up Action
The shortcut menu on IMA Group Configuration dialog box is as shown in Table 4-14.
Table 4-14 Shortcut Menu on IMA Group Configuration Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
4-125
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Close
Close All
Help
Observer
Unobserver
Get Status
Inhibit
Uninhibit
Restart
4.7.2 Creating IMA Link (ATM)

Abstract
l
l
When connecting ATM office through IMA link on IMAB+DTB mode, configure the IMA
link in IMA/TC group.
When connecting ATM office in CSTM-1 mode on IMAB+SDTB, configure the IMA/TC
link in IMA/TC group (IMA link bears over CSTM-1).
Prerequisites
1.
2.
3.
4.
5.
6.
7.

Rack, Shelf, and Board (DTB/SDTB) have been created.
IMA Group Configuration has been created in IMA mode.
Steps
1. On Configuration Resource Tree, right-click and choose IMA Group Configuration
> Create > IMA Link Configuration, as shown in Figure 4-164.
4-126
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-164 Selecting Create IMA Link Configuration
2. Link Configuration dialog box pops up, as shown in Figure 4-165.
Figure 4-165 Link Configuration Dialog Box
4-127
SJ-20100603155704-024|2011-08-31 (R3.0)
3. Click OK and the system has created IMA Link Configuration.

End of Steps
Follow-Up Action
The shortcut menu on IMA Link Configuration dialog box is as shown in Table 4-15.
Table 4-15 Shortcut Menu on IMA Link Configuration Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
Observer
Unobserver
Get Status
Inhibit
Uninhibit
4.7.3 Creating Node B Path Group (ATM)

Abstract
4-128
SJ-20100603155704-024|2011-08-31 (R3.0)
Note:
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
4-129
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
Example
Note:
numbered uniformly.

Path Group ID
1000000
1000000
1000000
1000000
1000000
1000000
4-130
SJ-20100603155704-024|2011-08-31 (R3.0)
Path Group ID
1000000
1000000
Follow-Up Action
1. Transport path
c.
paths.

4-131
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
4.7.4 Creating Node B Office (ATM)

Abstract
This section describes how to create the basic information of Node B office.
Prerequisites
4-132
SJ-20100603155704-024|2011-08-31 (R3.0)
3. RNC Config Set has been created.

4. RNC Ground Resource Management has been created.
5. Rack, Shelf, and Board have been created.
Steps
Configuration > Create > Node B Office, as shown in Figure 4-169.
Figure 4-169 Selecting Create Node B Office
2. Node B Office dialog box pops up, as shown in Figure 4-170~Figure 4-177.
Figure 4-170 Node B Office Dialog Box (Basic Configuration)
4-133
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-171 Node B Office Dialog Box (Basic Config-1 Tab)
Figure 4-172 Node B Office Dialog Box (Node B Config Tab)
4-134
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-173 Node B Office Dialog Box (CN/RNC Common Config Tab)
Figure 4-174 Node B Office Dialog Box (RNC Config Tab)
4-135
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-175 Node B Office Dialog Box (CN Config-1 Tab)
4-136
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-177 Node B Office Dialog Box (BSC Config Tab)
3. Set parameters and click OK. The system has created Node B Office.
End of Steps
Follow-Up Action
The shortcut menu on Node B Office dialog box is as shown in Table 4-18.
Table 4-18 Shortcut Menu on Node B Office Dialog Box
Shortcut Menu
Description
Modify
Cancel
Close
Close All
Help
4-137
SJ-20100603155704-024|2011-08-31 (R3.0)
4.7.5 Modifying Node B Office (ATM)

Steps
1. On Configuration Resource Tree, the created Node B Office appears under NE
Figure 4-178 Created Node B Office
2. Double-click Node B Office and its information box pops up on the right, as shown in
Figure 4-179.
4-138
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-179 Node B Office Information Page
3. Click
on the shortcut menu and the Node B Office tab becomes editable.

information on Node B Office tab, as shown in Figure 4-180.
Figure 4-180 Modifying Information on Node B Office Dialog Box
4-139
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-181 Modified Node B Office
End of Steps
4.7.6 Creating Node B ATM Office (ATM)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Node B Office has been created.
Steps
1. On Node B Office interface, click ATM Office Configuration tab, as shown in Figure
4-182.
4-140
SJ-20100603155704-024|2011-08-31 (R3.0)
ATM address is unique in all network elements.

4-141
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4.7.7 Creating Node B Path (ATM)

Abstract
This section describes how to configure the information of the transport path. It includes the
transport path bear type, transport path ID, transport path group ID, and path bandwidth.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Node B Office interface, click Path Configuration tab, as shown in Figure 4-185.
4-142
SJ-20100603155704-024|2011-08-31 (R3.0)

l
l
ID is [32, 127].
Path ID is [0, 31].
4-143
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
4.7.8 Creating Node B AAL2 Path (ATM)

Abstract
This section describes how to configure AAL2 PATH information of the user data.
It includes the AAL2 Path ID, transport path ID that AAL2 path belongs to, Service type
that AAL2 path bears, etc.
Prerequisites
1.
2.
3.
4.
5.

4-144
SJ-20100603155704-024|2011-08-31 (R3.0)
6. Node B Office has been created.
Steps
1. On Node B Office interface, click AAL2 Path Configuration tab, as shown in Figure
4-188.
4-145
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
4.7.9 Creating Node B Signaling Link (ATM)

Abstract
This section describes how to configure Node B signaling links, including signaling link and
No.7 link.
belongs to.
Prerequisites
4-146
SJ-20100603155704-024|2011-08-31 (R3.0)
3.
4.
5.
6.

Steps
1. On the Node B Office interface, click the Signaling Link Configuration tab, as shown
in Figure 4-191.
4-147
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
4-148
SJ-20100603155704-024|2011-08-31 (R3.0)
4.7.10 Creating Node B Port (ATM)

Abstract
This section describes how to configure the information of Node B's port that the local RNC
manages.
There are two types of ports for the Node B.
l
Node B control port

It is on the RNC side. One and only one control port is obligatory to be configured for
one Node B.
Node B communication control port

It is on the RNC side. The communication control port is obligatory to be configured
for one Node B and at most five can be configured.
NBAP control plane protocol on the Iub interface is sent and received through the control
port and communication control port of the Node B.
Prerequisites
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Sigtran has been created.
SCTP Association Configuration has been created.
Steps
1. On Node B Office interface, click Node B Port Configuration tab, as shown in Figure
4-194.
4-149
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-194 Node B Port Configuration Tab
2. Set parameters on the Node B Port Configuration tab, as shown in Figure 4-195.
Figure 4-195 Setting Parameters on the Node B Port Configuration Tab

4-150
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 4-196 Created Node B Port Configuration

End of Steps
Example
The example of Node B Port Configuration is as shown in Table 4-19.
Table 4-19 Example of Node B Port Configuration
Node B
Port Type
Outgoing Flow ID
Signaling Link 1 ID
NCP USET_CTRL-
Communication Port
ID, unique in Node B
1000
PORT
1000
CCPUSET_COMPORT
Follow-Up Action
The shortcut menu on Node B Port Configuration dialog box is as shown in Table 4-20.
Table 4-20 Shortcut Menu on Node Port Configuration Dialog Box
Shortcut Menu
Description
Modify
4-151
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
Observer
Unobserver
Get Status
4-152
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 5
Configuring NE Information
(IP)
Table of Contents
Local Office ................................................................................................................5-1
Adjacent RNC Office ................................................................................................5-16
MSC.........................................................................................................................5-32
SGSN.......................................................................................................................5-48
Sigtran .....................................................................................................................5-64
Node B.....................................................................................................................5-82
Creating Static Route (IP).........................................................................................5-99
5.1 Local Office

5.1.1 Creating Local Office (IP)
Abstract
This section describes how to create the basic configuration information for the ZXWR
RNC local office.
Prerequisites
1.
2.
3.
4.
5.

Steps
Configuration > Create > Local Office, as shown in Figure 5-1.
5-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-1 Selecting Create Local Office
2. Local Office dialog box pops up, as shown in Figure 5-2~Figure 5-9.
Figure 5-2 Local Office Dialog Box (Basic Configuration Tab)
5-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 5 Configuring NE Information (IP)
Figure 5-3 Local Office Dialog Box (Basic Config-1 Tab)
Figure 5-4 Local Office Dialog Box (Node B Config tab)
5-3
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-5 Local Office Dialog Box (CN/RNC Common Config Tab)
Figure 5-6 Local Office Dialog Box (RNC Config Tab)
5-4
SJ-20100603155704-024|2011-08-31 (R3.0)
5-5
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-9 Local Office Dialog Box (BSC Config Tab)
3. Set parameters and then click OK. The system has created the Local Office
Note:
To delete the Local Office, make sure that no RNC radio resources are configured in
the current RNC configuration set.
End of Steps
Follow-Up Action
The shortcut menu on Local Office dialog box is as shown in Table 5-1.
Table 5-1 Shortcut Menu on Local Office Dialog Box
Shortcut Menu
Description
Modify
Cancel
Close
Close All
5-6
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
5.1.2 Creating RNC ATM Office (IP)

Abstract
This section describes how to configure the information ofAAL2 office, including ATM
address code plan, ATM address, whether the Q2630.2 protocol is supported, etc.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click ATM Office Configuration tab, as shown in Figure
5-10.
5-7
SJ-20100603155704-024|2011-08-31 (R3.0)

5-8
SJ-20100603155704-024|2011-08-31 (R3.0)
The button of Create Commit contains two states:

l
l
Create Commit: In this state, the user can create a new object.
Switch to Create: In this state, the user can not create a new object.
The button of Modify also contains two states:

l
l
Modify: In this state, the user can modify the information of the object.
Switch to Modify: In this state, the user can not modify the information of the
object.
The buttons of Create Commit and Modify can not exist in the same state. When the
user click the Create Commit button and it turns into the Create Commit state, the
button of Modify turns into the Switch to Modify automatically. Vice versa.
Note:
On NE Information Configuration, the relations of Create Commit and Modify
buttons of all nodes are same. Therefore, the manual does not describe any more.

End of Steps
5-9
SJ-20100603155704-024|2011-08-31 (R3.0)
5.1.3 Creating No. 7 Signaling (IP)

Abstract
This section describes how to configure the signal point type (STP/SEP/STEP) and link
test code of the local office.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click No.7 Signaling Configuration tab, as shown in
Figure 5-13.
Figure 5-13 No. 7 Signaling Configuration Tab
5-10
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the No.7 Signaling Configuration tab, as shown in Figure 5-14.
Figure 5-14 Setting Parameters on the No.7 Signaling Configuration Tab

Figure 5-15 Created No.7 Signaling Configuration

5-11
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
5.1.4 Configuring RNC Local Office Signaling Point (IP)

Abstract
This section describes how to configure the signaling point code of the local office, including
24-digit signaling point code and 14-digit signaling point code.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click Local Office Signaling Point Configuration tab, as
Figure 5-16 Local Office Signaling Point Configuration
5-12
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Local Office Signaling Point Configuration tab, as shown in
Figure 5-17.
Tab

Figure 5-18 Created Local Office Signaling Point Configuration

5-13
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
5.1.5 Creating RNC Local Office Subsystem No. (IP)

Abstract
This section describes how to configure the subsystem ID for the local office. The system
generates the ID automatically and the user does not need to create manually. If the ID is
deleted manually, configure as below.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Local Office interface, click Local Office Subsystem No. tab, as shown in Figure
5-19.
Figure 5-19 RNC Local Office Subsystem No. Tab
5-14
SJ-20100603155704-024|2011-08-31 (R3.0)
2. Set parameters on the Local Office Subsystem No. tab, as shown in Figure 5-20.
Figure 5-20 Setting Parameters on the Local Office Subsystem No. Tab

Figure 5-21 Created Local Office Subsystem No.
Local Office Subsystem No. is unique in the office.

5-15
SJ-20100603155704-024|2011-08-31 (R3.0)
End of Steps
5.2 Adjacent RNC Office

5.2.1 Creating Adjacent RNC Path Group (IP)
Abstract
Note:
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
5-16
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5-17
SJ-20100603155704-024|2011-08-31 (R3.0)
Example
Note:
numbered uniformly.

Path Group ID
1000000
1000000
1000000
1000000
1000000
1000000
1000000
1000000
Follow-Up Action
1. Transport path
5-18
SJ-20100603155704-024|2011-08-31 (R3.0)
c.
paths.

5-19
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
5.2.2 Creating Adjacent RNC Office (IP)

Abstract
This section describes how to create the basic information for the adjacent ZXWR RNC,
including ATM address, target signal point, office route, and signaling link.
Prerequisites
1.
2.
3.
4.
5.

Steps
Configuration > Create > Adjacent RNC Office, as shown in Figure 5-25.
5-20
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-25 Selecting Create Adjacent RNC Office
2. Adjacent RNC Office dialog box pops up, as shown in Figure 5-26~Figure 5-33.
Figure 5-26 Adjacent RNC office Dialog Box (Basic Configuration Tab)
not be 0.
5-21
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-27 Adjacent RNC Office Dialog Box (Basic Config-1 Tab
Figure 5-28 Adjacent RNC Office Dialog Box (Node B Config Tab)
5-22
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-29 Adjacent RNC Office Dialog Box (CN/RNC Common Config Tab)
Figure 5-30 Adjacent RNC Office Dialog Box (RNC Config Tab)
5-23
SJ-20100603155704-024|2011-08-31 (R3.0)
5-24
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-33 Adjacent RNC Office Dialog Box (BSC Config Tab)
3. Set parameters and click OK. The system has created the Adjacent RNC Office
End of Steps
Follow-Up Action
The shortcut menu on Adjacent RNC Office dialog box is as shown in Table 5-4.
Table 5-4 Shortcut Menu on Adjacent RNC Office Dialog Box
Shortcut Menu
Description
Modify
Cancel
Close
Close All
Help
5-25
SJ-20100603155704-024|2011-08-31 (R3.0)
5.2.3 Creating Path of Adjacent Office (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
5-34.
5-26
SJ-20100603155704-024|2011-08-31 (R3.0)

l
l
ID is [31, 127].
Path ID is [0, 31].
Records column, as shown in .
5-27
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.2.4 Creating Adjacent Office Signaling Point (IP)

Abstract
This section describes how to configure the signaling point code, signaling point coding
format, signaling point type of adjacent offices, and the connection mode of the local office.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Adjacent RNC Office interface, click Adjacent Office Signaling Point
Configuration tab, as shown in Figure 5-37.
5-28
SJ-20100603155704-024|2011-08-31 (R3.0)
in Figure 5-38.
Figure 5-38 Setting Parameters on the Adjacent Office Signaling Tab

5-29
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.2.5 Creating Adjacent Office Subsystem No. (IP)

Abstract
The system generates the ID automatically and the user does not need to create manually.
If the ID is deleted manually, configure as below.
Prerequisites
1.
2.
3.
4.
5.
6.

5-30
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On Adjacent RNC Office interface, click Adjacent Office Subsystem No. tab, as

5-31
SJ-20100603155704-024|2011-08-31 (R3.0)
Adjacent Office Subsystem No. is unique in the office.

End of Steps
5.3 MSC
5.3.1 Creating MSC Path Group (IP)
Abstract
Note:
5-32
SJ-20100603155704-024|2011-08-31 (R3.0)
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
5-33
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
Example
Note:
numbered uniformly.

Path Group ID
1000000
1000000
1000000
1000000
1000000
1000000
1000000
1000000
Follow-Up Action
1. Transport path
5-34
SJ-20100603155704-024|2011-08-31 (R3.0)
c.
paths.

5-35
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
5.3.2 Creating MSC Office (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.

Steps
5-36
SJ-20100603155704-024|2011-08-31 (R3.0)
not be 0.
5-37
SJ-20100603155704-024|2011-08-31 (R3.0)
5-38
SJ-20100603155704-024|2011-08-31 (R3.0)
5-39
SJ-20100603155704-024|2011-08-31 (R3.0)
5-40
SJ-20100603155704-024|2011-08-31 (R3.0)
ID must be 0.
End of Steps
Follow-Up Action
Shortcut Menu
Description
Modify
Cancel
Close
Close All
5-41
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
5.3.3 Creating MSC Path (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
5-55.
5-42
SJ-20100603155704-024|2011-08-31 (R3.0)

l
l
ID is [31, 127].
Path ID is [0, 31].
Group ID have same Home Module No..
5-43
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
5.3.4 Creating MSC Adjacent Office Signaling Point (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

5-44
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
in Figure 5-59.

Configuration Tab
5-45
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.3.5 Creating MSC Adjacent Office Subsystem No. (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

5-46
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
Figure 5-61.
2. Set parameters on the Adjacent Office Subsystem No. tab, as shown in Figure 5-62.

5-47
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.4 SGSN
5.4.1 Creating SGSN Path Group (IP)
Abstract
Note:
Prerequisites
5-48
SJ-20100603155704-024|2011-08-31 (R3.0)
2.
3.
4.
5.
6.

Steps
5-49
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
Example
Note:
numbered uniformly.

Path Group ID
1000000
1000000
1000000
1000000
1000000
1000000
1000000
1000000
Follow-Up Action
1. Transport path
5-50
SJ-20100603155704-024|2011-08-31 (R3.0)
c.
paths.

5-51
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
5.4.2 Creating SGSN Office (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.

Steps
5-52
SJ-20100603155704-024|2011-08-31 (R3.0)
not be 0.
5-53
SJ-20100603155704-024|2011-08-31 (R3.0)
5-54
SJ-20100603155704-024|2011-08-31 (R3.0)
5-55
SJ-20100603155704-024|2011-08-31 (R3.0)
5-56
SJ-20100603155704-024|2011-08-31 (R3.0)
ID must be 0.
End of Steps
Follow-Up Action
Shortcut Menu
Description
Modify
Cancel
Close
Close All
5-57
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
5.4.3 Creating SGSN Path (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
5-76.
5-58
SJ-20100603155704-024|2011-08-31 (R3.0)

l
l
ID is [31, 127].
Path ID is [0, 31].
5-59
SJ-20100603155704-024|2011-08-31 (R3.0)


End of Steps
5.4.4 Creating SGSN Adjacent Office Signaling Point (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

5-60
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
in Figure 5-80.

Configuration Tab
5-61
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.4.5 Creating SGSN Adjacent Office Subsystem No. (IP)

Abstract
Prerequisites
1.
2.
3.
4.
5.
6.

5-62
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On CN Office interface, click Adjacent Office Subsystem tab, as shown in Figure
5-82.

5-63
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.5 Sigtran
5.5.1 Creating Sigtran (IP)
Abstract
This section describes how to configure SCTP association configuration information
when BME connects with RNC in IP mode and the signaling is borne through the SCTP
association.
Note:
The system automatically creates Sigtran Configuration when creating RNC Ground
Resource Management. If Sigtran Configuration has existed, do not create again.
5-64
SJ-20100603155704-024|2011-08-31 (R3.0)
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Configuration Resource Tree, right-click and choose RNC Ground Resource
Management > Create > Sigtran Configuration, as shown in Figure 5-85.
Figure 5-85 Selecting Create Sigtran Configuration
2. Sigtran Configuration dialog box pops up, as shown in Figure 5-86.
Figure 5-86 Sigtran Configuration Dialogue Box
5-65
SJ-20100603155704-024|2011-08-31 (R3.0)
3. Set parameters and click OK. The system has created Sigtran Configuration.
End of Steps
Result
The system automatically creates the nodes of Sigtran Configuration after it is created
successfully, as shown in Figure 5-87.
Figure 5-87 Created Sigtran Configuration
Follow-Up Action
The shortcut menu on Sigtran Configuration dialog box is as shown in Table 5-11.
Table 5-11 Shortcut Menu on Sigtran Configuration Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Close
Close All
5-66
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Help
5.5.2 Creating SCTP Association (IP)

Abstract
This section describes how to create the SCTP association between RNC and BME when
RNC connects with BME in IP mode.
Prerequisites
1.
2.
3.
4.
5.
6.
7.
8.
9.

Signaling Link Configuration in the Adjacent RNC Office has been created.
The virtual IP address of RPU or RCB (SMP) has been configured in the interface
table.
Steps
1. On Configuration Resource Tree, right-click and choose SCTP Association
Configuration > Create > SCTP Association Configuration, as shown in Figure
5-88.
5-67
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-88 Selecting Create SCTP Association Configuration
2. SCTP Association Configuration dialog box pops up, as shown in Figure 5-89,
Figure 5-90, and Figure 5-91.
5-68
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-89 SCTP Association Configuration Dialog Box (Basic Configuration of

SCTP Association Tab)
l
l
Peer-end office of SCTP association corresponds to Signaling Link No. of

Signaling Link Configuration in the Adjacent RNC Office.
Application property of SCTP association is negotiated with the peer end of the
association. One end selects SERVER mode and the other end selects CLIENT
Mode.
5-69
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-90 SCTP Association Configuration Dialog Box (RTO Configuration of

SCTP Association Tab)
5-70
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-91 SCTP Association Configuration Dialog Box (IP Configuration of SCTP
Association Tab)
Fill in Local-end port No., Peer-end port No., Local-end IP Address 1 and
Peer-end IP Address 1 according to the planned data.
3. Click OK and the system has created SCTP Association Configuration.

End of Steps
Follow-Up Action
The shortcut menu on SCTP Association Configuration dialog box is as shown in Table
5-12.
Table 5-12 Shortcut Menu on SCTP Association Configuration Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Close
5-71
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Close All
Help
Get Status
Establish
Release
Stop All Association
Restart All Association
5.5.3 Creating ASP Configuration Information (IP)

Abstract
This section describes how to create the process information for the application server.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Configuration Resource Tree, right-click and choose SCTP Association
Configuration > Create > ASP Configuration Information, as shown in Figure
5-92.
5-72
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-92 Selecting Create ASP Configuration Information
2. ASP Configuration Information dialog box pops up, as shown in Figure 5-93.
Figure 5-93 ASP Configuration Information
3. Set parameters and click OK. The system has created ASP Configuration
Information.
End of Steps
5-73
SJ-20100603155704-024|2011-08-31 (R3.0)
Follow-Up Action
The shortcut menu on ASP Configuration Information dialog box is as shown in Table
5-13.
Table 5-13 Shortcut Menu on ASP Configuration Information Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Close
Close All
Help
5.5.4 Creating AS Static Information (IP)

Abstract
This section describes how to configure the basic information of the AS (Application
Server), including the ASP serving for this AS.
Prerequisites
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.

Interface has been created.
No.7 Signaling Point Configuration has been created.
No. 7 Office Signaling Configuration has been created.
ASP Configuration Information has been created.
Steps
1. On Configuration Resource Tree, right-click and choose AS Static Information >
Create > AS Static Information, as shown in Figure 5-94.
5-74
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-94 Selecting Create AS Static Information
2. AS Static Information dialog box pops up, as shown in Figure 5-95 and Figure 5-96.
5-75
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-95 AS Static Information Dialogue Box (AS Static Information 1 Tab)
5-76
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-96 AS Static Information Dialogue Box (AS Static Information 2 Tab)
3. Set parameters and click OK. The system has created AS Static Information.
End of Steps
Follow-Up Action
The shortcut menu on AS Static Information dialog box is as shown in Table 5-14.
Table 5-14 Shortcut Menu on AS Static Information Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Close
Close All
Help
Get Status
5-77
SJ-20100603155704-024|2011-08-31 (R3.0)
5.5.5 Creating Static Route Information of M3UA (IP)

Abstract
This section describes how to configure the static route information of M3UA.
Prerequisites
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

AS Static Information has been created.
Steps
1. On Configuration Resource Tree, right-click and choose Static Route Information
of M3UA > Create > Static Route Information of M3UA, as shown in Figure 5-97.
Figure 5-97 Selecting Static Route Information of M3UA
2. Static Route Information of M3UA dialog box pops up, as shown in Figure 5-98.
5-78
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-98 Static Route Information of M3UA Dialog Box
3. Srt parameters and click OK. The system has created Static Route Information of
M3UA.
End of Steps
Follow-Up Action
The shortcut menu on Static Route Information of M3UA dialog box is as shown in Table
5-15.
Table 5-15 Shortcut Menu on Static Route Information of M3UA Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Close
5-79
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Close All
Help
5.5.6 Creating Route Information of M3UA Multi-RK (IP)

Abstract
This section describes how to configure the route information of M3UA multi-RK.
Prerequisites
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Route Information of M3UA Multi-RK has been created.
Steps
1. On Configuration Resource Tree, right-click and choose Route Information of
M3UA Multi-RK > Create > Route Information of M3UA Multi-RK, as shown in
Figure 5-99.
5-80
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-99 Selecting Route Information of M3UA Multi-RK
2. Route Information of M3UA Multi-RK dialog box pops up, as shown in Figure 5-100.
Figure 5-100 Route Information of M3UA Multi-RK Dialog Box
3. Set parameters and click OK. The system has created Route Information of M3UA
Multi-RK.
End of Steps
Follow-Up Action
The shortcut menu on Route Information of M3UA Multi-RK dialog box is as shown in
Table 5-16.
5-81
SJ-20100603155704-024|2011-08-31 (R3.0)
Table 5-16 Shortcut Menu on Route Information of M3UA Multi-RK Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Close
Close All
Help
5.6 Node B
5.6.1 Creating Node B Path Group (IP)
Abstract
Note:
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
5-82
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5-83
SJ-20100603155704-024|2011-08-31 (R3.0)
Example
Note:
numbered uniformly.

Path Group ID
1000000
1000000
1000000
1000000
1000000
1000000
1000000
1000000
Follow-Up Action
1. Transport path
5-84
SJ-20100603155704-024|2011-08-31 (R3.0)
c.
paths.

5-85
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
Close All
Help
5.6.2 Creating Node B Office (IP)

Abstract
This section describes how to create the basic information of Node B office.
Prerequisites
1.
2.
3.
4.
5.

Steps
Configuration > Create > Node B Office, as shown in Figure 5-104.
5-86
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-104 Selecting Create Node B Office
2. Node B Office dialog box pops up, as shown in Figure 5-105~Figure 5-112.
Figure 5-105 Node B Office Dialog Box (Basic Configuration)
5-87
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-106 Node B Office Dialog Box (Basic Config-1 Tab)
Figure 5-107 Node B Office Dialog Box (Node B Config Tab)
5-88
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-108 Node B Office Dialog Box (CN/RNC Common Config Tab)
Figure 5-109 Node B Office Dialog Box (RNC Config Tab)
5-89
SJ-20100603155704-024|2011-08-31 (R3.0)
5-90
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-112 Node B Office Dialog Box (BSC Config Tab)
3. Set parameters and click OK. The system has created Node B Office.
End of Steps
Follow-Up Action
The shortcut menu on Node B Office dialog box is as shown in Table 5-19.
Table 5-19 Shortcut Menu on Node B Office Dialog Bpx
Shortcut Menu
Description
Modify
Cancel
Close
Close All
Help
5-91
SJ-20100603155704-024|2011-08-31 (R3.0)
5.6.3 Configuring Node B Path (IP)

Abstract
transport path bear type, transport path ID, transport path group ID, and path bandwidth,
etc.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Node B Office interface, click Path Configuration tab, as shown in Figure 5-113.
5-92
SJ-20100603155704-024|2011-08-31 (R3.0)

l
l
ID is [31, 127].
Path ID is [0, 31].
5-93
SJ-20100603155704-024|2011-08-31 (R3.0)

End of Steps
5.6.4 Configuring SCTP Resource Relation (IP)

Abstract
This section describes how to configure the SCTP association that belongs to this Node B.
Prerequisites
1.
2.
3.
4.
5.
6.
7.

SCTP Association Configuration has been created and the value of Protocol Type
of SCTP Association on the Basic Configuration of SCTP Association is NBAP.
5-94
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On Node B Office interface, click SCTP Resource Relation tab, as shown in Figure
5-116.
Figure 5-116 SCTP Resource Relation Tab
2. Set parameters on the SCTP Resource Relation tab, as shown in Figure 5-117.
Figure 5-117 Setting Parameters on the SCTP Resource Relation Tab

5-95
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-118 Created SCTP Resource Relation

End of Steps
5.6.5 Creating Node B Port (IP)

Abstract
This section describes how to configure the information of Node B's port that the local RNC
manages.
There are two types of ports for the Node B.
l
Node B control port

It is on the RNC side. One and only one control port is obligatory to be configured for
one Node B.
Node B communication control port

It is on the RNC side. The communication control port is obligatory to be configured
for one Node B and at most five can be configured.
NBAP control plane protocol on the Iub interface is sent and received through the control
port and communication control port of the Node B.
5-96
SJ-20100603155704-024|2011-08-31 (R3.0)
Prerequisites
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Steps
1. On Node B Office interface, click Node B Port Configuration tab, as shown in Figure
5-119.
Figure 5-119 Node B Port Configuration Tab
2. Set parameters on the Node B Port Configuration tab, as shown in Figure 5-120.
5-97
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-120 Setting Parameters on the Node B Port Configuration Tab

Figure 5-121 Created Node B Port Configuration

End of Steps
5-98
SJ-20100603155704-024|2011-08-31 (R3.0)
Example
The example of Node B Port Configuration is as shown in Table 5-20.
Table 5-20 Example of Node B Port Configuration
Node B
Port Type
Outgoing Flow ID
Signaling Link 1 ID
1000
NCPUSET_CTRLPORT
1000
CCPUSET_COMPORT
Communication Port
ID, unique in Node B
5.7 Creating Static Route (IP)

Abstract
l
l
Configure the static route (the next hop type is IP) when the target IP and the interface
IP are not in the same network segment.
Configure the static route (the next hop type is Interface) when sending the data
through the interface without IP configurations.
Prerequisites
1.
2.
3.
4.
5.
6.

Interface Configuration has been created.
Steps
1. On Configuration Resource Tree, right-click and choose Static Route > Create >
Static Route, as shown in Figure 5-122.
5-99
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-122 Selecting Create Static Route
2. Static Route dialog box pops up, as shown in Figure 5-123.
5-100
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 5-123 Static Route Dialog Box
The drop-down menu of Is next hop IP or interface include two options, IP and
Interface.
l
l
When the user selects IP, create Interface Configuration first.

When the user selects Interface, create Point to Point Port Configuration first.
3. Click OK and the system has created Static Route.

End of Steps
Follow-Up Action
The shortcut menu on Static Route dialog box is as shown in Table 5-21.
Table 5-21 Shortcut Menu on Static Route Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
Batch Save
Close
5-101
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Close All
Help
5-102
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 6
Configuring QoS
Table of Contents
Creating QoS Configuration........................................................................................6-1
Editing QoS Configuration ..........................................................................................6-3
Modifying Priority and Rate Segment Related QoS Configuration Parameter .............6-4
Modifying Basic Priority Configuration Information Advanced Parameter ....................6-6
Modifying Scheduling Priority Configuration Information Advanced Parameter ...........6-7
Modifying Application Priority Configuration Information Advanced Parameter .........6-10
Modifying Basic Priority Transport Bearer Type Advanced Parameter ......................6-11
Modifying Basic Priority Transport Reserved Bandwidth Advanced Parameter
(Interactive/Background Class).................................................................................6-13
Modifying Access Control related to Basic Priority ....................................................6-14
6.1 Creating QoS Configuration

Abstract
This section describes how to create parameters related to QoS information in the RNC.
Note:
The system automatically creates QoS Configuration when creating RNC Config Set. If
QoS Configuration has existed, do not create again.
Prerequisites
1.
2.
3.
4.
5.
6.

Steps
1. On Configuration Resource Tree, right-click and choose RNC Config Set > Create
> QoS Configuration, as shown in Figure 6-1.
6-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-1 Selecting Create QoS Configuration
2. QoS Configuration dialog box pops up, as shown in Figure 6-2.
Figure 6-2 QoS Configuration Dialog Box
3. Set parameters and click OK. The system has created the information.
End of Steps
6-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 6 Configuring QoS
Follow-Up Action
The shortcut menu on QoS Configuration dialog box is as shown in Table 6-1.
Table 6-1 Shortcut Menu on QoS Configuration Dialog Box
Shortcut Menu
Description
Close
Close All
Help
6.2 Editing QoS Configuration

Abstract
This section describes how to modify, add, or delete the created QoS Configuration.
Prerequisites
QoS Configuration has been created.
Steps
1. On Configuration Resource Tree, double-click and choose RNC Config Set > QoS
Configuration, and QoS Configuration tab pops up, as shown in Figure 6-3.
Figure 6-3 QoS Configuration Tab
End of Steps
6-3
SJ-20100603155704-024|2011-08-31 (R3.0)
6.3 Modifying Priority and Rate Segment Related QoS

Configuration Parameter
Steps
1. On QoS Configuration tab in editable state, click Check and Modify on the end
of the Priority and Rate Segment Related QoS Configuration column. QoS
Configuration interface pops up, as shown in Figure 6-4.
Figure 6-4 QoS Configuration Interface
2. QoS Configuration interface contains the following columns:

l ARP Segment Number
l THP Segment Number
l Basic Priority Segment Number
l Uplink Rate Adjustment Level Number
l Downlink Rate Adjustment Level Number
Click the drop-down menu of ARP Segment Number, THP Segment Number,
Basic Priority Segment Number, Uplink Rate Adjustment Level Number, and
6-4
SJ-20100603155704-024|2011-08-31 (R3.0)
Downlink Rate Adjustment Level Number and select the number of lines to display
the information.
3. Double-click the information of Upper Limit on any column and the drop-down menu
pops up, where users can modify the value, as shown in Figure 6-5.
Figure 6-5 Modifying Values on QoS Configuration Interface
Double-click Uplink Nominal Bit Rate (kbps) and Downlink Nominal Bit Rate
(kbps) on the Basic Priority Segment Number column. The drop-down menu pops
up, where users can modify the values.
4. Click OK and the system saves the modifications.
End of Steps
6-5
SJ-20100603155704-024|2011-08-31 (R3.0)
6.4 Modifying Basic Priority Configuration Information

Advanced Parameter
Steps
1. On QoS Configuration tab in editable state, click Check and Modify on the end of
the Basic Priority Configuration Information Advanced Parameter column. Basic
Priority Management interface pops up, as shown in Figure 6-6.
Figure 6-6 Basic Priority Management Interface
2. Double-click any information column on the Basic Priority Management interface and
the drop-down menu pops up, where users can modify the value, as shown in Figure
6-7.
6-6
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-7 Modify Values on Basic Priority Management Interface

End of Steps
6.5 Modifying Scheduling Priority Configuration

Information Advanced Parameter
Steps
the Scheduling Priority Configuration Information Advanced Parameter column.
Scheduling Priority Management interface pops up, as shown in Figure 6-8.
6-7
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-8 Scheduling Priority Management Interface
2. You can perform the following operations on the Scheduling Priority Management
interface.
l Modify
i.
Double-click any information column on the Scheduling Priority

Management interface and the drop-down menu pops up, where users can
modify the value, as shown in Figure 6-9.
6-8
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-9 Modifying Values on Scheduling Priority Management Interface
ii.
l
After modifying the information, click Save to save the modification.
Add
i.
On Scheduling Priority Management interface, click Add Index and the

Index Input dialog box pops up, as shown in Figure 6-10.
Figure 6-10 Index Input Dialog Box I
ii.
l
On the Index Input dialog box, input related parameters and the click OK.
The system has added the information.
Delete
i.
On Scheduling Priority Configuration Information Advanced Parameter

interface, click Delete Index and the Index Input dialog box pops up, as
6-9
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-11 Index Input Dialog Box II
End of Steps
6.6 Modifying Application Priority Configuration

Information Advanced Parameter
Steps
the Application Priority Configuration Information Advanced Parameter column.
Application Priority Configuration Information interface pops up, as shown in
Figure 6-12.
Figure 6-12 Application Priority Configuration Information Interface
2. Double-click any information column on the Application Priority Configuration

Information interface and the drop-down menu pops up, where users can modify the
value, as shown in Figure 6-13.
6-10
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-13 Modifying Values on Application Priority Configuration Information

Interface
3. Click Save and the system saves the modifications.

4. To add/delete a record, select the record index from the drop-down menu of the Add
or Delete Index frame. Then, click Save.
l If the selected index ID has already existed, the system deletes the information.
l If the selected index ID does not exist, the system adds the information.
End of Steps
6.7 Modifying Basic Priority Transport Bearer Type

Advanced Parameter
Steps
1. On QoS Configuration tab in editable state, click Check and Modify on the end of the
Basic Priority Transport Bearer Type Advanced Parameter column. Basic Priority
Transport Bearer Type interface pops up, as shown in Figure 6-14.
6-11
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-14 Basic Priority Transport Bearer Type Interface
2. Double-click any information column on the Basic Priority Transport Bearer Type
interface and the drop-down menu pops up, where users can modify the value, as
Figure 6-15 Modifying Values on Basic Priority Transport Bearer Type Interface

4. To add/delete a record, select the record index from the drop-down menu of the Basic
Priority Transport Bearer Type Advanced Parameter column and then click OK.
End of Steps
6-12
SJ-20100603155704-024|2011-08-31 (R3.0)
6.8 Modifying Basic Priority Transport

Reserved Bandwidth Advanced Parameter
(Interactive/Background Class)
Steps
1. On QoS Configuration tab in editable state, click Check and Modify on the end
of the Basic Priority Transport Reserved Bandwidth Advanced Parameter
(Interactive/Background Class) column.
Basic Priority Transport Reserved
Bandwidth interface pops up, as shown in Figure 6-16.
Figure 6-16 Basic Priority Transport Reserved Bandwidth Interface
2. Double-click any information column on the Basic Priority Transport Reserved

Bandwidth (Interactive/Background Class) interface and the drop-down menu pops
up, where users can modify the value, as shown in Figure 6-17.
6-13
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-17 Modifying Values on Basic Priority Transport Reserved Bandwidth

Interface

4. To add/delete a record, select the record index from the drop-down menu of the Add
or Delete Index frame. Then, click OK.
End of Steps
6.9 Modifying Access Control related to Basic Priority

Steps
the Access Control related to Basic Priority column. Access Control related to
Basic Priority interface pops up, as shown in Figure 6-18.
6-14
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-18 Access Control related to Basic Priority Interface
2. You can perform the following operations on the Access Control related to Basic
Priority interface.
l Modify
i.
Double-click any information column on the Access Control related to Basic

Priority interface and the drop-down menu pops up, where users can modify
the value, as shown in Figure 6-19.
Figure 6-19 Modifying Values on Access Control related to Basic Priority
Interface
After modifying the information, click Save to save the modification.

l
Add
i.
On Access Control related to Basic Priority interface, click Add Index and
the Index Input dialog box pops up, as shown in Figure 6-20.
6-15
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 6-20 Index Input Dialog Box I
ii.
l
The system has added the information.
Delete
i.
On Access Control related to Basic Priority interface, click Delete Index

and the Index Input dialog box pops up, as shown in Figure 6-21.
Figure 6-21 Index Input Dialog Box II
ii.
The system has deleted all records that meet the requirements.
End of Steps
6-16
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 7
Setting Alarm Parameters

Table of Contents
Creating CLKG Board Alarm Parameters ...................................................................7-1
Creating CLKG (ICM) Board Alarm Parameters..........................................................7-4
Creating Power Board Alarm Parameters ...................................................................7-7
Creating MPX86/2 Alarm Parameters.......................................................................7-13
7.1 Creating CLKG Board Alarm Parameters

Abstract
This section describes how to set CLKG board alarm parameters after creating CLKG
board.
CLKG board can contain several clock bases, including one master clock base and several
standby clock bases. Users can manually switch between the master and slave clock
base.
1. Set the master clock base.
2. Set the standby clock base.
3. Set whether to give alarms and whether to shield the alarms when the master clock
base is lost.
4. Set whether to give alarms and whether to shield the alarm when other standby clock
base is lost.
Note:
After a CLKG board is created, the network management system creates CLKG Board
Alarm Parameters automatically. If the CLKG Board Alarm Parameters exist, they will
not be created repeatedly.
Prerequisites
1.
2.
3.
4.
5.

Rack, Shelf, and Board (CLKG) have been created.
7-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. On Configuration Resource Tree, right-click and choose Alarm Setting > Create >
CLKG Board Alarm Parameters, as shown in Figure 7-1.
Figure 7-1 Selecting CLKG Board Alarm Parameters
2. CLKG Board Alarm Parameters dialog box pops up, as shown in Figure 7-2.
7-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Chapter 7 Setting Alarm Parameters
Figure 7-2 CLKG Board Alarm Parameters Dialog Box
End of Steps
Follow-Up Action
The shortcut menu on CLKG Board Alarm Parameters dialog box is as shown in Table
7-1.
Table 7-1 Shortcut Menu on CLKG Board Alarm Parameters Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
7-3
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Batch Modify
Batch Save
Close
Close All
Help
7.2 Creating CLKG (ICM) Board Alarm Parameters

Abstract
This section describes how to set ICMG board alarm parameters after creating ICMG
board.
ICMG board can contain several clock bases, including one master clock base and several
standby clock bases. Users can manually switch between the master and slave clock
base.
1. Set the master clock base.
2. Set the standby clock base.
3. Set whether to give alarms and whether to shield the alarms when the master clock
base is lost.
4. Set whether to give alarms and whether to shield the alarm when other standby clock
base is lost.
Note:
After an ICM board is created, the network management system creates CLKG (ICM)
Board Alarm Parameters automatically. If the CLKG (ICM) Board Alarm Parameters
exist, they will not be created repeatedly.
Prerequisites
1.
2.
3.
4.
5.

Rack, Shelf, and Board (CLKG (ICM)) have been created.
7-4
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
CLKG (ICM) Board Alarm Parameters, as shown in Figure 7-3.
Figure 7-3 Selecting Create CLKG (ICM) Board Alarm Parameters
2. CLKG (ICM) Board Alarm Parameters dialog box pops up, as shown in Figure 7-4.
7-5
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-4 CLKG (ICM) Board Alarm Parameters Dialog Box
End of Steps
Follow-Up Action
The shortcut menu on CLKG (ICM) Board Alarm Parameters dialog box is as shown in
Table 7-2.
Table 7-2 Shortcut Menu on CLKG (ICM) Board Alarm Parameters Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
7-6
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Batch Modify
Batch Save
Close
Close All
Help
7.3 Creating Power Board Alarm Parameters

Abstract
This section describes how to set the threshold for the power supply, voltage, temperature,
humidity, door access, and rack fans alarms, and to set whether to shield the alarms.
Prerequisites
1.
2.
3.
4.
5.
6.

Rack has been created.
Get known of the actual cases of power board, fans, door access, and power supply.
Note:
After the RNC Ground Resource Management is created, the network management
system creates Power Board Alarm Parameters automatically. If the Power Board
Alarm Parameters exist, they will not be created repeatedly.
Steps
Power Board Alarm Parameters, as shown in Figure 7-5.
7-7
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-5 Selecting Create Power Board Alarm Parameters
2. Click Power Board Alarm Parameters and Power Board Alarm Parameters dialog
box pops up. Choose Power Board Configuration, Fans Configuration, Door
Access Configuration, and Power Configuration tabs to view information, as
shown in Figure 7-6 ~ Figure 7-9.
7-8
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-6 Power Board Alarm Parameters Dialog Box (Power Board Configuration
Tab)
7-9
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-7 Power Board Alarm Parameters Dialog Box (Fans Configuration Tab)
7-10
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-8 Power Board Alarm Parameters Dialog Box (Door Access Configuration
Tab)
7-11
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-9 Power Board Alarm Parameters Dialog Box (Power Config Tab)
End of Steps
Follow-Up Action
The shortcut menu on Power Board Alarm Parameters dialog box is as shown in Table
7-3.
Table 7-3 Shortcut Menu on Power Board Alarm Parameters Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
7-12
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Batch Modify
Batch Save
Close
Close All
Help
7.4 Creating MPX86/2 Alarm Parameters

Abstract
This section describes how to set the alarm parameters of OMP board.
Prerequisites
1.
2.
3.
4.
5.

Rack, Shelf, and Board (OMP) have been created.
Note:
After the RNC Ground Resource Management is created, the network management
system creates MPX86/2 Alarm Parameters automatically. If the MPX86/2 Board Alarm
Parameters exist, they will not be created repeatedly.
Steps
MPX86/2 Alarm Parameters, as shown in Figure 7-10.
7-13
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-10 Selecting Create MPX86/2 Alarm Parameters
2. MPX86/2 Alarm Parameters dialog box pops up, as shown in Figure 7-11.
7-14
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure 7-11 MPX86/2 Alarm Parameters Dialog Box
End of Steps
Follow-Up Action
The shortcut menu on MPX86/2 Alarm Parameters dialog box is as shown in Table 7-4.
Table 7-4 Shortcut Menu on MPX86/2 Alarm Parameters Dialog Box
Shortcut Menu
Description
Modify
Cancel
Save
Batch Modify
7-15
SJ-20100603155704-024|2011-08-31 (R3.0)
Shortcut Menu
Description
Batch Save
Close
Close All
Help
7-16
SJ-20100603155704-024|2011-08-31 (R3.0)
Appendix A
Common Configuration
Management Operations
Table of Contents
Starting the NetNumen M31 Client ...................................................................... A-1
Creating an NE Agent............................................................................................. A-3
Starting an NE Agent .............................................................................................. A-5
Synchronizing the Configuration Data..................................................................... A-7
Starting the NE Management.................................................................................. A-9
Opening the Configuration Management View ...................................................... A-10
A.1 Starting the NetNumen M31 Client

Abstract
This section describes how to start the NetNumen M31 client.
Prerequisites
The NetNumen M31 server and client have been installed and the server is properly
running.
Steps
1. In the Windows operating system, select Start > All Programs > NetNumen Unified
Management System > NetNumen Client, as shown in Figure A-1.
A-1
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure A-1 Starting the NetNumen M31 Client
The Login dialog box opens, as shown in Figure A-2.

Figure A-2 Login Window
2. Type the user name, password, and the server address, and then click OK.
End of Steps
A-2
SJ-20100603155704-024|2011-08-31 (R3.0)
Appendix A Common Configuration Management Operations
Result
After successful login, the client window appears with the Topology Management view
displayed, as shown in Figure A-3.
Figure A-3 Client Window
A.2 Creating an NE Agent

Abstract
This section describes how to create an Network Element (NE) agent.
An NE agent is an adaptation layer between the NetNumenM31 and the actual device.
Through the NE agent, the NetNumenM31 is connected to the NE for configuration
operations.
Prerequisites
l
l
The NE agent server is running properly.

The Topology Management view is open in the NetNumenM31 client window.
Steps
1. In the NE Tree pane, right-click the root node, and then select Create Object >
WCDMA Product > WCDMA NE Agent, as shown in Figure A-4.
A-3
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure A-4 Creating an NE Agent
The Create WCDMA OMM dialog box opens, as shown in Figure A-5.
Figure A-5 Create WCDMA OMM Dialog Box (Basic Attributes)
2. On the Basic attributes tab page, set the name and the IP address for the NE agent.
The other parameters are optional.
3. Click the Extended attributes tab, and then set the port and FTP port to be used, as
shown in Figure A-6.
A-4
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure A-6 Create WCDMA OMM Dialog Box (Extended Attributes)
4. Click OK.
End of Steps
A.3 Starting an NE Agent

Abstract
This section describes how to start an NE agent.
An NE agent is an adaptation layer between the NetNumenM31 and the actual device.
Through the NE agent, the NetNumenM31 is connected to the NE for configuration
operations.
Prerequisites
l
l
l
The NE agent server is running properly.

The NE agent has been created.
A-5
SJ-20100603155704-024|2011-08-31 (R3.0)
Steps
1. In the NE Tree pane, right-click the NE agent, and then click Start, as shown in Figure
A-7.
Figure A-7 Starting an NE Agent
End of Steps
Result
The NE agent can be managed by the NetNumenM31 system after it is successfully
started. At the same time, the system automatically synchronizes the configuration data
and alarm data from the NE agent, and then updates the status and icon of the NE agent
in the topology map.
A-6
SJ-20100603155704-024|2011-08-31 (R3.0)
A.4 Synchronizing the Configuration Data

Abstract
This section describes how to synchronize the configuration data from the
NetNumenM31 server to the client.
Prerequisites
l
l
The NE agent has been started.

Steps
1. In the NE Tree pane, right-click the NE agent, and then click Configuration
synchronization, as shown in Figure A-8.
A-7
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure A-8 Configuration Synchronization
2. Click Yes when the system prompts that the configuration synchronization will last for
a period of time.
End of Steps
A-8
SJ-20100603155704-024|2011-08-31 (R3.0)
A.5 Starting the NE Management

Abstract
This section describes how to start the NE management. The NetNumenM31 system
enables the configuration management functions only after the NE management is started.
Prerequisites
l
l

Steps
1. In the NE Tree pane, right-click the NE agent, and then select NE Management >
Start NE Management, as shown in Figure A-9.
Figure A-9 Starting the NE Management
End of Steps
Result
After a success message appears in the message bar, some new functional options are
added on the NE Management menu of the NE agent, as shown in Figure A-10.
A-9
SJ-20100603155704-024|2011-08-31 (R3.0)
Figure A-10 NE Management Menu of A Started NE
Note:
NE Management does not appear on the shortcut menu immediately after the NE agent
is started. This menu item is added on the shortcut menu only after you right-click the NE
agent and the upload of the NE management module is completed. You can check the
uploading process in the message pane.
A.6 Opening the Configuration Management View

Abstract
This section describes how to open the Configuration Management view.
Prerequisites
l
l

Steps
1. In the NE Tree pane, right-click the NE agent, and then select NE Management >
Configuration Management.
End of Steps
A-10
SJ-20100603155704-024|2011-08-31 (R3.0)
Result
The Configuration Management view opens in the client window, as shown in Figure
A-11.
Figure A-11 Configuration Management View
Note:
Users must obtain the Mutex right on a managed element before performing configuration
operations in the NetNumenM31 system. For how to apply for the Mutex right, refer to
ZXWR RNC (V3.09.30) Radio Network Controller Configuration Tool Operation Guide.
A-11
SJ-20100603155704-024|2011-08-31 (R3.0)
This page intentionally left blank.
A-12
SJ-20100603155704-024|2011-08-31 (R3.0)
Figures
Figure 1-1 Flow for RNC Ground Resource Configuration......................................... 1-2
Figure 2-1 Flow for the Public Resource Configuration.............................................. 2-2
Figure 2-2 UTRAN Subnetwork................................................................................. 2-3
Figure 2-3 RNC Managed Element ........................................................................... 2-3
Figure 2-4 RNC Config Set ....................................................................................... 2-5
Figure 2-5 RNC Ground Resource Management ...................................................... 2-6
Figure 2-6 The RNC Ground Resource Management Node and the Subnodes ........... 2-7
Figure 2-7 Global Supplemented Configuration......................................................... 2-8
Figure 3-1 Flow for the Hardware Resource Configuration ........................................ 3-2
Figure 3-2 Rack ........................................................................................................ 3-3
Figure 3-3 The Created Rack.................................................................................... 3-4
Figure 3-4 Creating a Shelf ....................................................................................... 3-5
Figure 3-5 Shelf ........................................................................................................ 3-5
Figure 3-6 Creating a Board...................................................................................... 3-6
Figure 3-7 Board....................................................................................................... 3-7
Figure 3-8 An Example of Board Configuration ......................................................... 3-9
Figure 3-9 Board..................................................................................................... 3-11
Figure 3-10 Unit Connection ................................................................................... 3-12
Figure 3-11 Show Board Properties Page ............................................................... 3-12
Figure 3-12 Unit Connection ................................................................................... 3-13
Figure 3-13 Choice of Interface Information ............................................................ 3-14
Figure 3-14 Interface Configuration......................................................................... 3-15
Figure 3-15 Warning ............................................................................................... 3-16
Figure 3-16 Service IP for DSP ............................................................................... 3-17
Figure 3-17 Choose Service IP ............................................................................... 3-18
Figure 3-18 The Batch Create is Successful ........................................................... 3-19
Figure 4-1 Transmission Interfaces Between RNC and Other NEs............................ 4-1
Figure 4-2 Selecting Create Local Office................................................................... 4-3
Figure 4-3 Local Office Dialog Box (Basic Configuration Tab) ................................... 4-4
Figure 4-4 Local Office Dialog Box (Basic Config-1 Tab) ........................................... 4-4
Figure 4-5 Local Office Dialog Box (Node B Config tab)............................................ 4-5
Figure 4-6 Local Office Dialog Box (CN/RNC Common Config Tab) .......................... 4-5
I
Figure 4-7 Local Office Dialog Box (RNC Config Tab) ............................................... 4-6
Figure 4-8 Local Office Dialog Box (CN Config-1 Tab)............................................... 4-6
Figure 4-10 Local Office Dialog Box (BSC Config Tab).............................................. 4-7
Figure 4-11 Created Local Office............................................................................... 4-9
Figure 4-12 Local Office Information Page .............................................................. 4-10
Figure 4-13 Modifying Information on Local Office Dialog Box ................................ 4-11
Figure 4-14 Modified Local Office ........................................................................... 4-12
Figure 4-15 ATM Office Configuration Tab............................................................... 4-13
Figure 4-16 Setting Parameters on the ATM Office Configuration Tab ..................... 4-13
Figure 4-17 Created ATM Office Configuration........................................................ 4-14
Figure 4-18 No. 7 Signaling Configuration Tab........................................................ 4-15
Figure 4-19 Setting Parameters on the No.7 Signaling Configuration Tab ............... 4-16
Figure 4-20 Created No.7 Signaling Configuration .................................................. 4-16
Figure 4-21 Local Office Signaling Point Configuration Tab ..................................... 4-17
Tab ....................................................................................................... 4-18
Figure 4-23 Created Local Office Signaling Point Configuration .............................. 4-18
Figure 4-24 Local Office Subsystem No. Tab .......................................................... 4-19
Figure 4-25 Setting Parameters on the Local Office Subsystem No. Tab ................ 4-20
Figure 4-26 Created Local Office Subsystem No. .................................................. 4-20
Figure 4-27 Selecting Create Path Group Configuration.......................................... 4-22
Figure 4-28 Path Group Configuration Dialogue Box............................................... 4-22
Figure 4-29 Transmission Form and Path Definition................................................ 4-24
Figure 4-30 Selecting Create Adjacent RNC Office ................................................. 4-26
Figure 4-31 Adjacent RNC office Dialog Box (Basic Configuration Tab) .................. 4-27
Figure 4-32 Adjacent RNC Office Dialog Box (Basic Config-1 Tab .......................... 4-27
Figure 4-33 Adjacent RNC Office Dialog Box (Node B Config Tab) ......................... 4-28
Figure 4-34 Adjacent RNC Office Dialog Box (CN/RNC Common Config
Tab) ...................................................................................................... 4-28
Figure 4-35 Adjacent RNC Office Dialog Box (RNC Config Tab) ............................. 4-29
Figure 4-36 Adjacent RNC Office Dialog Box (CN Config-1 Tab)............................. 4-29
Figure 4-38 Adjacent RNC Office Dialog Box (BSC Config Tab).............................. 4-30
Figure 4-39 Created Adjacent RNC Office .............................................................. 4-32
Figure 4-40 Adjacent RNC Office Information Page ................................................ 4-33
II
Figures
Figure 4-41 Modifying Information on Adjacent RNC Office Dialog Box................... 4-33
Figure 4-42 Modified Adjacent RNC Office.............................................................. 4-34
Figure 4-46 Path Configuration Tab ........................................................................ 4-37
Figure 4-47 Setting Parameters on the Path Configuration Tab ............................... 4-37
Figure 4-48 Created Path Configuration.................................................................. 4-38
Figure 4-49 AAL2 Path Configuration Tab ............................................................... 4-39
Figure 4-50 Setting Parameters on the AAL2 Path Configuration Tab ..................... 4-40
Figure 4-51 Created AAL2 Path Configuration ........................................................ 4-40
Figure 4-52 Shortcut Menu of AAL Path Configuration ............................................ 4-41
Figure 4-53 Adjacent Office Signaling Point Configuration Tab................................ 4-42
Configuration Tab.................................................................................. 4-43
Figure 4-55 Created Adjacent Office Signaling Point Configuration ......................... 4-43
Figure 4-56 Signaling Link Configuration Tab .......................................................... 4-44
Figure 4-57 Setting Parameters on the Signaling Link Configuration Tab ................ 4-45
Figure 4-58 Created Signaling Link Configuration ................................................... 4-45
Figure 4-59 Signaling Link Route Tab ..................................................................... 4-46
Figure 4-60 Setting Parameters on the Signaling Link Route Tab............................ 4-47
Figure 4-61 Created Signaling Link Route............................................................... 4-47
Figure 4-62 Office Route Tab .................................................................................. 4-49
Figure 4-63 Setting Parameters on the Office Route Tab ........................................ 4-49
Figure 4-64 Created Office Route ........................................................................... 4-50
Figure 4-65 Adjacent Office Subsystem No. Tab..................................................... 4-51
Figure 4-66 Setting Parameters on the Adjacent Office Subsystem No. Tab ........... 4-51
Figure 4-67 Created Adjacent Office Subsystem No. .............................................. 4-52
Figure 4-71 Selecting Create CN Office .................................................................. 4-57
Figure 4-72 CN Office Dialog Box (Basic Configuration Tab)................................... 4-57
Figure 4-73 CN Office Dialog Box (Basic Config-1 Tab) .......................................... 4-58
Figure 4-74 CN Office Dialog Box (Node B Config Tab) .......................................... 4-58
Figure 4-75 CN Office Dialog Box (CN/RNC Common Config Tab) ......................... 4-59
III
Figure 4-76 CN Office Dialog Box (RNC Config Tab)............................................... 4-59

Figure 4-77 CN Office Dialog Box (CN Config-1 Tab) .............................................. 4-60
Figure 4-79 CN Office Dialog Box (BSC Config Tab) ............................................... 4-61
Figure 4-80 Created CN Office................................................................................ 4-62
Figure 4-81 CN Office Information Page ................................................................. 4-63
Figure 4-82 Modifying Information on CN Office Dialog Box.................................... 4-64
Figure 4-83 Modified CN Office............................................................................... 4-64
Figure 4-90 AAL2 Path Configuration Tab ............................................................... 4-70
Figure 4-91 Setting Parameters on the AAL2 Path Configuration Tab ..................... 4-71
Figure 4-92 Created AAL2 Path Configuration ........................................................ 4-71
Figure 4-96 Signaling Link Configuration Tab .......................................................... 4-74
Figure 4-97 Setting Parameters on the Signaling Link Configuration Tab ................ 4-75
Figure 4-98 Created Signaling Link Configuration ................................................... 4-75
Figure 4-99 Signaling Link Route Tab ..................................................................... 4-77
Figure 4-100 Setting Parameters on the Signaling Link Route Tab.......................... 4-77
Figure 4-101 Created Signaling Link Route............................................................. 4-78
Figure 4-102 Office Route Tab ................................................................................ 4-79
Figure 4-103 Setting Parameters on the Office Route Tab....................................... 4-79
Figure 4-104 Created Office Route ......................................................................... 4-80
Figure 4-105 Adjacent Office Subsystem No. Tab................................................... 4-81
Figure 4-106 Setting Parameters on the Adjacent Office Subsystem No.
Tab ....................................................................................................... 4-81
Figure 4-107 Created Adjacent Office Subsystem No. ............................................ 4-82
Figure 4-108 Selecting Create CN Office ................................................................ 4-83
Figure 4-109 CN Office Dialog Box (Basic Configuration Tab) ................................. 4-83
IV
Figures
Figure 4-110 CN Office Dialog Box (Basic Config-1 Tab)......................................... 4-84

Figure 4-111 CN Office Dialog Box (Node B Config Tab) ......................................... 4-84
Figure 4-112 CN Office Dialog Box (CN/RNC Common Config Tab)........................ 4-85
Figure 4-113 CN Office Dialog Box (RNC Config Tab)............................................. 4-85
Figure 4-114 CN Office Dialog Box (CN Config-1 Tab) ............................................ 4-86
Figure 4-116 CN Office Dialog Box (BSC Config Tab) ............................................. 4-87
Figure 4-117 Adjacent Office Signaling Point Configuration Tab .............................. 4-89
Figure 4-119 Created Adjacent Office Signaling Point Configuration ....................... 4-90
Figure 4-120 Office Route Tab ................................................................................ 4-91
Figure 4-121 Setting Parameters on the Office Route Tab....................................... 4-91
Figure 4-122 Created Office Route ......................................................................... 4-92
Figure 4-123 Adjacent Office Subsystem No. Tab................................................... 4-93
Tab ....................................................................................................... 4-93
Figure 4-125 Created Adjacent Office Subsystem No. ............................................ 4-94
Figure 4-126 Selecting Create CN Office ................................................................ 4-95
Figure 4-127 CN Office Dialog Box (Basic Configuration Tab) ................................. 4-95
Figure 4-128 CN Office Dialog Box (Basic Config-1 Tab) ........................................ 4-96
Figure 4-129 CN Office Dialog Box (Node B Config Tab) ........................................ 4-96
Figure 4-130 CN Office Dialog Box (CN/RNC Common Config Tab) ....................... 4-97
Figure 4-131 CN Office Dialog Box (RNC Config Tab)............................................. 4-97
Figure 4-134 CN Office Dialog Box (BSC Config Tab) ............................................. 4-99
Figure 4-135 ATM Office Configuration Tab........................................................... 4-101
Figure 4-136 Setting Parameters on the ATM Office Configuration Tab ................. 4-101
Figure 4-137 Created ATM Office Configuration.................................................... 4-102
Figure 4-138 Adjacent Office Signaling Point Configuration Tab............................ 4-103
Configuration Tab................................................................................ 4-103
Figure 4-140 Created Adjacent Office Signaling Point Configuration ..................... 4-104
Figure 4-141 Signaling Link Configuration Tab ...................................................... 4-105
Figure 4-142 Setting Parameters on the Signaling Link Configuration Tab ............ 4-105
Figure 4-143 Created Signaling Link Configuration ............................................... 4-106

Figure 4-144 Signaling Link Route Tab ................................................................. 4-107
Figure 4-145 Setting Parameters on the Signaling Link Route Tab........................ 4-108
Figure 4-146 Created Signaling Link Route........................................................... 4-108
Figure 4-147 Office Route Tab .............................................................................. 4-109
Figure 4-148 Setting Parameters on the Office Route Tab..................................... 4-110
Figure 4-149 Created Office Route ....................................................................... 4-110
Figure 4-150 Adjacent Office Subsystem No. Tab..................................................4-111
Tab ..................................................................................................... 4-112
Figure 4-152 Created Adjacent Office Subsystem No. .......................................... 4-112
Figure 4-153 Selecting Create PVC Configuration ................................................ 4-114
Figure 4-154 PVC Configuration Dialog Box (Basic Configuration Tab) ................. 4-115
Figure 4-155 PVC Configuration Dialog Box (PVC Config-1 Tab) .......................... 4-116
Figure 4-156 PVC Configuration Dialog Box (PVC Config-2 Tab) .......................... 4-117
Figure 4-157 Selecting Create ATM and IP Binding Relation................................. 4-119
Figure 4-158 ATM and IP Binding Relation Dialogue Box...................................... 4-119
Figure 4-159 Selecting Create Static Route .......................................................... 4-121
Figure 4-160 Static Route Dialog Box ................................................................... 4-122
Figure 4-161 Selecting Create IMA Group Configuration....................................... 4-124
Figure 4-162 IMA Group Configuration Dialog Box (Basic Configuration
Tab) .................................................................................................... 4-124
Figure 4-163 IMA Group Configuration Dialog Box (IMA Set -1 Tab) ..................... 4-125
Figure 4-164 Selecting Create IMA Link Configuration .......................................... 4-127
Figure 4-165 Link Configuration Dialog Box .......................................................... 4-127
Figure 4-166 Selecting Create Path Group Configuration...................................... 4-129
Figure 4-167 Path Group Configuration Dialogue Box........................................... 4-130
Figure 4-168 Transmission Form and Path Definition............................................ 4-131
Figure 4-169 Selecting Create Node B Office........................................................ 4-133
Figure 4-170 Node B Office Dialog Box (Basic Configuration) ............................... 4-133
Figure 4-171 Node B Office Dialog Box (Basic Config-1 Tab) ................................ 4-134
Figure 4-172 Node B Office Dialog Box (Node B Config Tab) ................................ 4-134
Figure 4-173 Node B Office Dialog Box (CN/RNC Common Config Tab)............... 4-135
Figure 4-174 Node B Office Dialog Box (RNC Config Tab) .................................... 4-135
Figure 4-175 Node B Office Dialog Box (CN Config-1 Tab) ................................... 4-136
Figure 4-176 Node B Office Dialog Box (CN Config-2 Tab) ................................... 4-136
VI
Figures
Figure 4-177 Node B Office Dialog Box (BSC Config Tab) .................................... 4-137
Figure 4-178 Created Node B Office ..................................................................... 4-138
Figure 4-179 Node B Office Information Page....................................................... 4-139
Figure 4-180 Modifying Information on Node B Office Dialog Box ......................... 4-139
Figure 4-181 Modified Node B Office .................................................................... 4-140
Figure 4-182 ATM Office Configuration Tab........................................................... 4-141
Figure 4-183 Setting Parameters on the ATM Office Configuration Tab ................. 4-141
Figure 4-184 Created ATM Office Configuration.................................................... 4-142
Figure 4-185 Path Configuration Tab..................................................................... 4-143
Figure 4-186 Setting Parameters on the Path Configuration Tab ........................... 4-143
Figure 4-187 Created Path Configuration.............................................................. 4-144
Figure 4-188 AAL2 Path Configuration Tab ........................................................... 4-145
Figure 4-189 Setting Parameters on the AAL2 Path Configuration Tab ................. 4-145
Figure 4-190 Created AAL2 Path Configuration .................................................... 4-146
Figure 4-191 Signaling Link Configuration Tab ...................................................... 4-147
Figure 4-192 Setting Parameters on the Signaling Link Configuration Tab ............ 4-148
Figure 4-193 Created Signaling Link Configuration ............................................... 4-148
Figure 4-194 Node B Port Configuration Tab......................................................... 4-150
Figure 4-195 Setting Parameters on the Node B Port Configuration Tab ............... 4-150
Figure 4-196 Created Node B Port Configuration .................................................. 4-151
Figure 5-1 Selecting Create Local Office................................................................... 5-2
Figure 5-2 Local Office Dialog Box (Basic Configuration Tab) ................................... 5-2
Figure 5-3 Local Office Dialog Box (Basic Config-1 Tab) ........................................... 5-3
Figure 5-4 Local Office Dialog Box (Node B Config tab)............................................ 5-3
Figure 5-5 Local Office Dialog Box (CN/RNC Common Config Tab) .......................... 5-4
Figure 5-6 Local Office Dialog Box (RNC Config Tab) ............................................... 5-4
Figure 5-9 Local Office Dialog Box (BSC Config Tab)................................................ 5-6
Figure 5-10 ATM Office Configuration Tab................................................................. 5-8
Figure 5-11 Setting Parameters on the ATM Office Configuration Tab ....................... 5-8
Figure 5-12 Created ATM Office Configuration.......................................................... 5-9
Figure 5-13 No. 7 Signaling Configuration Tab........................................................ 5-10
Figure 5-14 Setting Parameters on the No.7 Signaling Configuration Tab ............... 5-11
Figure 5-15 Created No.7 Signaling Configuration .................................................. 5-11
VII
Figure 5-16 Local Office Signaling Point Configuration............................................ 5-12

Tab ....................................................................................................... 5-13
Figure 5-18 Created Local Office Signaling Point Configuration .............................. 5-13
Figure 5-19 RNC Local Office Subsystem No. Tab ................................................. 5-14
Figure 5-20 Setting Parameters on the Local Office Subsystem No. Tab ................ 5-15
Figure 5-21 Created Local Office Subsystem No..................................................... 5-15
Figure 5-25 Selecting Create Adjacent RNC Office ................................................. 5-21
Figure 5-26 Adjacent RNC office Dialog Box (Basic Configuration Tab) .................. 5-21
Figure 5-27 Adjacent RNC Office Dialog Box (Basic Config-1 Tab .......................... 5-22
Figure 5-28 Adjacent RNC Office Dialog Box (Node B Config Tab) ......................... 5-22
Figure 5-29 Adjacent RNC Office Dialog Box (CN/RNC Common Config
Tab) ...................................................................................................... 5-23
Figure 5-30 Adjacent RNC Office Dialog Box (RNC Config Tab) ............................. 5-23
Figure 5-33 Adjacent RNC Office Dialog Box (BSC Config Tab).............................. 5-25
Figure 5-38 Setting Parameters on the Adjacent Office Signaling Tab..................... 5-29
VIII
Figures
IX

Figure 5-85 Selecting Create Sigtran Configuration ................................................ 5-65
Figure 5-86 Sigtran Configuration Dialogue Box ..................................................... 5-65
Figure 5-87 Created Sigtran Configuration.............................................................. 5-66
Figure 5-88 Selecting Create SCTP Association Configuration ............................... 5-68
Figure 5-89 SCTP Association Configuration Dialog Box (Basic Configuration of
SCTP Association Tab) ......................................................................... 5-69
Figure 5-90 SCTP Association Configuration Dialog Box (RTO Configuration of
Figure 5-91 SCTP Association Configuration Dialog Box (IP Configuration of
Figure 5-92 Selecting Create ASP Configuration Information .................................. 5-73
Figure 5-93 ASP Configuration Information............................................................. 5-73
Figure 5-94 Selecting Create AS Static Information ................................................ 5-75
Figure 5-95 AS Static Information Dialogue Box (AS Static Information 1
Tab) ...................................................................................................... 5-76
Figure 5-96 AS Static Information Dialogue Box (AS Static Information 2
Tab) ...................................................................................................... 5-77
Figure 5-97 Selecting Static Route Information of M3UA......................................... 5-78
Figure 5-98 Static Route Information of M3UA Dialog Box ...................................... 5-79
Figure 5-99 Selecting Route Information of M3UA Multi-RK .................................... 5-81
Figure 5-100 Route Information of M3UA Multi-RK Dialog Box ............................... 5-81
Figure 5-101 Selecting Create Path Group Configuration........................................ 5-83
Figure 5-102 Path Group Configuration Dialogue Box............................................. 5-83
Figure 5-103 Transmission Form and Path Definition.............................................. 5-85
Figure 5-104 Selecting Create Node B Office.......................................................... 5-87
Figure 5-105 Node B Office Dialog Box (Basic Configuration) ................................. 5-87
Figure 5-106 Node B Office Dialog Box (Basic Config-1 Tab) .................................. 5-88
Figure 5-107 Node B Office Dialog Box (Node B Config Tab) .................................. 5-88
Figure 5-108 Node B Office Dialog Box (CN/RNC Common Config Tab)................. 5-89
Figure 5-109 Node B Office Dialog Box (RNC Config Tab) ...................................... 5-89
Figure 5-110 Node B Office Dialog Box (CN Config-1 Tab)...................................... 5-90
Figure 5-111 Node B Office Dialog Box (CN Config-2 Tab) ...................................... 5-90
Figure 5-112 Node B Office Dialog Box (BSC Config Tab)....................................... 5-91
Figure 5-113 Path Configuration Tab....................................................................... 5-92
Figure 5-114 Setting Parameters on the Path Configuration Tab ............................. 5-93
Figure 5-115 Created Path Configuration ................................................................ 5-94
X
Figures
Figure 5-116 SCTP Resource Relation Tab............................................................. 5-95

Figure 5-117 Setting Parameters on the SCTP Resource Relation Tab ................... 5-95
Figure 5-118 Created SCTP Resource Relation ...................................................... 5-96
Figure 5-119 Node B Port Configuration Tab ........................................................... 5-97
Figure 5-120 Setting Parameters on the Node B Port Configuration Tab ................. 5-98
Figure 5-121 Created Node B Port Configuration .................................................... 5-98
Figure 5-122 Selecting Create Static Route .......................................................... 5-100
Figure 5-123 Static Route Dialog Box ................................................................... 5-101
Figure 6-1 Selecting Create QoS Configuration ........................................................ 6-2
Figure 6-2 QoS Configuration Dialog Box ................................................................. 6-2
Figure 6-3 QoS Configuration Tab............................................................................. 6-3
Figure 6-4 QoS Configuration Interface..................................................................... 6-4
Figure 6-5 Modifying Values on QoS Configuration Interface .................................... 6-5
Figure 6-6 Basic Priority Management Interface........................................................ 6-6
Figure 6-7 Modify Values on Basic Priority Management Interface ............................ 6-7
Figure 6-8 Scheduling Priority Management Interface ............................................... 6-8
Figure 6-9 Modifying Values on Scheduling Priority Management Interface............... 6-9
Figure 6-10 Index Input Dialog Box I ......................................................................... 6-9
Figure 6-11 Index Input Dialog Box II ...................................................................... 6-10
Figure 6-12 Application Priority Configuration Information Interface ........................ 6-10
Figure 6-13 Modifying Values on Application Priority Configuration Information
Interface ............................................................................................... 6-11
Figure 6-14 Basic Priority Transport Bearer Type Interface ..................................... 6-12
Figure 6-15 Modifying Values on Basic Priority Transport Bearer Type
Interface ............................................................................................... 6-12
Figure 6-16 Basic Priority Transport Reserved Bandwidth Interface ........................ 6-13
Figure 6-17 Modifying Values on Basic Priority Transport Reserved Bandwidth
Interface ............................................................................................... 6-14
Figure 6-18 Access Control related to Basic Priority Interface ................................. 6-15
Figure 6-19 Modifying Values on Access Control related to Basic Priority
Interface ............................................................................................... 6-15
Figure 6-20 Index Input Dialog Box I ....................................................................... 6-16
Figure 6-21 Index Input Dialog Box II ...................................................................... 6-16
Figure 7-1 Selecting CLKG Board Alarm Parameters................................................ 7-2
Figure 7-2 CLKG Board Alarm Parameters Dialog Box ............................................. 7-3
Figure 7-3 Selecting Create CLKG (ICM) Board Alarm Parameters .......................... 7-5
XI
Figure 7-4 CLKG (ICM) Board Alarm Parameters Dialog Box ................................... 7-6
Figure 7-5 Selecting Create Power Board Alarm Parameters.................................... 7-8
Figure 7-6 Power Board Alarm Parameters Dialog Box (Power Board Configuration
Tab) ........................................................................................................ 7-9
Figure 7-7 Power Board Alarm Parameters Dialog Box (Fans Configuration
Tab) ...................................................................................................... 7-10
Figure 7-8 Power Board Alarm Parameters Dialog Box (Door Access Configuration
Tab) ...................................................................................................... 7-11
Figure 7-9 Power Board Alarm Parameters Dialog Box (Power Config Tab)............ 7-12
Figure 7-10 Selecting Create MPX86/2 Alarm Parameters...................................... 7-14
Figure 7-11 MPX86/2 Alarm Parameters Dialog Box ............................................... 7-15
Figure A-1 Starting the NetNumen M31 Client .......................................................A-2
Figure A-2 Login Window..........................................................................................A-2
Figure A-3 Client Window .........................................................................................A-3
Figure A-4 Creating an NE Agent..............................................................................A-4
Figure A-5 Create WCDMA OMM Dialog Box (Basic Attributes)................................A-4
Figure A-6 Create WCDMA OMM Dialog Box (Extended Attributes) .........................A-5
Figure A-7 Starting an NE Agent...............................................................................A-6
Figure A-8 Configuration Synchronization .................................................................A-8
Figure A-9 Starting the NE Management...................................................................A-9
Figure A-10 NE Management Menu of A Started NE .............................................A-10
Figure A-11 Configuration Management View ......................................................... A-11
XII
Tables
Table 2-1 SHORTCUT MENU ON THE RNC GROUND RESOURCE
MANAGEMENT TAB................................................................................ 2-7
Table 4-1 Shortcut Menu on Local Office Dialog Box................................................. 4-8
Table 4-2 Example for Path Group Configuration .................................................... 4-23
Table 4-3 Shortcut Menu on Path Group Configuration Dialog Box ......................... 4-25
Table 4-4 Shortcut Menu on Adjacent RNC Office Dialog Box ................................. 4-31
Table 4-7 Shortcut Menu on CN Office Dialog Box .................................................. 4-61
Table 4-10 Shortcut Menu on PVC Configuration Dialog Box ................................ 4-117
Table 4-11 Example for ATM and IP Binding Relation............................................ 4-120
Table 4-12 Shortcut Menu on ATM and IP Binding Relation Dialog Box ................ 4-120
Table 4-13 Shortcut Menu on Static Route Dialog Box .......................................... 4-122
Table 4-14 Shortcut Menu on IMA Group Configuration Dialog Box ...................... 4-125
Table 4-15 Shortcut Menu on IMA Link Configuration Dialog Box.......................... 4-128
Table 4-16 Example for Path Group Configuration ................................................ 4-130
Table 4-17 Shortcut Menu on Path Group Configuration Dialog Box ..................... 4-132
Table 4-18 Shortcut Menu on Node B Office Dialog Box ....................................... 4-137
Table 4-19 Example of Node B Port Configuration ................................................ 4-151
Table 4-20 Shortcut Menu on Node Port Configuration Dialog Box........................ 4-151
Table 5-1 Shortcut Menu on Local Office Dialog Box................................................. 5-6
Table 5-4 Shortcut Menu on Adjacent RNC Office Dialog Box ................................. 5-25
Table 5-10 Shortcut Menu on CN Office Dialog Box ................................................ 5-57
XIII
Table 5-11 Shortcut Menu on Sigtran Configuration Dialog Box............................... 5-66

Table 5-12 Shortcut Menu on SCTP Association Configuration Dialog Box ............. 5-71
Table 5-13 Shortcut Menu on ASP Configuration Information Dialog Box ................ 5-74
Table 5-14 Shortcut Menu on AS Static Information Dialog Box .............................. 5-77
Table 5-15 Shortcut Menu on Static Route Information of M3UA Dialog Box ........... 5-79
Table 5-16 Shortcut Menu on Route Information of M3UA Multi-RK Dialog
Box ........................................................................................................ 5-82
Table 5-17 Example for Path Group Configuration .................................................. 5-84
Table 5-18 Shortcut Menu on Path Group Configuration Dialog Box ....................... 5-86
Table 5-19 Shortcut Menu on Node B Office Dialog Bpx ......................................... 5-91
Table 5-20 Example of Node B Port Configuration .................................................. 5-99
Table 5-21 Shortcut Menu on Static Route Dialog Box .......................................... 5-101
Table 6-1 Shortcut Menu on QoS Configuration Dialog Box ...................................... 6-3
Table 7-1 Shortcut Menu on CLKG Board Alarm Parameters Dialog Box .................. 7-3
Table 7-2 Shortcut Menu on CLKG (ICM) Board Alarm Parameters Dialog
Box .......................................................................................................... 7-6
Table 7-3 Shortcut Menu on Power Board Alarm Parameters Dialog Box................ 7-12
Table 7-4 Shortcut Menu on MPX86/2 Alarm Parameters Dialog Box...................... 7-15
XIV
Glossary
AAL2
- ATM Adaptation Layer type 2
APBE
- ATM Process Board Enhanced version
ATM
- Asynchronous Transfer Mode
CLKG
- CLOCK Generator
CN
- Core Network
DTB
- Digital Trunk Board
GIPI
- GE IP Interface
GUIM
- Gigabit Universal Interface Module
IMA
- Inverse Multiplexing over ATM
IMAB
- IMA Board
IMAP
- Internet Message Access ProtocolRFC2060
IP
- Internet Protocol
IPoA
- IP over ATM
IU
- Interface Unit
Iub
- Interface between an RNC and a Node B
Iur
- Interface between an RNC and another RNC
MAC
- Medium Access Control
XV
MGW
- Media GateWay
MSC
- Mobile Switching Center
NE
- Network Element
QoS
- Quality of Service
RNC
- Radio Network Controller
SCTP
- Stream Control Transmission Protocol
SDTB
- Sonet Digital Trunk Board
SEP
- Signaling End Point
SGSN
- Service GPRS Supporting Node
SLC
- Signaling Link Code
STEP
- Signaling Transfer/End Point
STP
- Signaling Transfer Point
TC
- Trunk Circuit
UDP
- User Datagram Protocol
UIMU
- Universal Interface Module for User Plane
XVI

SJ-20100603155704-024-ZXWR RNC (V3.09.30) Ground Configuration Operation Guide

Transféré par

Informations du document

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

SJ-20100603155704-024-ZXWR RNC (V3.09.30) Ground Configuration Operation Guide

Transféré par

Droits d'auteur :

Formats disponibles

ZXWR RNC

Radio Network Controller

Ground Configuration Operation Guide

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Third Edition (V3.09.30.12)

Second Edition (V3.09.30.09)

The following sections have been modified:

The following topics have been modified:

The following sections have been added:

Serial Number: SJ-20100603155704-024

First Edition (V3.09.30.03)

Chapter 2 Public Resource Configuration ............................................... 2-1

Chapter 3 Hardware Resource Configuration.......................................... 3-1

Chapter 4 Configuring NE Information (ATM).......................................... 4-1

4.7.1 Creating IMA Group (ATM).....................................................................4-123

Chapter 5 Configuring NE Information (IP) .............................................. 5-1

5.5.2 Creating SCTP Association (IP) .............................................................. 5-67

Chapter 6 Configuring QoS ....................................................................... 6-1

Chapter 7 Setting Alarm Parameters ........................................................ 7-1

Appendix A Common Configuration Management Operations ............ A-1

About This Manual

Network management basics

What is in This Manual

Chapter 2, Public Resource Configuration

Describes the details of the Public Resource Configuration.

Chapter 3, Hardware Resource Configuration

Describes the configuration of racks, shelves and

Chapter 4, NE Information (ATM)

Describes the configuration of NE information in ATM

Chapter 5, NE Information (IP)

Describes the configuration of NE information in IP

Chapter 6, QoS Configuration

Describes the QoS Configuration.

Chapter 7, Alarm Notification

Describes the configuration of alarm notification.

Appendix A, Common Configuration Manage-

Describes the common operations for the Configura-

ZTE Proprietary and Confidential

ZXWR RNC Ground Configuration Operation Guide

1.3 Ground Resource Configuration Flow

ZTE Proprietary and Confidential

ZTE Proprietary and Confidential

ZXWR RNC Ground Configuration Operation Guide

Figure 2-1 Flow for the Public Resource Configuration

2.2 Creating a UTRAN Subnetwork Node

The Network Management System (NMS) is operating properly.

ZTE Proprietary and Confidential

Chapter 2 Public Resource Configuration

The UTRAN Subnetwork dialog box opens, as shown in Figure 2-2.

2. Set the Alias and Subnetwork ID parameters.

2.3 Creating an RNC Managed Element

ZTE Proprietary and Confidential

ZXWR RNC Ground Configuration Operation Guide

2.4 Creating an RNC configuration Set

master configuration set, and

ZTE Proprietary and Confidential

Chapter 2 Public Resource Configuration

Figure 2-4 RNC Config Set

2. Set necessary parameters according to the planning data.

2.5 Creating a RNC Ground Resource Management

ZTE Proprietary and Confidential

ZXWR RNC Ground Configuration Operation Guide

Figure 2-5 RNC Ground Resource Management