ZXUR 9000 UMTS (V4.14.10) Commissioning Guide-06 Quick Data Configuration - R1.1

ZXUR 9000 UMTS(V4.14.
10)
Commissioning Guide
06 Quick Data Configuration
ZXUR 9000 UMTS(V4.14.10) Commissioning Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following
terms. If you do not agree to the following terms, please notice that you are not allowed
to use this document.
Copyright 2016 ZTE CORPORATION. Any rights not expressly granted herein are
reserved. This document contains proprietary information of ZTE CORPORATION. Any
reproduction, transfer, distribution, use or disclosure 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.
is the registered trademark of ZTE CORPORATION. ZTEs company name, logo and
product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be
trademarks or trade names of their respective owners. Without the prior written consent
of ZTE CORPORATION or the third party owner thereof, anyones access to this
document should not be construed as granting, by implication, estoppel or otherwise,
any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and
personal security. This product shall be stored, used or discarded in accordance with
product manual, relevant contract or laws and regulations in relevant country
(countries).
This document is provided as is and as available. Information contained in this
document is subject to continuous update without further notice due to improvement
and update of ZTE CORPORATIONs products and technologies.
ZTE CORPORATION
Addres
s:
Websit
e:
Email:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
http://support.zte.com.cn
800@zte.com.cn
ZTE Confidential & Proprietary.
2016 ZTE CORPORATION. All rights reserved.
Revision History
Product Version
V12.14.10
V12.14.10
Document Version
Serial Number
Reason for Revision
R1.0
First published
R1.1
Add requirement for

RNC restart after alldata synchronization
in case of initial
comminissioning ; add
requirement for the
number of IUBCOM
addresses on ETCA
V2.
Author
Date
Document Version
Prepared by
Reviewed by
Approved by
2015-05-20
R1.0
Hu Zhigang
Chen Taiming
Zhang Zhongqi
2015-08-10
R1.1
Hu Zhigang
Chen Taiming
Zhang Zhongqi
Intended audience: RNC commissioning engineers (from both ZTE and the
subcontractor)
II
2016ZTE CORPORATION. All rights reserved.
About This Document

Summary
Chapter
Description
1 Notices in Data Configuration
Provides the matters for attention in data configuration
2 Introduction to Quick Data

Configuration
Provides an overview of Plan template and common

functions.
3 Method of Calculating the

Number of User-plane IPs
Introduces the method of calculating the number of userplane IPs
4 Specifications of Configuring
Equipment Template and Transport
Network Template
Introduces the specifications of configuring Equipment

template and Transport Network templates.
5 Specifications of Configuring
UMTS Radio Template
Introduces the specifications of configuring UMTS Radio

template.
6 Independent Board Configuration
Introduces some operations of independent board

configuration and related parameters.
7 Special Subject
Introduces some special subjects, such as ICM data

configuration, CMP module No. modification, etc.
III
TABLE OF CONTENTS
1
Notices in Data Configuration.........................................................................1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
Introduction to Quick Data Configuration......................................................2

Overview of Plan Template................................................................................2
Template Info Sheet...........................................................................................
Index Sheet........................................................................................................
Attributes of Parameters....................................................................................
Equipment Template..........................................................................................
Transport Network Template..............................................................................
UMTS Radio Template.......................................................................................
Common Functions............................................................................................8
Loading Templates.............................................................................................
Exporting Templates.........................................................................................
Check on Imported Quick Configuration Template...........................................
Restoring Modify Area from Snapshot Area.....................................................
Data Comparison Between Snapshot Area & Modify Area...............................
Method of Calculating the Number of User-plane IPs.................................18
4
Template
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8
4.1.9
4.1.10
4.1.11
4.1.12
4.1.13
4.1.14
4.1.15
4.1.16
4.1.17
4.1.18
4.1.19
4.2
4.2.1
4.2.2
4.2.3
Specifications of Configuring Equipment Template and Transport Network

20
Equipment Template........................................................................................20
Basic Info.........................................................................................................
Plmn Config.....................................................................................................
Shelf Config.....................................................................................................
Board Config....................................................................................................
Global Info.......................................................................................................
Interface IP......................................................................................................
Service IP........................................................................................................
CCIU Service Config........................................................................................
UCIU IP Combination Type..............................................................................
Slave or Dsp Service Config............................................................................
Channel Port....................................................................................................
Member Port....................................................................................................
Super Vlan.......................................................................................................
Super Vlan Member.........................................................................................
DHCP Server...................................................................................................
DHCP Client.....................................................................................................
DHCP Relay.....................................................................................................
VRF Attributes Config......................................................................................
VRF Route Target............................................................................................
TransportNetwork Template.............................................................................39
Local Office......................................................................................................
Static Route.....................................................................................................
IP Path Group..................................................................................................
IV
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
4.2.13
4.2.14
4.2.15
4.2.16
4.2.17
4.2.18
4.2.19
4.2.20
4.2.21
4.2.22
4.2.23
4.2.24
4.2.25
4.2.26
4.2.27
4.2.28
4.2.29
4.2.30
4.2.31
4.2.32
IUB Office........................................................................................................
ATM Bearer(IUB Auto).....................................................................................
ATM Bearer(IUB).............................................................................................
SCTP Config(IUB-ABIS)..................................................................................
IP Bearer(IUB).................................................................................................
IPOE Bearer(IUB)............................................................................................
SCTP Config(ABIS)..........................................................................................
IP Bearer(ABIS)...............................................................................................
Adjacent Office(CN).........................................................................................
SCTP Config(CN)............................................................................................
M3uaAS Config(CN)........................................................................................
M3uaRoute......................................................................................................
M3uaRouteSet.................................................................................................
IP Path(CN)......................................................................................................
PVC Config(IU-IUR).........................................................................................
Mtp2Link..........................................................................................................
Mtp3Route.......................................................................................................
No.7 PCM........................................................................................................
Itc or BSC Office..............................................................................................
PCM(ITC-MSC)................................................................................................
MSC Office.......................................................................................................
SGSN Office....................................................................................................
Fr Gb................................................................................................................
Ip Gb................................................................................................................
Lucent Channel................................................................................................
SCTP Config(S1).............................................................................................
Dynamic Sctpac...............................................................................................
S1 Link.............................................................................................................
S1 TrPath.........................................................................................................
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
Specifications of Configuring UMTS Radio Template.................................75

UTRAN Cell.....................................................................................................75
Logic Cell Configuration...................................................................................77
External UTRAN Cell.......................................................................................78
External GSM Cell...........................................................................................80
UExternalENBFunction....................................................................................81
External EUTRAN Cell FDD.............................................................................82
External EUTRAN Cell TDD.............................................................................86
Neighbouring Cell............................................................................................87
GSM Neighbouring Cell...................................................................................88
EUTRAN Neighbouring Cell.............................................................................88
User Authorized PLMN+SNAC Information......................................................89
MBMS Configuration........................................................................................90
MBMS Service Area Configuration...................................................................90
MBMS Frequency Layer Configuration............................................................90
6
6.1
6.2
6.3
6.4
Independent Board Configuration................................................................90

Checking the Link Status of an Independent Board.........................................90
Independent Board Configuration Related Parameters....................................91
Modifying and Synchronizing Parameters of an Independent Board................94
Performing NTP Synchronization to an Independent Board.............................95
7
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.9.1
7.9.2
7.9.3
7.10
7.11
7.12
7.13
7.14
7.15
7.16
7.16.1
7.16.2
7.17
VI
Special Subject..............................................................................................97
ICM Data Configuration Flow (All-Parameter Configuration)............................97
ICM Initialization...............................................................................................
Exporting Optimization Template (All Parameters)...........................................
Data Import....................................................................................................102
Deleting Plan Area.........................................................................................118
Features of NodeB Auto-configuration...........................................................120
CMP Module No. Modification (Transmission)...............................................123
Overall Office Information Deletion................................................................124
Site Bearer Migration Function.......................................................................124
RNCID NODEBID CELLID Modification Tool.................................................125
Notes for All-data Synchronization & RNCID Modification..............................125
Adding User-plane IP (USP)..........................................................................125
Board Configuration.......................................................................................126
Slot Requirement for Master/Slave Boards....................................................126
Configuration Guide of ATM Interface Board Properties.................................126
Introduction of USP Board.............................................................................127
PVC Configuration.........................................................................................130
ATM Address Conversion...............................................................................133
1588 Clock Configuration...............................................................................134
Shielding Alarms............................................................................................135
Rules of Configuring Master/Slave EGPB......................................................136
Rules of Configuring Slots for USP................................................................138
Iub-Interface Qos Planning Rules..................................................................139
QOS According to ARP/THP/TC....................................................................139
QOS According to Service Type.....................................................................140
IP Function Switch.........................................................................................141
FIGURES
Figure 2-1 Template Importing Flow........................................................................................2
Figure 2-2 Template Info Sheet...............................................................................................3
Figure 2-3 Index Sheet........................................................................................................... 3
Figure 2-4 Attributes of Parameters........................................................................................4
Figure 2-5 V4_Template_Equipment......................................................................................5
Figure 2-6 V4_Template_TransportNetwork...........................................................................6
Figure 2-7 UMTS Radio Quick Configuration Template..........................................................7
Figure 2-8 UMTS Radio Template..........................................................................................7
Figure 2-9 Configuration Management...................................................................................8
Figure 2-10 Create Subnetwork..............................................................................................8
Figure 2-11 Create Management Element..............................................................................9
Figure 2-12 Import Quick Configuration Data.........................................................................9
Figure 2-13 Choose the Template to Be Loaded...................................................................10
Figure 2-14 Import Template.................................................................................................10
Figure 2-15 Template Importing Completed..........................................................................11
Figure 2-16 Query Importing Result......................................................................................11
Figure 2-17 Logs of Importing Result....................................................................................11
Figure 2-18 Export Quick Configuration Data.......................................................................12
Figure 2-19 Template Exporting Interface.............................................................................13
Figure 2-20 Template Importing Check.................................................................................14
Figure 2-21 Global Validity Check.........................................................................................15
Figure 2-22 Restore Modify Area from Snapshot Area..........................................................16
Figure 2-23 Restore Modify Area..........................................................................................16
Figure 2-24 Data Comparison...............................................................................................17
Figure 2-25 Comparison Result............................................................................................17
Figure 3-1 IP Number Calculating Tool.................................................................................18
Figure 6-1 Independent Board Configuration Online.............................................................90
Figure 6-2 Check the Link Status of an Independent Board..................................................91
Figure 6-3 Independent Board Configuration Online.............................................................92
Figure 6-4 Modify Parameters..............................................................................................94
Figure 6-5 Activate Data.......................................................................................................95
VII
Figure 6-6 Data Activation Completed..................................................................................95

Figure 6-7 Controller Rack in Status Management...............................................................96
Figure 6-8 Rack Diagram......................................................................................................96
Figure 6-9 Operation Result of the NTP Synchronization.....................................................96
Figure 7-1 ICM Data Area.....................................................................................................97
Figure 7-2 Plan Data Management.......................................................................................98
Figure 7-3 Live Data Area Synchronization...........................................................................99
Figure 7-4 Export Optimization Template on ICM.................................................................99
Figure 7-5 Query and Export..............................................................................................100
Figure 7-6 Storage Path of Exported File............................................................................101
Figure 7-7 Data Exported Successfully...............................................................................102
Figure 7-8 ICM Operation Flow...........................................................................................103
Figure 7-9 Create Plan Area...............................................................................................103
Figure 7-10 Create Plan Area.............................................................................................104
Figure 7-11 Confirm Dialog Box..........................................................................................104
Figure 7-12 Import Template...............................................................................................105
Figure 7-13 Import Plan Template.......................................................................................106
Figure 7-14 View Detail.......................................................................................................107
Figure 7-15 Import Optimization Template..........................................................................108
Figure 7-16 Validity Check..................................................................................................109
Figure 7-17 Data Check-Validity..........................................................................................110
Figure 7-18 Check Result....................................................................................................111
Figure 7-19 Conflict Check..................................................................................................112
Figure 7-20 Confirm Live Data............................................................................................112
Figure 7-21 Conflict Check Result.......................................................................................113
Figure 7-22 Data Submission..............................................................................................114
Figure 7-23 Data Activation.................................................................................................114
Figure 7-24 Activate Task Management..............................................................................115
Figure 7-25 Compare to Get Delta......................................................................................115
Figure 7-26 Compare Success...........................................................................................116
Figure 7-27 Download.........................................................................................................116
Figure 7-28 Download Success..........................................................................................117
Figure 7-29 Data Activation.................................................................................................117
Figure 7-30 Activate Success..............................................................................................118
Figure 7-31 Delete Activation Task......................................................................................118
VIII
Figure 7-32 Switch Submit Status.......................................................................................119

Figure 7-33 Delete Plan Area..............................................................................................120
Figure 7-34 Confirm Plan Area Deletion.............................................................................120
Figure 7-35 Module Restore 1............................................................................................121
Figure 7-36 Module Restore 2............................................................................................122
Figure 7-37 Module Adjust..................................................................................................122
Figure 7-38 Get Suggestions for Module Adjustment..........................................................123
Figure 7-39 Execute Module Adjustment............................................................................123
Figure 7-40 CMP Module No. Modification.........................................................................123
Figure 7-41 Overall Office Information Deletion..................................................................124
Figure 7-42 Site Bearer Migration.......................................................................................125
Figure 7-43 Diagram of Master/Slave Board Slots..............................................................126
Figure 7-44 Configure CDR Board......................................................................................129
Figure 7-45 Configure PVC in V3.......................................................................................131
Figure 7-46 Configure PVC in V4.......................................................................................131
Figure 7-47 ATM Address Format.......................................................................................133
Figure 7-48 1588 Clock Configuration 1.............................................................................135
Figure 7-49 1588 Clock Configuration 2.............................................................................135
Figure 7-50 Shield Alarms...................................................................................................136
Figure 7-51 Port Switch......................................................................................................138
Figure 7-52 Transport Qos Profile Type..............................................................................139
Figure 7-53 Used Transport Bearer Type Profile Related to Basic Priority..........................139
Figure 7-54 Used Dedicated Service Transport Bearer Qos Profile....................................140
Figure 7-55 IP Function Switch...........................................................................................141
TABLES
Table 1-1 Notices in Data Configuration..................................................................................1
Table 2-1 Parameter Attributes...............................................................................................4
Table 4-1 Basic Info..............................................................................................................20
Table 4-2 Plmn Config..........................................................................................................22
IX
Table 4-3 Shelf Config..........................................................................................................23

Table 4-4 Board Config.........................................................................................................23
Table 4-5 Global Info.............................................................................................................24
Table 4-6 Interface IP............................................................................................................ 25
Table 4-7 Service IP..............................................................................................................26
Table 4-8 CCIU Service Config.............................................................................................28
Table 4-9 UCIU IP Combination Type...................................................................................28
Table 4-10 Slave or Dsp Service Config...............................................................................31
Table 4-11 Channel Port.......................................................................................................31
Table 4-12 Member Port.......................................................................................................32
Table 4-13 Super Vlan..........................................................................................................33
Table 4-14 Super Vlan Member............................................................................................34
Table 4-15 DHCP Server......................................................................................................34
Table 4-16 DHCP Client........................................................................................................35
Table 4-17 DHCP Relay........................................................................................................36
Table 4-18 VRF Attributes Config..........................................................................................37
Table 4-19 VRF Route Target...............................................................................................38
Table 4-20 Local office.......................................................................................................... 39
Table 4-21 Static route.......................................................................................................... 40
Table 4-22 IP Path Group.....................................................................................................41
Table 4-23 IUB Office............................................................................................................ 42
Table 4-24 ATM Bearer(IUB Auto).........................................................................................45
Table 4-25 ATM Bearer(IUB).................................................................................................46
Table 4-26 SCTP Config(IUB-ABIS)......................................................................................50
Table 4-27 IP Bearer(IUB).....................................................................................................51
Table 4-28 IPOE Bearer(IUB)...............................................................................................52
Table 4-29 Adjacent Office(CN)............................................................................................54
Table 4-30 SCTP Config(CN)................................................................................................59
Table 4-31 M3uaAS Config(CN)...........................................................................................61
Table 4-32 M3uaRoute......................................................................................................... 63
Table 4-33 M3uaRouteSet....................................................................................................64
Table 4-34 IP Path(CN).........................................................................................................64
Table 4-35 PVC Config(IU-IUR)............................................................................................66
Table 4-36 Mtp3Route..........................................................................................................72
Table 5-1 UTRAN Cell.......................................................................................................... 75
Table 5-2 Logic Cell Configuration........................................................................................77

Table 5-3 External UTRAN Cell............................................................................................78
Table 5-4 External GSM Cell.................................................................................................80
Table 5-5 External ENodeB Function....................................................................................81
Table 5-6 External EUTRAN Cell FDD..................................................................................82
Table 5-7 External EUTRAN Cell TDD..................................................................................86
Table 5-8 Neighbouring Cell..................................................................................................87
Table 5-9 GSM Neighbouring Cell........................................................................................88
Table 5-10 EUTRAN Neighbouring Cell................................................................................88
Table 5-11 User Authorized PLMN+SNAC Information.........................................................89
Table 6-1 Common Parameter Configuration........................................................................92
Table 7-1 Sheets to Be Configured for Each Transmission Type of a New Site..................124
Table 7-2 Configuring Data of ATM Interface Board............................................................127
Table 7-3 Introduction of USP Board...................................................................................127
Table 7-4 UDP Port No.......................................................................................................130
Table 7-5 Relation between PVC Traffic Type, Traffic Parameter, and PVC Service Type. .131
Table 7-6 AFI of ATM Address.............................................................................................134
Table 7-7 1588 Clock Configuration Related Parameters...................................................134
Table 7-8 Port Switch..........................................................................................................137
Table 7-9 IUB QOS Planning Rules 1..............................................................................140
Table 7-10 IUB QOS Planning Rules 2............................................................................140
XI
Notices in Data Configuration

In the data configuration process, please pay close attention to the parameters that may
be configured improperly, as detailed in Table 1 -1.
Table 1-1 Notices in Data Configuration

No.
Contents
Description
Master/slave configuration,
alternate backup slots
(1,3), (2,4), (11,13), (12,14)
PLMN ID
It is recommended to set PLMN ID as a

combination of MCC + MNC, each
composed of 3 digits, e.g., for 460/1, the PLMN
ID should be set as 460001.
Configuration of integrated
CDR
Each master and slave CDR board needs to be

configured with one CMP module, two DMP
modules, and one RUB unit, among which the
CMP module NO. ranges 3-31, DMP module
NO. ranges 64-127.
IUBCOM
The IUBCOM address needs to be added in

the IUB interface planning.
ETCA V1 shelf: one IUBCOM address should
be configured for every two shelves; two
IUBCOM addresses are required for three
shelves.
ETCA V2 shelf: two IUBCOM addresses should
be configured for each shelf; six IUBCOM
addresses are required for three shelves.
Signaling point code
Set it as a decimal value.
Netmask
Set it as a decimal value.
OMCB gateway IP
It must be configured on the virtual port.
Global check
In the synchronization process, the system will

check both the required items and the optional
items by default. Sometimes the optional items
may cause synchronization failure and the
check can be cleared manually.
Introduction to Quick Data

Configuration
There are three MO quick data configuration templates, i.e., V4_Template_Equipment,
V4_Template_TransportNetwork, and UMTS Radio Quick Configuration Template, which
can be loaded into OMM one by one.
Figure 2-1 Template Importing Flow
2.1
Overview of Plan Template
2.1.1
Template Info Sheet

The first sheet of all quick data configuration templates is the Template Info sheet,
which provides the basic template information for OMM. By this sheet, OMM can judge
whether the template matches with OMM and acquire the categorization information of
templates. Therefore, the content of this sheet must be kept complete no matter which of
other sheets are selected.
Figure 2-2 Template Info Sheet
2.1.2
Index Sheet
The second sheet of all templates is the Index sheet. It provides the overall information
about the content of the template and the categorization (UMTS/GSM) of the sheets for
the user. It also provides hyperlinks, and the user can click the corresponding link to go
to the target sheet.
Figure 2-3 Index Sheet
2.1.3
Attributes of Parameters
The fifth line of the template is parameter attributes, as shown in Figure 2 -4.
Figure 2-4 Attributes of Parameters
The attributes of the parameters fall into the following categories according to different
applications. Please refer to Table 2 -2 for the method of filling the parameters of
different attributes (Modifying this line is prohibited).
Table 2-2 Parameter Attributes

Parameter Attributes
Meaning
Description
Read
Read only
R-W
Read and Write
Can be read and

modified
R-I
Read and Initial
This parameter must be

configured in the data
creation process.
R-W-I
Read, Write and Initial
Can be read and

modified. This parameter
must be configured.
Read, Modify and Initial
Can be read. This

parameter must be
creation and modification
process.
Primary Key

creation and modification
process.
R-M-I
Primary Key
Note:
Do not modify the first line and the fifth line of the template. Otherwise, template loading
error will occur.
2.1.4
Equipment Template
2.1.4.1
Introduction to Equipment Template

Figure 2 -5 shows the sheets included in the Equipment template, which can fulfill
rack, shelf, board, global information, and basic networking related data configuration.
All sheets in this template, except Row 13, are related to UMTS network. Field engineers
shall select the sheets according to the actual application scenario.
Figure 2-5 V4_Template_Equipment
2.1.4.2
An Example of Equipment Template

The template is corresponding to OMMR V12.14.10.
V4_Template_Equip
ment.xls
2.1.5
Transport Network Template
2.1.5.1
Introduction to Equipment Template

Figure 2 -6 shows the sheets included in the Transport Network template.
Transmission parameters on the IU/IUR/IUB interfaces and office integration parameters
are configured by this template.
Some sheets in this template are for UMTS data configuration and some are for GSM
and AG data configuration. Field engineers shall select the sheets according to the
actual application scenario, and click Generate to filter related templates automatically.
Filter the template according to radio type, transmission type, and special scene. The
principles are as shown below:
1.
Select a radio type. Only one mode can be selected here. The template generated
will display all configuration parameters of the specified radio mode.
2.
Select a combination of radio type and transmission type. The template generated
will display the configuration parameters involved in the specified radio mode and
transmission type. This applies to the scenario of initial commissioning.
3.
Select a combination of radio type and special scene. The template generated will
display the configuration parameters involved in the specified radio mode and
special scene. This applies to the scenario of transmission modification.
4.
Select no filtering condition. The template will not perform filtering and will display
the contents of all sheets.
Figure 2-6 V4_Template_TransportNetwork
2.1.5.2
An Example of Filled UMTS Radio Template

V4_Template_Trans
portNetwork.xls
2.1.6
UMTS Radio Template
2.1.6.1
Introduction to UMTS Radio Template

Error: Reference source not found shows the sheets included in the UMTS Radio Quick
Configuration Template. The radio parameters on the Iub interface are configured with
this template.
All sheets in this template are for UMTS data configuration. Six of the sheets are
required. Other sheets should be filled in according to the actual application scenario.
Figure 2-7 UMTS Radio Quick Configuration Template
The parameters in red in the first line must be filled in. This is similar to the yellow areas
in the V3 non-MO templates.
Figure 2-8 UMTS Radio Template
2.1.6.2
An Example of Filled UMTS Radio Template

UMTS Radio Quick

Configuration Template.xls
2.2
Common Functions
2.2.1
Loading Templates
Step 1: Choose View > Configuration Management.
Figure 2-9 Configuration Management
Step 2: Right-click and choose Create Subnetwork. Set Subnetwork ID and Set of
MCC according to the actual situation.
Figure 2-10 Create Subnetwork
Step 3: Right-click SubNetwork, choose Create Management Element, and set

Management Element modetype and Management Element IP Address according to
the actual situation.
Figure 2-11 Create Management Element
Step 4: Right-click ME and choose Import Quick Configuration Data.
Figure 2-12 Import Quick Configuration Data
Step 5: Click Choose, select the template to be loaded, and click Open.
Figure 2-13 Choose the Template to Be Loaded
Step 6: Select the sheet to be imported. If all sheets need to be imported, select ALL
Imported Object. Then, click Execute to start importing template.
Figure 2-14 Import Template
If the number displayed in Result on the right is equal to the total number of records, it
means all records are loaded successfully. Otherwise, some records fail to be loaded.
10
Figure 2-15 Template Importing Completed
Step 7: Under the directory for loading template, OMM will generate a zipped Result file
automatically. This file can be viewed after it is unzipped.
Figure 2-16 Query Importing Result
In the result file, the detailed information is displayed in column A, and the value of
MODIND in column B will change to P for the fields loaded successfully.
Figure 2-17 Logs of Importing Result
Note:
There is only one loading method for V4 quick configuration, no matter whether it is for
Equipment template & Transport Network template or for UMTS Radio Quick Configuration
template.
2.2.2
Exporting Templates
Step 1: Right-click ME and choose Export Quick Configuration Data.
Figure 2-18 Export Quick Configuration Data
Step 2: Fill in the values for Choose Directory, File Name Prefix, and Export File
according to the actual situation, export the required template sheet by sheet, and click
Execute.
12
Figure 2-19 Template Exporting Interface
2.2.3
Check on Imported Quick Configuration Template

The competed quick data configuration template can only be synchronized to RNC when
it meets the related restrictions on OMM and passes the validity check.
1.
Template importing: In this process, OMM will check the validity, effectiveness, and
completeness of the format in the quick configuration template.
Figure 2-20 Template Importing Check
2.
14
Global validity check: It is required this step be performed before data

synchronization. It aims to check whether the OMM data is valid and meets the
restrictions completely.
Figure 2-21 Global Validity Check
3.
License Center Check

Check whether the data configuration in OMM satisfies License control
requirements applied in the License Center. License check will be triggered
automatically when data synchronization is performed. If the data configuration
does not satisfy the requirements, the check will fail and the system will report the
cause of the failure.
Note:
Only the data that passes the above three checks can be synchronized to RNC. Loading data
into OMM does not necessarily indicate successful data synchronization.
2.2.4
Restoring Modify Area from Snapshot Area

Click Configuration Management > Advanced >Batch NEs Operation.
Figure 2-22 Restore Modify Area from Snapshot Area
After the Batch NEs Operation window pops up on OMM, select the target NE, and
click Restore modify area from Snapshot Area to restore data from the snapshot area
to the modify area. If Copied is displayed in Status, it means the operation succeeds.
Figure 2-23 Restore Modify Area
2.2.5
Data Comparison Between Snapshot Area & Modify Area

Click Configuration Management > Data Comparison Between Snapshot Area and
Modify Area.
16
Figure 2-24 Data Comparison
Select the target NE, click Run (the Fast comparison mode is used by default), and click
OK to start comparison.
Observe the value of Result. If it is identical, it means that the data in the snapshot
area is the same as that in the modify area.
Figure 2-25 Comparison Result
Method of Calculating the Number of

User-plane IPs
In initial commissioning, we can use the EXCEL tool provided by OMM to calculate the
number of service IPs according to the value of "the ratio of control plane for sharing
CPU Resource" (it determines the number of Slave subunits available in the system and
can be acquired from the documents transferred from pre-sales), IPINTFTYPEs, and
PLMNCOMBTYPEs. The field engineer can apply for the related IP resources from the
operator according to the result of the tool.
This is an off-line tool that is realized by the Macro of the Excel template. Fill in the
parameters needed for counting IPs in the Excel template, and click the "Count the
number of IP address" button to display the counting result. The design of the Excel
template is as shown in the figure below.
Figure 3-26 IP Number Calculating Tool
In the Excel template, the values of the parameters are as shown below:
USPBOARDNUM: 0..42
USP2ABOARDNUM: 0..42
Restriction: If the numbers of USP and USP2a are both "0," an error will be prompted,
indicating it is necessary to fill in the number correctly.
18
The ratio of control plane for sharing CPU Resource: 20..67; default: 20; based on
the default value "20," we can get the upper limit for the number of IPs needed. In the
calculation process, it is recommended that "20" be used to work out the upper limit, so
that there are some redundant IPs.
IPINTFTYPE 1-5:
Bit0=1: 3G Iub interface
Bit1=1: 3G Iur interface
Bit2=1: 3G IuCS interface
Bit3=1: 3G IuPS interface
Bit4=1: 3G Iubprecfg interface
In the whole system, the interface types supported by the service IP of each Slave are
the same. The five IPINTFTYPE parameters show the interface types supported by the
service IPs allocated to each Slave and the corresponding interface combinations. Each
RNC occupies one record in the template.
Refer to the following examples:
1.
IPINTFTYPE1=11111,IPINTFTYPE2~IPINTFTYPE5=0: The interfaces share an IP

and support the pre-configuration of the Iub interface.
2.
IPINTFTYPE1=1,IPINTFTYPE2=10,IPINTFTYPE3=100,IPINTFTYPE4=1000,
IPINTFTYPE5=0: Each interface uses an independent IP and does not support the
pre-configuration of the Iub interface.
3.
IPINTFTYPE5=0: Iub and Iur share an IP, and IuCs and IuPs share an IP, and preconfiguration of iUb is not supported.
Restriction: Check whether the interface types involved are conflicted with each other,
i.e., after the AND operation is performed to every two of IPINTFTYPE1~ IPINTFTYPE5,
the value of the five bits should not be "1."
PLMNCOMBTYPE 1-5:
The PLMN combinations corresponding to IPINTFTYPE 1-5.
If different PLMNs use different IPs, separate the IPs with ";". If different PLMNs share
IPs, separate the IPs with @.
When filling in PLMNCOMBTYPE, fill in all the PLMN IDs supported by the NE.
Because an RNC supports four PLMNs at most, we use 1, 2, 3, and 4 to represent four
PLMN IDs respectively.
Suppose an NE supports four PLMNs, and PLMN 1 and PLMN 2 share an IP, PLMN 3
and PLMN 4 use two independent IPs, this parameter should be set to "1@2;3;4."
If this parameter is not configured, it means all PLMNs are supported.
If the system supports only one PLMN, fill in either the exact PLMNID or null.
Restriction: If the value of PLMNCOMBTYPE is not 0, either fill in null or fill in 1, 2, 3,
4" and make sure the PLMN IDs filled in are not repeated. For all non-0
PLMNCOMBTYPEs, the number of PLMNs must be consistent with PLMN IDs, but
PLMNID does not need to match PLMNCOMBTYPE.
Fill in the supported IP types, and click the Count the number of IP address button, and
then the Excel template will count the service IPs.
The Excel template has both Chinese and English versions, which are stored under the
\ums-clnt\tools\UCIUIpNum directory.
Specifications of Configuring
Equipment Template and Transport
Network Template
4.1
Equipment Template
4.1.1
Basic Info
Table 4-3 Basic Info
20
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,M,P
A:Add,
D:Delete,
M:Modify, P:Pass
Managed
Element ID
long:
[1..4095]
Primary
Key
Mode Type
long:[2..4]
2:UMTS
3:GSM
4:GU
R-I
Omp's omc
port ip
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
Omp's omc
port mask
length
long:[0..32]
R-W-I
Omp's omc
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
Description
Parameter
Name
Parameter
Value
port
gateway
Description
Remarks
UMTS:It should be as same

as the IP address of bond2:1
IP address
of SNTP
server
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
OMCB
Agent IP
Address to
NODEB
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
OMCB
Server IP
Address
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
OMCB
Server IP
Mask
Length
long:[0..32]
R-W-I
ipv4
eg:xxx.xxx.xxx.xxx
It can be used when it
supports multipath
protection.
Otherwise, it is filled in
default value 0.0.0.0 .
R-W-I
long:[-720,660,-600,540,-480,420,-360,300,-240,180,-120,60,0,60,120
,180,240,30
0,360,420,4
80,540,600,
660,720,78
0]
The value range:

-720:GMT-12
-660:GMT-11
-600:GMT-10
-540:GMT-9
-480:GMT-8
-420:GMT-7
-360:GMT-6
-300:GMT-5
-240:GMT-4
-180:GMT-3
-120:GMT-2
-60:GMT-1
0:GMT
60:GMT+1
120:GMT+2
180:GMT+3
240:GMT+4
300:GMT+5
360:GMT+6
420:GMT+7
480:GMT+8
540:GMT+9
600:GMT+10
660:GMT+11
720:GMT+12
780:GMT+13
R-W-I
OMCB
Inner Ip
Address
Time Zone
Daylight
Saving
long:[0,1]
0:Stop
1:Start
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
Time using
flag
4.1.2
Start time
of the
Daylight
Saving
Time(Mon/
Day/Hour/
Min)
string
eg:Mon/Day/Hour/Min
R-W
End time of
the Daylight
Saving
Time(Mon/
Day/Hour/
Min)
string
eg:Mon/Day/Hour/Min
R-W
Step of
Daylight
Saving
Time(minut
e)
long:
[0..33008]
60 is recommended value.
R-W
Plmn Config
Table 4-4 Plmn Config
22
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete, M:Modify,

P:Pass
User label
string
R-W
Managed
Element ID
long:
[1..4095]
Primary
Key
PLMN
Group
Object ID
long:
[0..429496
7295]
Primary
Key
Mobile
Country
Code
long:
[0..999]
R-W-I
Mobile
Network
Code
long:
[0..999]
R-W-I
MNC BCD
Code
Length
long:[2..3]
R-W-I
Description
4.1.3
Parameter
Name
Parameter
Value
Default
PLMN
Indicator
long:[0..1]
0:false
1:true
R-W-I
Is Local
Office's
PLMN
long:[0..1]
0:false
1:true
R-I
Description
Remarks
Filling
Instructions
Shelf Config
Table 4-5 Shelf Config
Parameter
Name
4.1.4
Parameter
Value
Description
Remarks
Filling
Instruction
s
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
Managed
Element ID
long:[1..4095]
Primary
Key
Rack No.
long:[1..1]
Primary
Key
Shelf No.
long:[1..3]
Primary
Key
Shelf Type
long:[33,34]
33:ETCA V1
34:ETCA V2
Primary
Key
Master Shelf
Flag
long:[0..1]
0:Not Master Shelf

1:Is Master Shelf
R-W-I
Board Config
Table 4-6 Board Config
Parameter
Name
Parameter
Value
Description
Remarks
Modification
Indication
A,D,P
A:Add, D:Delete,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
rack/shelf/slot
string
eg:1/2/7
Primary
Key
Physical
Board Type
string
eg:UMP
R-I
Filling
Instructions
Parameter
Name
Logical Board
Type
Remarks
Description
string
eg:OMP
R-I
Module No.
string
It should be filled multi

module No.,if there are
multi modules on one
board.
eg:3;4;5
R-I
Backup Mode
long:[0,1,5]
0:No Backup
1:1+1 Backup
5:1TO1 Backup
R-I
long:[0..2]
0:PUBLIC
1:2G
2:3G
3:AG
R-I
long:[0..8]
0:INVALID
1:SDH-63E1
2:SDH-63T1
3:SDH-84T1
4:POS
5:ATM
6:E1
7:T1
8:Ethernet
R-I
Multiplex
structure of
the optical
port
long:[0..4]
0:INVALID
1:SDH AU-4
2:SDH AU-3
3:SONET STS-1
4:SONET STS-3C
R-I
PCM Map
Type
long:[0,1,255]
0:ITUT-G.707 type
1:Tributary type
255:Invalid
long:[0,1,4,6]
0:Multi-Frame
1:Double Frame
4:Multi-Frame with
checked
6:Forced MultiFrame(default value)
It can be empty.
E1
Impedance
long:[0,1,3]
0:75(default value of
Electric E1)
1:120
3:Invalid(default value
of Channelized E1)
It can be empty.
Cable Type of
Ethernet Port
long:[2,3]
2:Fiber(default value)
3:Cable
Mode Type
Port Type
E1 Frame
Type
Use Scene of
2G CRP
Board
24
Parameter
Value
long:[0,1,2]
It is valid for GSM

mode type.
0:Invalid
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
1:TDMA
2:IPA
4.1.5
Global Info
Table 4-7 Global Info
Parameter
Name
Parameter
Value
Description
Modification
Indication
A,M,P
A:Add, M:Modify,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
IP Segment
ReAssemble
Default Unit
string
eg:rack/shelf/slot
R-W
The First IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Second
IP Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Third IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Fourth
IP Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Fifth IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Sixth IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Seventh
IP Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
4.1.6
Interface IP
Table 4-8 Interface IP
Parameter
Name
26
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User Label
string
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Interface
Board
string
eg:rack/shelf/slot
Primary
Key
Module No.
long:[1..127]
It is usually filled with

1. For virtual port, fill in
the actual module No.
Primary
Key
Port Type
long:[0,1,2]
0:Interface
1:Loopback port
2:Virtual port
Primary
Key
Interface
Local Port
No.
long:[0..128]
0:invalid,
1~4:real port,
1~128:loop port
1~244Interface(ATM
port)
Primary
Key
VLAN
Sequence
long:[0..4095]
0 is invalid
Primary
Key
Vlan ID
long:[0..4095]
0 is invalid.
It is valid when it is sub
interface.
R-W-I
VPN ID of
sub port
long:[0..254]
0 is invalid
R-W-I
MAC
address
string
eg:
xx-xx-xx-xx-xx-xx
R-W
IP address of
interface
ipv4
eg:
xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
R-W-I
Mask Length
of interface
IP
long:[0..32]
eg:24;24
R-W-I
4.1.7
Service IP
Table 4-9 Service IP
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Service IP
ipv4
eg:
xxx.xxx.xxx.xxx
Primary
Key
string
Bit0=1:A Interface of
GSM Network
Bit1=1:Abis PS
Interface of GSM
Network
Bit2=1:Abis CS
Interface of GSM
Network
Bit3=1:Gb Interface of
GSM Network
string
Bit0=1:Iub Interface of
3G Network
Bit1=1: Iur Interface of
3G Network
Bit2=1: IuCS Interface
of 3GNetwork
Bit3=1: IuPS Interface
of 3G Network
Bit4=1:Iub Common
Interface of 3G
Network (for CCIU)
Bit5=1:Preconfiguratio
n IuB Interface of 3G
Network
string
Bit0=1:IuCS Interface
of HNB GW Network
Bit1=1:IuPS Interface
of HNB GW Network
Bit2=1:IuhCS Interface
of HNB GW Network
Bit3=1:IuhPS Interface
of HNB GW Network
Bit4=1:HenbS1
Interface of HeNB GW
Network
Bit5=1:MmeS1
Interface of HeNB GW
Network
Application
Type of IP
address(2G)
Application
Type of IP
address(3G)
Application
Type of IP
address(AG)
Parameter
Name
VPN ID of
sub port
PLMN info of
Service IP
4.1.8
Parameter
Value
Remarks
Description
long:[0..254]
0 is invalid
R-I
string
eg:
MCC1:MNC1;MCC2:M
NC3
or 65535:65535,
65535:65535 denotes
supporting all PLMN
R-W-I
Filling
Instructions
CCIU Service Config

Table 4-10 CCIU Service Config
Parameter
Name
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,P
A:Add, D:Delete,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
string
Data Format(Iub
Common Interface):
x.xxx.xxx
Primary
Key
string
Data Format(Iub
Preconfiguration):
x.xxx.xxx
Primary
Key
Service IP
Address of
CCIU SLAVE
Service IP for
Preconfigurat
ion Iub
Interface
4.1.9
Parameter
Value
UCIU IP Combination Type

Table 4-11 UCIU IP Combination Type
Parameter
Name
Description
Remarks
Modification
Indication
A,D,P
A:Add, D:Delete,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary Key
string
Data Format:
binary mode, 5 bits
in total: xxxxx
Bit0=1:Iub Interface
of 3G Network
Primary Key
Interface
Type
Combination
1 of Service
IP
28
Parameter
Value
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Bit1=1:Iur Interface
of 3G Network
Bit2=1:IuCS
Interface of 3G
Network
Bit3=1:IuPS
Interface of 3G
Network
Bit4=1:Preconfigura
tion IuB Interface of
3G Network
The PLMN
Combination
for "Interface
Type
Combination
1 of Service
IP"
Interface
Type
Combination
2 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
2 of Service
IP"
Interface
Type
Combination
3 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
3 of Service
IP"
string
string
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
eg:
If this parameter is
not configured, it
means all PLMNs
are supported.
If the system
supports only one
PLMN, fill in either
the exact PLMNID
or nothing.
Data Format:
binary mode, 5 bits
in total: xxxxx
Primary Key
Primary Key
string
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Primary Key
string
Data Format:
binary mode, 5 bits
in total: xxxxx
Primary Key
string
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Primary Key
Filling
Instructions
Parameter
Name
Interface
Type
Combination
4 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
4 of Service
IP"
Interface
Type
Combination
5 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
5 of Service
IP"
Parameter
Value
string
string
string
string
Description
Remarks
Data Format:
binary mode, 5 bits
in total: xxxxx
Primary Key
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Data Format:
binary mode, 5 bits
in total: xxxxx
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Filling
Instructions
Primary Key
Primary Key
Primary Key
IPINTFTYPE 1-5:
The five IPINTFTYPE parameters show the interface types supported by the service IPs
allocated to each Slave and the corresponding interface combinations. Each RNC
occupies one record in the template.
Refer to the following examples:
1.
IPINTFTYPE1=11111,IPINTFTYPE2~IPINTFTYPE5=0: The interfaces share an IP

and support the pre-configuration of the Iub interface.
2.
IPINTFTYPE5=0: Each interface uses an independent IP and does not support the
pre-configuration of the Iub interface.
3.
IPINTFTYPE5=0: Iub and Iur share an IP, and IuCs and IuPs share an IP, and preconfiguration of iUb is not supported.
Restriction: Check whether the interface types involved are conflicted with each other,
i.e., after the AND operation is performed to every two of IPINTFTYPE1~ IPINTFTYPE5,
the value of the five bits should not be "1."
PLMNCOMBTYPE 1-5:
30
The PLMN combinations corresponding to IPINTFTYPE 1-5.

If different PLMNs use different IPs, separate the IPs with ";". If different PLMNs share
IPs, separate the IPs with @.
When filling in PLMNCOMBTYPE, fill in all the PLMN IDs supported by the NE.
Because an RNC supports four PLMNs at most, we use 1, 2, 3, and 4 to represent four
PLMN IDs respectively.
Suppose an NE supports four PLMNs, and PLMN 1 and PLMN 2 share an IP, PLMN 3
and PLMN 4 use two independent IPs, this parameter should be set to "1@2;3;4."
If this parameter is not configured, it means all PLMNs are supported.
If the system supports only one PLMN, fill in either the exact PLMNID or null.
Restriction: If the value of PLMNCOMBTYPE is not 0, either fill in null or fill in 1, 2, 3,
4" and make sure the PLMN IDs filled in are not repeated. For all non-0
PLMNCOMBTYPEs, the number of PLMNs must be consistent with PLMN IDs, but
PLMNID does not need to match PLMNCOMBTYPE.
4.1.10
Slave or Dsp Service Config

Table 4-12 Slave or Dsp Service Config
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,P
A:Add, D:Delete, P:Pass

Applicable to UMTS
Supports only D:Delete and
P:Pass
Does not support A:Add
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
string
Data Format:
RACK/SHELF/SLOT,
2G: CRP or ETCB or EDTB
or ESDTB board,
3G: 0/0/0. Don't assign IP
resource by board for 3G.
Primary
Key
string
Data Format:
xxx.xxx.xxx.xxx;xxx.xxx.xxx
.xxx;xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
Primary
Key
Data Format(Iub
Preconfiguration):
Primary
Key
Board Info
Service IP
Address of
SLAVE
Service IP
for
string
Parameter
Name
Parameter
Value
Preconfigur
ation Iub
Interface
4.1.11
Remarks
Description
Filling
Instructions
xxx.xxx.xxx.xxx;xxx.xxx.xxx
.xxx
Channel Port
Table 4-13 Channel Port
Parameter
Name
4.1.12
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Channel
Group ID
long:[1..16]
Primary
Key
VLAN
Sequence
long:[0..4095]
0 is invalid
Primary
Key
Vlan ID
long:[0..4095]
0 is invalid.
It is valid when it is sub
interface.
R-W-I
Bound Mode
long:[3..5]
3:on Mode
4:backup Mode
5:802.3AD Mode
R-W-I
VPN ID of
sub port
long:[0..254]
0 is invalid
R-W-I
MAC
address
string
eg:
xx-xx-xx-xx-xx-xx
R-W
IP address of
interface
ipv4
eg:
x.xxx.xxx
R-W-I
Mask Length
of interface
IP
long:[0..32]
eg:24;24
R-W-I
Member Port
Table 4-14 Member Port
Parameter
Name
Modification
32
Parameter
Value
A,D,M,P
Description
A:Add, D:Delete,
Remarks
Filling
Instructions
Parameter
Name
Parameter
Value
Indication
Remarks
Filling
Instructions
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Member port
ID of
Channel
Group
long:[1..128]
Primary
Key
Interface
Board
string
eg:rack/shelf/slot
R-I
Local port
No. of
member port
long:[1..4]
R-I
Channel
Group ID
long:[1..16]
R-I
Bounding
mode of
member port
long:[1..4]
1:active
2:passive
3:on
4:backup
R-W-I
System
Priority of
LACP
protocol
long:[1..65535]
The default value is

32768.
R-W
long:[0..1]
0:long time,
1:short time,
The defaulte value is
0.
R-W
Timeout Type
of LACP
protocol
4.1.13
Description
Super Vlan
Table 4-15 Super Vlan
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Supervlan ID
long:[1..16]
Primary
Key
Switch of
inner-route
function
long:[0..1]
0:Closed
1:Open
R-W-I
Parameter
Name
MAC
address
4.1.14
Parameter
Value
Remarks
Description
string
eg:
xx-xx-xx-xx-xx-xx
R-W
IP address of
Super Vlan
Interface
ipv4
At most 4 IP for one

port.
eg:xxx.xxx.xxx.xxx;xxx.
xxx.xxx.xxx
R-W-I
Mask Length
of interface
IP
long:[0..32]
eg:24;24
R-W-I
VPN ID of
port
long:[0..254]
0 is invalid
R-W-I
Filling
Instructions
Super Vlan Member

Table 4-16 Super Vlan Member
Parameter
Name
Remarks
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
string
eg:rack/shelf/slot.
When Vlan Sub
Interface of Ethernet
Port joins to supervlan,
this parameter should
be filled in the EGPB
board.
When Vlan Sub
Interface of Channel
Group joins to
supervlan,
this parameter should
be filled in 0/0/0.
Primary
Key
Interface
Board
Real Port
No.
34
Parameter
Value
long:[1..16]
When Vlan Sub

Interface of Ethernet
Port joins to supervlan,
LOCALPORT is
Ethernet Port No.
When Vlan Sub
Interface of Channel
Group joins to
supervlan,
LOCALPORT is
Filling
Instructions
Primary
Key
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Channel-group ID.
4.1.15
VLAN
Sequence
long:[1..4095]
It is the sub interface

of the super vlan
member.
Primary
Key
Supervlan
ID
long:[1..16]
Quote Super VLAN
R-I
DHCP Server
Table 4-17 DHCP Server
Parameter
Name
Parameter
Value
Description
Remarks
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
DHCP
Server
Object ID
long:[1..2800]
Unique in ME
Primary
Key
Type of
DHCP
Server
Address
long:[0..2]
0:DHCP Server IP
Address-Inner
Controller
1:DHCP Server IP
Address-Outer
Controller
2:DHCP Server BoardLogical Address
Module No.
long:[1..127]
It is valid if
DHCPSVRIPTYPE=2.
R-W
DHCP
Server IP
Address
ipv4
It is valid if
DHCPSVRIPTYPE=0
or 1.
R-W
Mask
Length of
DHCP
Server IP
Address
long:[0..32]
It is valid if
DHCPSVRIPTYPE=0
or 1.
R-W
VPN ID of
Port
long:[0..254]
It is valid if
DHCPSVRIPTYPE=0.
The default value is 0.
R-W
R-W-I
Filling
Instructions
4.1.16
DHCP Client
Table 4-18 DHCP Client
Parameter
Name
36
Parameter
Value
Remarks
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Client
Number
long:
[1..2800]
Unique in ME
String
R-W-I
Hardware
Address
String
eg:
xxx.xxx...xxx.xxxx(leng
th is 16)
R-W-I
Client
Identity
String
eg:
xxx.xxx...xxx.xxxx(leng
th is 16)
R-W-I
Client
Identity
ipv4
eg:
xxx.xxx.xxx.xxx
R-W-I
Mask Length
of DHCP
Client IP
Address
long:[0..32]
32 is recommended
R-W-I
DHCP Client
Host Name
String
1 to 128 characters of
ASCII, the same as
vendor class of Node
B
R-W
DHCP
Server
Object ID
long:
[1..2800]
DHCP
Server
Identity(Interf
ace IP)
ipv4
It must be the interface

IP.
R-W-I
RNC OAM IP
Address to
NodeB
ipv4
eg:
xxx.xxx.xxx.xxx
R-W-I
DHCP
Gateway IP
Address
ipv4
eg:
xxx.xxx.xxx.xxx
R-W-I
Quote DHCP Server
Primary
Key
1 to 16 characters of
ASCII, the same as
vendor class of Node
B
Vendor Class
Identity of
DHCP Client
Filling
Instructions
R-W-I
4.1.17
DHCP Relay
Table 4-19 DHCP Relay
Parameter
Name
Parameter
Value
Description
Remarks
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
DHCP Relay
Object ID
long:[1..2800]
IP interface
board
Real Port
No.
Unique in ME
Primary
Key
string
eg:rack/shelf/slot
It must be EGPB
board info if DHCP
relay port is real port
or sub interface of real
port.
Others, it can be filled
in 0/0/0.
R-I
long:[0..4]
0 is invalid.
It is valid only if DHCP
relay port is real port
or sub interface of real
port.
R-I
0 is invalid.
Channel
Group ID
long:[0..16]

relay port is channel
port or sub interface of
channel port.
R-I
long:[0..4095]
0 is invalid.
relay port is sub
interface of real port or
sub interface of
channel port.
R-I
Relay IP
Address
ipv4
It must be the interface

IP address of DHCP
relay port.
It can be the supervlan
interface IP address if
the DHCP relay port is
sub interface..
R-W-I
Mask Length
of Relay IP
Address
long:[0..32]
It must be the mask

length of the relay IP
address.
R-W-I
VLAN
Sequence
Filling
Instructions
Parameter
Name
DHCP
Server
Object ID
4.1.18
Parameter
Value
Remarks
Description
long:[1..2800]
Quote DHCP Server
Filling
Instructions
R-W-I
VRF Attributes Config

Table 4-20 VRF Attributes Config
Parameter
Name
38
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
VPN Name
string
no more than 30
characters
VPN ID of
Port
long:[1..254]
Route
Distinguisher
Type
long:[1,2]
1:ASN:nn format,
2:IP-address:nn format
R-W-I
Route
Distinguisher
Value
string
If the RD TYPE is
"ASN:nn", the format of
RD VALUE is (165535):(04294967295).
If the RD TYPE is "IPaddress:nn", the
format of RD VALUE is
(0.0.0.0255.255.255.255): (065535)
R-W-I
VRF
description
information
string
no more than 80
characters
R-W
R-W-I
Primary
Key
4.1.19
VRF Route Target

Table 4-21 VRF Route Target
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
VPN Name
string
no more than 30
characters
VPN ID of
Port
long:[1..254]
Target-VPN
community
long:[2,3]
2:Export
3:Import
Primary
Key
VRF Route
Target Type
long:[1,2]
1:ASN:nn format,
2:IP-address:nn format
Primary
Key
string
If the RT TYPE is
"ASN:nn", the format
of RT VALUE is (165535):(04294967295).
If the RT TYPE is "IPaddress:nn", the
format of RT VALUE is
(0.0.0.0255.255.255.255): (065535)
Primary
Key
VRF Route
Target
Value
R
Primary
Key
4.2
TransportNetwork Template
4.2.1
Local Office
Table 4-22 Local office
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Parameter
Name
Parameter
Value
Description
Net type of
local office
long:[1..255]
When the Controller has

only one signaling point,
NET1 is recommended.
When the RNC has more
than one signaling point,
the values are used in
sequence.
Primary
Key
Whether to
enable
network
appearance
long:[1,2]
1:Enable
2:Disable
R-W-I
Network
appearance
long:
[0..42949672
95]
Default value is 0 if this

parameter cant be
configured.
It is valid when
NETAPPEARANCEFLAG
=1.
R-W
14-bit
signalling
point code
of local
office on
the net
long:
[0..16383]
This is an interconnection
parameter, so the peer
must be identical to the
local setting.
R-W-I
24-bit
signalling
point code
of local
office on
the net
long:
[0..16777215
]
parameter, so the peer
must be identical the local
setting.
R-W-I
Mode Type
long:[0,1]
0:2G
1:3G (UMTS, AG)
R-I
ATM
Address
string
20 Bytes, decimal.
parameter.
GSM doesn't need to
config.
R-W
Network
Resource
Identifier Bit
Num in CS
Domain
long:[0..10]
It is valid just for UMTS,

and the default value is 0.
R-W
Network
Resource
Identifier Bit
Num in PS
Domain
long:[0..10]
It is valid just for UMTS,

and the default value is 0.
R-W
BSC ID
40
long:
[1..4095]
Remarks
It should be filled when

Managed Element is GU
mode, and BSCID !=
MEID.
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
Other, it can be empty.
4.2.2
Static Route
Table 4-23 Static route
Parameter
Name
Parameter
Value
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
It contains no more than

80 characters.
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Static
Route
Number
long:[1..5000]
Unique in ME
Primary
Key
ipv4
This field is configured to

the destination IP
address, that is, the
expected destination IP
network prefix. This prefix
cannot start with 0, 127,
224 to 239, or 240 to 255.
When configuring it on
the Controller, we should
use the prefix of the
address at the Controller
side.
R-W-I
Static route
network
mask
length
long:[8..32]
This field refers to the

mask of the destination
network number. The
network prefix and
network mask must
match each other, and the
result of NOT mask AND
prefix must be 0
(ip&~mask = 0).
R-W-I
Route next
hop
address
ipv4
The Next Hop IP Address

is the address the
Controller needs to reach.
R-W-I
VPN ID of
sub port
long:[0..254]
0 is invalid
R-W-I
long:[1..254]
In the multi-route case,

the smaller the
management distance,
R-W-I
Static route
network
prefix
Route
distance
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
the higher the priority. If

there is only one route
that can reach the same
destination network
address, the default value
1 should be used.
The flag if
bfd is
enabled
4.2.3
long:[0..1]
0:unactived
1:actived
R-W-I
IP Path Group
Table 4-24 IP Path Group
Parameter
Name
Remarks
Description
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Path Group
Id
long:
[0..4095]
Unique in ME.
Father Path
Group Id
long:
[0..65535]
65535 is invalid, other

value must be in [0..4095]
R-I
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
AG:3..31
Support to modify the
module No. of path group
for Iu interface.
R-W-I
Path Group
Bear Type
long:[2,5]
2:ETHERNET_NOVLAN
5:ETHERNET_VLANTAG
R-W-I
PLMN
Group
Object ID
sequence<lo
ng,4>
eg:1;2
R-I
Ratio of
occupied
private
bandwidth
of Path
Group by
operator
sequence<lo
ng,4>
0 to 1000
If more than one
MCC/MNC, separate
each value by ';'
R-W-I
long:
Configure the actual
R-W-I
Forward
bandwidth(
42
Parameter
Value
Primary
Key
Parameter
Name
4.2.4
Parameter
Value
Description
kbps)
[0..4294967]
physical bandwidth.
Backward
bandwidth(
kbps)
long:
[0..4294967]
Configure the actual

physical bandwidth.
Remarks
Filling
Instructions
R-W-I
IUB Office
Table 4-25 IUB Office
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
A,D,M,S,P
A:Add, D:Delete,
M:Modify,
S:Swap,
P:Pass
User label
string

80 characters.
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
ATM/ATM+IP:101 to 999,
IP/IPOE:1001 to 3999
Primary
Key
Net
Element ID
long:
[1..65534]
Depend on the real

situation.
R-I
sequence<lo
ng,4>

filled when the
modification indication is
A(Add) or M(Modify),but it
doesn't support the
modifying operation.
PLMN ID:
[0..4294967295], eg:1;2
R-M-I
CMP
Module No.
long:[3..31]
Each Node B must be

homed to one CMP for
processing. In principle, it
is required that the
geographically adjacent
Node Bs should be
processed by the same
CMP module whenever
possible.
R-W-I
Config for
Bear Type
of Service
in IUB
long:[0,1,2]
0: ATM
1: IP
2: ATM+IP
R-I
Modification
Indication
PLMN
Group
Object ID
Parameter
Name
Remarks
Description
Config for
Bear Type
of NBAP in
IUB
long:[0,1,2]
0: ATM
1: IP
2: ATM+IP
R-I
Config for
Bear Type
of
Common
Channel in
IUB
long:[0,1,2]
0: ATM
1: IP
2: ATM+IP
R-I
long:[0..2]
0: Protection OFF
1: Support multipath
protection
2: Support ATM+IP
protection
R-W-I
Transport
Qos Profile
Type
long:[1..2]
1: QoS(according to
ARP/THP/TC)
2: QoS(according to
service type)
The default value is 2 if
this parameter is empty.
R-W
Subsystem
of RUP
long:
[1,2,3,255]
The recommended value

is 255.
R-W-I
ATM
address of
adjacent
office
string
20 Bytes, decimal
R-W
NodeB
Inner IP
ipv4
Configure this parameter

only when IP SEC is
used.
R-W-I
ipv4
It must be unique if it is
valid(not 0.0.0.0).
It can be configured under
multipath protection.
R-W-I
long:[1..255]
1:ATM+IP Transport,
2:Only IP Transport.
It cant be filled when it is
only ATM transport.
System will configure it
according office's bear
type when it is empty.
This parameter is valid if
UPQOSMAPTYPE= 1.
R-W
Switch of
IUB
multipath
protection
OMCB
Inner
Service Ip
Address
Profile ID of
Transport
Bearer
Type Profile
Related to
Basic
Priority
Transport
Qos Profile
parameter
Index
44
Parameter
Value
long:[1..32]
1:One or Two IP Paths,

2:Three IP Paths,
3:One ATM Path and Two
IP Paths,
4:ATM Paths,
5:One IPOE Path and
One IP Path,
Filling
Instructions
R-W
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
6:One ATM and One IP

Path.
This parameter is valid if
UPQOSMAPTYPE=2.
Single Path Scene:
1)ATM, default valued is
4;
2)IPoFE, default valued is
1;
3)IPoE1, default valued is
1.
Multi Path Scene:
1)ATM Multi Path, default
valued is 4;
2)IP Multi Path, default
valued is 5;
3)ATM+IP, default valued
is 6;
4)IPoE1+IPoFE, default
valued is 5.
4.2.5
ATM Bearer(IUB Auto)

Table 4-26 ATM Bearer(IUB Auto)
Parameter
Name
Parameter
Value
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:[1..4095]
Quote ANEID of "IUB

Office" sheet.
Primary
Key
Destination
IP address
ipv4
Depend on the real

situation.
R-W-I
Destination
IP Address
Mask
Length
long:[0..32]
It is the mask length of

the destination IP
address.
R-W-I
OMCB Path
priority
long:[1..3]
It should be configured
when IUB office is
multipath production.
R-W
Path Group
long:[0..4095]
R-I
Parameter
Name
Parameter
Value
Id
Filling
Instructions
is the same as ANEID.
Atm
Interface
Board
string
It must be the EDTA or

ESDTA board info.
eg:rack/shelf/slot
R-W-I
E1 List
string
e1 index, separated by ";"
R-W-I
Iub Plan
long:[1..2]
1:Normal,
2:High load
R-I
long:[1..20]
If this parameter is empty,

it will be configured by the
default template.
The number of UBR Aal2
PVC by user defined
cannot be less than the
number of default
template.
R-W
The
number of
UBR Aal2
PVC
4.2.6
Remarks
Description
ATM Bearer(IUB)
Table 4-27 ATM Bearer(IUB)
Parameter
Name
46
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete, M:Modify,

P:Pass
User label
string
It contains no more than 80

characters.
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
Quote ANEID of "IUB

Office" sheet.
PVC ID
long:
[1..12600]
The recommended value is

1 to 10000.
Unique in ME.
Primary
Key
Atm
Interface
Board
string
It must be the EAPB board

info.
eg:rack/shelf/slot
R-I
ATM
Optical Port
long:[1..4]
R-I
VPI on
High End
long:
[0..4095]
For the external

CVPI/CVCI, this is unique
in the office and must be
identical to the value of the
connected office. It is
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
recommended to use a
value smaller than or equal
to 4.
VCI on
High End
long:
[32..65535]
For the external

identical to the value of the
connected office. It is
value smaller than or equal
to 256.
PVC
Service
Type
long:[0,2,4]
0: AAL5 signal
2: AAL2 user data
4: OMCB
R-W-I
R-I
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
CBR supports:
atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3),
atmNoClpNoScr(1)
atmClpTransparentNoScr(8
),
atmNoClpNoScrCdvt(11).
Service
Category
long:[0,1,2,4]
rtVBR and nrtVBR support:

atmNoClpNoScr(1),
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt(
13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
R-W-I
UBR supports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCdvt(11),
atmNoClpTaggingNoScr(10
).
Traffic Type
long:[0..15]
0: NOTRF
1: atmNoClpNoScr
2: atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
atmClpTransparentNoScr
9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
atmClpNoTaggingScrCdvt
14: atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell
rate for
CLP=0+1
(PCR0+1)
Peak cell
rate for
CLP=0
(PCR0)
Cell delay
variation
tolerance
(CDVT)
Sustainable
cell rate for
CLP=0
(SCR0)
Sustainable
cell rate for
CLP=0+1
(SCR0)
48
long:
[0..18210661
33]
Unit: Kbps.
This Traffic Para supports
all Service Category and all
Traffic Type.
R-W-I
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
CBR ,rtVBR and nrtVBR.
Traffic Type:
atmClpTaggingNoScr(3).
R-W
long:
[0..42949672
95]
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
(8),
atmNoClpNoScrCdvt (11),
).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
13),
atmClpTaggingScrCdvt(14).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
R-W
Parameter
Name
Parameter
Value
Description
Remarks
atmNoClpScr(4).
Maximum
burst cell
number
(MBS)
long:
[0..42949672
95]
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
13),
atmNoClpScr(4).
Path Group
Id
long:
[0..4095]
The recommended value is

the same as ANEID.
TrPath ID
sequence<lo
ng,4>
For one PLMN, the value

range of TrPath ID is
[32..127].
As the path ID of the AAL2
channel, this is globally
unique and starts with 32
for the ATM office.
AAL2 Path
ID intra
office
long:
[1..42949672
95]
As an interconnection
parameter, this number
must have the same
configuration as the peer
office.
long:[0..1]
0:Local End
1:Peer End
If Local Office is configured,
the AAL2 PATH ID will be
allocated in the ascending
order.
If Adjacent Office is
configured, the AAL2 PATH
ID will be allocated in the
descending order.
For two interconnected
RNCs, one end should be
configured as the Local
Office, while the other as
the Adjacent Office.
AAL2 Path
Ownership
AAL2 Path
Service
Type
long:[10..14]
10:RT
11: NRT1
12: NRT2
13: NRT3
14: MIX
RT: for bearing real-time
service,
NRT1: for bearing R99 nonreal-time service,
R-W
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
NRT2: for bearing HS nonreal-time service,

MIX: for bearing all types of
service.
4.2.7
Application
Type of UNI
Link
long:[1..3]
1: ALCAP
2: NBAP(NCP)
3: NBAP(CCP)
Destination
IP address
ipv4
Depend on the real

situation.
R-W
Destination
IP Address
Mask
Length
long:[0..32]
It is the mask length of the

destination IP address.
R-W
OMCB
Path
priority
long:[1..3]
when IUB office is multipath
production.
R-W
SCTP Config(IUB-ABIS)
Table 4-28 SCTP Config(IUB-ABIS)
Parameter
Name
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..65535]
Quote ANEID of "IUB

Office" sheet.
Primary
Key
Association
ID
long:
[1..8400]

for UMTS is:
1)IP: ANEID+1000,
2)IPOE: ANEID+1000,
3)IP+IPOE:
IP=ANEID+1000,
IPOE=ANEID+4000
Primary
Key
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
R-I
Local port
50
Parameter
Value
long:
[1..65535]
This is the port number of

the associated local end,
and must be the same as
the Peer-End Port No.
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
configured for the

associated peer end.
ipv4
This is the Controller

signaling plane IP
address.
It can be filled in one IP
address.
R-W-I
long:
[1..65535]

the associated peer end,
the Local-End Port No.
configured for the
R-W-I
Remote IP
address
ipv4
This is the service IP

address of the Site.
It can be filled in one IP
address.
R-W-I
SCTP
association
bearer
protocol
type
long:[15,21]
15:NBAP (3G)
21:IPABIS (2G)
R-I
Max
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:500
R-W
Min
Retransmis
sion
Timeout(10
millisecond)
long:
[10..1000]
default value:50
R-W
Initial
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:100
R-W
Heartbeat
Interval(10
millisecond)
long:
[10..6000]
default value:500
R-W
Delayack
interval(10
millisecond)
long:[0..20]
default value:20
R-W
Local IP
address
Remote
port
Filling
Instructions
4.2.8
IP Bearer(IUB)
Table 4-29 IP Bearer(IUB)
Parameter
Name
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
Quote ANEID of "IUB

Office" sheet.
Primary
Key
TrPath ID
long:[0..7]
This ID is unique in the

office.
Primary
Key
Path Group
ID
long:
[0..4095]

is 1001 to 3999.
PLMN
Group
Object ID
long:
[0..42949672
95]
Destination
IP address
ipv4
Depend on the real

situation.
Destination
IP Address
Mask
Length
long:[0..32]
It is the mask length of the

destination IP address.
long:
[0..4294967]
The bandwidth ratio of

TrPath reserved for
signalling must be less
than a specific value, and
the specific value is the
maximum of one third of
the minimum of Tx
bandwidth and the Rx
bandwidth, and
64000bps.
R-W-I
long:
[0..4294967]

TrPath reserved for
the minimum of Tx
bandwidth, and
64000bps.
R-W-I
Path Tx
Band width
of Trpath
(kbps)
Path Rx
Band width
of Trpath
(kbps)
52
Parameter
Value
Parameter
Name
4.2.9
Parameter
Value
Remarks
Description
IP Domain
No.
long:
[0,21,22,23]
0:Invalid,
21:IP Domain No.1,
22:IP Domain No.2,
23:IP Domain No.3
It should be configured to
effective value (21,22,23)
when IUB office is
OMCB Path
priority
long:[1..3]
when IUB office is
R-W
R-W
Filling
Instructions
IPOE Bearer(IUB)
Table 4-30 IPOE Bearer(IUB)
Parameter
Name
Parameter Value
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,
P:Pass
User label
string
It contains no
more than 80
characters.
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:[1..4095]
Quote ANEID of
"IUB Office"
sheet.
Primary
Key
string
rack/shelf/slot
It must be the
EDTI or ESDTI
board info for
IPOE bear type.
R-W
MP Port
No.
long:[0..120]
0:ppp
[1..512]:Mp
When it is MultiPPP link,
LOCALPORT is
usually not filled,
can be auto
generated by
system.
E1/T1 List
string
Separated by ";"
R-W
E1/T1 TS
string
Separated by ";"
R-W
Board Info
of IPOE
Description
Remarks
Filling
Instructions
Parameter
Name
Description
Remarks
List
and "-"
Path Group
ID
long:[0..4095]
The
recommended
value is 1001 to
3999.
R-I
TrPath ID
sequence<long,4>
TrPath ID :[0..7]
eg:0;1
Primary
Key
Destination
IP address
ipv4
Depend on the
real situation.
R-W-I
long:[0..32]
It is the mask
length of the
destination IP
address.
R-W-I
long:[0,21,22,23]
0:Invalid,
21:IP Domain
No.1,
22:IP Domain
No.2,
23:IP Domain
No.3
It should be
configured to
effective value
(21,22,23) when
IUB office is
multipath
production.
R-W
long:[1..3]
It should be
configured when
IUB office is
multipath
production.
R-W
Destination
IP Address
Mask
Length
IP Domain
No.
OMCB Path
priority
4.2.10
Parameter Value
Filling
Instructions
SCTP Config(ABIS)
Related to GSM network.
4.2.11
IP Bearer(ABIS)
54
4.2.12
Adjacent Office(CN)
Table 4-31 Adjacent Office(CN)
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]

for UMTS is 1 to 99.
Primary
Key
Adjacent
Office ID
long:
[1..2048]

for UMTS is the same as
ANEID.
R-I
Net
Element ID
sequence<lo
ng,8>
Mgw Id:[4096..65535],
Mscserver Id:[0..4095],
Sgsn Id:[0..4095],
Rnc Id[1..4095],
BSC Id:[1..4095],
SAS Id:[0..65535],
SMLC Id:[0..65535].
1)When the mode type is
UMTS or AG and the
office type is
MGW+MSCSERVER, the
number of NEID must be
double of the number of
PLMNID.
This parameter notes
NEID of MGW office and
NEID of MSCSERVER
office, such as
MgwId1;MscsId1;MgwId2;
MscsId2 .
When the mode type is
UMTS and the office type
is SAS, the number of
NEID must be 1.
Under other office type,
the number of NEID must
be equal to the number of
PLMNID.
2)When the mode type is
GSM, the number of NEID
must be 1.
R-I
PLMN
sequence<lo
R-M-I
Parameter
Name
Group
Object ID
ng,4>
Mode Type
long:[2,3,6]
Remarks
Description
2:UMTS
3:GSM
6:AG
R-I
long:
[16,32,64,51
2,576,1023,4
096,32768]
R-I
Bear type
long:[0..2]
0: ATM (3G)
1: IP
2: TDM (2G)
(Parameters can't be
modified)
When 2G office is
RNC,SRVBRSTYPE must
be 1.
R-I
Encode
type of
signalling
point
long:[14,24]
14:SPC 14 bits,
24:SPC 24 bits
R-W-I
Destination
point code
long:
[0..16777215
]
14 bits:0..16383
24 bits:0..16777215
R-W-I
SubService
Field
long:
[0,4,8,12]
Filling
Instructions
filled when the

modification indication is
A(Add) or M(Modify),but it
doesn't support the
modifying operation.
PLMN ID:
[0..4294967295], eg:1;2
2G office:
32:RNC
64:MGW
576:MGW+MSCSERVER
1023:SMLC
3G office:
16:BSC
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
32768:SAS
AG Office:
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
Type of
adjacent
office
56
Parameter
Value
0: International SPC,
international network, with
a code of 0x00H in the
signaling.
4: Reserved international
SPC, reserved
international network, with
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
a code of 0x04H in the

signaling.
8: National SPC, national
network, with a code of
0x08H in the signaling.
12: Reserved National
SPC, reserved national
network, with a code of
0x0CH in the signaling.
Fill in this field according
to the real situation.
Connection
relationship
with local
signalling
point
long:[1..3]
1:Associated
2:Quasi-associated
3:No connection
This field identifies
whether the local office
and the adjacent office
are directly associated or
quasi-associated in terms
of signaling relation.
Associated Mode means
there are directly
connected signaling links
between the local office
and the adjacent office.
Quasi-associated Mode
means there is no directly
connected signaling link
between the local office
and the adjacent office,
and they need one
signaling transfer point or
more in between. If the
RNC and MSC are
connected through
transfer of the MGW,
Quasi-associated Mode
should be used.
Fill in this field according
to the real situation.
Whether to
support
broadband
properties
long:[0..1]
0:Not Support
1:Support
R-W-I
Protocol
type
long:[1..3]
1:CHINA
2:ITU
3:ANSI
R-W-I
ATM
address
string
20 bytes, separate each

byte with ".", decimal.
For UMTS or AG, it must
configure the ATM
address when creating
R-W-I
R-W
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
MGW/MGW+MSC/MSC/S
GSN NE type and the
bear type is ATM.
And the ATM address
must be full 0 for
MSC/SGSN NE type.
It is invalid for GSM and
can be empty.
Default
Office Flag
Capacity
Weight in
CS/PS
Domain
Number of
Network
Resource
Identifier in
CS/PS
Domain
58
sequence<lo
ng,4>
For one PLMN,

0:Is Not Default Office
1:Is Default Office,
For multi PLMNs,eg: 1;0.
It must have one and only
one default office in the
CS domain when the NE
type is MSCSERVER.
It must have one and only
one default office in the
CS domain when the NE
type is SGSN.
Valid in the case of
IUFLEX networking.
can be empty.
R-W
sequence<lo
ng,4>

range is [0..100].
For multi PLMNs, eg: 1;0.
IUFLEX networking. This
field is valid only when the
NE type is
MSCSERVER/SGSN, and
uses 0 invariably when
invalid, indicating
disabling of the IU FLEX
function of the
corresponding CN.
can be empty.
R-W
sequence<lo
ng,4>

range is [0..4].
For multi PLMNs, eg: 1;0.
IUFLEX networking. This
field is valid only when the
NE type is
MSCSERVER/SGSN, and
uses 0 invariably when
invalid.
It is invalid for GSM.
can be empty.
R-W
Parameter
Name
Network
Resource
Identifier in
CS/PS
Domain
4.2.13
Parameter
Value
string
Description
The value range of one
Network Resource
Identifier is [0..1023].
If there are two PLMNs,
the NUMOFNRI of
PLMN1 is 2 and the
NUMOFNRI of PLMN2 is
3,then NRILIST is
10;11@100;101;103.
IUFLEX networking.
parameter, this parameter
will appear in the
TMSI/PTMSI allocated to
the UE by the network.
can be empty.
Remarks
Filling
Instructions
R-W
SCTP Config(CN)
Table 4-32 SCTP Config(CN)
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]
Quote the Adjacent Office

ID of "Adjacent
Office(CN)" sheet.
Primary
Key
Association
ID
long:
[1..3000]
2G:1..2048
3G:1..3000
AG:1..3000
for UMTS is
1 to 1000.
Primary
Key
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
AG:3..31
R-W-I
Application
type of
association
long:[1..2]
1:Server
2:Client
For the two ends
associated, at least one
R-W-I
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
must serve as the Client.
long:
[1..65535]

the associated local end,
the Peer-End Port No.
configured for the
R-W-I
ipv4
It can be filled in four IP

address at most, such as
xxx.xxx.xxx.xxx;xxx.xxx.xx
x.xxx
R-W-I
long:
[1..65535]

the associated peer end,
the Local-End Port No.
configured for the
R-W-I
ipv4
It can be filled in four IP

address at most, such as
xxx.xxx.xxx.xxx;xxx.xxx.xx
x.xxx
R-W-I
ASP
Number
long:
[1..8400]
This is the ID number of

the application server.
One ASP corresponds to
one and only one SCTP
association, and one AS
can have up to 16 ASPs.
R-I
Max
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:500
R-W
Min
Retransmis
sion
Timeout(10
millisecond)
long:
[10..1000]
default value:50
R-W
Initial
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:100
R-W
Heartbeat
Interval(10
millisecond)
long:
[10..6000]
default value:500
R-W
Delayack
interval(10
millisecond)
long:[0..20]
default value:20
R-W
Local port
Local IP
Address
Remote
port
Remote IP
Address
60
4.2.14
M3uaAS Config(CN)
Table 4-33 M3uaAS Config(CN)
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]

ID of "Adjacent
Office(CN)" sheet.
Primary
Key
AS Number
long:[1..640]
Adopt the corresponding

AS ID number
Primary
Key
ASP
Number
sequence<lo
ng,16>
The value range of ASP

Number is 1..8400.
eg:1;2
R-W-I
long:[0..1]
0: FALSE
1: TRUE
Each group of values
indicates whether the
local end and the peer
end are configured with
routing context.
Select TRUE if one ASP
occurs to more than one
AS, or select FALSE
otherwise. In the
Controller, one ASP
usually occurs to one AS,
so it is unnecessary to
configure the routing
context ID.
R-W-I
long:
[0..4294967
295]
If one ASP occurs to more

than one AS, it is
necessary to specify
which AS this message
belongs to, that is, to
specify the routing
context. The routing
context is used as a
unique ID of an AS. The
invalid value is
4294967295.
R-W-I
Whether
exists
routing
context
Routing
context ID
Whether
exists peer
routing
long:[0..1]
0: FALSE
1: TRUE
R-W
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
context
long:
[0..4294967
295]
4294967295 is invalid
R-W
AS property
long:[1..5]
1: SGP,
2: ASP,
3: IPSP SERVER,
4: IPSP CLIENT,
5: DOUBLE EXCHANGE
MODEL
parameter, so when the
IUR and IU are
interconnected, note that
the two ends should be
configured respectively as
the IPSP Server and IPSP
Client. Be sure to
negotiate with the peer
end for consistency to
avoid configuration of
both ends as the IPSP
Server.
If DOUBLE EXCHANGE
MODEL is configured, the
local end and the peer
end are allowed to have
different routing contexts.
R-W-I
AS traffic
mode
long:[1..2]
Peer routing
context ID
62
1: Override,
2: Loadshare
N+K load sharing means
the multiple ASPs in one
AS are simultaneously in
the service state, so that
the messages can be
transmitted through the
ASPs in turn. The N value
indicates the minimum
number of ASPs that must
be activated before the
AS can be activated. The
K value makes little sense
now. Override means only
one ASP is in the service
state at certain time in
one AS, while other ASPs
are standing by and will
substitute when the ASP
in service breaks down.
Select NO during normal
running, or otherwise
select YES for the test
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
purpose.
value of N
value of K
4.2.15
long:[0..16]
It is OK to select the
default value, or as
required, make the AS
available only when
multiple ASPs are
activated.
R-W-I
long:[0..16]
With little sense, this

value is not used now,
and it is recommended to
configure it to the
difference between the
total number of the
associations and the N
value.
R-W-I
M3uaRoute
Table 4-34 M3uaRoute
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Route
Number
long:[1..640]
Unique in ME
Primary
Key
Route
range mode
long:[0..2]
0:natural sort
1:ikebana sort
2:handworked sort
R-W-I
AS1
Number
long:[1..640]
Quote AS Number of
"M3uaAS Config(CN)"
sheet.
R-W-I
AS2
Number
long:[0..640]
0 is valid
R-W-I
AS3
Number
long:[0..640]
0 is valid
R-W-I
AS4
Number
long:[0..640]
0 is valid
R-W-I
4.2.16
M3uaRouteSet
Table 4-35 M3uaRouteSet
Parameter
Name
4.2.17
Parameter
Value
Remarks
Description
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Adjacent
Office ID
long:[1..2048]
Quote the Adjacent

Office ID of "Adjacent
Office(CN)" sheet.
Primary
Key
Route ID 1
long:[1..640]
Quote the Route Number

of "M3uaRoute" sheet.
R-W-I
Route ID 2
long:[0..640]
0 is valid
R-W-I
IP Path(CN)
Table 4-36 IP Path(CN)
Parameter
Name
64
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
Quote ANEID of "Adjacent

Office(CN)" sheet.
Primary
Key
Path ID
long:[0..7]

office.
Primary
Key
Path Group
ID
long:
[0..4095]
This is a globally unique

ID.
for UMTS is
4001 to 4095.
Primary
Key
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
AG:3..31
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
PLMN
Group
Object ID
long:
[0..42949672
95]
Quote the PLMN Group

Object ID of "Plmn
Config" sheet. It must be
the same as the plmn of
office.
R-I
Destination
IP Address
ipv4
This is the service

address of the peer office.
R-W-I
long:[0..32]
Destination
IP Address
Mask
Length
This field refers to the

mask length of the
destination network. The
network prefix and
network mask must match
each other, and the result
of NOT mask AND prefix
must be 0 (ip&~mask =
0).
Forward
bandwidth(
kbps)

TrPath reserved for
the minimum of Tx
bandwidth, and
64000bps.
If there is only one path in
the path group, it is
advised that this
bandwidth should be
identical to that of the
path group. If there is
more than one path, the
bandwidth sum of all
paths in the same path
group should not exceed
the bandwidth of the path
group.
Backword
bandwidth(
kbps)
long:
[0..4294967]
long:
[0..4294967]

TrPath reserved for
signaling must be less
the minimum of Tx
bandwidth, and
64000bps.
If there is only one path in
the path group, it is
advised that this
bandwidth should be
R-W-I
R-W-I
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
identical to that of the

path group. If there is
more than one path, the
bandwidth sum of all
paths in the same path
group should not exceed
the bandwidth of the path
group.
4.2.18
PVC Config(IU-IUR)
Table 4-37 PVC Config(IU-IUR)
Parameter
Name
Description
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]

ID of "Adjacent
Office(CN)" sheet.
Primary
Key
long:
[1..12600]

for UMTS is:
AAL5 Signal of IUCS is
from 12000 to 12049;
AAL2 Data of IUCS is
from 12050 to 12499;
AAL5 Signal of IUPS is
from 12500 to 12509;
AAL5 Data of IUPS is
from 12510 to 12599;
AAL5 Signal of IUR is
from 11000 to 11049;
AAL2 Data of IUR is
from 11050 to 11999.
Primary
Key
Atm
Interface
Board
string
It must be the
EAPB/EDTA/ESDTA
board info.
eg:rack/shelf/slot
R-I
ATM port
long:[1..244]
ATM Optical Port:[1..4],

IMA Port:[5..244]
R-I
E1 list
string
IMA port need to be

configured.
Separated by ";"
R-W
PVC ID
66
Parameter
Value
Parameter
Name
VPI on
High End
VCI on
High End
Parameter
Value
Description
Remarks
long:
[0..4095]
For the external

identical to the value of
the connected office. It is
value smaller than or
equal to 4.
R-W-I
long:
[32..65535]
For the external

identical to the value of
the connected office. It is
value smaller than or
equal to 256.
R-W-I
0: AAL5 Signal,
1: AAL5 Data,
2: AAL2 Data
PVC
Service
Type
long:[0..2]
PVC
interface
type
long:[2..4]
Service
Category
long:[0,1,2,4]
AAL5 Signal: the

Signaling over ATM,
AAL5 Data: IUPS is the
service over ATM,
AAL2 Data: IUCS or IUR
is the service over ATM.
2; IUR,
3: IUCS,
4: IUPS
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
CBR supports:
atmClpNoTaggingNoScr(2
),
atmNoClpNoScr(1)
atmClpTransparentNoScr(
8),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR
support:
atmNoClpNoScr(1),
),
(13),
R-I
R-I
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
atmClpTaggingScrCdvt(14
),
atmNoClpScr(4).
UBR supports:
NOTRF(0),
atmNoClpNoScr(1),
0).
IU interface: CBR is
recommended.
IUR interface: CBR is
recommended for
signaling, while a
combination of CBR and
UBR is recommended for
service.
Traffic Type
long:[0..15]
0: NOTRF
1: atmNoClpNoScr
2:
atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
14:
atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell
rate for
CLP=0+1
(PCR0+1)
long:
[0..18210661
33]
Unit: Kbps.
This Traffic Para supports
all Service Category and
all Traffic Type.
Peak cell
rate for
CLP=0
(PCR0)
68
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
CBR ,rtVBR and nrtVBR.
Traffic Type:
R-W-I
R-W-I
R-W
Parameter
Name
Parameter
Value
Description
Remarks
),
atmClpTaggingNoScr(3).
long:
[0..42949672
95]
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
(8),
atmNoClpNoScrCdvt (11),
),
0).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
(13),
).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmNoClpScr(4).
R-W
Maximum
burst cell
number
(MBS)
long:
[0..42949672
95]
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
(13),
),
atmNoClpScr(4).
R-W
Path Group
ID
long:
[0..4095]
Cell delay
variation
tolerance
(CDVT)
Sustainable
cell rate for
CLP=0
(SCR0)
Sustainable
cell rate for
CLP=0+1
(SCR0)
This is a globally unique

ID.
for UMTS is
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
4001 to 4095.
TrPath ID
sequence<lo
ng,4>

range of TrPath ID is
[32..127].
office.
AAL2
Attached
Module
long:[3..31]
Select the number of the

module to which this path
is attached.
R-W
AAL2 Path
ID intra
office
long:
[1..42949672
95]
parameter, this number
must have the same
office.
long:[10..14]
10:RT
11: NRT1
12: NRT2
13: NRT3
14: MIX
RT: for bearing real-time
service,
NRT1: for bearing R99
non-real-time service,
NRT2: for bearing HS
non-real-time service,
MIX: for bearing all types
of service.
AAL2 Path
Ownership
long:[0..1]
0:Local End
1:Peer End
If Local Office is
configured, the AAL2
PATH ID will be allocated
in the ascending order.
If Adjacent Office is
configured, the AAL2
PATH ID will be allocated
in the descending order.
For two interconnected
RNCs, one end should be
configured as the Local
Office, while the other as
the Adjacent Office.
Signalling
link number
long:
[1..9000]
Unique in ME
Linkset
number
long:
[1..1024]
Unique in ME
long:[3..31]
Just select the number of

the module that manages
this link. Now only the
CMP module is available.
R-W
AAL2 Path
Service
Type
Signalling
Link
Attached
Module
70
Parameter
Name
Signaling
Link Code
Destination
IP address
4.2.19
Parameter
Value
Description
Remarks
long:[0..15]
This field value is unique

as the link of the same
Office ID. For the
signaling link of the same
physical bearer, the
signaling link code must
have the same
office. As an
interconnection
parameter, this code must
be compatible with the
peer. Each office can
have up to 16 signaling
link codes.
R-W
ipv4
This is the IP address of

the virtual peer interface
board, and must be in the
same network segment as
the Controller interface
board. This IP address is
not an interconnection
parameter. It is reflected
in the binding relation
between the ATM and IP,
and has a 32-bit mask by
default, which needs no
modification.
R-W
Filling
Instructions
Mtp2Link
4.2.20
Mtp3Route
Table 4-38 Mtp3Route
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string

80 characters.
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Route ID
long:[1..2000]
Unique in ME
Primary
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
Key
Used
Signalling
Linkset 1
long:[1..1024]
Quote the Linkset number

of "PVC Config(IU-IUR)"
sheet.
R-W-I
Used
Signalling
Linkset 2
long:[0..1024]
0:Invalid
R-W-I
long:[0..8]
0:Any arrangement
(default value)
1:According to SLS_bit0
choose routing groups
choose link groups
choose link groups
choose link groups
and SLS_bit1 choose link
groups
groups
groups
8:Floral sort
R-W
Permutation
of signalling
links
4.2.21
No.7 PCM
4.2.22
Itc or BSC Office

4.2.23
PCM(ITC-MSC)
4.2.24
MSC Office
72
4.2.25
SGSN Office
4.2.26
Fr Gb
4.2.27
Ip Gb
4.2.28
Lucent Channel
4.2.29
SCTP Config(S1)
4.2.30
Dynamic Sctpac
4.2.31
S1 Link
4.2.32
S1 TrPath
Specifications of Configuring UMTS

Radio Template
The first six sheets are required, while other sheets are optional. Select the sheets
according to the neighbor cells configured.
5.1
UTRAN Cell
Table 5-39 UTRAN Cell
Parameter
Name
Parameter Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
Cannot use invalid

character < > & ' "
R-W
RNC ID
long:[0..4095]
Primary
Key
NodeB No
long:[0..65535]
R-W-I
Cell ID
long:[0..65534]
Primary
Key
Local Cell
Identity
long:
[0..268435455]
R-W-I
Frequency
Band
Indicator
0:Band I,1:Band
II,2:Band
III,3:Band
IV,4:Band
V,5:Band
VI,7:Band VIII
R-W-I
long:
[9612..9888,9262.
.9538,12,37,62,87
,112,137,162,187,
212,237,262,287,
937..1288,1312..1
513,1662,1687,17
12,1737,1762,178
7,1812,1837,1862
,4132..4233,782,7
87,807,812,837,8
62,4162..4188,81
2,837,2712..2863]
uarfcnUl is calculated
by uarfcnDl, should not
input any value.
{freqBandInd==0}
[9612..9888],
{freqBandInd==1}
[9262..9538][12][37]
[62][87][112][137][162]
[187][212][237][262]
[287],
{freqBandInd==2}
[937..1288],
{freqBandInd==3}
UUARFCN
74
Description
Parameter
Name
Parameter Value
Description
Remarks
[1312..1513][1662]
[1687][1712][1737]
[1762][1787][1812]
[1837][1862],
{freqBandInd==4}
[4132..4233][782][787]
[807][812][837][862],
{freqBandInd==5}
[4162..4188][812]
[837],
{freqBandInd==7}
[2712..2863]
DUARFCN
long:
[10562..10838,96
62..9938,412,437,
462,487,512,537,
562,587,612,637,
662,687,1162..15
13,1537..1738,18
87,1912,1937,196
2,1987,2012,2037
,2062,2087,4357..
4458,1007,1012,1
032,1037,1062,10
87,4387..4413,10
37,1062,2937..30
88]
{freqBandInd==0}
[10562..10838],
{freqBandInd==1}
[9662..9938][412][437]
[462][487][512][537]
[562][587][612][637]
[662][687],
{freqBandInd==2}
[1162..1513],
{freqBandInd==3}
[1537..1738][1887]
[1912][1937][1962]
[1987][2012][2037]
[2062][2087],
{freqBandInd==4}
[4357..4458][1007]
[1012][1032][1037]
[1062][1087],
{freqBandInd==5}
[4387..4413][1037]
[1062],
{freqBandInd==7}
[2937..3088]
R-W-I
Cell
Primary
Scrambling
Code
long:[0..511]
R-W-I
Location
Area Code
long:
[1..65533,65535]
R-W-I
Routing
Area Code
long:[0..255]
R-W-I
Service
Area Code
long:[0..65535]
R-W-I
URA
Identity
sequence<long,4
>
Element Data Range

in Array is
[0..65535],and
separated by ";".
R-W-I
Service
Area Code
long:[0..65535]
R-W-I
Filling
Instructions
Parameter
Name
Parameter Value
Description
Remarks
Filling
Instructions
for BC
Domain
T_Cell
5.2
long:
[0..9],<default:0>
R-W-I
Logic Cell Configuration

Table 5-40 Logic Cell Configuration
Parameter
Name
5.3
Parameter
Value
Description
Remarks
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
Mobile
Country
Code
long:[0..999]
Primary
Key
Mobile
Network
Code
long:[0..999]
Primary
Key
Cell ID
long:[0..65534]
can not repeat in the

same PLMN.
Primary
Key
Common
PLMN
Indicator
0:False,1:True,
<default:1>
R-W-I
Filling
Instructions
External UTRAN Cell

Table 5-41 External UTRAN Cell
Parameter
Name
76
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
Parameter
Name
Parameter
Value
Description
Remarks
RNC ID
long:[0..4095]
Primary
Key
Cell Identity
of Adjacent
Cell
long:[0..65535]
Primary
Key
RNC
Identity of
Adjacent
RNC
long:[0..4095]
Primary
Key
Mobile
Country
Code
long:[0..999]
R-W-I
Mobile
Network
Code
long:[0..999]
R-W-I
Location
Area Code
long:
[1..65533,65535
]
R-W-I
Frequency
Band
Indicator
0:Band I,1:Band
II,2:Band
III,3:Band
IV,4:Band
V,5:Band
VI,7:Band VIII
R-W-I
long:
[9612..9888,926
2..9538,12,37,6
2,87,112,137,16
2,187,212,237,2
62,287,937..128
8,1312..1513,16
62,1687,1712,1
737,1762,1787,
1812,1837,1862
,4132..4233,782
,787,807,812,83
7,862,4162..418
8,812,837,2712.
.2863]
{freqBandInd==0}
[9612..9888],
{freqBandInd==1}
[9262..9538][12][37]
[62][87][112][137][162]
[187][212][237][262]
[287],
{freqBandInd==2}
[937..1288],
{freqBandInd==3}
[1312..1513][1662]
[1687][1712][1737]
[1762][1787][1812]
[1837][1862],
{freqBandInd==4}
[4132..4233][782][787]
[807][812][837][862],
{freqBandInd==5}
[4162..4188][812]
[837],
{freqBandInd==7}
[2712..2863]
long:
[10562..10838,9
662..9938,412,4
37,462,487,512,
{freqBandInd==0}
[10562..10838],
{freqBandInd==1}
[9662..9938][412][437]
UUARFCN
DUARFCN
R-W-I
Filling
Instructions
Parameter
Name
5.4
Parameter
Value
Remarks
Description
537,562,587,61
2,637,662,687,1
162..1513,1537.
.1738,1887,191
2,1937,1962,19
87,2012,2037,2
062,2087,4357..
4458,1007,1012
,1032,1037,106
2,1087,4387..44
13,1037,1062,2
937..3088]
[462][487][512][537]
[562][587][612][637]
[662][687],
{freqBandInd==2}
[1162..1513],
{freqBandInd==3}
[1537..1738][1887]
[1912][1937][1962]
[1987][2012][2037]
[2062][2087],
{freqBandInd==4}
[4357..4458][1007]
[1012][1032][1037]
[1062][1087],
{freqBandInd==5}
[4387..4413][1037]
[1062],
{freqBandInd==7}
[2937..3088]
Cell
Primary
Scrambling
Code
long:[0..511]
R-W-I
Service
Area Code
for CS and
PS Domain
long:[0..65535]
R-W-I
URA
Identity
sequence<long,
4>
Element Data Range

in Array is
[0..65535],and
seperated by ";".
R-W-I
Filling
Instructions
External GSM Cell

Table 5-42 External GSM Cell
78
Parameter
Name
Parameter Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
Cell
long:[0..65535]
Primary
Description
Parameter
Name
Parameter Value
Description
Identifier of
Adjacent
GSM Cell
Remarks
Key
Location
Area Code
of Adjacent
GSM Cell
long:
[1..65533,65535]
Primary
Key
Band
Indicator
0:DCS 1800 Band

Used,1:PCS 1900
Band
Used,2:GSM 900
Band
Used,3:GSM 450
Band
Used,4:GSM 480
Band
Used,5:GSM 750
Band
Used,6:GSM 850
Band
Used,<default:0>
R-W-I
BCCH
ARFCN
long:
[512..885,512..81
2,0..124,955..102
3,259..293,306..3
40,438..511,128..
251]
{bandIndicator==0}
[512..885],
{bandIndicator==1}
[512..812],
{bandIndicator==2}
[0..124][955..1023],
{bandIndicator==3}
[259..293],
{bandIndicator==4}
[306..340],
{bandIndicator==5}
[438..511],
{bandIndicator==6}
[128..251]
R-W-I
Network
Colour
Code
long:[0..7]
R-W-I
Base
Station
Colour
Code
long:[0..7]
R-W-I
Mobile
Country
Code
long:[0..999]
R-W-I
Mobile
Network
Code
long:[0..999]
R-W-I
BSC
Identifier
long:[0..65535]
R-W-I
Filling
Instructions
5.5
UExternalENBFunction
Table 5-43 External ENodeB Function
5.6
Parameter
Name
Parameter Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
ENodeB ID
long:
[0..268435455]
Primary
Key
Rnc ID
Attached by
Eutran Cell
long:[0..4095]
R-W
ENodeB
Type
0:Macro
eNodeB,1:Home
eNodeB,<default:
0>
R-W
Description
External EUTRAN Cell FDD

Table 5-44 External EUTRAN Cell FDD
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
eNodeB ID
long:
[0..2684354
55]
EUTRAN
Cell
Identity
long:
[0..255]
Primary
Key
long:
R-W-I
EUTRAN
Physical
80
Description
Primary
Key
Parameter
Name
Parameter
Value
Cell
Identity
[0..503]
Mobile
Country
Code
long:
[0..999]
R-W-I
Mobile
Network
Code
long:
[0..999]
R-W-I
Eutran
Frequency
Band
Indicator
0:Band
1,1:Band
2,2:Band
3,3:Band
4,4:Band
5,5:Band
6,6:Band
7,7:Band
8,8:Band
9,9:Band
10,10:Band
11,11:Band
12,12:Band
13,13:Band
14,16:Band
17,17:Band
18,18:Band
19,19:Band
20,20:Band
21,22:Band
23,23:Band
24,24:Band
25
R-W-I
{eutranFreqBandInd==0}
[0..599],
[600..1199],
[1200..1949],
[1950..2399],
[2400..2649],
[2650..2749],
[2750..3449],
[3450..3799],
[3800..4149],
R-W-I
Downlink
EUTRAN
Absolute
Radio
Frequency
Channel
Number
long:
[0..65535]
Description
Remarks
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
[4150..4749],
[4750..4999],
[5000..5179],
[5180..5279],
[5280..5379],
[5730..5849],
[5850..5999],
[6000..6149],
[6150..6449],
[6450..6599],
[7500..7699],
[7700..8039],
[8040..8689]
Uplink
EUTRAN
Absolute
Radio
Frequency
Channel
Number
82
long:
[0..65535]
[18000..18599],
[18600..19199],
[19200..19949],
[19950..20399],
[20400..20649],
[20650..20749],
[20750..21449],
[21450..21799],
[21800..22149],
[22150..22749],
[22750..22999],
[23000..23179],
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
[23180..23279],
[23280..23379],
[23730..23849],
[23850..23999],
[24000..24149],
[24150..24449],
[24450..24599],
[25500..25699],
[25700..26039],
[26040..26689]
5.7
Tracking
Area Code
long:
[0..65535]
Location
Area Code
long:
[0..65533,6
5535]
R-W
Routing
Area Code
long:
[0..255]
R-W
MNC BCD
Code
Length
long:
[2,3],<defa
ult:2>
EUTRAN
Measurem
ent
Bandwidth
0:6,1:15,2:2
5,3:50,4:75,
5:100,<def
ault:0>
R-W-I
R-W
External EUTRAN Cell TDD

Table 5-45 External EUTRAN Cell TDD
Parameter
Name
Parameter
Value
Modificatio
n Indication
A,D,M,P
[Managed
Element
Object ID]
long:
[1..4095]
Remarks
Filling
Instructions
A:Add, D:Delete,
M:Modify,P:Pass
Primary
Key
Description
Parameter
Name
Parameter
Value
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
eNodeB ID
long:
[0..2684354
55]
EUTRAN
Cell
Identity
long:
[0..255]
Primary
Key
EUTRAN
Physical
Cell
Identity
long:
[0..503]
R-W-I
Mobile
Country
Code
long:
[0..999]
R-W-I
Mobile
Network
Code
long:
[0..999]
R-W-I
Eutran
Frequency
Band
Indicator
32:Band
33,33:Band
34,34:Band
35,35:Band
36,36:Band
37,37:Band
38,38:Band
39,39:Band
40,40:Band
41,41:Band
42,42:Band
43
R-W-I
[36200..36349],
[36350..36949],
[36950..37549],
[37550..37749],
[37750..38249],
[38250..38649],
{eutranFreqBandInd==39 }
[38650..39649],
[39650..41589],
R-W-I
EUTRAN
Absolute
Radio
Frequency
Channel
Number
84
long:
[0..65535]
Remarks
Description
Filling
Instructions
Primary
Key
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
[41590..43589],
[43590..45589]
5.8
Tracking
Area Code
long:
[0..65535]
Location
Area Code
long:
[0..65533,6
5535]
R-W
Routing
Area Code
long:
[0..255]
R-W
MNC BCD
Code
Length
long:
[2,3],<defa
ult:2>
EUTRAN
Measurem
ent
Bandwidth
0:6,1:15,2:2
5,3:50,4:75,
5:100,<def
ault:0>
R-W-I
R-W
Neighbouring Cell
Table 5-46 Neighbouring Cell
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
Cell ID
long:
[0..65534]
Primary
Key
Target RNC
ID
long:
[0..4095]
Primary
Key
Target Cell
ID
long:
[0..65535]
Primary
Key
Description
5.9
GSM Neighbouring Cell

Table 5-47 GSM Neighbouring Cell
5.10
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
Cell ID
long:
[0..65534]
Primary
Key
Location
Area Code
long:
[1..65533,6
5535]
Primary
Key
Cell
Identifier
long:
[0..65535]
Primary
Key
Description
EUTRAN Neighbouring Cell

Table 5-48 EUTRAN Neighbouring Cell
86
Parameter
Name
Parameter
Value
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
Cell ID
long:
[0..65534]
Primary
Key
EUTRAN
Cell Type
0:EUTRAN
FDD,1:EUT
RAN TDD
eNodeB ID
long:
[0..2684354
55]
Primary
Key
EUTRAN
long:
Primary
Description
Remarks
Filling
Instructions
R-I
5.11
Parameter
Name
Parameter
Value
Cell Identity
[0..255]
Description
Remarks
Filling
Instructions
Key
User Authorized PLMN+SNAC Information

Table 5-49 User Authorized PLMN+SNAC Information
Parameter
Name
5.12
Paramet
er Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
[User
Authorized
PLMN+SNA
C Information
Object ID]
long:
[0..42949
67295]
Primary
Key
MCC of
Shared
Network
sequence
<long,10>
Element Data Range in

Array is [0..999],and
separated by ";".
R-W-I
MNC of
Shared
Network
sequence
<long,10>

Array is [0..65535],and
separated by ";".
R-W-I
The Imsi
Matched
Digits Num
long:
[1..15]
R-W-I
The Imsi
Matched
Digit
sequence
<long,15>

Array is [0..9],and
separated by ";".
R-W-I
Number of
Shared
Network
Code
long:
[1..10],<d
efault:1>
MBMS Configuration
It is not necessary to configure this sheet at present.
R-W-I
5.13
MBMS Service Area Configuration

5.14
MBMS Frequency Layer Configuration

Independent Board Configuration
6.1
Checking the Link Status of an Independent

Board
1.
Click View > Configuration Management, and select Independent Board

Configuration Online, as shown in the figure below.
Figure 6-27 Independent Board Configuration Online
2.
88
Click Link Status on the Independent Board Configuration Online window, and
check whether the link status of ECMM, EGBS, and EGFS is ON. Refer to the
ZXUR 9000 UMTS (V4.14.10) Commissioning Guide 04 Board Power-On to load
the software of the boards and make sure ECMM, EGBS, and EGFS are all in the
ON state.
Figure 6-28 Check the Link Status of an Independent Board
6.2
Independent Board Configuration Related

Parameters
Click Shelf, and open the Independent Board Configuration Online interface.
Figure 6-29 Independent Board Configuration Online
Independent board configuration parameters consist of three parts, i.e., common

parameter configuration, EGFS clock information configuration, and ECMM shelf board
information configuration. The details of the parameters are as shown below:
1.
Common parameter configuration: The configuration of DST has two formats, i.e.,
YY/MM/DD and the weekly mode. Either is OK, but the YY/MM/DD format is
recommended.
Table 6-50 Common Parameter Configuration

Common
Parameter
configuration
Parameter
Name
Descriptio
n
Remarks
R-W-I
Master
SNTP
server
address
ipv4
e.g.:
xxx.xxx.xxx.x
xx,
recommende
d
configuration:
129.0.100.10
0
SNTP
Synchroniz
ation cycle
millisecond
Recommend
ed value:
1800000.
long:[-720,660,-600,540,-480,-
The value
range:
-720:GMT-12
Time Zone
90
Parameter
Value
Filling
Instructio
ns
R-W-I
Common
Parameter
configuration
Parameter
Name
Parameter
Value
Descriptio
n
420,-360,300,-240,180,-120,60,0,60,120,
180,240,300,
360,420,480,
540,600,660,
720,780]
-660:GMT-11
-600:GMT-10
-540:GMT-9
-480:GMT-8
-420:GMT-7
-360:GMT-6
-300:GMT-5
-240:GMT-4
-180:GMT-3
-120:GMT-2
-60:GMT-1
0:GMT
60:GMT+1
120:GMT+2
180:GMT+3
240:GMT+4
300:GMT+5
360:GMT+6
420:GMT+7
480:GMT+8
540:GMT+9
600:GMT+10
660:GMT+11
720:GMT+12
780:GMT+13
Daylight
Saving
Time using
flag
long:[0,1]
0:Stop
1:Start
R-W-I
Start time
of the
Daylight
Saving
Time(Mon/
Day/Hour/M
in)
string
eg:Mon/Day/
Hour/Min
R-W
End time of
the Daylight
Saving
Time(Mon/
Day/Hour/M
in)
string
eg:Mon/Day/
Hour/Min
R-W
Step of
Daylight
Saving
Time(minut
e)
long:
[0..33008]
60 is
recommende
d value.
R-W
Remarks
Filling
Instructio
ns
6.3
2.
EGFS clock information configuration: set the information of master/slave shelves

and the corresponding clock information according to the clock reference currently
used.
3.
ECMM shelf board information configuration: configure related environment

monitoring parameters and board configuration information as needed; it is not
necessary to modify the board configuration information, just keep the default
values.
Modifying and Synchronizing Parameters of an

Independent Board
1.
Click Modify and then the corresponding button on the right to modify related
parameters.
Figure 6-30 Modify Parameters
2.
92
After the modification is completed, click Activate to synchronize the parameters to

the target board.
Figure 6-31 Activate Data
3.
The following Message box is displayed after the data is activated.
Figure 6-32 Data Activation Completed
6.4
Performing NTP Synchronization to an

Independent Board
1.
Click View > Status Management on OMC, double-click Physical Resource of

the target NE, and select Controller Rack. Double-click the list on the right to open
the Rack diagram of RNC, as shown below.
Figure 6-33 Controller Rack in Status Management
Figure 6-34 Rack Diagram
2.
Click the icon in the red circle in the above figure, and the following operation result
appears.
Figure 6-35 Operation Result of the NTP Synchronization
94
Special Subject
7.1
ICM Data Configuration Flow (All-Parameter

Configuration)
ICM (Integrated Configuration & Management) is tool used for configuration data
storage, management, analysis, and conversion. It can be used to configure and
optimize the data of the whole network. It can import the configuration data obtained
from CNO or after manual modification.
ICM can also compare the existing network data, history data, plan data, and the backup
data in the plan area, providing a necessary reference for planning configuration data.
Figure 7-36 ICM Data Area
Description of different ICM data areas:
Live Data Area: ICM synchronizes the configuration data running in the existing
network from OMMR to Live Data Area. This data is used as a reference for data
modification.
Live Data: The latest configuration data under the current node in the Live Data
Area.
History data: The backed-up configuration data under the node in Live Data Area
(usually named as AutoBackup).
Plan Data Area: To make sure multiple users can operate on ICM at the same time.
Data importing, exporting, and activation can be performed Plan Data Area by Plan
Data Area.
When a Plan Area is created, the Live Data of the NEs in the subnetwork selected
will be copied to the Plan Data and Reference Data of the Plan Area.
Plan Data: The data that can be modified in Plan Area. Copy the master plan data
from the Live Data Area and create slave plan data manually The Import, Export,
and Activate operations are for master plan data.
ICM supports two types of template configuration:
7.1.1
Plan Template: It is the quick configuration template on OMMR. The plan template
uses a simplified filling method, i.e., the values of the parameters not displayed in
the template will be calculated with the fixed method and will be generated
automatically. Plan template consists of three templates: Equipment template,
TransportNetwork, template, and UMTS Radio template. This template can be used
on both OMMR and ICM.
MO Template: It can only be operated through ICM and is similar to the OMMR MO
Template. It consists of two templates: Uni Ground template and UMTS Radio
template.
ICM Initialization
Open EMS client, choose Configuration > Plan Data Management, and open the Plan
Data Management window.
Figure 7-37 Plan Data Management
Click Live Data Area, and select the record of the target OMMR in the dialog box on the
right. Right-click the record and choose Synchronize to synchronize ICM live data area
and OMMR data and start manually the synchronization between the live data area and
OMMR.
96
Figure 7-38 Live Data Area Synchronization
Note:
ICM can only synchronize data with the snapshot area of the OMMR, because the snapshot
area is always consistent with RNC and the data can be used as the reference.
If the data in the snapshot area is changed (i.e., the data is synchronized from OMMR to
RNC) ICM will monitor this operation in real time and trigger data upload automatically.
This can make sure the data in the live data area of ICM is consistent with that in snapshot
area of OMMR, i.e., consistent with the RNC data.
If data upload cannot be triggered automatically, it is necessary to perform data upload
manually with the method mentioned above.
7.1.2
Exporting Optimization Template (All Parameters)

Choose Live Data Area, right-click the target OMMR subnet and choose Export to
export all parameters.
Figure 7-39 Export Optimization Template on ICM
Select the type of the data to be exported in Data Type, e.g., UMTS Radio for UMTS
radio data and Uni_Ground for ground data, and click Next. In Figure 7 -40, UMTS
Radio is taken as the example.
Figure 7-40 Query and Export
Click Select and select the directory for the exported file. Click Save > Export.
98
Figure 7-41 Storage Path of Exported File
The interface for the data exported successfully is as shown in Figure 7 -42. Click Quit
to exit the Query and Export window.
Figure 7-42 Data Exported Successfully
Note:
The Optimization Template can be exported from either Live Data Area or Plan Area, but
because the data in Live Data Area is consistent with the RNC data fixedly, it is
recommended to export the Optimization Template from Live Data Area.
7.1.3
Data Import
Data importing is based on Plan Area and is usually performed according the flow in
Figure 7 -43.
100
Figure 7-43 ICM Operation Flow
7.1.3.1
Creating Plan Area

Choose Live Data Area, right-click the record of the target OMMR subnet and
choose Create Plan Area.
Figure 7-44 Create Plan Area
Configure User Label in the pop-up Create Plan Area dialog box, select the check box
of the corresponding subnet record, and click OK.
Figure 7-45 Create Plan Area
Figure 7-46 Confirm Dialog Box
7.1.3.2
Importing Template
Right-click the target Plan_Area under Data Area, and choose Import to import data.
102
Figure 7-47 Import Template
1.
Importing Plan Template
In the Data Import window, choose Plan, and modify Data Type to the type of the data
to be imported, such as, Uni_Ground/Uni_Office for ground data, and UMTS Radio for
radio data.
Figure 7-48 Import Plan Template
Right-click the imported file record and choose View Detail to view the details of the
imported file.
The importing result will be automatically saved under the path in the red box in the
figure below.
104
Figure 7-49 View Detail
Note:
When importing the Plan Template from ICM, pay attention to the following two points:
In the Plan template, the ME ID field can be left un-configured. This is different from the
rules of OMMR.
The Data Type selected should match with the template name, as shown below:
Uni_Ground for V3_Template_Equipment.xls
Uni_Office for V3_Template_TransportNetwork.xls
UMTS Radio for UMTS Radio Quick Configuration Template.xls
2.
Importing Optimization Template
In the Data Import window, choose Optimization, and modify Data Type to the type of
the data to be imported, such as, Uni_Ground for ground data, and UMTS Radio for
radio data.
Click Import to import the template.
Figure 7-50 Import Optimization Template
The process of importing Optimization Template is the same as that of importing Plan
Template. Check whether the number of successful records in Succeed/All Counts is
the same as the number of all records. If it is, the template is loaded successfully.
Note:
When importing the Optimization Template from ICM, pay attention to the following points:
1. In the Optimization template, the ME ID field must be configured. This is different
from the rules of filling in the Plan template.
2.
The Data Type selected should match with the template name, as shown below:
Uni_Ground for OMMR_Optimization_uni_ground_20130129131315.zip

UMTS Radio for OMMR_Optimization_umts_radio_20130129131327.zip
3.
106
For the Transaction Mode field, it is recommended to use Best Effort.
7.1.3.3
Validity Check
Right-click the target Plan_Area under Data Area, and choose Check to perform data
validity check.
Figure 7-51 Validity Check
In the pop-up Data Check-Validity window, click OK to start data validity check. By
default, Full Data and All Rules will not be selected, because the system will use the
most efficient way to perform the operation by default. If there is no special requirement,
do not select these two items.
Figure 7-52 Data Check-Validity
After validity check is completed, observe the import result in the figure below. If Validity
is Pass, it means the validity check succeeds.
108
Figure 7-53 Check Result
If there is some error found in the check process, the number of ERROR/WARN records
will be displayed in Result. If there are ERROR records, please check whether the data
is correct. Otherwise, the configuration cannot be activated. If there is only the WARN
record, the activation can be performed normally. This record will appear when the
optional global validity check fails to pass, and the detailed information is displayed in
the CSV file under the path in Detail.
7.1.3.4
Conflict Check
Choose the Conflict tab and click OK to start conflict check.
Figure 7-54 Conflict Check
Before conflict check is started, the following dialog box will pop up. Confirm the live data
is synchronized and click OK.
Figure 7-55 Confirm Live Data
If the Progress is 100%, the "Conflict" is No, the Result is Success, and the
Detail is Finished, this means the conflict check is finished and there is no conflict. In
this case, enter the Submit tab to perform the subsequent operations.
110
Figure 7-56 Conflict Check Result
7.1.3.5
Data Submission
After the conflict check passes, choose the Submit tab, and click Submit to submit the
activation request.
Click Quit to quit the Check interface.
Figure 7-57 Data Submission
7.1.3.6
Data Activation
Choose Activate to display the Activation Management window.
Figure 7-58 Data Activation
112
Click the Add button to open the Activation task management tab, and add the plan
area to be activated to the Selected Plan Area. Fill in the Task Name and click OK.
Figure 7-59 Activate Task Management
Choose the task to be activated. Right-click the task and choose Compare to Get Delta
to create incremental data.
Figure 7-60 Compare to Get Delta
Observe the execution result in Status in the record and the Result in the log.
Figure 7-61 Compare Success
Right-click the task and choose Download to download data.
Figure 7-62 Download
114
Figure 7-63 Download Success
Right-click the task and choose Activate to activate data.
Figure 7-64 Data Activation
Figure 7-65 Activate Success
After the activation is completed, the data is synchronized to RNC.
7.1.4
Deleting Plan Area
7.1.4.1
Checking Whether There is Activation Task

In the Activation Management window, observe whether there is some activation task
that is related to the Plan Area to be deleted. If there is, choose the activation task to be
deleted, click Delete, and click Yes in the pop-up Confirm dialog box.
Figure 7-66 Delete Activation Task
116
7.1.4.2
Checking Submit Status

Right-click the Plan Area to be deleted, and choose Check. Choose the Submit tab in
the pop-up dialog box, and observe whether the status is Editing. If it is, it is necessary
to click To Edit and switch the status to Editing.
Figure 7-67 Switch Submit Status
7.1.4.3
Deleting Plan Area

After the above two checks are completed, the Plan Area can be deleted.
Right-click the Plan Area to be deleted and choose Delete.
Figure 7-68 Delete Plan Area
Click OK to confirm the deletion operation.
Figure 7-69 Confirm Plan Area Deletion
7.2
Features of NodeB Auto-configuration

In UR13, each site has a corresponding home module, which is configured in the IUB
Office sheet. The home module actually contains the home modules of site transmission
resource and radio resource. In UR14, the CMP module configured in the IUB Office
sheet just contains the home module of site transmission resource, while the home
module of site radio resource is flexibly configured and adjusted by RNC according to its
current load.
The dynamic configuration of NodeB and cell refers to that the ZXUR 9000 controller
automatically adjusts the data of NodeB and cells and etc. configured on it according to
the CU CPU load on each control plane. The advantages of this function are as follows:
118
When the user uses commands to configure the objects like NodeB/cell, there is no
need to appoint the board of the object and the CU of control plane, which are
automatically allocated by ZXUR 9000. Therefore, the complexity of configuration is
reduced for the users and the operation and maintenance efficiency is improved.
In addition, the load of the CUs on different control planes is balanced, which helps
avoid the situation when the CUs of some control planes are overloaded (which may
result in access control) while the CUs of some other control planes are light-loaded. In
this way, the use rate of equipment and resources is improved and customers
satisfaction is promoted.
ZXUR 9000 provides the regular swap function and the immediate swap function to
dynamically adjust the NodeBs and cells deployed on the subnets of control planes. The
regular swap function can be performed automatically or manually.
1.
Module Restore: synchronize the module information configured for the site radio
resource in OMMR to RNC.
Figure 7-70 Module Restore 1
Select the configuration file saved in OMMR.
Figure 7-71 Module Restore 2
2.
Module Adjust: export the suggestions for module adjustment from RNC and adjust
the home module of radio resource accordingly.
Figure 7-72 Module Adjust
120
Figure 7-73 Get Suggestions for Module Adjustment
Figure 7-74 Execute Module Adjustment
7.3
CMP Module No. Modification (Transmission)

The home module of the IUB office can be modified in the IUB Office sheet. Meanwhile,
the Module Nos. of office, SCTP, and path group are also modified. Whats different from
UR13 is that the modification here is just effective to the transmission resource. For the
module adjustment to the radio resource, refer to the modification and adjustment
method in chapter 7.2.
Figure 7-75 CMP Module No. Modification
7.4
Overall Office Information Deletion

Acquire the V4_Template_TransportNetwork file, open the IUB Office sheet, modify the
value of MODIND to D, and fill in a proper value of Primary Key. Then, load the file
into OMM, and OMM will delete all the ground and radio resource data related to the site
automatically.
Figure 7-76 Overall Office Information Deletion
7.5
Site Bearer Migration Function

Site bearer migration is an operation that the bearer of a site is changed from one type
to another type. In other words, it is a combined operation of deleting overall office
information + creating office.
Acquire V4_Template_TransportNetwork, and fill in the data of the new site according to
Table 7 -51.
Table 7-51 Sheets to Be Configured for Each Transmission Type of a New Site
No
.
IPoE1+IPoF
E
IPoFE
ATMoE1
ATM+IP
IUB Office
IUB Office
IUB Office
IUB Office
IUB Office
IUB Office
IP Bear(IUB)
IP
Bear(IUB)
IP
Bear(IUB)
ATM
Bearer(IU
B Auto)
IP
Bear(IUB)
ATM
Bearer(IUB)
SCTP Config
(IUB-ABIS)
SCTP
Config
(IUBABIS)
SCTP
Config
(IUBABIS)
SCTP
Config
(IUBABIS)
Static Route
Static
Route
Static
Route
Static
Route
IP Path
Group
IP Path
Group
IP Path
Group
IP Path
Group
122
ATMoSTM1
IPoE1
ATM
Bearer(IU
B Auto)
Modify the value of MODIND in the IUB Office sheet to S.
Figure 7-77 Site Bearer Migration
Load the IUB Office sheet first, and then load other sheets.
Note:
Make sure the IUB Office sheet is loaded before other sheets and they are loaded by two
separate templates.
7.6
RNCID NODEBID CELLID Modification Tool

The tool is under the \ums-clnt\tools\ID-Change directory. Refer to the Instruction
Of RNCID-NodeBID-CID Modifying Tool.doc for the method of using this tool. With this
tool, we can modify RNCID, NODEBID, and CELLID
7.7
Notes for All-data Synchronization & RNCID

Modification
In case of commissioning with quick configuration tool for the first time or modification to
RNC ID, whole-system reset of RNC is demanded after all-data synchronization is
executed.
7.8
Adding User-plane IP (USP)

In V4.13, if USP is newly added, the IP addresses applied previously may be insufficient.
In this case, it is necessary to add user-plane IPs, for which three sheets need to be
filled in:
1.
Interface IP: Fill in the newly-added user-plane IP (operation type A).
2.
Service IP: Fill in the interface type supported by the user-plane IP added at step 1
(operation type A).
3.
UCIU IP Combination Type: Fill in the combination type of UCIU IP, which needs
only one record (operation type A).
After completing the above three sheets, import them into OMM to finish adding userplane IPs.
7.9
Board Configuration
Pay attention to the following new concepts and general cares in board configuration of
V4.
7.9.1
Slot Requirement for Master/Slave Boards

Most of ZXUR 9000 UMTS boards are required to support 1+1 master/slave board
configuration mode. However, not all the master/slave boards are configured in the
neighbor slots. The master/slave boards at Slots 1 to 4 and 11 to 14 are configured in
the alternate slots. That means the pairs of boards in the following slots are in the
master/slave configuration: Slot 1 and Slot 3, Slot 2 and Slot 4, Slot 11 and Slot 13, and
Slot 12 and Slot 14. As shown in Figure 7 -78, the boards in the same color are in the
master/slave configuration.
Figure 7-78 Diagram of Master/Slave Board Slots
7.9.2
Configuration Guide of ATM Interface Board Properties

According to different physical bearers, the configuration of ATM interface properties is
different. When configuring the properties with the template, refer to the following table
for the related parameters:
124
Table 7-52 Configuring Data of ATM Interface Board
Board
Physic
al
Board
Parts (Subcard, etc.)
0: INVALID
0: INVALID
No sub-card
Not
supported
Not
supported
Not supported
EDTS_2/EDTS
_3
6:E1;
7:T1
0: INVALID
0: INVALID
ESDTA
ESDTS_2
1:SDH63E1;
2:SDH63T1;
3:SDH84T1
1:STM-1
1:SDH-AU-4;
2:SDH-AU-3;
3:SONET-STS-1
EAPB
EXIS
5:ATM
1:STM-1
1:SDH-AU-4;
4:SONET-STS3C
ESDTI
ESDHS
1:SDH63E1;
2:SDH63T1;
3:SDH84T1
1:STM-1
1:SDH-AU-4;
2:SDH-AU-3;
3:SONET-STS-1
EDTI
EDTS_3/EMDT
S
6:E1;
7:T1
0: INVALID
0: INVALID
EDTA
EMSI
7.9.3
Available
Optical Port
Multiplexing
Structure
(sdhtype)
6:E1;
7:T1
ASPB
EAPB_
2
Available
Port Type
(porttype)
Available
Optical Port
Speed
Mode
(speedmod
e)
Introduction of USP Board

The functions of Universal Service Processing board (USP) are shown in the following
table:
Table 7-53 Introduction of USP Board

Physical
Board
USP
Logical
Board Name
CDR
Function
Completes control-plane
protocol and user-plane
protocol processing of all
interfaces. It is equivalent to the
combination of CMP, DMP, and
RUP in RU12.
Configuration
Description
It is strongly
recommended that
master/slave
configuration be used
for this board. Each
master board should
be configured with
one CMP module No.
Physical
Board
Logical
Board Name
Configuration
Description
Function
If master/slave
configuration is not
used, the cells cannot
be allocated to the
CMPs of CDR.
USP2a
7.9.3.1
CDR
Completes control-plane
protocol and user-plane
protocol processing of all
interfaces. It is equivalent to the
combination of CMP, DMP, and
RUP in RU12.
It is strongly
recommended that
master/slave
configuration be used
for this board. Each
master board should
be configured with
one CMP module No.
If master/slave
configuration is not
used, the cells cannot
be allocated to the
CMPs of CDR.
Integrated CDR Board

For V4.13 series and later versions, CDR is used, i.e., the functions of CMP+DMP+RUP
are integrated into a CDR board.
126
CMP: Firstly, it provides service for NodeB/cell. The common NBAP protocols and
cell radio resource are processed in CMP. Each cell must be allocated to a certain
CMP. Secondly, CMP processes the connectionless messages on the IU/IUR
interfaces, such as paging, etc. Finally, CMP processes signaling transmission
protocols, such as SCCP/M3UA/ SCTP/ MTP3B/ALCAP, etc. This means
transmission bandwidth resources need to be taken into account for CMP.
DMP: It only processes the radio process related to UE, such as special
RRC/RANAP/RNSAP/NBAP processes and special radio resource algorithm. No
resource relation is configured in the DMP module.
RUP processes only the common services and dedicated services of the user
plane.
For V4.13 series and later versions, the processing units of the user plane are all
processed by the RUB unit of CDR, which is divided into two parts, i.e., UCIU
(processing special user plane service) and CCIU (processing common user plane
service).
UCIU: It is the DSP for the special UE calling service, and the user plane sub-unit
processing special service. In ZXUR 9000 UMTS, it is deployed in RUP of the CDR
board.
CCIU: It is the DSP resource required during CCH establishment, and the user
plane sub-unit processing cell and common transmission channel instances. In
ZXUR 9000 UMTS, it is deployed in the RUB of the CDR board.
The configuration of CDR is as shown in the figure below:
Figure 7-79 Configure CDR Board
7.9.3.2
IUB COM IP Address

After CDR is integrated in UR13.1, it is necessary to allocate an independent IP address
(IUB COM IP address), which can be regarded as the special Iub interface IP address.
If the Iub interface is not in the L3 networking, the IP is only for internal use, and it is not
integrated with external NEs. If it is in the L3 networking, apply for this IP from the
operator.
According to IP allocation and the connection on the Iub interface, the requirements for
IP allocation are as follows:
1.
If Iux IP separation is set on site, the source of the IP can be one IP allocated to the
Iub interface. When the IP is used by the integrated CDR board (IUB COM IP), it
cannot be used by the special part of the Iub interface as the service IP. Therefore,
an IP should be reserved for the Iub interface on site, which can be regarded as the
IP allocated to the Iub interface. If there is no router set on the Iub interface, the
integrated NE is not required to be configured with other devices. If a router is set

on the Iub interface, the integrated NE should be configured with another router.
2.
If Iux IP separation is not set on site, Iux interfaces share the IP. In this condition,
the IP should be planned. This IP is only provided for the integrated CDR board
(IUB COM IP), and it is used as the service IP for common channel establishment.
This IP is only used on the Iub interface. If there is no router on the Iub interface,
the integrated NE is not required to be set with other devices.
Note:
If two shelves are configured, it is necessary to plan an IUB COM IP. If three shelves are
configured, it is necessary to plan two IUB COM IPs.
It is recommended that IUB COM IP and Iub user plane IP be planned in the same subnet. It
is convenient for the data communication engineer to configure the route.
7.9.3.3
Number of Ports Using User-Plane IP

USP is used CDR. The number of Slaves can be configured: at most two CCIU Slaves
and 10 UCIU Slaves. UCIU Slaves should be used for the user plane. The number of
UDP ports of different interfaces is as shown in the table below:
Table 7-54 UDP Port No.

System
7.10
Field Name
User-Plane Board
Type
UDP Port No.
V4 UMTS
IUB
SBCJ/SBCR
3200
V4 UMTS
IUR
SBCJ/SBCR
1152
V4 UMTS
IUCS
SBCJ/SBCR
1280
PVC Configuration
The PVC traffic parameters include L2HtrfType and L2HtrfPara1 to L2HtrfPara5 and the
corresponding high traffic to low traffic type and parameters, all of which are used to
define the traffic bandwidth and characters on both receiving and sending directions of
PVC.
In the quick configuration version in V3 series, only Para1 to Para5 are displayed based
on the above principle. For different traffic types, the same traffic parameter may have
different meanings.
128
Figure 7-80 Configure PVC in V3
From the V4 version, all the parameters related to traffic parameters are displayed. The
engineer can choose the corresponding parameters according to onsite situation.
Figure 7-81 Configure PVC in V4
The relation of PVC traffic type, traffic parameter, and PVC service type is shown in the
following table:
Table 7-55 Relation between PVC Traffic Type, Traffic Parameter, and PVC Service
Type
Servic
e Type
cbr
rtVbr
ntrVbr
Traffic Type
Para1
Para2
atmClpNoTaggingNoScr (3)
PCR0+
1
PCR0
atmClpTaggingNoScr (4)
PCR0+
1
PCR0
atmNoClpNoScr (2)
PCR0+
1
atmClpTransparentNoScr (9)
PCR0+
1
CDVT
atmNoClpNoScrCdvt (12)
PCR0+
1
CDVT
atmNoClpNoScr(2)
PCR0+
1
atmClpNoTaggingNoScr(3)
PCR0+
1
PCR0
atmClpTaggingNoScr(4)
PCR0+
1
PCR0
atmClpNoTaggingScr(6)
Para
3
PCR0+
1
SCR0
MBS
Para
4
Para5
Servic
e Type
abr
Para
3
Para
4
SCR0
MBS
CDV
T
PCR0+
1
SCR0
MBS
atmClpTaggingScrCdvt(15)
PCR0+
1
SCR0
MBS
CDV
T
atmClpTransparentScr(10)
PCR0+
1
SCR0+
1
MBS
CDV
T
atmNoClpScrCdvt(13)
PCR0+
1
SCR0+
1
MBS
CDV
T
atmNoClpScr(5)
PCR0+
1
SCR0+
1
MBS
atmClpNoTaggingMcr(8)
PCR0+
1
CDVT
MCR
Traffic Type
Para1
atmClpNoTaggingScrCdvt(14
)
PCR0+
1
atmClpTaggingScr(7)
Para2
Para5
atmNoTrafficDescriptor(1)
ubr
ubr+
atmNoClpNoScr(2)
PCR0+
1
atmNoClpNoScrCdvt(12)
PCR0+
1
CDVT
atmNoClpTaggingNoScr(11)
PCR0+
1
CDVT
atmTrafficForUbr+(16)
PCR0+
1
MCR
MBS
MFS
CDVT
PCR0+1: Peak cell rate for CLP=0+1

PCR0: Peak cell rate for CLP=0
CDVT: Cell delay variation tolerance
SCR0: Sustainable cell rate for CLP=0
SCR0+1: Sustainable cell rate for CLP=0+1
MBS: Maximum burst cell number
MCR: Minimum cell rate
MFS: Maximum frame size
Note:
For different PVC service types, only the corresponding traffic types in the above table can
be used.
130
All the parameters in the above table should be configured as integer numbers.
In the running system, in order to modify PVC traffic parameters safely, block the upperlevel applications associated with PVC, such as AAL2PATH and ATMSIGLINK, before
modifying the parameters. Otherwise, call loss may occur.
7.11
ATM Address Conversion

The format of the ATM address falls into three categories, as shown in Figure 7 -82.
Figure 7-82 ATM Address Format
The ATM address provided by the operator is usually in the format of E164, that is, a
string of 15 decimal numbers. Our OMM supports two ways of configuration: E164 and
NSAP. By default, NSAP will be adopted. The conversion between the two ways is as
follows: Put 45 before 905325000000001, so we get 45905325000000001. Separate the
string of numbers and put every two numbers into a group: 45-90-53-25-0-0-0-0-1F.
Since the last number 1 cannot form a group by itself, the letter F is added here. It
should be noticed that 45 is hexadecimal, which becomes 69 in the decimal system.
Therefore, when the E164 format mentioned above is converted into the NSAP format, it
becomes 69.144.83.37.0.0.0.0.31.
According to the values of AFI, there are four frequently-used AESAs, as shown in Table
7 -56.
Table 7-56 AFI of ATM Address

AFI (hexadecimal)
Format
0x39
DCC ATM format
0x47
IDC ATM format
0x45
E.164 ATM format
0x49
Local ATM format
At present, in the test environment, manufacturers use the E.164 format of AFI=0x45
most frequently.
For the address in the E.164 format, the IDI field is marked by an ISDN number. This
field has all together eight bytes, and it adopts the BCD (Binary Coded Decimal) coding
method. 15 digits of it will be used, and each digit is a semi octet. If the first semi octets
are not used, they should all be replaced by the number 0.The entered ISDN number will
work as a management organization and be responsible for the DSP coding.
Here is an example which shows how to convert the NSAP format to the E164 format.
For example, 101.101.101 in the NASP format can be converted to 0X 45+65 65 65 in
the E164 format.
7.12
1588 Clock Configuration

For 1588 clock configuration, it is necessary to set PTP Interface Configuration manually
for the EBPB board in OMM.
Choose Managed Element > Transport Network > IP Configuration > PTP Global
Configuration > PTP Interface Configuration.
Pay attention to the parameters in Table 7 -57.
Table 7-57 1588 Clock Configuration Related Parameters

Parameter Name
Value
Used Ethernet IP Interface(IPV4)
Select the slot No. for EGBP in the dropdown list.
The flag if PTP is enabled
Enable
Step mode
One step
Port state
Master
The flag if unicast negotiation is enabled
Enable
The screenshots are as shown in Figure 7 -83 and Error: Reference source not found
132
Figure 7-83 1588 Clock Configuration 1
Figure 7-84 1588 Clock Configuration 2
7.13
Shielding Alarms
Configuration Path: Managed Element > Equipment > Rack > Gate controls
configuration.
Figure 7-85 Shield Alarms
7.14
Rules of Configuring Master/Slave EGPB

For EGPB, it is usually recommended to use load sharing mode, but if master/slave
mode is needed in the field for some reason, whether port switch function is needed
depends on the actual situation.
7.14.1.1
Port Switch
There are three types of port switch under master-slave EGPB configuration.
1.
Default: Switch triggered by the changes in the RX signal strength.
2.
Follow the way:
The system can detect and follow the switchover of the peer-end equipment
automatically according to the received packets. Besides monitoring the RX physical
signals, the master/slave ports collect the real-time statistics of the packets received,
including the statistics of the packets received on the slave port but not received on the
master port when there is no fault on the physical port. The system will trigger
master/slave port switchover, and the working port will be transferred to the original
slave port. After the switchover finishes, the new slave port will be closed temporarily
and stops transmitting physical signals for 10 seconds, so that the peer-end equipment
can detect the master-slave switchover process of the local equipment synchronously.
3.
AH function based on:
The system can make the switch decision according to the result monitored by the
IEEE802.3ah protocol of the master and slave ports. The master port at the RNC side
134
judges the link accessibility by the 802.3ah heartbeat detection. If there is a link fault, the
system will trigger master-slave port switchover automatically.
7.14.1.2
Application of Port Switch

Scenario 1
Usually, it is required that our GE interface board use 1+1 master-slave mode. In the
integration with peer-end equipment (PTN or MSTP), if the peer-end uses L2 switch or
there is the build-in L2 switch function between the master and slave ports, our default
1+1 master-slave policy can meet the requirement of this scenario.(The default switch
mode needs no configuration).
Scenario 2:
If 1+1 master-slave mode is required for our GE interface board, but the peer-end
equipment does not satisfy the above requirement, it is possible that our equipment
cannot coordinate with the peer-end equipment. To guarantee interoperability, please
select AH function based on or Follow the way according to the actual situation.
(Configure Port Switch).
Scenario 3:
If the networking of the peer-end equipment cannot satisfy the requirement of Scenario 1
and its switchover system cannot coordinate with or satisfy the requirement of Scenario
2, the master-slave mode cannot be used normally.
7.14.1.3
Configuring Port Switch

There are five parameters, as shown in the following table.
Table 7-58 Port Switch

PARAMETER NAME
VALUE
Subsystem No.
0~19
Module No.
1~127
Unit No.
1~17
SubUnit No.
1~254
Switch Type
AH function based on / Follow the way
Figure 7-86 Port Switch
Note:
For the master-slave configuration:
1. If the optical port and the electrical port of EGPB are configured with self-adaption, it is
not necessary to configure Switch Type.
2. If the optical port and the electrical port of EGPB are configured with the forced mode,
the Switch Type needs to be configured. Under this mode, our Tx transmission will be
stopped and the peer-end will follow the switchover when our equipment has problems in Rx
and Tx transmission.
Besides 1+1 configuration, when the LACP of the Backup mode is used, the member ports of
the LACP group can use the above three fault detection and switchover modes (Follow the
way should be used in priority, i.e., perform switchover according to the statistics of the
packets received by the Rx port), provided the switchover mode of the interface board of all
the member ports is consistent.
7.15
Rules of Configuring Slots for USP

Considering the design of UR13.1 and later versions, plug the board in the slots in
master/slave configuration first in the slot planning.
The front board must in master/slave configuration in the following slot pairs: {1,3}, {2,4},
{5,6}, {7,8}, {9,10}, {11,13}, and {12,14}. In data configuration, if the number of USPs in
this shelf is an even number m, it is necessary to select m/2 groups from the above slot
pairs to configure board slot, e.g., there are six USPs, select slot pairs {1,3}, {2,4}, and
{5,6}, instead of {1,3}, 5,7,9,11 or {1,3}, {2,4}, 5,7.
136
If the number of USPs is an odd number m, it is necessary to select (m-1)/2 groups

from the above pairs to configure board slot, e.g., there are seven USPs, select {1,3},
{2,4}, {5,6}, and 7, instead of {1,3}, 5,7,9,11,13 or {1,3}, {2,4}, 5,7,9.
7.16
Iub-Interface Qos Planning Rules

There are two options for the Transport Qos Profile Type filed, i.e., QOS According to
ARP/THP/TC and QOS According to Service Type, as shown in Figure 7 -87.
Figure 7-87 Transport Qos Profile Type
Each option has several configuration templates. Each template has a fixed relation with
different IUB transmission.
7.16.1
QOS According to ARP/THP/TC

In most sites, this QOS configuration applies only to the single-path IP transmission and
is invalid to ATM transmission.
Path of selecting template: Managed Element > Local ManagementElement Plmn
information > Logical Iub Link > Used Transport Bearer Type Profile Related to
Basic Priority.
Figure 7-88 Used Transport Bearer Type Profile Related to Basic Priority
There are two templates in total. The relation between the templates and transmission
bearers is as shown in Table 7 -59.
Table 7-59 IUB QOS Planning Rules 1

No.
7.16.2
Name
Common Scenarios
Template 1
ATM+IP Transport
ATM+IP dual stack, ATM+IP

multi-path scenario
Template 2
Only IP Transport
IPoFE and IPoE1 scenarios
QOS According to Service Type

When the IUb-interface QOS is configured as QOS According to Service Type, select
the template in the following path: Managed Element > Local ManagementElement
Plmn information > Logical Iub Link > Used Dedicated Service Transport Bearer
Qos Profile.
Figure 7-89 Used Dedicated Service Transport Bearer Qos Profile
The relation between the value of Used Dedicated Service Transport Bearer Qos
Profile and IUB-interface transmission bearer is as shown in Error: Reference source
not found.
Table 7-60 IUB QOS Planning Rules 2

No.
138
Name
Template 1
Two IP Paths
Template 2
Three IP Paths
Template 3
One ATM Path and Two IP

Paths
Template 4
Two ATM Paths
Common Scenarios
IPoFE and IPoE1 scenarios
ATMoE1 scenario
No.
7.17
Name
Common Scenarios
Template 5
One IPOE Path and One

IPOFE Path
IPoE1+IPoFE multi-path scenario
Template 6
One ATM Path and One IP

Path
ATM+IP dual stack, ATM+IP multipath scenario
IP Function Switch
In the MO version and later versions, if IP transmission needs to be used on the IUX
interface, it is not only necessary to apply for the license but also necessary to enable
license control switches on OMM, as shown in Error: Reference source not found
Path: Managed Element > UMTS Logical Function Configuration > Link
Configuration > IP Function Switch.
Figure 7-90 IP Function Switch

ZXUR 9000 UMTS (V4.14.10) Commissioning Guide-06 Quick Data Configuration - R1.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXUR 9000 UMTS (V4.14.10) Commissioning Guide-06 Quick Data Configuration - R1.1

Uploaded by

Copyright:

Available Formats

ZXUR 9000 UMTS(V4.14.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

ZTE Confidential & Proprietary.

2016 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Reason for Revision

Add requirement for

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential & Proprietary.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

About This Document

1 Notices in Data Configuration

Provides the matters for attention in data configuration

2 Introduction to Quick Data

Provides an overview of Plan template and common

3 Method of Calculating the

Introduces the method of calculating the number of userplane IPs

Introduces the specifications of configuring Equipment

Introduces the specifications of configuring UMTS Radio

6 Independent Board Configuration

Introduces some operations of independent board

Introduces some special subjects, such as ICM data

ZTE Confidential & Proprietary.

2016 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Notices in Data Configuration.........................................................................1

Introduction to Quick Data Configuration......................................................2

Method of Calculating the Number of User-plane IPs.................................18

Specifications of Configuring Equipment Template and Transport Network

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential & Proprietary.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Specifications of Configuring UMTS Radio Template.................................75

Independent Board Configuration................................................................90

ZTE Confidential & Proprietary.

2016 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential & Proprietary.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

ZTE Confidential & Proprietary.

2016 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Figure 6-6 Data Activation Completed..................................................................................95

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential & Proprietary.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Figure 7-32 Switch Submit Status.......................................................................................119

ZTE Confidential & Proprietary.

2016 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Table 4-3 Shelf Config..........................................................................................................23

2016ZTE CORPORATION. All rights reserved.

ZTE Confidential & Proprietary.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Table 5-2 Logic Cell Configuration........................................................................................77

ZTE Confidential & Proprietary.

2016 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS(V4.14.10) Commissioning Guide

Notices in Data Configuration

Table 1-1 Notices in Data Configuration

(1,3), (2,4), (11,13), (12,14)

It is recommended to set PLMN ID as a