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. ZTE’s 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, anyone’s 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 CORPORATION’s products and technologies.
ZTE CORPORATION
Addres NO. 55
s: Hi-tech Road South
ShenZhen
P.R.China
518057
Websit
http://support.zte.com.cn
e:
Email: 800@zte.com.cn
ZTE Confidential & Proprietary. © 2016 ZTE CORPORATION. All rights reserved. I
Revision History
Product Version Document Version Serial Number Reason for Revision

V12.14.10 R1.0 First published
Add requirement for
RNC restart after all-
data synchronization
in case of initial
V12.14.10 R1.1 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. ZTE Confidential & Proprietary.

About This Document
Summary
Chapter Description
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
Configuration functions.
3 Method of Calculating the Introduces the method of calculating the number of user-
Number of User-plane IPs plane IPs
4 Specifications of Configuring Introduces the specifications of configuring Equipment
Equipment Template and Transport template and Transport Network templates.
Network Template
5 Specifications of Configuring Introduces the specifications of configuring UMTS Radio
UMTS Radio Template 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.
ZTE Confidential & Proprietary. © 2016 ZTE CORPORATION. All rights reserved. III
TABLE OF CONTENTS
1 Notices in Data Configuration.........................................................................1
2 Introduction to Quick Data Configuration......................................................2

2.1 Overview of Plan Template................................................................................2
2.1.1 Template Info Sheet...........................................................................................
2.1.2 Index Sheet........................................................................................................
2.1.3 Attributes of Parameters....................................................................................
2.1.4 Equipment Template..........................................................................................
2.1.5 Transport Network Template..............................................................................
2.1.6 UMTS Radio Template.......................................................................................
2.2 Common Functions............................................................................................8
2.2.1 Loading Templates.............................................................................................
2.2.2 Exporting Templates.........................................................................................
2.2.3 Check on Imported Quick Configuration Template...........................................
2.2.4 Restoring Modify Area from Snapshot Area.....................................................
2.2.5 Data Comparison Between Snapshot Area & Modify Area...............................
3 Method of Calculating the Number of User-plane IPs.................................18
4 Specifications of Configuring Equipment Template and Transport Network

Template 20
4.1 Equipment Template........................................................................................20
4.1.1 Basic Info.........................................................................................................
4.1.2 Plmn Config.....................................................................................................
4.1.3 Shelf Config.....................................................................................................
4.1.4 Board Config....................................................................................................
4.1.5 Global Info.......................................................................................................
4.1.6 Interface IP......................................................................................................
4.1.7 Service IP........................................................................................................
4.1.8 CCIU Service Config........................................................................................
4.1.9 UCIU IP Combination Type..............................................................................
4.1.10 Slave or Dsp Service Config............................................................................
4.1.11 Channel Port....................................................................................................
4.1.12 Member Port....................................................................................................
4.1.13 Super Vlan.......................................................................................................
4.1.14 Super Vlan Member.........................................................................................
4.1.15 DHCP Server...................................................................................................
4.1.16 DHCP Client.....................................................................................................
4.1.17 DHCP Relay.....................................................................................................
4.1.18 VRF Attributes Config......................................................................................
4.1.19 VRF Route Target............................................................................................
4.2 TransportNetwork Template.............................................................................39
4.2.1 Local Office......................................................................................................
4.2.2 Static Route.....................................................................................................
4.2.3 IP Path Group..................................................................................................
IV ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

4.2.4 IUB Office........................................................................................................

4.2.5 ATM Bearer(IUB Auto).....................................................................................
4.2.6 ATM Bearer(IUB).............................................................................................
4.2.7 SCTP Config(IUB-ABIS)..................................................................................
4.2.8 IP Bearer(IUB).................................................................................................
4.2.9 IPOE Bearer(IUB)............................................................................................
4.2.10 SCTP Config(ABIS)..........................................................................................
4.2.11 IP Bearer(ABIS)...............................................................................................
4.2.12 Adjacent Office(CN).........................................................................................
4.2.13 SCTP Config(CN)............................................................................................
4.2.14 M3uaAS Config(CN)........................................................................................
4.2.15 M3uaRoute......................................................................................................
4.2.16 M3uaRouteSet.................................................................................................
4.2.17 IP Path(CN)......................................................................................................
4.2.18 PVC Config(IU-IUR).........................................................................................
4.2.19 Mtp2Link..........................................................................................................
4.2.20 Mtp3Route.......................................................................................................
4.2.21 No.7 PCM........................................................................................................
4.2.22 Itc or BSC Office..............................................................................................
4.2.23 PCM(ITC-MSC)................................................................................................
4.2.24 MSC Office.......................................................................................................
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.........................................................................................................
5 Specifications of Configuring UMTS Radio Template.................................75

5.1 UTRAN Cell.....................................................................................................75
5.2 Logic Cell Configuration...................................................................................77
5.3 External UTRAN Cell.......................................................................................78
5.4 External GSM Cell...........................................................................................80
5.5 UExternalENBFunction....................................................................................81
5.6 External EUTRAN Cell FDD.............................................................................82
5.7 External EUTRAN Cell TDD.............................................................................86
5.8 Neighbouring Cell............................................................................................87
5.9 GSM Neighbouring Cell...................................................................................88
5.10 EUTRAN Neighbouring Cell.............................................................................88
5.11 User Authorized PLMN+SNAC Information......................................................89
5.12 MBMS Configuration........................................................................................90
5.13 MBMS Service Area Configuration...................................................................90
5.14 MBMS Frequency Layer Configuration............................................................90
6 Independent Board Configuration................................................................90

6.1 Checking the Link Status of an Independent Board.........................................90
6.2 Independent Board Configuration Related Parameters....................................91
6.3 Modifying and Synchronizing Parameters of an Independent Board................94
6.4 Performing NTP Synchronization to an Independent Board.............................95
ZTE Confidential & Proprietary. © 2016 ZTE CORPORATION. All rights reserved. V
7 Special Subject..............................................................................................97
7.1 ICM Data Configuration Flow (All-Parameter Configuration)............................97
7.1.1 ICM Initialization...............................................................................................
7.1.2 Exporting Optimization Template (All Parameters)...........................................
7.1.3 Data Import....................................................................................................102
7.1.4 Deleting Plan Area.........................................................................................118
7.2 Features of NodeB Auto-configuration...........................................................120
7.3 CMP Module No. Modification (Transmission)...............................................123
7.4 Overall Office Information Deletion................................................................124
7.5 Site Bearer Migration Function.......................................................................124
7.6 RNCID NODEBID CELLID Modification Tool.................................................125
7.7 Notes for All-data Synchronization & RNCID Modification..............................125
7.8 Adding User-plane IP (USP)..........................................................................125
7.9 Board Configuration.......................................................................................126
7.9.1 Slot Requirement for Master/Slave Boards....................................................126
7.9.2 Configuration Guide of ATM Interface Board Properties.................................126
7.9.3 Introduction of USP Board.............................................................................127
7.10 PVC Configuration.........................................................................................130
7.11 ATM Address Conversion...............................................................................133
7.12 1588 Clock Configuration...............................................................................134
7.13 Shielding Alarms............................................................................................135
7.14 Rules of Configuring Master/Slave EGPB......................................................136
7.15 Rules of Configuring Slots for USP................................................................138
7.16 Iub-Interface Qos Planning Rules..................................................................139
7.16.1 QOS According to ARP/THP/TC....................................................................139
7.16.2 QOS According to Service Type.....................................................................140
7.17 IP Function Switch.........................................................................................141
VI ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

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
ZTE Confidential & Proprietary. © 2016 ZTE CORPORATION. All rights reserved. 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 ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.
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
ZTE Confidential & Proprietary. © 2016 ZTE CORPORATION. All rights reserved. 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
X ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

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
ZTE Confidential & Proprietary. © 2016 ZTE CORPORATION. All rights reserved. XI
1 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,
1 (1,3), (2,4), (11,13), (12,14)
alternate backup slots
It is recommended to set PLMN ID as a
combination of “MCC” + “MNC,” each
2 PLMN ID
composed of 3 digits, e.g., for 460/1, the PLMN
ID should be set as 460001.
Each master and slave CDR board needs to be
configured with one CMP module, two DMP
Configuration of integrated
3 modules, and one RUB unit, among which the
CDR
CMP module NO. ranges 3-31, DMP module
NO. ranges 64-127.
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
4 IUBCOM 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.
5 Signaling point code Set it as a decimal value.
6 Netmask Set it as a decimal value.
7 OMCB gateway IP It must be configured on the virtual port.
In the synchronization process, the system will
check both the required items and the optional
8 Global check items by default. Sometimes the optional items
may cause synchronization failure and the
check can be cleared manually.
2 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
2 © 2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

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

R Read Read only
Can be read and
R-W Read and Write
modified
This parameter must be
R-I Read and Initial configured in the data
creation process.
Can be read and
R-W-I Read, Write and Initial modified. This parameter
must be configured.
Can be read. This
parameter must be
R-M-I Read, Modify and Initial configured in the data
creation and modification
process.
configured in the data
Primary Key Primary Key
creation and modification
process.
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.

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.

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

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

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

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.
IPINTFTYPE5=0: Iub and Iur share an IP, and IuCs and IuPs share an IP, and pre-
configuration 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.
4 Specifications of Configuring
Equipment Template and Transport
Network Template
4.1 Equipment Template
4.1.1 Basic Info
Table 4-3 Basic Info
Parameter Parameter Filling

　Description Remarks
Name Value Instructions
A:Add,
Modificatio
A,M,P D:Delete, 　　
n Indication
M:Modify, P:Pass
Managed long: Primary
　
Element ID [1..4095] Key
2:UMTS
Mode Type long:[2..4] 3:GSM R-I
4:GU
Omp's omc
ipv4 eg:xxx.xxx.xxx.xxx R-W-I
port ip
Omp's omc
port mask long:[0..32] 　 R-W-I
length
Omp's omc ipv4 eg:xxx.xxx.xxx.xxx R-W-I


port UMTS:It should be as same
gateway as the IP address of bond2:1
IP address
of SNTP ipv4 eg:xxx.xxx.xxx.xxx R-W-I
server
OMCB
Agent IP
ipv4 eg:xxx.xxx.xxx.xxx R-W-I
Address to
NODEB
OMCB
Server IP ipv4 eg:xxx.xxx.xxx.xxx R-W-I
Address
OMCB
Server IP
long:[0..32] 　 R-W-I
Mask
Length
eg:xxx.xxx.xxx.xxx
It can be used when it
OMCB
supports multipath
Inner Ip ipv4 R-W-I
protection.
Address
Otherwise, it is filled in
default value 0.0.0.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
long:[-720,-
-300:GMT-5
660,-600,-
-240:GMT-4
540,-480,-
-180:GMT-3
420,-360,-
-120:GMT-2
300,-240,-
-60:GMT-1
180,-120,-
Time Zone 0:GMT R-W-I
60,0,60,120
60:GMT+1
,180,240,30
120:GMT+2
0,360,420,4
180:GMT+3
80,540,600,
240:GMT+4
660,720,78
300:GMT+5
0]
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 long:[0,1] 0:Stop R-W-I
Saving 1:Start

Time using
flag
Start time
of the
Daylight
Saving string eg:Mon/Day/Hour/Min R-W
Time(Mon/
Day/Hour/
Min)
End time of
the Daylight
Saving
string eg:Mon/Day/Hour/Min R-W
Time(Mon/
Day/Hour/
Min)
Step of
Daylight
long:
Saving 60 is recommended value. R-W
[0..33008]
Time(minut
e)
4.1.2 Plmn Config
Table 4-4 Plmn Config

Modification A:Add, D:Delete, M:Modify,
A,D,M,P 　　
Indication P:Pass
User label string 　 R-W
Managed long: Primary
　
Element ID [1..4095] Key
PLMN long:
Primary
Group [0..429496 　
Key
Object ID 7295]
Mobile
long:
Country 　 R-W-I
[0..999]
Code
Mobile
long:
Network 　 R-W-I
[0..999]
Code
MNC BCD
Code long:[2..3] 　 R-W-I
Length


Default
0:false
PLMN long:[0..1] R-W-I
1:true
Indicator
Is Local
0:false
Office's long:[0..1] R-I
1:true
PLMN
4.1.3 Shelf Config
Table 4-5 Shelf Config
Filling
Parameter Parameter
　Description Remarks Instruction
Name Value
s　
Modification A:Add, D:Delete,
A,D,M,P 　　
Indication M:Modify, P:Pass
Managed Primary
long:[1..4095] 　
Element ID Key
Primary
Rack No. long:[1..1] 　
Key
Primary
Shelf No. long:[1..3] 　
Key
33:ETCA V1 Primary
Shelf Type long:[33,34]
34:ETCA V2 Key
Master Shelf 0:Not Master Shelf
long:[0..1] R-W-I
Flag 1:Is Master Shelf
4.1.4 Board Config
Table 4-6 Board Config

A,D,P 　　
Indication P:Pass
Managed
Primary
Element long:[1..4095] 　
Key
Object ID
Primary
rack/shelf/slot string eg:1/2/7
Key
Physical
string eg:UMP R-I
Board Type

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


1:TDMA
2:IPA
4.1.5 Global Info
Table 4-7 Global Info

Modification A:Add, M:Modify,
A,M,P 　　
Indication P:Pass
Managed
Primary
Key
Object ID
IP Segment
ReAssemble string eg:rack/shelf/slot R-W
Default Unit
The First IP
Segment
string eg:rack/shelf/slot R-W
ReAssemble
Unit
The Second
IP Segment
ReAssemble
Unit
The Third IP
Segment
ReAssemble
Unit
The Fourth
IP Segment
ReAssemble
Unit
The Fifth IP
Segment
ReAssemble
Unit
The Sixth IP
Segment
ReAssemble
Unit
The Seventh
IP Segment
ReAssemble
Unit
4.1.6 Interface IP
Table 4-8 Interface IP

A,D,M,P 　　
User Label string 　 R-W
Managed
Primary
Key
Object ID
Interface Primary
string eg:rack/shelf/slot
Board Key
It is usually filled with
Primary
Module No. long:[1..127] 1. For virtual port, fill in
Key
the actual module No.
0:Interface
Primary
Port Type long:[0,1,2] 1:Loopback port
Key
2:Virtual port
0:invalid,
Interface 1~4:real port,
1~128:loop port Primary
Local Port long:[0..128]
Key
No. 1~244Interface(ATM
port)
VLAN Primary
long:[0..4095] 0 is invalid
Sequence Key
0 is invalid.
Vlan ID long:[0..4095] It is valid when it is sub R-W-I
interface.
VPN ID of
long:[0..254] 0 is invalid R-W-I
sub port
MAC eg:
string R-W
address xx-xx-xx-xx-xx-xx
eg:
IP address of
ipv4 xxx.xxx.xxx.xxx;xxx.xx R-W-I
interface
x.xxx.xxx
Mask Length
of interface long:[0..32] eg:24;24 R-W-I
IP

4.1.7 Service IP
Table 4-9 Service IP

A,D,M,P 　　
Managed
Primary
Key
Object ID
eg: Primary
Service IP ipv4
xxx.xxx.xxx.xxx Key
Bit0=1:A Interface of
GSM Network
Bit1=1:Abis PS
Interface of GSM
Application
Network
Type of IP string R
Bit2=1:Abis CS
address(2G)
Interface of GSM
Network
Bit3=1:Gb Interface of
GSM Network
Bit0=1:Iub Interface of
3G Network
Bit1=1: Iur Interface of
3G Network
Bit2=1: IuCS Interface
of 3GNetwork
Application Bit3=1: IuPS Interface
Type of IP string of 3G Network R
address(3G) Bit4=1:Iub Common
Interface of 3G
Network (for CCIU)
Bit5=1:Preconfiguratio
n IuB Interface of 3G
Network
Bit0=1:IuCS Interface
of HNB GW Network
Bit1=1:IuPS Interface
of HNB GW Network
Bit2=1:IuhCS Interface
of HNB GW Network
Application
Type of IP string Bit3=1:IuhPS Interface R
address(AG) of HNB GW Network
Bit4=1:HenbS1
Interface of HeNB GW
Network
Bit5=1:MmeS1
Interface of HeNB GW
Network

VPN ID of
long:[0..254] 0 is invalid R-I
sub port
eg:
MCC1:MNC1;MCC2:M
PLMN info of NC3
string R-W-I
Service IP or 65535:65535,
65535:65535 denotes
supporting all PLMN
4.1.8 CCIU Service Config
Table 4-10 CCIU Service Config

A,D,P 　　
Indication P:Pass
Managed
Primary
Key
Object ID
Data Format(Iub
Service IP
Common Interface): Primary
Address of string
xxx.xxx.xxx.xxx;xxx.xx Key
CCIU SLAVE
x.xxx.xxx
Service IP for Data Format(Iub
Preconfigurat Preconfiguration): Primary
string
ion Iub xxx.xxx.xxx.xxx;xxx.xx Key
Interface x.xxx.xxx
4.1.9 UCIU IP Combination Type
Table 4-11 UCIU IP Combination Type

　Description Remarks　
Name Value Instructions　
A,D,P 　　
Indication P:Pass
Managed
Element long:[1..4095] 　 Primary Key
Object ID
Interface string Data Format: Primary Key
Type binary mode, 5 bits
Combination in total: xxxxx
1 of Service Bit0=1:Iub Interface
IP of 3G Network


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
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
The PLMN xx.xxx
Combination
eg:
for "Interface
If this parameter is
Type string Primary Key
not configured, it
Combination
means all PLMNs
1 of Service
are supported.
IP"
If the system
supports only one
PLMN, fill in either
the exact PLMNID
or nothing.
Interface Data Format:
Combination string in total: xxxxx Primary Key
2 of Service
IP
The PLMN
Combination Data Format:
for "Interface xxx.xxx.xxx.xxx;xxx
Type string .xxx.xxx.xxx;xxx.xx Primary Key
Combination x.xxx.xxx;xxx.xxx.x
2 of Service xx.xxx
IP"
Interface
Type Data Format:
Combination string binary mode, 5 bits Primary Key
3 of Service in total: xxxxx
IP
The PLMN
3 of Service xx.xxx
IP"

4 of Service
IP
The PLMN
4 of Service xx.xxx
IP"
5 of Service
IP
The PLMN
5 of Service xx.xxx
IP"
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.
IPINTFTYPE5=0: Each interface uses an independent IP and does not support the
pre-configuration of the Iub interface.
IPINTFTYPE5=0: Iub and Iur share an IP, and IuCs and IuPs share an IP, and pre-
configuration 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.
4.1.10 Slave or Dsp Service Config
Table 4-12 Slave or Dsp Service Config

A:Add, D:Delete, P:Pass
Applicable to UMTS
Modificatio
A,D,P Supports only D:Delete and 　　
n Indication
P:Pass
Does not support A:Add
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Data Format:
RACK/SHELF/SLOT,
2G: CRP or ETCB or EDTB Primary
Board Info string
or ESDTB board, Key
3G: 0/0/0. Don't assign IP
resource by board for 3G.
Data Format:
Service IP
xxx.xxx.xxx.xxx;xxx.xxx.xxx Primary
Address of string
.xxx;xxx.xxx.xxx.xxx;xxx.xx Key
SLAVE
x.xxx.xxx
Service IP string Data Format(Iub Primary
for Preconfiguration): Key

Preconfigur
xxx.xxx.xxx.xxx;xxx.xxx.xxx
ation Iub
.xxx
Interface
4.1.11 Channel Port
Table 4-13 Channel Port

A,D,M,P 　　
User label string 　 R-W
Managed
Primary
Key
Object ID
Channel Primary
long:[1..16] 　
Group ID Key
VLAN Primary
long:[0..4095] 0 is invalid
Sequence Key
0 is invalid.
Vlan ID long:[0..4095] It is valid when it is sub R-W-I
interface.
3:on Mode
Bound Mode long:[3..5] 4:backup Mode R-W-I
5:802.3AD Mode
VPN ID of
sub port
MAC eg:
string R-W
eg:
IP address of
ipv4 xxx.xxx.xxx.xxx;xxx.xx R-W-I
interface
x.xxx.xxx
Mask Length
IP
4.1.12 Member Port
Table 4-14 Member Port

Modification A,D,M,P A:Add, D:Delete, 　　


User label 　　 R-W
Managed
Primary
Key
Object ID
Member port
ID of Primary
long:[1..128] 　
Channel Key
Group
Interface
string eg:rack/shelf/slot R-I
Board
Local port
No. of long:[1..4] 　 R-I
member port
Channel
long:[1..16] 　 R-I
Group ID
1:active
Bounding
2:passive
mode of long:[1..4] R-W-I
3:on
member port
4:backup
System
Priority of The default value is
long:[1..65535] R-W
LACP 32768.
protocol
0:long time,
Timeout Type
1:short time,
of LACP long:[0..1] R-W
The defaulte value is
protocol
0.
4.1.13 Super Vlan
Table 4-15 Super Vlan

A,D,M,P 　　
Managed
Primary
Key
Object ID
Primary
Supervlan ID long:[1..16] 　
Key
Switch of 0:Closed
inner-route long:[0..1] R-W-I
function 1:Open

MAC eg:
string R-W
　At most 4 IP for one
IP address of port.
Super Vlan ipv4 R-W-I
Interface eg:xxx.xxx.xxx.xxx;xxx.
xxx.xxx.xxx
Mask Length
IP
VPN ID of
port
4.1.14 Super Vlan Member
Table 4-16 Super Vlan Member

A,D,M,P 　　
Managed
Primary
Key
Object ID
eg:rack/shelf/slot.
When Vlan Sub
Interface of Ethernet
Port joins to supervlan,
this parameter should
be filled in the EGPB
Interface Primary
string board.
Board Key
When Vlan Sub
Interface of Channel
Group joins to
supervlan,
this parameter should
be filled in 0/0/0.
Real Port long:[1..16] When Vlan Sub Primary
No. Interface of Ethernet Key
Port joins to supervlan,
LOCALPORT is
Ethernet Port No.
When Vlan Sub
Interface of Channel
Group joins to
supervlan,
LOCALPORT is


Channel-group ID.
It is the sub interface
VLAN Primary
long:[1..4095] of the super vlan
Sequence Key
member.
Supervlan
long:[1..16] 　Quote Super VLAN R-I
ID
4.1.15 DHCP Server
Table 4-17 DHCP Server

A,D,M,P 　
Managed
Primary
Key
Object ID
DHCP 　Unique in ME Primary
Server long:[1..2800]
Key
Object ID
0:DHCP Server IP
Address-Inner
Type of Controller
DHCP 1:DHCP Server IP
long:[0..2] R-W-I
Server Address-Outer
Address Controller
2:DHCP Server Board-
Logical Address
It is valid if
Module No. long:[1..127] R-W
DHCPSVRIPTYPE=2.
DHCP It is valid if
Server IP ipv4 DHCPSVRIPTYPE=0 R-W
Address or 1.
Mask
Length of It is valid if
DHCP long:[0..32] DHCPSVRIPTYPE=0 R-W
Server IP or 1.
Address
It is valid if
VPN ID of DHCPSVRIPTYPE=0.
long:[0..254] R-W
Port
The default value is 0.
4.1.16 DHCP Client
Table 4-18 DHCP Client

A,D,M,P 　　
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Client long: 　Unique in ME Primary
Number [1..2800] Key
1 to 16 characters of
Vendor Class
ASCII, the same as
Identity of String R-W-I
vendor class of Node
DHCP Client
B
eg:
Hardware
String xxx.xxx...xxx.xxxx(leng R-W-I
Address
th is 16)
eg:
Client
String xxx.xxx...xxx.xxxx(leng R-W-I
Identity
th is 16)
Client eg:
ipv4 R-W-I
Identity xxx.xxx.xxx.xxx
Mask Length
of DHCP
long:[0..32] 32 is recommended R-W-I
Client IP
Address
1 to 128 characters of
DHCP Client ASCII, the same as
String R-W
Host Name vendor class of Node
B
DHCP 　Quote DHCP Server
long:
Server R-W-I
[1..2800]
Object ID
DHCP
Server It must be the interface
ipv4 R-W-I
Identity(Interf IP.
ace IP)
RNC OAM IP eg:
Address to ipv4 R-W-I
NodeB xxx.xxx.xxx.xxx
DHCP eg:
Gateway IP ipv4 R-W-I
Address xxx.xxx.xxx.xxx

4.1.17 DHCP Relay
Table 4-19 DHCP Relay

A,D,M,P 　　
Managed
Primary
Key
Object ID
DHCP Relay 　Unique in ME Primary
long:[1..2800]
Object ID Key
eg:rack/shelf/slot
It must be EGPB
board info if DHCP
IP interface relay port is real port
string R-I
board or sub interface of real
port.
Others, it can be filled
in 0/0/0.
0 is invalid.
Real Port It is valid only if DHCP
long:[0..4] relay port is real port R-I
No.
or sub interface of real
port.
0 is invalid.
Channel It is valid only if DHCP

long:[0..16] R-I
Group ID relay port is channel
port or sub interface of
channel port.
0 is invalid.
It is valid only if DHCP
VLAN relay port is sub
long:[0..4095] R-I
Sequence interface of real port or
sub interface of
channel port.
It must be the interface
IP address of DHCP
relay port.
Relay IP
ipv4 It can be the supervlan R-W-I
Address
interface IP address if
the DHCP relay port is
sub interface..
Mask Length It must be the mask
of Relay IP long:[0..32] length of the relay IP R-W-I
Address address.

DHCP
Server long:[1..2800] Quote DHCP Server R-W-I
Object ID
4.1.18 VRF Attributes Config
Table 4-20 VRF Attributes Config

A,D,M,P 　　
Managed
Primary
Key
Object ID
　no more than 30
VPN Name string characters R-W-I
VPN ID of Primary
long:[1..254]
Port Key
Route 1:ASN:nn format,
Distinguisher long:[1,2] R-W-I
Type 2:IP-address:nn format
If the RD TYPE is
"ASN:nn", the format of
RD VALUE is (1-
65535):(0-
Route 4294967295).
Distinguisher string If the RD TYPE is "IP- R-W-I
Value address:nn", the
format of RD VALUE is
(0.0.0.0-
255.255.255.255): (0-
65535)
VRF
no more than 80
description string R-W
characters
information

4.1.19 VRF Route Target
Table 4-21 VRF Route Target

A,D,M,P 　　
Managed
Primary
Key
Object ID
　no more than 30
VPN Name string characters R
VPN ID of Primary
long:[1..254]
Port Key
Target-VPN 2:Export Primary
long:[2,3]
community 3:Import Key
VRF Route 1:ASN:nn format, Primary
long:[1,2]
Target Type 2:IP-address:nn format Key
If the RT TYPE is
"ASN:nn", the format
of RT VALUE is (1-
65535):(0-
VRF Route 4294967295).
Primary
Target string If the RT TYPE is "IP- Key
Value address:nn", the
format of RT VALUE is
(0.0.0.0-
255.255.255.255): (0-
65535)
4.2 TransportNetwork Template
4.2.1 Local Office
Table 4-22 Local office

Modificatio A:Add, D:Delete,
A,D,M,P 　　
n Indication M:Modify, P:Pass
Managed
long: Primary
Element 　
[1..4095] Key
Object ID

When the Controller has
only one signaling point,
NET1 is recommended.
Net type of Primary
long:[1..255] When the RNC has more
local office Key
than one signaling point,
the values are used in
sequence.
Whether to
enable 1:Enable
long:[1,2] R-W-I
network 2:Disable
appearance
Default value is 0 if this
parameter can’t be
long:
Network configured.
[0..42949672 R-W
appearance It is valid when
95]
NETAPPEARANCEFLAG
=1.
14-bit
signalling This is an interconnection
point code long: parameter, so the peer
R-W-I
of local [0..16383] must be identical to the
office on local setting.
the net
24-bit
signalling This is an interconnection
long:
point code parameter, so the peer
[0..16777215 R-W-I
of local must be identical the local
]
office on setting.
the net
0:2G
Mode Type long:[0,1] R-I
1:3G (UMTS, AG)
20 Bytes, decimal.
This is an interconnection
ATM
string parameter. R-W
Address
GSM doesn't need to
config.
Network
Resource
It is valid just for UMTS,
Identifier Bit long:[0..10] R-W
and the default value is 0.
Num in CS
Domain
Network
Resource
It is valid just for UMTS,
Identifier Bit long:[0..10] R-W
and the default value is 0.
Num in PS
Domain
BSC ID long: It should be filled when R
[1..4095] Managed Element is GU
mode, and BSCID !=
MEID.


Other, it can be empty.
4.2.2 Static Route
Table 4-23 Static route

A,D,M,P 　　
It contains no more than
User label string R-W 　
80 characters.
Managed
Primary
Key
Object ID
Static
Primary
Route long:[1..5000] Unique in ME
Key
Number
This field is configured to
the destination IP
address, that is, the
expected destination IP
network prefix. This prefix
Static route
cannot start with 0, 127,
network ipv4 R-W-I
224 to 239, or 240 to 255.
prefix
When configuring it on
the Controller, we should
use the prefix of the
address at the Controller
side.
This field refers to the
mask of the destination
network number. The
Static route
network prefix and
network
long:[8..32] network mask must R-W-I
mask
match each other, and the
length
result of NOT mask AND
prefix must be 0
(ip&~mask = 0).
Route next The Next Hop IP Address
hop ipv4 is the address the R-W-I
address Controller needs to reach.
VPN ID of
sub port
Route long:[1..254] In the multi-route case, R-W-I
distance the smaller the
management distance,

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
0:unactived
bfd is long:[0..1] R-W-I
1:actived
enabled
4.2.3 IP Path Group
Table 4-24 IP Path Group

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Path Group long: Primary
Id [0..4095] Unique in ME. Key
Father Path long: 65535 is invalid, other
R-I
Group Id [0..65535] value must be in [0..4095]
2G:3..63
3G:3..31
CMP AG:3..31
long:[3..63] R-W-I
Module No. Support to modify the
module No. of path group
for Iu interface.
Path Group 2:ETHERNET_NOVLAN
long:[2,5] R-W-I
Bear Type 5:ETHERNET_VLANTAG
PLMN
sequence<lo
Group eg:1;2 R-I
ng,4>
Object ID
Ratio of
occupied
0 to 1000
private
sequence<lo If more than one
bandwidth R-W-I
ng,4> MCC/MNC, separate
of Path
each value by ';'
Group by
operator
Forward long: Configure the actual R-W-I
bandwidth(


kbps) [0..4294967] physical bandwidth.
Backward
long: Configure the actual
bandwidth( R-W-I
[0..4294967] physical bandwidth.
kbps)
4.2.4 IUB Office
Table 4-25 IUB Office

A:Add, D:Delete,
Modification M:Modify,
A,D,M,S,P 　　
Indication S:Swap,
P:Pass
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Adjacent
Net long: ATM/ATM+IP:101 to 999, Primary
Element [1..4095] IP/IPOE:1001 to 3999 Key
Identifier
Net long: Depend on the real
R-I
Element ID [1..65534] situation.
filled when the
modification indication is
PLMN
sequence<lo A(Add) or M(Modify),but it
Group R-M-I
ng,4> doesn't support the
Object ID
modifying operation.
PLMN ID:
[0..4294967295], eg:1;2
Each Node B must be
homed to one CMP for
processing. In principle, it
is required that the
CMP
long:[3..31] geographically adjacent R-W-I
Module No.
Node Bs should be
processed by the same
CMP module whenever
possible.
Config for
0: ATM
Bear Type
long:[0,1,2] 1: IP R-I
of Service
2: ATM+IP
in IUB

Config for
0: ATM
Bear Type
long:[0,1,2] 1: IP R-I
of NBAP in
2: ATM+IP
IUB
Config for
Bear Type
0: ATM
of
long:[0,1,2] 1: IP R-I
Common
2: ATM+IP
Channel in
IUB
0: Protection OFF
Switch of
1: Support multipath
IUB
long:[0..2] protection R-W-I
multipath
2: Support ATM+IP
protection
protection
1: QoS(according to
ARP/THP/TC)
Transport
2: QoS(according to
Qos Profile long:[1..2] R-W
service type)
Type
The default value is 2 if
this parameter is empty.
Subsystem long: The recommended value
R-W-I
of RUP [1,2,3,255] is 255.
ATM
address of
string 20 Bytes, decimal R-W
adjacent
office
Configure this parameter
NodeB
ipv4 only when IP SEC is R-W-I
Inner IP
used.
OMCB It must be unique if it is
Inner valid(not 0.0.0.0).
ipv4 R-W-I
Service Ip It can be configured under
Address multipath protection.
1:ATM+IP Transport,
Profile ID of 2:Only IP Transport.
Transport It can’t be filled when it is
Bearer only ATM transport.
Type Profile long:[1..255] System will configure it R-W
Related to according office's bear
Basic type when it is empty.
Priority This parameter is valid if
UPQOSMAPTYPE= 1.
Transport long:[1..32] 1:One or Two IP Paths, R-W
Qos Profile 2:Three IP Paths,
parameter 3:One ATM Path and Two
Index IP Paths,
4:ATM Paths,
5:One IPOE Path and
One IP Path,


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)

A,D,M,P 　　
User label string R 　
80 characters.
Managed
Primary
Key
Object ID
Adjacent
Net Quote ANEID of "IUB Primary
long:[1..4095]
Element Office" sheet. Key
Identifier
Destination Depend on the real
ipv4 R-W-I
IP address situation.
Destination
It is the mask length of
IP Address
long:[0..32] the destination IP R-W-I
Mask
address.
Length
It should be configured
OMCB Path
long:[1..3] when IUB office is R-W
priority
multipath production.
Path Group long:[0..4095] The recommended value R-I

Id is the same as ANEID.
Atm It must be the EDTA or
Interface string ESDTA board info. R-W-I
Board eg:rack/shelf/slot
E1 List string e1 index, separated by ";" R-W-I
1:Normal,
Iub Plan long:[1..2] R-I
2:High load
If this parameter is empty,
it will be configured by the
The default template.
number of The number of UBR Aal2
long:[1..20] R-W
UBR Aal2 PVC by user defined
PVC cannot be less than the
number of default
template.
4.2.6 ATM Bearer(IUB)
Table 4-27 ATM Bearer(IUB)

Modificatio A:Add, D:Delete, M:Modify,
A,D,M,P 　　
n Indication P:Pass
It contains no more than 80
characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Adjacent
Net long: Quote ANEID of "IUB
R
Element [1..4095] Office" sheet.
Identifier
The recommended value is
long: Primary
PVC ID 1 to 10000.
[1..12600] Key
Unique in ME.
Atm It must be the EAPB board
Interface string info. R-I
Board eg:rack/shelf/slot
ATM
long:[1..4] 　 R-I
Optical Port
VPI on long: For the external R-W-I
High End [0..4095] CVPI/CVCI, this is unique
in the office and must be
identical to the value of the
connected office. It is


recommended to use a
value smaller than or equal
to 4.
For the external
CVPI/CVCI, this is unique
VCI on long: identical to the value of the
R-W-I
High End [32..65535] connected office. It is
value smaller than or equal
to 256.
PVC 0: AAL5 signal
Service long:[0,2,4] 2: AAL2 user data R-I
Type 4: OMCB
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
CBR supports:
atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3),
atmNoClpNoScr(1)
atmClpTransparentNoScr(8
),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR support:

atmNoClpNoScr(1),
Service atmClpNoTaggingNoScr(2),
long:[0,1,2,4] R-W-I
Category atmClpTaggingNoScr(3),
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt(
13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
UBR supports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCdvt(11),
atmNoClpTaggingNoScr(10
).
Traffic Type long:[0..15] 0: NOTRF R-W-I
1: atmNoClpNoScr
2: atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr

6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
atmClpTransparentNoScr
9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
atmClpNoTaggingScrCdvt
14: atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell Unit: Kbps.
long:
rate for This Traffic Para supports
[0..18210661 R-W-I
CLP=0+1 all Service Category and all
33]
(PCR0+1) Traffic Type.
Unit: Kbps.
Peak cell Service Category:
long:
rate for CBR ,rtVBR and nrtVBR.
[0..18210661 R-W
CLP=0 Traffic Type:
33]
(PCR0) atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3).
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
Cell delay atmClpTransparentNoScr
long:
variation (8),
[0..42949672 R-W
tolerance atmNoClpNoScrCdvt (11),
95]
(CDVT) atmClpTaggingScrCdvt(14),
).
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Sustainable
long: Traffic Type:
cell rate for
[0..18210661 atmClpNoTaggingScr(5), R-W
CLP=0
33] atmClpNoTaggingScrCdvt(
(SCR0)
13),
atmClpTaggingScrCdvt(14).
Sustainable long: Unit: Kbps. R-W
cell rate for [0..18210661 Service Category:
CLP=0+1 33] rtVBR and nrtVBR.
(SCR0) Traffic Type:


atmNoClpScr(4).
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
Maximum atmClpNoTaggingScr(5),
long:
burst cell atmClpNoTaggingScrCdvt(
[0..42949672 R-W
number 13),
95]
(MBS) atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14),
atmNoClpScr(4).
Path Group long: The recommended value is
R
Id [0..4095] the same as ANEID.
For one PLMN, the value
range of TrPath ID is
[32..127].
sequence<lo
TrPath ID As the path ID of the AAL2 R
ng,4>
channel, this is globally
unique and starts with 32
for the ATM office.
As an interconnection
AAL2 Path long: parameter, this number
ID intra [1..42949672 must have the same R
office 95] configuration as the peer
office.
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
AAL2 Path
long:[0..1] configured, the AAL2 PATH R
Ownership
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 long:[10..14] 10:RT R
Service 11: NRT1
Type 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.
Application 1: ALCAP
Type of UNI long:[1..3] 2: NBAP(NCP) R
Link 3: NBAP(CCP)
ipv4 R-W
Destination
IP Address It is the mask length of the
long:[0..32] R-W
Mask destination IP address.
Length
OMCB It should be configured
Path long:[1..3] when IUB office is multipath R-W
priority production.
4.2.7 SCTP Config(IUB-ABIS)
Table 4-28 SCTP Config(IUB-ABIS)

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Adjacent
Net long: Quote ANEID of "IUB Primary
Element [1..65535] Office" sheet. Key
Identifier
The recommended value
for UMTS is:
1)IP: ANEID+1000,
Association long: Primary
2)IPOE: ANEID+1000,
ID [1..8400] Key
3)IP+IPOE:
IP=ANEID+1000,
IPOE=ANEID+4000
CMP 2G:3..63
long:[3..63] R-I
Module No. 3G:3..31
Local port long: This is the port number of R-W-I
[1..65535] the associated local end,
and must be the same as
the Peer-End Port No.


configured for the
associated peer end.
This is the Controller
signaling plane IP
Local IP
ipv4 address. R-W-I
address
It can be filled in one IP
address.
This is the port number of
the associated peer end,
Remote long: and must be the same as
R-W-I
port [1..65535] the Local-End Port No.
configured for the
This is the service IP
Remote IP address of the Site.
ipv4 R-W-I
address It can be filled in one IP
address.
SCTP
association
15:NBAP (3G)
bearer long:[15,21] R-I
21:IPABIS (2G)
protocol
type
Max
Retransmis
long:
sion default value:500 R-W
[10..3000]
Timeout(10
millisecond)
Min
Retransmis
long:
[10..1000]
Timeout(10
millisecond)
Initial
Retransmis
long:
[10..3000]
Timeout(10
millisecond)
Heartbeat
long:
Interval(10 default value:500 R-W
[10..6000]
millisecond)
Delayack
interval(10 long:[0..20] default value:20 R-W
millisecond)
4.2.8 IP Bearer(IUB)
Table 4-29 IP Bearer(IUB)

A,D,M,P 　　
User label string R
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Adjacent
Net long: Quote ANEID of "IUB Primary
Element [1..4095] Office" sheet. Key
Identifier
This ID is unique in the Primary
TrPath ID long:[0..7]
office. Key
Path Group long: The recommended value
ID [0..4095] is 1001 to 3999.
PLMN long:
Group [0..42949672
Object ID 95]
ipv4
Destination
IP Address It is the mask length of the
long:[0..32]
Mask destination IP address.
Length
The bandwidth ratio of
TrPath reserved for
signalling must be less
Path Tx than a specific value, and
Band width long: the specific value is the
R-W-I
of Trpath [0..4294967] maximum of one third of
(kbps) the minimum of Tx
bandwidth and the Rx
bandwidth, and
64000bps.
TrPath reserved for
Path Rx than a specific value, and
Band width long: the specific value is the
R-W-I
of Trpath [0..4294967] maximum of one third of
(kbps) the minimum of Tx
bandwidth, and
64000bps.


0:Invalid,
21:IP Domain No.1,
22:IP Domain No.2,
IP Domain long: 23:IP Domain No.3
R-W
No. [0,21,22,23] It should be configured to
effective value (21,22,23)
when IUB office is
It should be configured
OMCB Path
long:[1..3] when IUB office is R-W
priority
4.2.9 IPOE Bearer(IUB)
Table 4-30 IPOE Bearer(IUB)
Parameter Filling
Parameter Value 　Description Remarks
Name Instructions　
A:Add, D:Delete,
Modification
A,D,M,P M:Modify, 　
Indication
P:Pass
It contains no
User label string more than 80 R
characters.
Managed
Primary
Key
Object ID
Adjacent
Quote ANEID of
Net Primary
long:[1..4095] "IUB Office"
Element Key
sheet.
Identifier
rack/shelf/slot
It must be the
Board Info
string EDTI or ESDTI R-W
of IPOE
board info for
IPOE bear type.
0:ppp
[1..512]:Mp
When it is Multi-
MP Port PPP link,
long:[0..120] LOCALPORT is R
No.
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
Parameter Filling
Name Instructions　
List and "-"
The
Path Group recommended
long:[0..4095] R-I
ID value is 1001 to
3999.
TrPath ID :[0..7] Primary
TrPath ID sequence<long,4>
eg:0;1 Key
Destination Depend on the
ipv4 R-W-I
IP address real situation.
Destination It is the mask
IP Address length of the
long:[0..32] R-W-I
Mask destination IP
Length address.
0:Invalid,
21:IP Domain
No.1,
22:IP Domain
No.2,
23:IP Domain
IP Domain No.3
long:[0,21,22,23] R-W
No. It should be
configured to
effective value
(21,22,23) when
IUB office is
multipath
production.
It should be
configured when
OMCB Path
long:[1..3] IUB office is R-W
priority
multipath
production.
4.2.10 SCTP Config(ABIS)

Related to GSM network.
4.2.11 IP Bearer(ABIS)

4.2.12 Adjacent Office(CN)
Table 4-31 Adjacent Office(CN)

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Adjacent
Net long: The recommended value Primary
Element [1..4095] for UMTS is 1 to 99. Key
Identifier
Adjacent long:
for UMTS is the same as R-I
Office ID [1..2048]
ANEID.
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
Net sequence<lo
NEID of MGW office and R-I
Element ID ng,8>
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.
PLMN sequence<lo This parameter must be R-M-I

filled when the
modification indication is
A(Add) or M(Modify),but it
Group
ng,4> doesn't support the
Object ID
modifying operation.
PLMN ID:
[0..4294967295], eg:1;2
2:UMTS
Mode Type long:[2,3,6] R-I
3:GSM
6:AG
2G office:
32:RNC
64:MGW
576:MGW+MSCSERVER
1023:SMLC
3G office:
16:BSC
long: 32:RNC
Type of
[16,32,64,51 64:MGW
adjacent R-I
2,576,1023,4 512:MSCSERVER
office
096,32768] 576:MGW+MSCSERVER
4096:SGSN
32768:SAS
AG Office:
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
0: ATM (3G)
1: IP
2: TDM (2G)
(Parameters can't be
Bear type long:[0..2] R-I
modified)
When 2G office is
RNC,SRVBRSTYPE must
be 1.
Encode
type of 14:SPC 14 bits,
long:[14,24] R-W-I
signalling 24:SPC 24 bits
point
long:
Destination 14 bits:0..16383
[0..16777215 R-W-I
point code 24 bits:0..16777215
]
Sub- long: 0: International SPC, R-W-I
Service [0,4,8,12] international network, with
Field a code of 0x00H in the
signaling.
4: Reserved international
SPC, reserved
international network, with


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.
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
Connection between the local office
relationship and the adjacent office.
with local long:[1..3] Quasi-associated Mode R-W-I
signalling means there is no directly
point 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 0:Not Support
long:[0..1] R-W-I
broadband 1:Support
properties
1:CHINA
Protocol
long:[1..3] 2:ITU R-W-I
type
3:ANSI
ATM string 20 bytes, separate each R-W
address byte with ".", decimal.
For UMTS or AG, it must
configure the ATM
address when creating

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.
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
Default sequence<lo type is MSCSERVER.
R-W
Office Flag ng,4> 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.
range is [0..100].
For multi PLMNs, eg: 1;0.
IUFLEX networking. This
field is valid only when the
Capacity
NE type is
Weight in sequence<lo
MSCSERVER/SGSN, and R-W
CS/PS ng,4>
uses 0 invariably when
Domain
invalid, indicating
disabling of the IU FLEX
function of the
corresponding CN.
can be empty.
range is [0..4].
For multi PLMNs, eg: 1;0.
Number of
IUFLEX networking. This
Network
field is valid only when the
Resource sequence<lo
NE type is R-W
Identifier in ng,4>
MSCSERVER/SGSN, and
CS/PS
uses 0 invariably when
Domain
invalid.
It is invalid for GSM.
can be empty.


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
Network
3,then NRILIST is
Resource
10;11@100;101;103.
Identifier in string R-W
CS/PS
IUFLEX networking.
Domain
parameter, this parameter
will appear in the
TMSI/PTMSI allocated to
the UE by the network.
can be empty.
4.2.13 SCTP Config(CN)
Table 4-32 SCTP Config(CN)

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Quote the Adjacent Office
Adjacent long: Primary
ID of "Adjacent
Office ID [1..2048] Key
Office(CN)" sheet.
2G:1..2048
3G:1..3000
Association long: AG:1..3000 Primary
ID [1..3000] The recommended value Key
for UMTS is
1 to 1000.
2G:3..63
CMP
long:[3..63] 3G:3..31 R-W-I
Module No.
AG:3..31
Application long:[1..2] 1:Server R-W-I
type of 2:Client
association For the two ends
associated, at least one

must serve as the Client.
the associated local end,
long: and must be the same as
Local port R-W-I
[1..65535] the Peer-End Port No.
configured for the
It can be filled in four IP
Local IP address at most, such as
ipv4 R-W-I
Address xxx.xxx.xxx.xxx;xxx.xxx.xx
x.xxx
the associated peer end,
Remote long: and must be the same as
R-W-I
port [1..65535] the Local-End Port No.
configured for the
It can be filled in four IP
Remote IP address at most, such as
ipv4 R-W-I
Address xxx.xxx.xxx.xxx;xxx.xxx.xx
x.xxx
This is the ID number of
the application server.
ASP long: One ASP corresponds to
R-I
Number [1..8400] one and only one SCTP
association, and one AS
can have up to 16 ASPs.
Max
Retransmis
long:
[10..3000]
Timeout(10
millisecond)
Min
Retransmis
long:
[10..1000]
Timeout(10
millisecond)
Initial
Retransmis
long:
[10..3000]
Timeout(10
millisecond)
Heartbeat
long:
Interval(10 default value:500 R-W
[10..6000]
millisecond)
Delayack
interval(10 long:[0..20] default value:20 R-W
millisecond)

4.2.14 M3uaAS Config(CN)
Table 4-33 M3uaAS Config(CN)

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
ID of "Adjacent
Office(CN)" sheet.
Adopt the corresponding Primary
AS Number long:[1..640]
AS ID number Key
The value range of ASP
ASP sequence<lo
Number is 1..8400. R-W-I
Number ng,16>
eg:1;2
0: FALSE
1: TRUE
Each group of values
indicates whether the
local end and the peer
end are configured with
Whether routing context.
exists Select TRUE if one ASP
long:[0..1] R-W-I
routing occurs to more than one
context 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.
If one ASP occurs to more
than one AS, it is
necessary to specify
which AS this message
long: belongs to, that is, to
Routing
[0..4294967 specify the routing R-W-I
context ID
295] context. The routing
context is used as a
unique ID of an AS. The
invalid value is
4294967295.
Whether long:[0..1] 0: FALSE R-W
exists peer 1: TRUE
routing

context
long:
Peer routing
[0..4294967 4294967295 is invalid R-W
context ID
295]
1: SGP,
2: ASP,
3: IPSP SERVER,
4: IPSP CLIENT,
5: DOUBLE EXCHANGE
MODEL
This is an interconnection
parameter, so when the
IUR and IU are
interconnected, note that
the two ends should be
configured respectively as
AS property long:[1..5] R-W-I
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.
AS traffic long:[1..2] 1: Override, R-W-I
mode 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


purpose.
It is OK to select the
default value, or as
required, make the AS
value of N long:[0..16] R-W-I
available only when
multiple ASPs are
activated.
With little sense, this
value is not used now,
and it is recommended to
configure it to the
value of K long:[0..16] R-W-I
difference between the
total number of the
associations and the N
value.
4.2.15 M3uaRoute
Table 4-34 M3uaRoute

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Route Primary
long:[1..640] Unique in ME
Number Key
0:natural sort
Route
long:[0..2] 1:ikebana sort R-W-I
range mode
2:handworked sort
Quote AS Number of
AS1
long:[1..640] "M3uaAS Config(CN)" R-W-I
Number
sheet.
AS2
long:[0..640] 0 is valid R-W-I
Number
AS3
Number
AS4
Number
4.2.16 M3uaRouteSet
Table 4-35 M3uaRouteSet

A,D,M,P 　　
80 characters.
Managed
Primary
Key
Object ID
Quote the Adjacent
Adjacent Primary
long:[1..2048] Office ID of "Adjacent
Office ID Key
Office(CN)" sheet.
Quote the Route Number
Route ID 1 long:[1..640] R-W-I
of "M3uaRoute" sheet.
Route ID 2 long:[0..640] 0 is valid R-W-I
4.2.17 IP Path(CN)
Table 4-36 IP Path(CN)

A,D,M,P 　　
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
Adjacent
Net long: Quote ANEID of "Adjacent Primary
Element [1..4095] Office(CN)" sheet. Key
Identifier
This ID is unique in the Primary
Path ID long:[0..7]
office. Key
This is a globally unique
ID.
Path Group long: Primary
ID [0..4095] Key
for UMTS is
4001 to 4095.
2G:3..63
CMP
long:[3..63] 3G:3..31 R-W-I
Module No.
AG:3..31


Quote the PLMN Group
PLMN long: Object ID of "Plmn
Group [0..42949672 Config" sheet. It must be R-I
Object ID 95] the same as the plmn of
office.
Destination This is the service
ipv4 R-W-I
IP Address address of the peer office.
long:[0..32] This field refers to the R-W-I
mask length of the
destination network. The
Destination
network prefix and
IP Address
network mask must match
Mask
each other, and the result
Length
of NOT mask AND prefix
must be 0 (ip&~mask =
0).
TrPath reserved for
than a specific value, and
the specific value is the
maximum of one third of
the minimum of Tx
bandwidth, and
64000bps.
Forward
long: If there is only one path in
bandwidth( R-W-I
[0..4294967] the path group, it is
kbps)
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 long: The bandwidth ratio of R-W-I
bandwidth( [0..4294967] TrPath reserved for
kbps) signaling must be less
than a specific value, and
the specific value is the
maximum of one third of
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.
4.2.18 PVC Config(IU-IUR)
Table 4-37 PVC Config(IU-IUR)

A,D,M,P 　
User label string R
80 characters.
Managed
long: Primary
Element 　
[1..4095] Key
Object ID
ID of "Adjacent
Office(CN)" sheet.
for UMTS is:
AAL5 Signal of IUCS is
from 12000 to 12049;
AAL2 Data of IUCS is
from 12050 to 12499;
long: AAL5 Signal of IUPS is Primary
PVC ID
[1..12600] from 12500 to 12509; Key
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.
It must be the
Atm
EAPB/EDTA/ESDTA
Interface string R-I
board info.
Board
eg:rack/shelf/slot
ATM Optical Port:[1..4],
ATM port long:[1..244] R-I
IMA Port:[5..244]
IMA port need to be
E1 list string configured. R-W
Separated by ";"


For the external
VPI on long: identical to the value of
R-W-I
High End [0..4095] the connected office. It is
value smaller than or
equal to 4.
For the external
VCI on long: identical to the value of
R-W-I
High End [32..65535] the connected office. It is
value smaller than or
equal to 256.
0: AAL5 Signal,
1: AAL5 Data,
2: AAL2 Data
PVC
AAL5 Signal: the
Service long:[0..2] R-I
Signaling over ATM,
Type
AAL5 Data: IUPS is the
service over ATM,
AAL2 Data: IUCS or IUR
is the service over ATM.
PVC 2; IUR,
interface long:[2..4] 3: IUCS, R-I
type 4: IUPS
Service long:[0,1,2,4] 0:CBR R-W-I
Category 1:rtVBR
2:nrtVBR
4:UBR
CBR supports:
atmClpNoTaggingNoScr(2
),
atmNoClpNoScr(1)
atmClpTransparentNoScr(
8),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR

support:
atmNoClpNoScr(1),
),
(13),

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.
0: NOTRF
1: atmNoClpNoScr
2:
atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
Traffic Type long:[0..15] atmClpTransparentNoScr R-W-I
9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
14:
atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell Unit: Kbps.
long:
rate for This Traffic Para supports
[0..18210661 R-W-I
CLP=0+1 all Service Category and
33]
(PCR0+1) all Traffic Type.
Peak cell long: Unit: Kbps. R-W
rate for [0..18210661 Service Category:
CLP=0 33] CBR ,rtVBR and nrtVBR.
(PCR0) Traffic Type:


),
atmClpTaggingNoScr(3).
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
atmClpTransparentNoScr
Cell delay
long: (8),
variation
[0..42949672 atmNoClpNoScrCdvt (11), R-W
tolerance
95] atmClpTaggingScrCdvt(14
(CDVT)
),
0).
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Sustainable Traffic Type:
long:
cell rate for atmClpNoTaggingScr(5),
[0..18210661 R-W
CLP=0 atmClpNoTaggingScrCdvt
33]
(SCR0) (13),
).
Unit: Kbps.
Service Category:
Sustainable
long: rtVBR and nrtVBR.
cell rate for
[0..18210661 Traffic Type: R-W
CLP=0+1
33] atmClpTransparentScr(9),
(SCR0)
atmNoClpScr(4).
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
Maximum
long: atmClpNoTaggingScrCdvt
burst cell
[0..42949672 (13), R-W
number
95] atmClpTaggingScr(6),
(MBS)
),
atmNoClpScr(4).
Path Group long: This is a globally unique R
ID [0..4095] ID.
for UMTS is

4001 to 4095.
range of TrPath ID is
sequence<lo
TrPath ID [32..127]. R
ng,4>
This ID is unique in the
office.
AAL2 Select the number of the
Attached long:[3..31] module to which this path R-W
Module is attached.
AAL2 Path long: parameter, this number
ID intra [1..42949672 must have the same R
office 95] configuration as the peer
office.
10:RT
11: NRT1
12: NRT2
13: NRT3
14: MIX
AAL2 Path RT: for bearing real-time
Service long:[10..14] service, R
Type NRT1: for bearing R99
non-real-time service,
NRT2: for bearing HS
non-real-time service,
MIX: for bearing all types
of service.
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
AAL2 Path
long:[0..1] configured, the AAL2 R
Ownership
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 long:
Unique in ME R
link number [1..9000]
Linkset long:
Unique in ME R
number [1..1024]
Signalling Just select the number of
Link the module that manages
long:[3..31] R-W
Attached this link. Now only the
Module CMP module is available.


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
Signaling
long:[0..15] configuration as the peer R-W
Link Code
office. As an
interconnection
parameter, this code must
be compatible with the
peer. Each office can
have up to 16 signaling
link codes.
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
Destination
ipv4 not an interconnection R-W
IP address
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.
4.2.19 Mtp2Link
4.2.20 Mtp3Route
Table 4-38 Mtp3Route

A,D,M,P 　　
User label string R-W
80 characters.
Managed
Primary
Key
Object ID
Route ID long:[1..2000] Unique in ME Primary

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

4.2.22 Itc or BSC Office

4.2.23 PCM(ITC-MSC)
4.2.24 MSC Office


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
5 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 Filling
Name Instructions
A,D,M,P 　　
n Indication M:Modify,P:Pass
[Managed
Primary
Key
Object ID]
Cannot use invalid
User Label string:[0..80] R-W
character < > & ' "
Primary
RNC ID long:[0..4095] 　
Key
NodeB No long:[0..65535] 　 R-W-I
Primary
Cell ID long:[0..65534] 　
Key
Local Cell long:
　 R-W-I
Identity [0..268435455]
0:Band I,1:Band
II,2:Band
Frequency
III,3:Band
Band 　 R-W-I
IV,4:Band
Indicator
V,5:Band
VI,7:Band VIII
UUARFCN long: uarfcnUl is calculated R
[9612..9888,9262. by uarfcnDl, should not
.9538,12,37,62,87 input any value.
,112,137,162,187, {freqBandInd==0}
212,237,262,287, [9612..9888],
937..1288,1312..1 {freqBandInd==1}
513,1662,1687,17 [9262..9538][12][37]
12,1737,1762,178 [62][87][112][137][162]
7,1812,1837,1862 [187][212][237][262]
,4132..4233,782,7 [287],
87,807,812,837,8 {freqBandInd==2}
62,4162..4188,81 [937..1288],
2,837,2712..2863] {freqBandInd==3}

Parameter Filling
Name Instructions
[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]
{freqBandInd==0}
[10562..10838],
{freqBandInd==1}
[9662..9938][412][437]
long: [462][487][512][537]
[10562..10838,96 [562][587][612][637]
62..9938,412,437, [662][687],
462,487,512,537, {freqBandInd==2}
562,587,612,637, [1162..1513],
662,687,1162..15 {freqBandInd==3}
13,1537..1738,18 [1537..1738][1887]
DUARFCN 87,1912,1937,196 [1912][1937][1962] R-W-I
2,1987,2012,2037 [1987][2012][2037]
,2062,2087,4357.. [2062][2087],
4458,1007,1012,1 {freqBandInd==4}
032,1037,1062,10 [4357..4458][1007]
87,4387..4413,10 [1012][1032][1037]
37,1062,2937..30 [1062][1087],
88] {freqBandInd==5}
[4387..4413][1037]
[1062],
{freqBandInd==7}
[2937..3088]
Cell
Primary
long:[0..511] 　 R-W-I
Scrambling
Code
Location long:
　 R-W-I
Area Code [1..65533,65535]
Routing
long:[0..255] 　 R-W-I
Area Code
Service
long:[0..65535] 　 R-W-I
Area Code
Element Data Range
URA sequence<long,4 in Array is
R-W-I
Identity > [0..65535],and
separated by ";".
Service long:[0..65535] 　 R-W-I
Area Code
Parameter Filling
Name Instructions
for BC
Domain
long:
T_Cell 　 R-W-I
[0..9],<default:0>
5.2 Logic Cell Configuration
Table 5-40 Logic Cell Configuration

A,D,M,P 　　
[Managed
Primary
Key
Object ID]
User Label string:[0..80] 　 R-W
Primary
RNC ID long:[0..4095] 　
Key
Mobile
Primary
Country long:[0..999] 　
Key
Code
Mobile
Primary
Network long:[0..999] 　
Key
Code
can not repeat in the Primary
Cell ID long:[0..65534]
same PLMN. Key
Common
0:False,1:True,
PLMN 　 R-W-I
<default:1>
Indicator
5.3 External UTRAN Cell
Table 5-41 External UTRAN Cell

A,D,M,P 　　
[Managed
Primary
Key
Object ID]


Primary
RNC ID long:[0..4095] 　
Key
Cell Identity
Primary
of Adjacent long:[0..65535] 　
Key
Cell
RNC
Identity of Primary
long:[0..4095] 　
Adjacent Key
RNC
Mobile
Country long:[0..999] 　 R-W-I
Code
Mobile
Network long:[0..999] 　 R-W-I
Code
long:
Location
[1..65533,65535 　 R-W-I
Area Code
]
0:Band I,1:Band
II,2:Band
Frequency
III,3:Band
Band 　 R-W-I
IV,4:Band
Indicator
V,5:Band
VI,7:Band VIII
{freqBandInd==0}
[9612..9888],
{freqBandInd==1}
[9262..9538][12][37]
long:
[62][87][112][137][162]
[9612..9888,926
[187][212][237][262]
2..9538,12,37,6
[287],
2,87,112,137,16
{freqBandInd==2}
2,187,212,237,2
[937..1288],
62,287,937..128
{freqBandInd==3}
8,1312..1513,16
[1312..1513][1662]
UUARFCN 62,1687,1712,1 R
[1687][1712][1737]
737,1762,1787,
[1762][1787][1812]
1812,1837,1862
[1837][1862],
,4132..4233,782
{freqBandInd==4}
,787,807,812,83
[4132..4233][782][787]
7,862,4162..418
[807][812][837][862],
8,812,837,2712.
{freqBandInd==5}
.2863]
[4162..4188][812]
[837],
{freqBandInd==7}
[2712..2863]
DUARFCN long: {freqBandInd==0} R-W-I
[10562..10838,9 [10562..10838],
662..9938,412,4 {freqBandInd==1}
37,462,487,512, [9662..9938][412][437]

[462][487][512][537]
[562][587][612][637]
[662][687],
{freqBandInd==2}
537,562,587,61
[1162..1513],
2,637,662,687,1
{freqBandInd==3}
162..1513,1537.
[1537..1738][1887]
.1738,1887,191
[1912][1937][1962]
2,1937,1962,19
[1987][2012][2037]
87,2012,2037,2
[2062][2087],
062,2087,4357..
{freqBandInd==4}
4458,1007,1012
[4357..4458][1007]
,1032,1037,106
[1012][1032][1037]
2,1087,4387..44
[1062][1087],
13,1037,1062,2
{freqBandInd==5}
937..3088]
[4387..4413][1037]
[1062],
{freqBandInd==7}
[2937..3088]
Cell
Primary
long:[0..511] 　 R-W-I
Scrambling
Code
Service
Area Code
long:[0..65535] 　 R-W-I
for CS and
PS Domain
Element Data Range
URA sequence<long, in Array is
R-W-I
Identity 4> [0..65535],and
seperated by ";".
5.4 External GSM Cell
Table 5-42 External GSM Cell
Parameter Filling
Parameter Value 　Description Remarks　
Name Instructions
A,D,M,P 　　
[Managed
Primary
Key
Object ID]
Primary
RNC ID long:[0..4095] 　
Key
Cell long:[0..65535] 　 Primary

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

A,D,M,P 　　
[Managed
long: Primary
Element 　
[1..4095] Key
Object ID]
string:
User Label 　 R-W
[0..80]
long: Primary
RNC ID 　
[0..4095] Key
long:
Primary
eNodeB ID [0..2684354
Key
55]
EUTRAN
long: Primary
Cell 　
[0..255] Key
Identity
EUTRAN long: 　 R-W-I
Physical


Cell
[0..503]
Identity
Mobile
long:
Country 　 R-W-I
[0..999]
Code
Mobile
long:
Network 　 R-W-I
[0..999]
Code
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
Eutran
10,10:Band
Frequency
11,11:Band 　 R-W-I
Band
12,12:Band
Indicator
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
Downlink long: 　{eutranFreqBandInd==0} R-W-I
EUTRAN [0..65535] [0..599],
Absolute {eutranFreqBandInd==1}
Radio [600..1199],
Frequency {eutranFreqBandInd==2}
Channel [1200..1949],
Number
{eutranFreqBandInd==3}
[1950..2399],
[2400..2649],
[2650..2749],
[2750..3449],
[3450..3799],
[3800..4149],

[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 long: {eutranFreqBandInd==0} R-W-I
EUTRAN [0..65535] [18000..18599],
Absolute {eutranFreqBandInd==1}
Radio [18600..19199],
Frequency {eutranFreqBandInd==2}
Channel [19200..19949],
Number
[19950..20399],
[20400..20649],
[20650..20749],
[20750..21449],
[21450..21799],
[21800..22149],
[22150..22749],
[22750..22999],
[23000..23179],


[23180..23279],
[23280..23379],
[23730..23849],
[23850..23999],
[24000..24149],
[24150..24449],
[24450..24599],
[25500..25699],
[25700..26039],
[26040..26689]
Tracking long:
R-W-I
Area Code [0..65535]
long:
Location
[0..65533,6 　 R-W
Area Code
5535]
Routing long:
　 R-W
Area Code [0..255]
MNC BCD long:
Code [2,3],<defa R-W
Length ult:2>
EUTRAN 0:6,1:15,2:2
Measurem 5,3:50,4:75,
ent 5:100,<def
Bandwidth ault:0>
5.7 External EUTRAN Cell TDD
Table 5-45 External EUTRAN Cell TDD

A,D,M,P 　　
[Managed
long: Primary
Element 　
[1..4095] Key
Object ID]

string:
User Label 　 R-W
[0..80]
long: Primary
RNC ID 　
[0..4095] Key
long:
Primary
eNodeB ID [0..2684354
Key
55]
EUTRAN
long: Primary
Cell 　
[0..255] Key
Identity
EUTRAN
Physical long:
　 R-W-I
Cell [0..503]
Identity
Mobile
long:
Country 　 R-W-I
[0..999]
Code
Mobile
long:
Network 　 R-W-I
[0..999]
Code
32:Band
33,33:Band
34,34:Band
35,35:Band
Eutran 36,36:Band
Frequency 37,37:Band
　 R-W-I
Band 38,38:Band
Indicator 39,39:Band
40,40:Band
41,41:Band
42,42:Band
43
EUTRAN long: {eutranFreqBandInd==33} R-W-I
Absolute [0..65535] [36200..36349],
Radio {eutranFreqBandInd==34}
Frequency [36350..36949],
Channel {eutranFreqBandInd==35}
Number [36950..37549],
[37550..37749],
[37750..38249],
[38250..38649],
{eutranFreqBandInd==39 }
[38650..39649],
[39650..41589],


[41590..43589],
[43590..45589]
Tracking long:
R-W-I
Area Code [0..65535]
long:
Location
[0..65533,6 　 R-W
Area Code
5535]
Routing long:
　 R-W
Area Code [0..255]
MNC BCD long:
Code [2,3],<defa R-W
Length ult:2>
EUTRAN 0:6,1:15,2:2
Measurem 5,3:50,4:75,
ent 5:100,<def
Bandwidth ault:0>
5.8 Neighbouring Cell
Table 5-46 Neighbouring Cell

A,D,M,P 　　
[Managed
long: Primary
Element 　
[1..4095] Key
Object ID]
string:
User Label 　 R-W
[0..80]
long: Primary
RNC ID 　
[0..4095] Key
long: Primary
Cell ID 　
[0..65534] Key
Target RNC long: Primary
　
ID [0..4095] Key
Target Cell long: Primary
　
ID [0..65535] Key
5.9 GSM Neighbouring Cell
Table 5-47 GSM Neighbouring Cell

A,D,M,P 　　
[Managed
long: Primary
Element 　
[1..4095] Key
Object ID]
User Label string[0..80] 　 R-W
long: Primary
RNC ID 　
[0..4095] Key
long: Primary
Cell ID 　
[0..65534] Key
long:
Location Primary
[1..65533,6 　
Area Code Key
5535]
Cell long: Primary
　
Identifier [0..65535] Key
5.10 EUTRAN Neighbouring Cell
Table 5-48 EUTRAN Neighbouring Cell

A,D,M,P 　　
[Managed
long: Primary
Element 　
[1..4095] Key
Object ID]
string:
User Label 　 R-W
[0..80]
long: Primary
RNC ID 　
[0..4095] Key
long: Primary
Cell ID 　
[0..65534] Key
0:EUTRAN
EUTRAN
FDD,1:EUT R-I
Cell Type
RAN TDD
long:
Primary
eNodeB ID [0..2684354 　　
Key
55]
EUTRAN long: 　 Primary 　


Cell Identity [0..255] Key
5.11 User Authorized PLMN+SNAC Information
Table 5-49 User Authorized PLMN+SNAC Information
Parameter Paramet Filling

Name er Value Instructions　
A,D,M,P 　　
[Managed
long: Primary
Element 　
[1..4095] Key
Object ID]
string:
User Label 　 R-W
[0..80]
long: Primary
RNC ID 　
[0..4095] Key
[User
Authorized long:
Primary
PLMN+SNA [0..42949 　
Key
C Information 67295]
Object ID]
MCC of Element Data Range in
sequence
Shared Array is [0..999],and R-W-I
<long,10>
Network separated by ";".
MNC of 　Element Data Range in
sequence
Shared Array is [0..65535],and R-W-I
<long,10>
Network separated by ";".
The Imsi
long:
Matched 　 R-W-I
[1..15]
Digits Num
The Imsi Element Data Range in
sequence
Matched Array is [0..9],and R-W-I
<long,15>
Digit separated by ";".
Number of
long:
Shared
[1..10],<d R-W-I
Network
efault:1>
Code
5.12 MBMS Configuration

It is not necessary to configure this sheet at present.
5.13 MBMS Service Area Configuration

5.14 MBMS Frequency Layer Configuration

6 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. 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 Filling
Parameter Parameter 　Descriptio
Parameter Remarks Instructio
Name Value n
configuration ns　
e.g.:
xxx.xxx.xxx.x
Master xx,
SNTP recommende
ipv4 R-W-I
server d
address configuration:
129.0.100.10
0
SNTP Recommend
Synchroniz millisecond ed value:
ation cycle 1800000.
Time Zone long:[-720,- The value R-W-I
660,-600,- range:
540,-480,- -720:GMT-12

Common Filling
Parameter Parameter 　Descriptio
Parameter Remarks Instructio
Name Value n
configuration ns　
-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
420,-360,-
-120:GMT-2
300,-240,-
-60:GMT-1
180,-120,-
0:GMT
60,0,60,120,
60:GMT+1
180,240,300,
120:GMT+2
360,420,480,
180:GMT+3
540,600,660,
240:GMT+4
720,780]
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 0:Stop
long:[0,1] R-W-I
Time using 1:Start
flag
Start time
of the
Daylight
eg:Mon/Day/
Saving string R-W
Hour/Min
Time(Mon/
Day/Hour/M
in)
End time of
the Daylight
Saving eg:Mon/Day/
string R-W
Time(Mon/ Hour/Min
Day/Hour/M
in)
Step of
Daylight 60 is
long:
Saving recommende R-W
[0..33008]
Time(minut d value.
e)
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.
6.3 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. 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

7 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:
 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.
7.1.1 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.

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.

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.
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.
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.
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. 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.
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.
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
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
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
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:
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 customer’s
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
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. What’s 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 ATMoSTM-
IPoE1 IPoFE ATMoE1 ATM+IP
. E 1
1 IUB Office IUB Office IUB Office IUB Office IUB Office IUB Office
ATM
IP IP IP ATM
2 IP Bear(IUB) Bearer(IU
Bear(IUB) Bear(IUB) Bear(IUB) Bearer(IUB)
B Auto)
SCTP SCTP SCTP
SCTP Config Config Config Config
3
(IUB-ABIS) (IUB- (IUB- (IUB-
ABIS) ABIS) ABIS)
Static Static Static
4 Static Route
Route Route Route
IP Path IP Path IP Path IP Path
5
Group Group Group Group
ATM
6 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 user-
plane 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:
Table 7-52 Configuring Data of ATM Interface Board
Available
Available
Optical Port
Physic Available Optical Port
Parts (Sub- Speed
Board al Port Type Multiplexing
card, etc.) Mode
Board (porttype) Structure
(speedmod
(sdhtype)
e)
6:E1;
ASPB 0: INVALID 0: INVALID
7:T1
Not Not
No sub-card Not supported
supported supported
EDTS_2/EDTS 6:E1;
EDTA 0: INVALID 0: INVALID
_3 7:T1
1:SDH-
EAPB_ 63E1;
2 1:SDH-AU-4;
2:SDH-
ESDTA ESDTS_2 1:STM-1 2:SDH-AU-3;
63T1;
3:SONET-STS-1
3:SDH-
84T1
1:SDH-AU-4;
EAPB EXIS 5:ATM 1:STM-1 4:SONET-STS-
3C
1:SDH-
63E1;
1:SDH-AU-4;
2:SDH-
ESDTI ESDHS 1:STM-1 2:SDH-AU-3;
63T1;
EMSI 3:SONET-STS-1
3:SDH-
84T1
EDTS_3/EMDT 6:E1;
EDTI 0: INVALID 0: INVALID
S 7:T1
7.9.3 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 Logical Configuration

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

Function
Board Board Name Description
If master/slave
configuration is not
used, the cells cannot
be allocated to the
CMPs of CDR.
It is strongly
recommended that
master/slave
configuration be used
Completes control-plane
for this board. Each
protocol and user-plane
master board should
protocol processing of all
USP2a CDR be configured with
interfaces. It is equivalent to the
one CMP module No.
combination of CMP, DMP, and
If master/slave
RUP in RU12.
configuration is not
used, the cells cannot
be allocated to the
CMPs of CDR.
7.9.3.1 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.
 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.
User-Plane Board
System Field Name UDP Port No.
Type
V4 UMTS IUB SBCJ/SBCR 3200
V4 UMTS IUR SBCJ/SBCR 1152
V4 UMTS IUCS SBCJ/SBCR 1280
7.10 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.
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 Para Para

Traffic Type Para1 Para2 Para5
e Type 3 4
PCR0+
atmClpNoTaggingNoScr (3) PCR0
1
PCR0+
atmClpTaggingNoScr (4) PCR0
1
atmNoClpNoScr (2) PCR0+
cbr
1
PCR0+
atmClpTransparentNoScr (9) CDVT
1
PCR0+
atmNoClpNoScrCdvt (12) CDVT
1
rtVbr PCR0+
atmNoClpNoScr(2)
ntrVbr 1
PCR0+
atmClpNoTaggingNoScr(3) PCR0
1
PCR0+
atmClpTaggingNoScr(4) PCR0
1
atmClpNoTaggingScr(6) PCR0+ SCR0 MBS
1
Servic Para Para

Traffic Type Para1 Para2 Para5
e Type 3 4
atmClpNoTaggingScrCdvt(14 PCR0+ CDV
SCR0 MBS
) 1 T
PCR0+
atmClpTaggingScr(7) SCR0 MBS
1
PCR0+ CDV
atmClpTaggingScrCdvt(15) SCR0 MBS
1 T
PCR0+ SCR0+ CDV
atmClpTransparentScr(10) MBS
1 1 T
PCR0+ SCR0+ CDV
atmNoClpScrCdvt(13) MBS
1 1 T
PCR0+ SCR0+
atmNoClpScr(5) MBS
1 1
PCR0+
abr atmClpNoTaggingMcr(8) CDVT MCR
1
atmNoTrafficDescriptor(1)
PCR0+
atmNoClpNoScr(2)
1
ubr PCR0+
atmNoClpNoScrCdvt(12) CDVT
1
PCR0+
atmNoClpTaggingNoScr(11) CDVT
1
PCR0+
ubr+ atmTrafficForUbr+(16) MCR MBS MFS CDVT
1
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.
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 upper-
level 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

Select the slot No. for EGBP in the drop-
Used Ethernet IP Interface(IPV4)
down 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
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 control’s
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
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.
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. Name Common Scenarios

ATM+IP dual stack, ATM+IP
Template 1 ATM+IP Transport
multi-path scenario
Template 2 Only IP Transport IPoFE and IPoE1 scenarios
7.16.2 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

Template 1 Two IP Paths IPoFE and IPoE1 scenarios
Template 2 Three IP Paths
One ATM Path and Two IP
Template 3 Paths
Template 4 Two ATM Paths ATMoE1 scenario

One IPOE Path and One
Template 5 IPOFE Path
IPoE1+IPoFE multi-path scenario
One ATM Path and One IP ATM+IP dual stack, ATM+IP multi-
Template 6 Path path scenario
7.17 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.

06 Quick Data Configuration

Product Version Document Version Serial Number Reason for Revision

Date Document Version Prepared by Reviewed by Approved by

II ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

About This Document

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

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

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

4 Specifications of Configuring Equipment Template and Transport Network

IV ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

4.2.4 IUB Office........................................................................................................

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

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

VI ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

Figure 2-1 Template Importing Flow........................................................................................2

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

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

Table 1-1 Notices in Data Configuration..................................................................................1

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

X ©2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

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

1 Notices in Data Configuration

Table 1-1 Notices in Data Configuration

No. Contents Description

2 Introduction to Quick Data

Figure 2-1 Template Importing Flow

2.1 Overview of Plan Template

2.1.1 Template Info Sheet

2 © 2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

Figure 2-2 Template Info Sheet

2.1.2 Index Sheet

Figure 2-3 Index Sheet

2.1.3 Attributes of Parameters

Figure 2-4 Attributes of Parameters

Table 2-2 Parameter Attributes

Parameter Attributes Meaning Description

4 © 2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

2.1.4 Equipment Template

2.1.4.1 Introduction to Equipment Template

Figure 2-5 V4_Template_Equipment

2.1.4.2 An Example of Equipment Template

The template is corresponding to OMMR V12.14.10.

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.

Figure 2-6 V4_Template_TransportNetwork

2.1.5.2 An Example of Filled UMTS Radio Template

The template is corresponding to OMMR V12.14.10.

6 © 2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.

2.1.6 UMTS Radio Template

2.1.6.1 Introduction to UMTS Radio Template

Figure 2-7 UMTS Radio Quick Configuration Template

Figure 2-8 UMTS Radio Template

2.1.6.2 An Example of Filled UMTS Radio Template

The template is corresponding to OMMR V12.14.10.

UMTS Radio Quick

2.2 Common Functions

2.2.1 Loading Templates

Figure 2-9 Configuration Management

Figure 2-10 Create Subnetwork

Step 3: Right-click SubNetwork, choose Create Management Element, and set

8 © 2016ZTE CORPORATION. All rights reserved. ZTE Confidential & Proprietary.