ZXUR 9000 UMTS (V41120) Commissioning Guide-Quick Data Configuration - R14

A-PDF OFFICE TO PDF DEMO: Purchase from www.A-PDF.
com to remove the watermark
ZXUR 9000 UMTS (V4.11.20)

Quick Data Configuration
1
2
ZXUR 9000 UMTS (V4.11.20) Commissioning Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION
CORPORATI N 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 © 2014 ZTE CORPORAT

CORPORATION. ION. 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,
eans, without the prior written consent of ZTE CORPORATION is prohibited.
and are registered trademarks 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 asa granting, by
implication, estopped 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
without further notice due to improvement and update of ZTE
CORPORATION’s products and technologies.
ZTE CORPORATION
Address: Address: NO. 55

Hi-tech
tech Road South
ShenZhen
P.R.China
518057
Website: http://dms.zte.com.cn
Email: TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. I
3
Revision History
Product Version Document Version Serial Number Reason for Revision
OMMRV12.11.40P02 R1.0 First published
OMMRV12.11.40P03 R1.1 Some
ome contents added
Section
ection 5.5.3.4
User
User-Plane IP
OMMRV12.11.40P04 R1.2
Configuration Rules is
added
The
he templates
OMMRV12.11.40P05 R1.3 upgraded to
V12.11.40P05
1. ICM configuration
flow is updated.
2. Alarm shielding
configuration is
added.
3. Rules of
configuring
master/slave
EGPB are added.
4. Rules of
configuring slots
for USP are
OMMRV12.11.40P05 R1.4
added.
5. Iub-interface Qos
planning rules are
added.
6. Configuration of IP
function switch is
added.
7. The attachments
in Sections
2.1.4.2, 2.1.5.2,
and 2.1.6.2 are
updated.
Author
Prepared
Date Document Version Reviewed by Approved by
by
2012-06-28 R1.0 Cheng Chen Taiming, Hu
Hao Zhigang
Hao Zhigang
Hao Zhigang
Hao Zhigang
ZTE Confidential Proprietary

II ©2014ZTE CORPORATION.
C All rights reserved. Proprietary
4
Prepared
Date Document Version Reviewed by Approved by
by
Hao Zhigang
Intended audience: RNC commissioning engineer
About
Summary This Document
Chapter Description
1 Notices in Data Configuration Notices in Data Configuration
2 Introduction to Quick Data Introduction to Quick Data Configuration
Configuration
3 Specifications
cations of Configuring Specifications of Configuring Equipment Template &
Equipment Template & Transport Transport Network Template
Network Template
4 Specifications of Configuring Specifications of Configuring UMTS Radio Template
UMTS Radio Template
5 Special Subject Special Subject
ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. III
5
TABLE
1 Notices inOF
DataCONTENTS
Configuration 1
2 Introduction to Quick Data Configuration 2
2.1 Overview of Plan Templates 2
2.1.1 Template Info Sheet 2
2.1.2 Index Sheet 2
2.1.3 Attributes of Parameters 3
2.1.4 Equipment Template 4
2.1.5 Transport Network Template 4
2.1.6 UMTS Radio Template 6
2.2 Common Functions 7
2.2.1 Loading Templates 7
2.2.2 Exporting Templates 11
2.2.3 Check on Imported Quick Configuration Template 12
2.2.4 Restoring Data from Snapshot Area to Modify Area 13
2.2.5 Data Comparison Between Snapshot Area & Modify Area 14
3 Specifications of Configuring Equipment Template & Transport Network
Template 17
3.1 Equipment Template 17
3.1.1 Basic Info 17
3.1.2 Plmn Config 18
3.1.3 Shelf Config 19
3.1.4 Board Config 19
3.1.5 Global Info 20
3.1.6 Interface IP 21
3.1.7 Service IP 22
3.1.8 Slave or Dsp Service Config 22
3.1.9 CCIU Service Config 23
3.1.10 Channel Port 23
3.1.11 Member Port 23
3.1.12 Super Vlan 24
3.1.13 Super Vlan Member 24
3.1.14 DHCP Server 24
3.1.15 DHCP Client 24
3.1.16 DHCP Relay 24
3.1.17 VRF Attributes Config 24
3.1.18 VRF Route Target 24
3.2 TransportNetwork Template 24
3.2.1 Local Office 24
3.2.2 IUB Office 25
3.2.3 ATM Bearer(IUB Auto) 27
3.2.4 ATM Bearer(IUB) 27
3.2.5 IP Bearer(IUB) 30
3.2.6 IP Bearer (ABIS) 31
3.2.7 SCTP Config (IUB-ABIS)
ABIS) 31
3.2.8 Static Route 32
3.2.9 IP Path Group 32
3.2.10 IP Path (CN) 33
3.2.11 Adjacent Office (CN) 34
3.2.12 SCTP Config (CN) 36
3.2.13 M3uaAS Config (CN) 37

IV ©2014ZTE CORPORATION.
6
3.2.14 M3uaRoute 37
3.2.15 M3uaRouteSet 38
3.2.16 PVC Config (IU-IUR)
IUR) 38
3.2.17 Mtp3Route 41
3.2.18 Mtp3RouteSet 42
3.2.19 No.7 PCM 42
3.2.20 PCM(ITC-MSC) 42
3.2.21 Mtp2Link 42
3.2.22 MSC Office 42
3.2.23 SGSN Office42
3.2.24 Fr Gb 42
3.2.25 Ip Gb 42
3.2.26 Lucent Channel 43
3.2.27 iTC Office 43
4 Specificationsns of Configuring UMTS Radio Template44
4.1 UTRAN Cell 44
4.2 Logic Cell Configuration 45
4.3 External UTRAN Cell 46
4.4 External GSM Cell 47
4.5 Neighbouring Cell 49
4.6 GSM Neighbouring Cell 49
4.7 External ENodeB Function 49
4.8 External EUTRAN Cell FDD 49
4.9 External EUTRAN Cell TDD 49
4.10 EUTRAN Neighbouring Cell 49
4.11 User Authorized PLMN+SNAC Information 50
4.12 MBMS Configuration 50
4.13 MBMS Service Area Configuration50
4.14 MBMS Frequency Layer Configuration 50
5 Special Subject 51
5.1 ICM Data Configuration Flow (All-Parameter
(All Configuration) 51
5.1.1 ICM Initialization 51
5.1.2 Exporting Optimization Template (All Parameters) 52
5.1.3 Data Import 55
5.1.4 Deleting Plan Area 67
5.2 CMP Module No. Modification 68
5.3 Overall Office Information Deletion (Including Ground & Radio Resources)
69
5.4 Site Bearer Migration Function 69
5.5 Board Configuration 70
5.5.1 Slot Requirement for Master/Slave Boards 70
5.5.2 Configuration Guide of ATM Interface Board Properties 70
5.5.3 Introduction of USP Board 71
5.6 PVC Configuration 74
5.7 ATM Address Conversion 76
5.8 1588
88 Clock Configuration 77
5.9 Shielding Alarms 78
5.10 Rules of Configuring Master/Slave EGPB 78
5.11 Rules of Configuring Slots for USP 80
5.12 Iub-Interface
Interface Qos Planning Rules 80
5.12.1 QOS According to ARP/THP/TC 80
ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. V
7
5.12.2 QOS According to Service Type 81

5.13 IP Function Switch 81

VI ©2014ZTE CORPORATION.
8
FIGURES
Figure 2-1
1 Template Loading Flow 2
Figure 2-2
2 Template Info Sheet2
Figure 2-3 Index Sheet 3
Figure 2-4
4 Parameter Attributes 3
Figure 2-5
5 V4_Template_Equipment 4
Figure 2-6
6 V4_Template_TransportNetwork 4
Figure 2-7
7 UMTS Radio Quick Configuration Template 6
Figure 2-8
8 UMTS Radio Template 7
Figure 2-9
9 Configuration Management 7
Figure 2-10
10 Create Subnetwork 8
Figure 2-11
11 Create Management Element 8
Figure 2-12
12 Import Quick Configuration Data 8
Figure 2-13
13 Selecting the Template to Be Loaded 9
Figure 2-14
14 Executing Template Loading 9
Figure 2-15
15 Template Loaded Completely 10
Figure 2-16
16 Querying the Loading Result File 10
Figure 2-17
17 Loading Result 11
Figure 2-18
18 Export Quick Configuration Data 11
Figure 2-19
19 Template Exporting Interface 12
Figure 2-20
20 Check on Loaded Template12
Template
Figure 2-21
21 Global Check 13
Figure 2-22
22 Restoring Data from Snapshot Area to Modify Area 13
Figure 2-23
23 Restore Modify Area 14
Figure 2-24
24 Data Comparison 14
Figure 2-25
25 Select Compare Type 15
Figure 2-26
26 Comparison Result-1
Result 15
Figure 2-27
27 Comparison Result-2
Result 15
Figure 5-1
1 ICM Data Area 51
Figure 5-2
2 Plan Data Management 51
Figure 5-3
3 Live Data Area Synchronization 52
Figure 5-4
4 Exporting Optimization Template on ICM 52
Figure 5-5
5 Query and Export 53
Figure 5-6
6 Storage Path of Exported File 53
Figure 5-7
7 Data Exported Successfully 54
Figure 5-8
8 ICM Operation Flow 55
Figure 5-9 Creating Plan Area 55
Figure 5-10
10 Create Plan Area 55
Figure 5-11 Confirm 56
Figure 5-12
12 Importing Template 56
Figure 5-13
13 Importing Plan Template 57
Figure 5-14
14 Importing Optimization Template 58
Figure 5-15
15 Validity Check 59
Figure 5-16 Data Check-Validity
Validity 60
Figure 5-17
17 Check Result 60
Figure 5-18
18 Conflict Check 61
Figure 5-19
19 Confirm Live Data 62
Figure 5-20
20 Conflict Check Result 62
Figure 5-21
21 Submitting Data 63
Figure 5-22
22 Activating Data 63
Figure 5-23
23 Activating Task Management 64
ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. VII
9
Figure 5-24
24 Compare to Get Delta 64
Figure 5-25
25 Compare Success 65
Figure 5-26 Download 65
Figure 5-27
27 Download Success 66
Figure 5-28 Activate 66
Figure 5-29
29 Activate Success 66
Figure 5-30
30 Deleting Activation Task 67
Figure 5-31
31 Switching Submit Status 67
Figure 5-32
32 Deleting Plan Area 68
Figure 5-33
33 Confirming Plan Area 68
Figure 5-34 CMP Module No. Modification 68
Figure 5-35
35 Office Information Deletion (Including Ground & Radio Resources)
69
Figure 5-36
36 Site Bearer Migration 69
Figure 5-37
37 Diagram of Master/Slave Board Slots 70
Figure 5-38
38 Configuring Integrated UC Board 72
Figure 5-39
39 Configuring PVC in V3 Version 74
Figure 5-40
40 Configuring PVC in V4 Version 75
Figure 5-41
41 ATM Address Format 76
Figure 5-42
42 1588 Clock Configuration 1 77
Figure 5-43
43 1588 Clock Configuration 2 77
Figure 5-44
44 Shielding Alarms 78
Figure 5-45 Port Switch 79
Figure 5-46
46 Transport Qos Profile Type 80
Figure 5-47 Used Transport
ransport Bearer Type Profile Related to Basic Priority 80
Figure 5-48
48 Used Dedicated Service Transport Bearer Qos Profile 81
Figure 5-49
49 IP Function Switch 82
TABLES
Table 1-1
1 Notices in Data Configuration 1
Table 2-1
1 Parameter Attributes 3
Table 2-2
2 Sheets to Be Configured for IU/IUR and IUB 5
Table 2-3
3 Sheets to Be Configured for Different IUB-Interface
IUB Bearers 5
Table 2-4
4 Sheets to Be Configured for Different IU/IUR-Interface
IU/IUR Interface Bearers 6
Table 3-1 Basic Info 17
Table 3-2 Plmn Config 18
Table 3-3 Shelf Config 19
Table 3-4 Board Config 19
Table 3-5 Global Info 20
Table 3-6 Interface IP 21
Table 3-7 Service IP 22
Table 3-8
8 Slave or Dsp Service Config 22
Table 3-9
9 CCIU Service Config 23
Table 3-10 Channel Port 23
Table 3-11 Member Port 23
Table 3-12 Local Office 24
Table 3-13 IUB Office 25
Table 3-14
14 ATM Bearer (IUB Auto) 27
Table 3-15
15 ATM Bearer (IUB) 27
Table 3-16
16 IP Bearer (IUB) 30
Table 3-17
17 SCTP Config (IUB-ABIS)
(IUB 31
Table 3-18 Static Route 32

VIII ©2014ZTE CORPORATION.
10
Table 3-19
19 IP Path Group 32
Table 3-20 IP Path (CN) 33
Table 3-21
21 Adjacent Office (CN) 34
Table 3-22
22 SCTP Config (CN) 36
Table 3-23
23 M3uaAS Config (CN) 37
Table 3-24 M3uaRoute 37
Table 3-25
25 M3uaRouteSet 38
Table 3-26
26 PVC Config (IU-IUR)
(IU 38
Table 3-27 Mtp3Route 41
Table 3-28
28 Mtp3RouteSet 42
Table 4-1 UTRAN Cell 44
Table 4-2
2 Logic Cell Configuration 45
Table 4-3
3 External UTRAN Cell 46
Table 4-4
4 External GSM Cell 47
Table 4-5
5 Neighbouring Cell 49
Table 4-6
6 GSM Neighbouring Cell 49
Table 5-1
1 Sheets to Be Configured for Each Transmission Type of a New Site
69
Table 5-2
2 Configuring Data of ATM Interface Board 70
Table 5-3
3 Introduction of USP Board 71
Table 5-4 UDP Port No. 73
Table 5-5
5 Relation of PVC Traffic Type, Traffic Parameter, and PVC Service Type
75
Table 5-6
6 AFI of ATM Address 77
Table 5-7
7 1588 Clock Configuration Related Parameters 77
Table 5-8 Port Switch 79
Table 5-9
9 IUB QOS Planning Rules – 1 81
Table 5-10
10 IUB QOS Planning Rules – 2 81
ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. IX
11
12
ZXUR 9000 UMTS (V4.11.20) Com
Commissioning Guide
1In the
Notices inprocess,
data configuration Data Configuration
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. Item 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,”
2 PLMN ID each composed of 3 digits, e.g., for
460/1, the PLMN ID should be set as
460001.
Each master CMP board needs to
CMP Module No. for integrated UC
3 be configured with four CMPMP module
(CMP & UCIU)
Nos.
It is an address that needs to be
added for IUB-interface OMM
4 IUBCOM planning. Every 3 master CMPs
should be configured with one
IUBCOM.
5 Signaling point code Set it as a decimal value.
6 Netmask Set it as a decimal value.
It must be configured on the virtual
7 OMCB gateway IP
port.
In the synchronization process, the
system will check both the required
items and the optional items by
8 Global check default. Sometimes the optional
items may cause synchronization
failure andd the check can be cleared
manually.
In the “Slave or Dsp Service The IP of each line must include four
Config” sheet of the quick data types of protocol interfaces
9
configuration template, the (IUB/CS/PS/R). Do not fill in them in
granularity of each line is board. separate lines.
The description of Default Office The correct description should be:
10 Flag in the Adjacent Office (CN) 1:Is Default Office
sheet is incorrect. 0:Is Not Default Office
When the template is imported,
make sure the ATM Bearer (IUB
Auto) sheet and the IP Bearer (IUB)
sheet are both imported
successfully, or load the ATM Bearer
Bearer (IUB Auto) sheet
Matters for attention in ATM+IP
11 successfully first and then load the
multipath protection
IP Bearer (IUB) sheet. If the IP
Bearer (IUB) sheet is loaded before
the ATM Bearer (IUB Auto) sheet,
the system will report error, e.g., one
IUB office can only be configured with
with one NBAP link of NCP type.
ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 1
13
2There
Introduction to Quick
are three V4 quick data configuration Data
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 Loading Flow
2.12.1.1
Overview of Plan Templates
Template Info Sheet
The first sheet of all quick data configuration templates is the “Template Info”
sheet, which provides the basic template information for OMM. By this sheet,
OMM can judge whether the template matches with OMM and acquire the
categorization information of templates. Therefore, the content of this sheet must
be kept complete no matter which of other sheets are selected.
Figure 2-2 Template Info Sheet
2.1.2 Index Sheet

The second sheet of all templates is the “Index” sheet. It provides the overall
information about the content of the template and the categorization (UMTS/GSM)

2 © 2014ZTE
ZTE C
CORPORATION. All rights reserved. Proprietary
14
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 Parameter Attributes
The attributes of the parameters fall into the following categories according to
different applications. Please refer to Table 2-1
2 1 for the method of filling the
parameters of different attributes (Modifying this line is prohibited).
Table 2-1 Parameter Attributes
Parameter Attributes Meaning Description
R Read Read only
R-W Read and Write Can be read and 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.
This parameter must be
configured in the data
Primary Key Primary Key
creation and modification
process.
15
Note:
Do not modify the first line and the fifth line of the template. Otherwise, template
loading error will occur
occur.
2.1.4 Equipment Template
2.1.4.1 Introduction to the Equipment Template
Figure 2-5 shows the sheets included
included in the “Equipment” template, which can
fulfill rack, shelf, board, global information, and basic networking related data
configuration.
All sheets in this template 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 Filled Equipment Template

The
he template is corresponding to OMMR V12.11.40P03.
V4_Template_Equip
ment.xls
2.1.5 Transport Network Template

2.1.5.1 Introduction to the Transport Network 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 data configuration. Field engineers shall select the sheets according
to the actual application scenario.
Figure 2-6 V4_Template_TransportNetwork

4 © 2014ZTE
ZTE C
16
1. Sheets for IU/IUR and IUB

Select and fill in different
different sheets for the IU/IUR interface and IUB interface
according to the actual application scenario.
Table 2-2 Sheets to Be Configured for IU/IUR and IUB
No. IU/IUR IUB
1 Local Office IUB Office
2 Adjacent Office IP Bear (IUB)
3 SCTP Config (CN CN) SCTP Config (IUB-ABIS)
4 M3uaAS Config (CN) ATM Bearer (IUB Auto)
5 M3uaRoute ATM Bearer (IUB)
6 M3uaRouteSet
7 PVC Config (IU--IUR)
8 Mtp3Route
9 Mtp3RouteSet
10 IP Path(CN)
11 IP Path Group IP Path Group
12 Static Route Static Route
2. Sheets for different bearers on the IUB interface
The application of the IUB interface involves multiple bearers. Different
sheets should be filled in for different
different bearers on the IUB interface. The basic
rules of selecting the sheets are as listed in Table 2-3.
Table 2-3 Sheets to Be Configured for Different IUB-Interface
Interface Bearers
17
No IPoE1+IPoF ATMoSTM
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-ABIS
ABIS (IUB-ABIS (IUB-ABIS
) ) )
Static Static Static
4 Static Route
Route Route Route
IP Path IP Path IP Path
5
Group Group Group
ATM
6 Bearer(IU
B Auto)
3. Sheets for different bearers on the IU/IUR interface
The application of the IU/IUR interface involves multiple bearers. Different
sheets should be filled in for different bearers on the IUB interface. The basic
rules of selecting the sheets are as listed in Table 2-4.
Table 2-4 Sheets to Be Configured for Different IU/IUR-Interface
Interface Bearers
No. IUCS/R(ATM) IUCS/PS/R(IP) IUPS(IPOA)
1 Local Office Local Office Local Office
2 Adjacent Office Adjacent Office Adjacent Office
3 SCTP Config (CN) SCTP Config (CN)
4 M3uaAS Config (CN) M3uaAS Config (CN CN)
5 M3uaRoute M3uaRoute
6 M3uaRouteSet M3uaRouteSet
PVC Config
7 PVC Config (IU-IURIUR)
(IU-IUR)
8 Mtp3Route
9 Mtp3RouteSet
10 IP Path(CN) IP Path(CN)
11 IP Path Group IP Path Group
12 Static Route Static Route
2.1.5.2 An Example of Filled Transport Network Template
The template is corresponding to OMMR V12.11.40P03.
V4_Template_Trans
portNetwork.xls
2.1.6 UMTS Radio Template

2.1.6.1 Introduction to the UMTS Radio Template
Figure 2-7 shows the sheets included in the UMTS Radio Quick Configuration
Template. The radio parameters on the Iub interface
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

6 © 2014ZTE
ZTE CORPORATION.
18
The parameters in red in the first line must be filled in. This is similar to the
yellow areas in the V3 templates.
Figure 2-8 UMTS Radio Template
2.1.6.2 An Example of Filled UMTS Radio Template

The template is corresponding to OMMR V12.11.40P03.
V12.11.40P03
UMTS Radio Quick

Configuration Template.xls
2.22.2.1
Common Functions
Loading Templates
Step 1: Choose View > Configuration Management.
Figure 2-9 Configuration Management
19
Step 2: Right-click
click and choose Create Subnetwork. Set Subnetwork ID and Set
MCC according to the actual situation.
Figure 2-10 Create Subnetwork
Step 3: Right-click
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
Eleme
Step 4: Right-click ME and choose Import Quick Configuration Data..

Figure 2-12 Import Quick Configuration Data

8 © 2014ZTE
ZTE CORPORATION.
20
Step 5: Click Choose,

Choose select the template to be loaded, and click Open..
Figure 2-13 Selecting the Template to Be Loaded
Step 6: Click Execute to start loading template.

Figure 2-14 Executing Template Loading
21
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 Loaded Completely
C
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 Querying the Loading Result File Fil

10 © 2014ZTE
ZTE CORPORATION.
22
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 Loading Result
Note:
There is only one loading method for V4 quick configuration, no matter whether it is for
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
23
ZXUR 9000 UMTS (V4.11.20) Commiss
Commissioning Guide
Step 2: Fill in the values for Choose Directory and File Name Prefix according to
the actual situation, load the template needed by sheet, and click Execute
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
ZXUR 9000 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 Check on Loaded Template

12 © 2014ZTE
ZTE CORPORATION.
24
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.
This step can also be performed manually, as shown in Figure 2-21.
Figure 2-21 Global Check
3. License Center Check

Check whether the data configuration in OMM satisfies License control
requirements applied in the License Center. The execution of data
synchronization will trigger License check. If the data does not match the
the license,
the check will fail and the cause will be reported.
Note:
Only the data that passes the above three checks can be synchronized to ZXUR 9000.
9000. Loading data into OMM does not necessarily indicate successful data
synchronization.
2.2.4 Restoring Data from Snapshot Area to Modify Area
Click Configuration Management > Batch Network Elements Operation..
Figure 2-22 Restoring Data from Snapshot Area to Modify Area
25
After the Batch Network Elements Operation window pops up on OMM, select
target NE, and click Restore modify area to restore data from the snapshot area
the modify area. If Restored 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 Batch Compare Between Snapshot area
And Modify area.
Figure 2-24 Data Comparison
Comp

14 © 2014ZTE
ZTE CORPORATION.
26
Select the target NE, and click run. After the Select Compare Type window pops
up on OMM, choose a comparison mode and click OK.
Figure 2-25 Select
elect Compare Type
Observe the value of Result. If it is Difference,, it means there is some difference

between the snapshot area and the modify area.
Figure 2-26 Comparison Result-1
Result
Double-click
click the record to view the details.
Figure 2-27 Comparison Result-2
Result
27
Note:
There are two modes for comparing data:
1. Fast Compare: It is used to compare only the “last modify time.” The advantage of this
of this mode is its fast speed.
2. Full Compare: It is used to compare all parameters. The advantage is its preciseness.
preciseness.

16 © 2014ZTE
ZTE C
28
3ThisSpecificationscations
Guide deals mainly of sheets
with the common Configuring
for UMTS products. For the sheets not
introduced in this Guide, please contact the chief engineers in the head office for
confirmation in advance.
3.13.1.1
Equipment Template
Basic Info
Table 3-1 Basic Info
Parameter Parameter
Description Remark
Name Value
Modificatio A:Add,
n A,M,P D:Delete,
Indication M:Modify, P:Pass
Managed long:[1..409 Primary
Element ID 5] Key
2:UMTS
Mode Type long:[2..4] 3:GSM R-I
4:GU
Omp's
ipv4 eg:xxx.xxx.xxx.xxx R-W-II
omc port ip
Omp's
omc port
long:[0..32] R-W-II
mask
length
Omp's eg:xxx.xxx.xxx.xxx
omc port ipv4 UMTS It should be as same as the IP
UMTS: R-W-II
gateway address of bond2:1
IP address
of SNTP ipv4 eg:xxx.xxx.xxx.xxx R-W-II
server
SNTP 0:Not use NTP clock synchronization,
networking long:[0..2] 1:Connected by OMM server, R-W-II
mode 2:Connected by RPU
OMCB
Agent IP
ipv4 eg:xxx.xxx.xxx.xxx R-W-II
Address to
NODEB
OMCB
Server IP ipv4 eg:xxx.xxx.xxx.xxx R-W-II
Address
OMCB
Server IP
long:[0..32] R-W-II
Mask
Length
eg:xxx.xxx.xxx.xxx
OMCB
It can be used when it supports multipath
Inner Ip ipv4 R-W-II
protection.
Address
Other,it is filled in default value 0.0.0.0 .
29
ZXUR 9000
00 UMTS (V4.11.20) Commissioning Guide
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,-6 -
-300:GMT-5
60,-600,-54 -
-240:GMT-4
0,-480,-420, -
-180:GMT-3
-360,-300,-2 -
-120:GMT-2
40,-180,-12 -
-60:GMT-1
Time Zone 0,-60,0,60,1 0:GMT R-W-II
20,180,240, 60:GMT+1
300,360,420 120:GMT+2
,480,540,60 180:GMT+3
0,660,720,7 240:GMT+4
80] 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
0:
long:[0,1] R-W-II
Time using 1:Start
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:[0..330
Saving 60 is recommended value. R-W
08]
Time(minut
te)
3.1.2 Plmn Config
Table 3-2 Plmn Config
Parameter Parameter
Description Remark
Name Value

18 © 2014ZTE
ZTE CORPORATION.
30
Modificatio
A,D,M,P A:Add, D:Delete, M:Modify, P:Pass
n Indication
User label String R-W
Managed long:[1..409 Primary
Element ID 5] Key
PLMN
long:[0..429 Primary
Group
4967295] Key
Object ID
Mobile
long:[0..999
Country R-W-II
]
Code
Mobile
long:[0..999
Network R-W-II
]
Code
MNC BCD
Code long:[2..3] R-W-II
Length
Default
0:false
PLMN long:[0..1] R-W-II
1:true
Indicator
Is Local
0:false
Office's long:[0..1] R-I
1:true
PLMN
3.1.3 Shelf Config
Table 3-3 Shelf Config
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed Primary
long:[1..4095]
Element ID Key
Primary
Rack No. long:[1..1]
Key
Primary
Shelf No. long:[1..3]
Key
Master 0:Not Master Shelf
long:[0..1] R-W-I
Shelf Flag 1:Is Master Shelf
3.1.4 Board Config
Table 3-4 Board Config
Parameter Parameter
Description Remark
Name Value
Modification
A,D,P A:Add, D:Delete, P:Pass
Indication
Managed
long:[1..4095] Primary
Element ] Key
Object ID
Primary
rack/shelf/slot string eg:1/2/7
Key
Physical
string eg:UMP R-I
Board Type
31
Logical Board
string eg:OMP R-I
Type
It should be filled multi module No., if
Module No. string there are multi modules on one board. R-I
eg:3;4;5
0:No Backup
Backup Mode long:[0,1,5] 1:1+1 Backup R-I
5:1TO1 Backup
0:PUBLIC
Mode Type long:[0..2] 1:2G R-I
2:3G
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
1:SDH AU-4
Sdh speed
long:[0..4] 2:SDH AU-3 R-I
mode
3:SONET STS-1
4:SONET STS-3C
0:Multi-Frame
1:Double Frame
E1 Frame
long:[0,1,4,6] 4:Multi-Frame with checked R
Type
6:Forced Multi-Frame(default value)
It can be empty.
0:75Ω(default value of Electric E1)
1:120Ω
E1
long:[0,1,3] 3:Invalid(default value of Channelized R
Impedance
E1)
It can be empty.
Cable Type of
2:Fiber(default value)
of Ethernet long:[2,3] R
3:Cable
Port
CS Slave It is valid for GSM mode type.
Number Per long:[0..15] The default value is 6(SBCJ) for 2G R
RUP RUP board.
3.1.5 Global Info
Table 3-5 Global Info
Parameter Parameter
Description Remark
Name Value
Modification
A,M,P A:Add, M:Modify, P:Pass
Indication
Managed
long:[1..4095]
Element ]
Primary Key
Object ID
IP Segment
ReAssemble string eg:rack/shelf/slot R-W
Default Unit

20 © 2014ZTE
ZTE CORPORATION.
32
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
3.1.6 Interface IP
Table 3-6 Interface IP
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User Label string R-W
Managed
Element long:[1..4095] Primary Key
Object ID
Interface
string eg:rack/shelf/slot Primary Key
Board
It should be filled when it is Virtual
Module No. long:[1..127] Primary Key
port. Other,it can be filled in 1.
0:Interface
Port Type long:[0,1,2] 1:Loopback port Primary Key
2:Virtual port
Interface 0:invalid,
Local Port long:[0..128] 1~4:real port, Primary Key
No. 1~128:loop port
VLAN
long:[0..4095] 0 is invalid Primary Key
Sequence
0 is invalid.
Vlan ID long:[0..4095] R-W-I
It is valid when it is sub interface.
33
VPN ID of sub
sub port
long:[0..254] 0 is invalid R-W-I
MAC eg:
string R-W
address xx-xx-xx-xx-xx-xx
IP address of eg:
ipv4 R-W-I
interface xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx
Mask Length
of interface long:[0..32] eg:24;24 R-W-I
IP
3.1.7 Service IP
Table 3-7 Service IP
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
long:[1..4095]
Element ]
Primary Key
Object ID
eg:
Service IP ipv4 Primary Key
xxx.xxx.xxx.xxx
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 Interface of GSM
address(2G)
Network
Bit3=1:Gb Interface of GSM Network
Bit0=1:Iub Interface of 3G Network
Bit1=1: Iur Interface of 3G Network
Application
Bit2=1: IuCS Interface of 3GNetwork
Type of IP string R
Bit3=1: IuPS Interface of 3G Network
address(3G)
Bit4=1:Iub Common Interface of 3G
Network (for CCIU)
VPN ID of sub
sub port
long:[0..254] 0 is invalid R-I
eg:
MCC1:MNC1;MCC2:MNC3
PLMN info of
string or 65535:65535, R-W-I
Service IP
65535:65535 denotes supporting all
PLMN
3.1.8 Slave or Dsp Service Config
Table 3-8 Slave or Dsp Service Config
Parameter Parameter
Description Remark
Name Value
Modificatio
n Indication
Managed
Element 5] Key
Object ID
Data Format:
RACK/SHELF/SLOT, Primary
Board Info string
2G:RUP or ETCB or EDTB or ESDTB board Key
3G:RUP or DRP board

22 © 2014ZTE
ZTE CORPORATION.
34
Service IP Data Format:

Address of Primary
string xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx;xxx.xxx.xxx
SLAVE Key
.xxx;xxx.xxx.xxx.xxx
3.1.9 CCIU Service Config
Table 3-9 CCIU Service Config
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element 5] Key
Object ID
Service IP
Address of Data Format(Iub Common Interface): Primary
string
CCIU xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx Key
SLAVE
3.1.10 Channel Port
Table 3-10 Channel Port
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label string R-W
Managed
Element 5] Key
Object ID
Channel Primary
Group ID
long:[1..16]
Key
VLAN long:[0..409 Primary
0 is invalid
Sequence 5] Key
long:[0..409 0 is invalid.
Vlan ID R-W-II
5] It is valid when it is sub interface.
3:on Mode
Bound
long:[3..5] 4:backup Mode R-W-II
Mode
5:802.3AD Mode
VPN ID of long:[0..254
sub port ]
0 is invalid R-W-II
MAC eg:
string R-W
address xx
xx-xx-xx-xx-xx-xx
IP address eg:
ipv4 R-W-II
of interface xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx
Mask
Length of long:[0..32] eg:24;24 R-W-II
interface IP
3.1.11 Member Port
Table 3-11 Member Port
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label R-W
35
Managed
Element 5] Key
Object ID
Member
port ID of long:[1..128] Primary
Channel ] Key
Group
Interface
Board string eg:rack/shelf/slot R-I
Local port
No. of
member port long:[1..4] R-I
port
Channel
Group ID
long:[1..16] R-I
Bounding 1:active
mode of 2:passive
long:[1..4] R-W-II
member 3:on
port 4:backup
System
Priority of long:[1..655
35]
The default value is 32768. R-W
LACP
protocol
Timeout
0:long time,
Type of
long:[0..1] 1:short time, R-W
LACP
The default value is 0.
protocol
3.1.12 Super Vlan
Configure this sheet according to the specifications of the quick configuration
template.
3.1.13 Super Vlan Member
template.
3.1.14 DHCP Server
template.
3.1.15 DHCP Client
template.
3.1.16 DHCP Relay
Configure this sheet according to the specifications
specifications of the quick configuration
template.
3.1.17 VRF Attributes Config
template.
3.1.18 VRF Route Target
template.
3.23.2.1
TransportNetwork
Local Office
Template
Table 3-12 Local Office
Parameter Parameter
Description Remark
Name Value

24 © 2014ZTE
ZTE CORPORATION.
36
Modification
Indication
Managed
Element
5] Key
Object ID
Net type of long:[1..255] Primary
local office ] Key
Whether to
enable 1:Enable
network long:[1,2] R-W-I
2:Disable
appearance
Default value is 0 if this parameter cann't be
Network long:[0..4294 be configurated.
It is valid when NETAPPEARANCEFLAG=1. R-W
appearance 4967295]
NETAPPEARANCEFLAG=1.
14-bit
signalling point
point code of long:[0..1638
R-W-I
local office on 83]
on the net
24-bit
signalling point
point code of long:[0..1677
R-W-I
local office on 77215]
on the net
0:2G
Mode Type long:[0,1] R-I
1:3G
20 Bytes, decimal.
ATM address string R-W
GSM doesn't need to config.
Network
Resource
Identifier Bit It is valid just for UMTS, and the default value is
long:[0..10] R-W
Num in CS value is 0.
Domain
Network
Resource
Identifier Bit It is valid just for UMTS, and the default value is
long:[0..10] R-W
Num in PS value is 0.
Domain
It should be filled when Managed Element is

long:[1..4095
BSC ID is GU mode, and BSCID != MEID. R
5]
Other, it can be empty.
3.2.2 IUB Office
Table 3-13 IUB Office
Parameter Parameter
Description Remark
Name Value
A:Add, D:Delete, M:Modify,
Modification
A,D,M,S,P S:Swap,
Indication
P:Pass
37
Managed
Element 5] Key
Object ID
Adjacent Net
Element 5] Key
Identifier
Net Element long:[1..655
R-I
ID 34]
PLMN Group sequence<l eg:1;2
R-I
Object ID ong,4> PLMN ID:[0..4294967295]
CMP Module
long:[3..31] R-W-II
No.
Config for
0: ATM
Bear Type of
long:[0,1,2] 1: IP R-I
Service in
2: ATM+IP
IUB
Config for 0: ATM
Bear Type of long:[0,1,2] 1: IP R-I
NBAP in IUB 2: ATM+IP
Config for
Bear Type of 0: ATM
Common long:[0,1,2] 1: IP R-I
Channel in 2: ATM+IP
IUB
Protection
0: Protection OFF
flag in IUB
long:[0..2] 1: Support multipath protection R-W-II
mutual
2: Support ATM+IP protection
production
1: QoS(according to ARP/THP/TC)
Transport
2: QoS(according to service type)
Qos Profile long:[1..2] R-W
The default value is 2 if this parameter is
Type
empty.
Subsystem long:[1,2,3,
The recommended value is 255. R-W-II
of RUP 255]
ATM address
of adjacent string 20 Bytes, decimal R-W
office
NodeB Inner
ipv4 R-W-II
IP
OMCB Inner
Service Ip ipv4 R-W-II
Address
1:ATM+IP Transport,
Profile ID of 2:Only IP Transport.
Transport It cann't be filled when it is only ATM
Bearer Type long:[1..255 transport.
R-W
Profile ] System will configure it according office's
Related to bear type when it is empty.
Basic Priority This parameter is valid if
UPQOSMAPTYPE= 1.

26 © 2014ZTE
ZTE CORPORATION.
38
1:Two IP Paths,
2:Three IP Paths,
3:One ATM Path and Two IP Paths,
Transport
4:Two ATM Paths,
Qos Profile
long:[1..32] 5:One IPOE Path and One IPOFE Path, R-W-I
parameter
6:One ATM Path and One IP Path.
Index
This parameter is valid if
UPQOSMAPTYPE=2.It can be filled in any
value if it is invalid.
3.2.3 ATM Bearer(IUB Auto)
Table 3-14 ATM Bearer (IUB Auto)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label string R
Managed
Element 5] Key
Object ID
Adjacent Net
Element 5] Key
Identifier
Destination
ipv4 R-I
IP address
Destination
IP Address long:[0..32] R-I
Mask Length
OMCB Path It should be configured when IUB office is
priority long:[1..3] multipath production. R
Path Group long:[0..409
R-I
Id 5]
Atm Interface
string rack/shelf/slot R-I
Board
E1 List string e1 index, separated by ";" R-I
3.2.4 ATM Bearer(IUB)
Table 3-15 ATM Bearer (IUB)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label string R
Managed
Element
5] Key
Object ID
Adjacent Net
long:[1..4095
Element R
5]
Identifier
PVC ID
00] Key
Atm Interface
string rack/shelf/slot R-I
Board
39
ZXUR 9000 UMTS (V4.11.20)
.20) Commissioning Guide
ATM port long:[1..4] ATM Optical Port:[1..4] R-I

VPI on High long:[0..4095
R-W-I
End 5]
VCI on High long:[32..655
R-W-I
End 535]
0: AAL5 signal
PVC Service
long:[0,2,4] 2: AAL2 user data R-I
Type
4: OMCB
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
CBR surpports:
atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3),
atmNoClpNoScr(1)
atmClpTransparentNoScr(8),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR surpport:

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

28 © 2014ZTE
ZTE C
40
Peak cell rate Unit: Kbps.

long:[0..1821
for CLP=0+1 This Traffic Para surpports all Service Category R-W-I
1066133]
(PCR0+1) Category and all Traffic Type.
Unit: Kbps.
Service Category:
Peak cell rate CBR ,rtVBR and nrtVBR.
long:[0..1821
for CLP=0 Traffic Type: R-W
1066133]
(PCR0) atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3).
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and UBR.
Traffic Type:
Cell delay atmClpTransparentNoScr (8),
variation long:[0..4294 atmNoClpNoScrCdvt (11),
tolerance R-W
4967295] atmClpTaggingScrCdvt(14),
(CDVT) atmClpTransparentScr(9),
Unit: Kbps.
Service Category:
Sustainable rtVBR and nrtVBR.
cell rate for long:[0..1821 Traffic Type:
CLP=0 (SCR0) atmClpNoTaggingScr(5), R-W
1066133]
(SCR0) atmClpNoTaggingScrCdvt(13),
atmClpTaggingScrCdvt(14).
Unit: Kbps.
Service Category:
CLP=0+1 R-W
1066133] atmClpTransparentScr(9),
(SCR0) atmNoClpScrCdvt(12),
atmNoClpScr(4).
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
Maximum atmClpNoTaggingScr(5),
burst cell long:[0..4294 atmClpNoTaggingScrCdvt(13),
number (MBS) R-W
4967295] atmClpTaggingScr(6),
(MBS) atmClpTaggingScrCdvt(14),
atmNoClpScr(4).
Path Group Id long:[0..4095

R
Id 5]
sequence<lo For one PLMN, the value range of TrPath ID is
TrPath ID R
ong,4> ID is [32..127].
AAL2 Path ID long:[1..4294
R
intra office 4967295]
AAL2 Path 0:Local End
long:[0..1] R
Ownership 1:Peer End
41
10:RT
11: NRT1
AAL2 Path long:[10..14] 12: NRT2 R
Service Type ] 13: NRT3
14: MIX
Application 1: ALCAP
Type of UNI long:[1..3] 2: NBAP(NCP) R
Link 3: NBAP(CCP)
Destination IP
ipv4 R-W
IP address
Destination IP
IP Address long:[0..32] R-W
Mask Length
long:[1..3] R-W
priority multipath production.
3.2.5 IP Bearer(IUB)
Table 3-16 IP Bearer (IUB)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label string R
Managed
Element 5] Key
Object ID
Adjacent Net
Element 5] Key
Identifier
SCTP
association
0] Key
ID
The bandwidth ratio of TrPath reserved for
signalling must be less than a specific
Path Tx Band
long:[0..429 value, and the specific value is the
width of R-W
4967] maximum of one third of the minimum of
Trpath (kbps)
Tx bandwidth and the Rx bandwidth, and
64000bps.
Path Rx
Band width of R-W
Trpath (kbps)
64000bps.
R
ID 5]
Board Info of
string rack/shelf/slot R-W
IPOE
E1 List string Separated by ";" R-W
E1 TS List string Separated by ";" and "-" R-W
long:[0..120 0:ppp
MP Port No. [1..120]:Mp
R
]

30 © 2014ZTE
ZTE C
42
If MPLINK>0, then filling the Ip address of

Ip Address of
MP or port, else filling the Ip Address of
MP or PPP ipv4 R
PPP or port.
Port
It can be empty.
If MPLINK>0, then filling the Ip address
Ip Address
mask length of MP or port, else filling the
Mask Length
long:[8..32] Ip address mask length of PPP or port. R
of MP or PPP
It can be empty.
Port
Default is 24.
21:IP Domain No.1,
IP Domain long:[21..23
22:IP Domain No.2, R-W
No. ]
23:IP Domain No.3
long:[1..3] R-W
priority multipath production.
3.2.6 IP Bearer (ABIS)
Related to GSM network.
3.2.7 SCTP Config (IUB-ABIS)
Table 3-17 SCTP Config (IUB-ABIS)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element 5] Key
Object ID
Association long:[1..840 Primary
ID 0] Key
CMP Module 2G:3..63
long:[3..63] R-I
No. 3G:3..31
long:[1..655
Local port 35]
R-W-II
Local IP
ipv4 It can be filled in one IP address R-W-II
address
long:[1..655
Remote port 35]
R-W-II
Remote IP
ipv4 It can be filled in one IP address R-W-II
address
SCTP
association 15:NBAP
long:[15,21] R-I
bearer 21:IPABIS
protocol type
Max
Retransmissi
long:[10..30
on default value:500 R-W
00]
Timeout(10m
illisecond)
Min
Retransmissi
long:[10..10
00]
Timeout(10m
illisecond)
43
Initial
Retransmissi
long:[10..30
00]
Timeout(10m
illisecond)
Heartbeat
long:[10..60
Interval(10mil default value:500 R-W
00]
lisecond)
Delayack
interval(10mil long:[0..20] default value:20 R-W
lisecond)
3.2.8 Static Route
Table 3-18 Static Route
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label R-W
Managed
Element 5] Key
Object ID
Static Route long:[1..500 Primary
Number 0] Key
Static route
eg:
network ipv4 R-W-II
xxx.xxx.xxx.xxx
prefix
Static route
network long:[8..32] R-W-II
mask length
Route next
long:[0..0] 0:IP address R-I
hop type
Route next eg:
ipv4 R-W-II
hop address xxx.xxx.xxx.xxx
VPN ID of sub long:[0..254
sub port ]
0 is invalid R-W-II
Route long:[1..254]
]
R-W-II
distance
The flag if bfd 0:unactived
long:[0..1] R-W-II
is enabled 1:actived
3.2.9 IP Path Group
Table 3-19 IP Path Group
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element 5] Key
Object ID
Path Group long:[0..409 Primary
Id 5] Key

32 © 2014ZTE
ZTE C
44
ZXUR 9000 UMTS (V4.11.20) Commissioning Gu
Guide
Father Path long:[0..655 65535 is invalid, other value must be in

R-I
Group Id 35] [0..4095]
2G:3..63
CMP Module 3G:3..31
No.
long:[3..63] R-W-II
Support to modify the module No. of path
group for Iu interface.
Path Group 2:ETHERNET_NOVLAN
long:[2,5] R-W-II
Bear Type 5:ETHERNET_VLANTAG
PLMN Group sequence<l
eg:1;2 R-I
Object ID ong,4>
Ratio of
occupied
0 to 1000
private sequence<l
If more than one MCC/MNC, separate R-W-II
bandwidth of ong,4>
each value by ';'
Path Group
by operator
Forward
long:[0..429
bandwidth(kb R-W-II
4967]
ps)
Backward
long:[0..429
bandwidth(kb R-W-II
4967]
ps)
3.2.10 IP Path (CN)
Table 3-20 IP Path (CN)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element 5] Key
Object ID
Adjacent Net
Element
5] Key
Identifier
Primary
Path ID long:[0..7]
Key
Path Group long:[0..409 Primary
ID 5] Key
CMP Module 2G:3..63
No.
long:[3..63] R-W-II
3G:3..31
PLMN Group long:[0..429
R-I
Object ID 4967295]
Destination
ipv4 R-W-II
IP Address
Destination
IP Address long:[0..32] R-W-II
Mask Length
45

Forward
bandwidth(kb R-W-II
ps)
64000bps.
Backword
bandwidth(kb R-W-II
ps)
64000bps.
3.2.11 Adjacent Office (CN)
Table 3-21 Adjacent Office (CN)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element 5] Key
Object ID
Adjacent Net
Element
5] Key
Identifier
Adjacent long:[1..204
R-I
Office ID 8]
Mgw Id:[4096..65535],
Mscserver Id:[0..4095],
Sgsn Id:[0..4095],
Rnc Id[1..4095],
BSC Id:[1..4095],
SAS Id:[0..65535],
ITC Id:[501..600],
SMLC Id:[0..65535].
Net Element sequence<l
If NETYPE is MGW+MSCSERVER and R-I
ID ong,8>
one PLMN is configured for 3G office,
NEID should be filled in MgwId;MscsId,
eg:4096;2
If NETYPE is MGW+MSCSERVER and
two PLMNs are configured for 3G office,
NEID should be filled in
MgwId1;MscsId1;MgwId2;MscsId2,
eg:4096;2;4097;4.
PLMN Group sequence<l PLMN ID:[0..4294967295].
R-I
Object ID ong,4> eg:1;2
2:UMTS
Mode Type long:[2..3] R-I
3:GSM

34 © 2014ZTE
ZTE C
46
2G office:
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
long:[16,32, 1023:SMLC
Type of
64,512,576, 3G office:
adjacent R-I
1023,4096, 16:BSC
office
32768] 32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
32768:SAS
0: ATM (3G)
1: IP
Bear type long:[0..2] R-I
2: TDM (2G)
(Parameters can't be modified)
Encode type
14:SPC 14 bits,
of signalling long:[14,24] R-W-II
24:SPC 24 bits
point
Destination long:[0..167 14 bits:0..16383
R-W-II
point code 77215] 24 bits:0..16777215
0: International SPC,
Sub-Service long:[0,4,8, 4: Reserved international SPC,
R-W-II
Field 12] 8: National SPC,
12: Reserved National SPC
Connection
relationship 1:Associated
with local long:[1..3] 2:Quasi-associated R-W-II
signalling 3:No connection
point
Whether to
support 0:Not Support
long:[0..1] R-W-II
broadband 1:Support
properties
1:CHINA
Protocol type long:[1..3] 2:ITU R-W-II
3:ANSI
20 bytes, separate each byte with ".",
ATM address string decimal. R-W
2G office dosen't congifg it
For one PLMN,
Default Office sequence<l 0:Is Default Office
1:Is Not Default Office,
R-W
Office Flag ong,4>
eg:1;0
Capacity
Weight in sequence<l For one PLMN,the value range is [0..100].
R-W
CS/PS ong,4> eg:1;0
Domain
47
Number of
Network
Resource sequence<l For one PLMN,the value range is [0..4].
R-W
Identifier in ong,4> eg:1;0
CS/PS
Domain
The value range of one Network Resource
Network
Identifier is [0..1023].
Resource
If there are two PLMNs,the NUMOFNRI of
Identifier in string R-W
PLMN1 is 2 and the NUMOFNRI of
CS/PS
PLMN2 is 3,then NRILIST is
Domain
10;11@100;101;103
3.2.12 SCTP Config (CN)
Table 3-22 SCTP Config (CN)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element 5] Key
Object ID
Adjacent long:[1..204 Primary
Office ID 8] Key
Association long:[1..300 2G:1..2048 Primary
ID 0] 3G:1..3000 Key
CMP Module 2G:3..63
long:[3..63] R-W-II
No. 3G:3..31
Application
1:Server
type of long:[1..2] R-W-II
2:Client
association
long:[1..655
Local port R-W-II
35]
Local IP It can be filled in four IP address at most,
ipv4 R-W-II
Address such as xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx
long:[1..655
Remote port R-W-II
35]
It can be filled in four IP address at
Remote IP
ipv4 most,such as R-W-II
Address
xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx
long:[1..840
ASP Number R-I
0]
Max
Retransmissi
long:[10..30
00]
Timeout(10m
illisecond)
Min
Retransmissi
long:[10..10
00]
Timeout(10m
illisecond)

36 © 2014ZTE
ZTE C
48
Initial
Retransmissi
long:[10..30
00]
Timeout(10m
illisecond)
Heartbeat
long:[10..60
Interval(10mil default value:500 R-W
00]
lisecond)
Delayack
interval(10mil long:[0..20] default value:20 R-W
lisecond)
3.2.13 M3uaAS Config (CN)
Table 3-23 M3uaAS Config (CN)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
User label string R
Managed
Element
5] Key
Object ID
Office ID 8] Key
AS Number
] Key
The value range of ASP Number is 1..8400.
sequence<lo
ASP Number 1..8400. R-W-I
ong,16>
eg:1;2
Whether exists
0: FALSE
exists routing long:[0..1] R-W-I
1: TRUE
context
Routing long:[0..4294
4294967295 is invalid R-W-I
context ID 4967295]
Whether exists
exists peer 0: FALSE
routing context long:[0..1] R-W
1: TRUE
context
Peer routing long:[0..4294
4294967295 is invalid R-W
context ID 4967295]
1: SGP,
2: ASP,
AS property long:[1..5] 3: IPSP SERVER, R-W-I
4: IPSP CLIENT,
5: DOUBLE EXCHANGE MODEL
AS traffic 1: Override,
long:[1..2] R-W-I
mode 2: Loadshare
value of N long:[0..16] R-W-I
value of K long:[0..16] R-W-I
3.2.14 M3uaRoute
Table 3-24 M3uaRoute
Parameter Parameter
Description Remark
Name Value
49
Modification
Indication
Managed
Element
5] Key
Object ID
Route Number long:[1..640] Primary
Number ] Key
0:natural sort
Route range
long:[0..2] 1:ikebana sort R-W-I
mode
2:handworked sort
long:[1..640]
AS1 Number R-W-I
]
long:[0..640]
AS2 Number R-W-I
]
long:[0..640]
AS3 Number R-W-I
]
long:[0..640]
AS4 Number R-W-I
]
3.2.15 M3uaRouteSet
Table 3-25 M3uaRouteSet
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element
5] Key
Object ID
Office ID 8] Key
long:[1..640]
Route ID 1 ]
R-W-II
long:[0..640]
Route ID 2 ]
R-W-II
3.2.16 PVC Config (IU-IUR)

Table 3-26 PVC Config (IU-IUR)
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element
5] Key
Object ID
Office ID 8] Key
PVC ID
00] Key

38 © 2014ZTE
ZTE C
50
Atm
Interface string rack/shelf/slot R-W-II
Board
ATM Optical Port:[1..4],
ATM port long:[1..244] R-I
IMA Port:[5..244]
IMA port need to be configured.
E1 list string R-W
Separated by ";"
VPI on High long:[0..409
R-W-II
End 5]
VCI on High long:[32..65
R-W-II
End 535]
0: AAL5 Signal,
1: AAL5 Data,
2: AAL2 Data
PVC Service
long:[0..2] R-I
Type AAL5 Signal: the Signalling over ATM,
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
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
CBR surpports:
atmNoClpNoScr(1)
atmClpTransparentNoScr(8),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR surpport:

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

40 © 2014ZTE
ZTE C
52
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
Maximum
atmClpNoTaggingScr(5),
burst cell long:[0..429
atmClpNoTaggingScrCdvt(13), R-W
number 4967295]
(MBS)
atmNoClpScr(4).
R
ID 5]
sequence<l For one PLMN,the value range of TrPath
TrPath ID R
ong,4> ID is [32..127].
AAL2
Attached long:[3..31] R-W
Module
AAL2 Path
long:[1..429
ID intra R
4967295]
office
10: RT,
AAL2 Path 11: NRT1,
Service Type long:[10..14] 12: NRT2, R
Type 13: NRT3,
14: MIX
AAL2 Path 0:Local End
long:[0..1] R
Ownership 1:Peer End
Signalling long:[1..900
R
link number 0]
Signalling
Link
long:[3..31] R-W
Attached
Module
Signalling
long:[0..15] R-W
Link Code
Destination
ipv4 R-W
IP address
3.2.17 Mtp3Route
Table 3-27 Mtp3Route
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
Element
5] Key
Object ID
Route ID 0] Key
Adjacent long:[1..204 It must be filled if LINKSET_1 is not filled.
R
Office ID 8] It should be filled for 3G.
53
long:[1..102
Link set 1 4]
R
long:[1..102
Link set 2 4]
R
0:Any arrangement (default value)
1:According to SLS_bit0 choose routing
groups
2:According to SLS_bit1 choose link
groups
groups
Permutation
of signalling long:[0..8] R-W
groups
links
5:According to SLS_bit0 and SLS_bit1
choose link groups
choose link groups
choose link groups
8:Floral sort
3.2.18 Mtp3RouteSet
Table 3-28 Mtp3RouteSet
Parameter Parameter
Description Remark
Name Value
Modification
Indication
Managed
long:[1..409
Element Primary Key
5]
Object ID
Adjacent long:[1..204
8]
Primary Key
Office ID
long:[1..200
Route ID 1 0]
R-W-I
long:[0..200
Route ID 2 0]
R-W-I
long:[0..200
Route ID 3 0]
R-W-I
long:[0..200
Route ID 4 0]
R-W-I
3.2.19 No.7 PCM

3.2.20 PCM(ITC--MSC)
3.2.21 Mtp2Link
3.2.22 MSC Office
3.2.23 SGSN Office
3.2.24 Fr Gb
3.2.25 Ip Gb

42 © 2014ZTE
ZTE C
54

3.2.26 Lucent Channel
3.2.27 iTC Office
55
ZXUR 9000 UMTS (V4.11.20) Commissioning
Commissioni Guide
4TheSpecifications of
first six sheets are required, while Configuring
other sheets are optional. UMTS
4.1 UTRAN Cell
Table 4-1 UTRAN Cell
Parameter Parameter
Description Remark
Name Value
Modification
A,D,M,P A:Add, D:Delete, M:Modify,P:Pass
n Indication
[Managed
Element
5] Key
Object ID]
string:[0..80]
User Label Cannot use invalid character < > & ' " R-W
W
]
RNC ID
5] Key
long:[0..6553
NodeB No R-W
W-I
35]
Cell ID
34] Key
Local Cell long:[0..2684
R-W
W-I
Identity 435455]
0:Band
I,1:Band
II,2:Band
Frequency III,3:Band
Band IV,4:Band R-W
W-I
Indicator V,5:Band
VI,7:Band
VIII
long:[9612..9
9888,9262..9
9538,12,37,6
62,87,112,13 uarfcnUl is calculated by uarfcnDl, should not input
37,162,187,2 input any value.
212,237,262, {freqBandInd==0} [9612..9888],
2,287,937..1 {freqBandInd==1}
1288,1312..1 [9262..9538][12][37][62][87][112][137][162][187][212
1513,1662,1 ][212][237][262][287],
1687,1712,1 {freqBandInd==2} [937..1288],
UUARFCN 1737,1762,1 {freqBandInd==3} R
1787,1812,1 [1312..1513][1662][1687][1712][1737][1762][1787][1
1837,1862,4 87][1812][1837][1862],
4132..4233,7 {freqBandIn
{freqBandInd==4}
782,787,807, [4132..4233][782][787][807][812][837][862],
7,812,837,86 {freqBandInd==5} [4162..4188][812][837],
62,4162..418 {freqBandInd==7} [2712..2863]
88,812,837,2
2712..2863]

44 © 2014ZTE
ZTE C
56
long:[10562..
..10838,9662
2..9938,412,
,437,462,487
7,512,537,56 {freqBandInd==0} [10562..10838],
62,587,612,6 {freqBandInd==1}
637,662,687, [9662..9938][412][437][462][487][512][537][562][587
7,1162..1513 ][587][612][637][662][687],
3,1537..1738 {freqBandInd==2} [1162..1513],
8,1887,1912, {freqB
{freqBandInd==3}
2,1937,1962, [1537..1738][1887][1912][1937][1962][1987][2012][2
DUARFCN 2,1987,2012, 12][2037][2062][2087], W-I
R-W
2,2037,2062, {freqBandInd==4}
2,2087,4357. [4357..4458][1007][1012][1032][1037][1062][1087],
7..4458,1007 87],
7,1012,1032, {freqBandInd==5} [4387..4413][1037][1062],
2,1037,1062, {freqBandInd==7} [2937..3088]
2,1087,4387.
7..4413,1037
7,1062,2937.
7..3088]
Cell Primary
Primary long:[0..511]
Scrambling R-W
W-I
]
Code
Location long:[1..6553
R-W
W-I
Area Code 33,65535]
Routing Area long:[0..255]
R-W
W-I
Area Code ]
Service Area long:[0..6553
R-W
W-I
Area Code 35]
URA Identity sequence<lo Element Data Range in Array is [0..65535],and
R-W
W-I
Identity ong,4> separated by ";".
Service Area
Area Code long:[0..6553
for BC R-W
W-I
35]
Domain
long:[0..9],<d
T_Cell R-W
W-I
default:0>
4.2 Logic Cell Configuration

Table 4-2 Logic Cell Configuration
Parameter Parameter Remar
Description
Name Value k
Modification
n Indication
[Managed
Element
5] y Key
Object ID]
string:[0..80]
User Label R-W
W
]
RNC ID
5] y Key
57
Mobile
Country
] y Key
Code
Mobile
Network
] y Key
Code
Cell ID can not repeat in the same PLMN.
34] y Key
Common 0:False,1:Tru
PLMN rue,<default: R-W
W-I
Indicator t:1>
4.3 External UTRAN Cell

Table 4-3 External UTRAN Cell
Parameter Parameter
Description Remark
Name Value
Modification
n Indication
[Managed
Element
5] Key
Object ID]
string:[0..80]
User Label R-W
W
]
RNC ID
5] Key
Cell Identity
of Adjacent
35] Key
Cell
RNC Identity
Identity of long:[0..4095 Primary
Adjacent 5] Key
RNC
Mobile
long:[0..999]
Country R-W
W-I
]
Code
Mobile
long:[0..999]
Network R-W
W-I
]
Code
Location long:[1..6553
R-W
W-I
Area Code 33,65535]
0:Band
I,1:Band
II,2:Band
Frequency III,3:Band
Band IV,4:Band R-W
W-I
Indicator V,5:Band
VI,7:Band
VIII

46 © 2014ZTE
ZTE C
58
long:[9612..9
9888,9262..9
9538,12,37,6
62,87,112,13
37,162,187,2 {freqBandInd==0} [9612..9888],
212,237,262, {freqBandInd==1}
2,287,937..1 [926
[9262..9538][12][37][62][87][112][137][162][187][212
1288,1312..1 ][212][237][262][287],
1513,1662,1 {freqBandInd==2} [937..1288],
1687,1712,1 {freqBandInd==3}
UUARFCN 1737,1762,1 [1312..1513][1662][1687][1712][1737][1762][1787][1 R
1787,1812,1 87][1812][1837][1862],
1837,1862,4 {freqBandInd==4}
4132..4233,7 [4132..4233][782][787][807][812][837][862],
782,787,807, {freqBandInd== [4162..4188][812][837],
{freqBandInd==5}
7,812,837,86 {freqBandInd==7} [2712..2863]
62,4162..418
88,812,837,2
2712..2863]
long:[10562..
..10838,9662
2..9938,412,
,437,462,487
7,512,537,56 {freqBandInd==0} [10562..10838],
62,587,612,6 {freqBandInd==1}
637,662,687, [9662..9938][412][437][462][487][512][537][562][587
7,1162..1513 ][587][612][637][662][687],
3,1537..1738 {freqBandInd==2} [1162..1513],
8,1887,1912, {freqBandInd==3}
2,1937,1962, [1537..1738][1887][1912][1937][1962][1987][2012][2
DUARFCN 2,1987,2012, 12][2037
12][2037][2062][2087], R-W
W-I
2,2037,2062, {freqBandInd==4}
2,2087,4357. [4357..4458][1007][1012][1032][1037][1062][1087],
7..4458,1007 87],
7,1012,1032, {freqBandInd==5} [4387..4413][1037][1062],
2,1037,1062, {freqBandInd==7} [2937..3088]
2,1087,4387.
7..4413,1037
7,1062,2937.
7..3088]
Cell Primary
Primary long:[0..511]
Scrambling R-W
W-I
]
Code
Service Area
Area Code long:[0..6553
for CS and R-W
W-I
35]
PS Domain
URA Identity sequence<lo Element Data Range in Array is [0..65535],and
R-W
W-I
Identity ong,4> separated by ";".
4.4 External GSM Cell

Table 4-4 External GSM Cell
Parameter Parameter
Description Remark
Name Value
59
Modification
n Indication
[Managed
Element
5] Key
Object ID]
stirng:[0..80]
User Label R-W
W
]
RNC ID
5] Key
Cell Identifier
Identifier of long:[0..6553 Primary
Adjacent 35] Key
GSM Cell
Location
Area Code of long:[1..6553 Primary
of Adjacent 33,65535] Key
GSM Cell
0:DCS 1800
1800 Band
Used,1:PCS
S 1900 Band
Band
Used,2:GSM
M 900 Band
Band
Used,3:GSM
M 450 Band
Band
Band Used,4:GSM
M 480 Band R-W
W-I
Indicator
Band
Used,5:GSM
M 750 Band
Band
Used,6:GSM
M 850 Band
Band
Used,<defau
ult:0>
long:[512..88 {bandIndicator==0} [512..885],

85,512..812, {bandIndicator==1} [512..812],
,0..124,955.. {bandIndicator==2} [0..124][955..1023],
BCCH .1023,259..2 {bandIndicator==3} [259..293], R-W
W-I
ARFCN 293,306..340 {ba
{bandIndicator==4} [306..340],
0,438..511,1 {bandIndicator==5} [438..511],
128..251] {bandIndicator==6} [128..251]
Network
Colour Code long:[0..7] R-W
W-I
Code
Base Station
Station
Colour Code long:[0..7] R-W
W-I
Code

48 © 2014ZTE
ZTE C
60
Mobile
long:[0..999]
Country R-W
W-I
]
Code
Mobile
long:[0..999]
Network R-W
W-I
]
Code
BSC long:[0..6553
R-W
W-I
Identifier 35]
4.5 Neighbouring Cell

Table 4-5 Neighbouring Cell
Parameter Parameter
Description Remark
Name Value
Modification
n Indication
[Managed long:[1..4095 Primary
Element 5] Key
Object ID]
string:[0..80]
User Label R-W
]
RNC ID
5] Key
Cell ID
34] Key
Target RNC long:[0..4095 Primary
RNC ID 5] Key
Target Cell long:[0..6553 Primary
ID 35] Key
4.6 GSM Neighbouring Cell

Table 4-6 GSM Neighbouring Cell
Parameter Parameter
Description Remark
Name Value
Modification
n Indication
[Managed long:[1..4095 Primary
Element 5] Key
Object ID]
User Label string[0..80] R-W
RNC ID
5] Key
Cell ID
34] Key
Location long:[1..6553 Primary
Area Code 33,65535] Key
Cell Identifier long:[0..6553 Primary
Identifier 35] Key
4.7 External ENodeB Function

It is not necessary to configure this sheet at present.
4.8 External EUTRAN Cell FDD
4.9 External EUTRAN Cell TDD
61
ZXUR 9000 UMTS
MTS (V4.11.20) Commissioning Guide

present
4.10 EUTRAN Neighbouring Cell
4.11 User Authorized PLMN+SNAC Information
4.12 MBMS Configuration
4.13 MBMS Service Area Configuration
4.14 MBMS Frequency Layer Configuration

50 © 2014ZTE
ZTE C
62
5 5.1
Special Subject
ICM Data Configuration Flow (All-Parameter
(All Parameter
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 5-1 ICM Data Area
Description of different ICM data areas:

Live Data Area: ICM synchronize 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: Thehe latest configuration data under the current node in the Live Data
Area.
History data: The backed-up
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 opy 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 typess 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 willwill 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 similar to the OMMR MO
Template. It consists of two templates: Uni Ground template and UMTS Radio
template.
5.1.1 ICM Initialization
Open EMS client, choose Configuration > Plan Data Management,, and open
Plan Data Management window.
Figure 5-2 Plan Data Management
63
Click Live Data Area,

Area, and select the record of the target OMMR in the dialog box
on the right. Right-click
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 5-3 Live Data Area Synchronization
Note:
ICM can only synchronize da data
ta 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
OMMR to RNC) ICM will monitor this operation
operation in real time and trigger data upload
automatically. This can make sure the data in the live data area of ICM is consistent
consistent with that in snapshot area of OMMR, i.e., consistent with the RNC data.
If data upload cannot be triggered automatically, it it is necessary to perform data
upload manually with the method mentioned above.
5.1.2 Exporting Optimization Template (All Parameters)
Choose Live Data Area,
Area right-click
click the target OMMR subnet and choose Export
export all parameters.
Figure 5-4 Exporting Optimization Template on ICM

52 © 2014ZTE
ZTE C
64
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 5-5,
UMTS Radio is taken as the example.
Figure 5-5 Query and Export
Click Select and select the directory for the exported file. Click Save > Export
Export.
Figure 5-6 Storage Path of Exported
Export File
65
The interface for the data exported successfully is as shown in Figure 5--7. Click
Quit to exit the Query and Export window.
Figure 5-7 Data Exported Successfully
Note:
The Optimization Template can be exported from either Live Data Area or Plan Area,
Area, but because the data in Live Data Area is consistent with the RNC data fixedly,

54 © 2014ZTE
ZTE C
66
ZXUR 9000 UMTS (V4.11.20) Commis
Commissioning Guide
fixedly, it is recommended to export the Optimization Template from Live Data

Area.
5.1.3 Data Import
Data importing is based on Plan Area and is usually performed according the flow
in Figure 5-8.
Figure 5-8 ICM Operation Flow
5.1.3.1 Creating Plan Area

Choose Live Data Area,
Area right-click
click the record of the target OMMR subnet
choose Create Plan Area
Area.
Figure 5-9 Creating 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 5-10 Create
C Plan Area
67
Figure 5-11 C
Confirm
5.1.3.2 Importing Template

Right-click
click the target Plan_Area under Data Area, and choose Import to
import data.
Figure 5-12 Importing Template

56 © 2014ZTE
ZTE CORPORATION.
68
1. Importing Plan Template

In the Data Import window, choose Plan, and modify Data Type to the type
the data to be imported, such as, Uni_Ground/Uni_Office for ground data,
and UMTS Radio for radio data.
Figure 5-13 Importing Plan Template
Right-click
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.
69
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
un-configured.
configured. This is different
different from the rules of OMMR.
The Data Type selected should match with the template name, as as shown below:
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
ata Import window, choose Optimization, and modify Data Type to
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 5-14 Import
mporting Optimization Template

58 © 2014ZTE
ZTE C
70
The process of importing Optimization Template is the same as that of

importing Plan Template. Check whether the number of successful records in
ucceed/All Counts is the same as the number of all records. If it is, the
Succeed/All
template is loaded successfully.
Note:
When importing the Optimization Template from ICM, pay attention to the
following two points:
In the Optimization template, the ME ID field must be configured. This is
different from the rules of filling in the Plan template.
The Data Type selected should match with the template name, as shown below:
below:
Uni_Ground for OMMR_Optimization_uni_ground_20130129131315.zip
OMMR_Optimization_uni_ground_20130129131315.zip
UMTS Radio for OMMR_Optimization_umts_radio_20130129131327.zip
For the Transaction Mode field, it is recommended to use “Best Effort.”
5.1.3.3 Validity Check
Right-click
click the target Plan_Area under Data Area, and choose Check to
perform data validity
va check.
Figure 5-15 Validity Check
C
71
In the pop-up Data Check-Validity

Check window, click OK to start data validity
check. By default, “Full Data” and “All Rules” will not be selected, because the
system will
ill use the most efficient way to perform the operation by default. If
there is no special requirement, do not select these two items.
Figure 5-16 Data Check-Validity
Check
After validity check is completed, observe the import result in the figure below.
If Validity is “Pass,” it means the validity check succeeds.
Figure 5-17 Check
C Result

60 © 2014ZTE
ZTE C
72
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
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.
5.1.3.4 Conflict Check
Choose the Conflict tab and click OK to start conflict check.
Figure 5-18 Conflict
C Check
73
Before conflict check is started, the following dialog box will pop up. Confirm
the live data is synchronized and click OK.
Figure 5-19 Confirm
C 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 5-20 Conflict Check Result

62 © 2014ZTE
ZTE CORPORATION.
74
5.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 5-21 Submitting
S Data
5.1.3.6 Data Activation

Choose Activate to display the Activation Management window.
Figure 5-22 Activating Data
75
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
and click OK.
Figure 5-23 Activating Task Management
Choose the task to be activated. Right-click

Right the task and choose Compare to
Get Delta to create incremental data.
Figure 5-24 Compare to Get Delta

64 © 2014ZTE
ZTE CORPORATION.
76
Observe the execution result in Status in the record and the Result in the
Figure 5-25 Compare
C Success
Right-click
click the task and choose Download to download data.
Figure 5-26 Download
77
ZXUR 9000 UMTS (V4.11.20) Commissioning
ommissioning Guide
Figure 5-27 D
Download Success
Right-click
click the task and choose Activate to activate data.
Figure 5-28 Activate
Figure 5-29 Activate
A Success

66 © 2014ZTE
ZTE CORPORATION.
78
After the activation is completed, the data is synchronized to RNC.

5.1.4 Deleting Plan Area
5.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.
deleted. If there is,
choose the activation task to be deleted, click Delete, and click Yes in the
pop-up Confirm dialog box.
Figure 5-30 Deleting Activation Task
5.1.4.2 Checking “Submit” Status

Right-click
click the Plan Area to be deleted, and choose Check.. Choose the
Submit tab in the pop-up 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 5-31 Switching Submit Status
5.1.4.3 Deleting Plan Area
79
After the above two checks are completed, the Plan Area can be deleted.
Right-click
click the Plan Area to be deleted and choose Delete.
Figure 5-32 Deleting Plan Area
Click OK to confirm the delete operation.

Figure 5-33 Confirming Plan Area
Note:
In the in-depth
depth integration version of EMS and ICM, only two plan areas are
available to users by default. Too many plan areas will lead to resource waste
and will greatly affect the execution efficiency of other plan areas. Therefore,
after the use of the plan area is finished, the plan area needs to be deleted timely.
timely.
5.2 CMP Module No. Modification
The CMP Module No. of the IUB office can be modified in the IUB Office sheet.
Meanwhile, the Module Nos. of the office, SCTP, path
path group, and cell are also
modified.
Figure 5-34 CMP Module No. Modification

68 © 2014ZTE
ZTE CORPORATION.
80
5.3 Overall Office Information Deletion (Including

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 5-35 Office Information Deletion (Including Ground & Radio Resources)
5.4 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 5-1.
Table 5-1 Sheets to Be Configured for Each Transmission Type of a New Site
No IPoE1+IPoF ATMoSTM
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-ABIS
ABIS (IUB-ABIS (IUB-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 5-36 Site Bearer Migration
81
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
two separate templates.
5.5 Board Configuration
Pay attention to the following new concepts and general cares in ZXUR 9000 UMTS
board configuration.
5.5.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 alternative 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 the following figure, the
boards in the same color are in the master/slave configuration.
Figure 5-37 Diagram of Master/Slave Board Slots
5.5.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 5-2 Configuring Data of ATM Interface Board
Available
vailable
Available
Available Optical Port
Physica Parts Optical Port
Board Port Type Multiplexing
Board etc.) Speed Mode
(porttype) Structure
(speedmode
(sdhtype)
6: E1;
ASPB 0: INVALID 0: INVALID
7: T1
EAPB_ Not Not
No sub--card Not supported
2 supported supported

70 © 2014ZTE
ZTE CORPORATION.
82
EDTS_2/EDTS_ 6:E1;
EDTA 0: INVALID 0: INVALID
3 7:T1
1:
SDH-63E1
; 1: SDH-AU
AU-4;
2: 2: SDH-AU
AU-3;
ESDTA ESDTS_2 1: STM-1
SDH-63T1 3:
; SONET-STS
STS-1
3:
SDH-84T1
1: SDH-AU
AU-4;
EAPB EXIS 5:ATM 1: STM-1 4:
SONET-STS
STS-3
C
1:
SDH-63E1
; 1: SDH-AU
AU-4;
2: 2: SDH-AU
AU-3;
ESDTI ESDHS 1: STM-1
SDH-63T1 3:
EMSI ; SONET-STS
STS-1
3:
SDH-84T1
6: E1;
EDTI EDTS_3/EMDTS 0: INVALID 0: INVALID
7: T1
5.5.3 Introduction of USP Board
The functions of Universal Service Processing board (USP) are shown in the
following table:
troduction of USP Board
Table 5-3 Introduction
Name of the
Physical Configuration
Logical Function
Board Description
Board
Must be configured in
Processes the common control the master/slave
plane protocols on the Iub and Iu mode. Each master
USP CMP
interfaces. board must be
configured with four
CMP Module Nos.
Must be configured
Processes the special control as None. Each board
USP DMP plane protocols on the Iub and Iu must be configured
interfaces. with one DMP
Module No.
Must be configured
as None. Each board
Processes the user plane includes 15 slaves.
USP RUP
protocols of CS and PS services. Each slave must be
configured with user
plane IP address.
5.5.3.1 Integrated UC Board
From V3.11 series versions, the processing unit on the control plane is
divided into CMP (processing common control plane protocols) and DMP
(processing special control plane protocols).
83
CMP: Firstly, it provides service for NodeB/cell. The common NBAP

protocols and cell radio resource algorithm are processed in CMP. Each cell
must be allocated to a certain CMP. Secondly, CMP processes the 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. It also means CMP processing
ability is related to transmission bandwidth resource.
resourc
DMP: It only processes the radio flows related to UE, such as special
RRC/RANAP/RNSAP/NBAP flows and special algorithm of radio resource.
No resource relation is configured in the DMP module.
From ZXUR 9000 UMTS, the processing unit of the user plane is divided
into UCIU (processing special user plane service) and CCIU (processing
common user plane service), similar to DMP and CMP separation on the
control plane.
UCIU: It is the DSP for the sspecial
pecial UE calling service, and the user plane
sub-unit
unit processing special service. In ZXUR 9000 UMTS, it is deployed in
RUP.
CCIU: It is the DSP resource required during CCH establishment, and the
user plane sub--unit processing cell and common transmission on channel
instances. In ZXUR 9000 UMTS, it is deployed in logical board CMP.
For the current USP delivered to the site, if the board is used as the logical
board CMP, the board should be integrated UC board by default (integrated
CMP and CCIU), where the the special parts on the control plane and user plane
are integrated in the logical board CMP. That is, the logical board CMP has
both CMP processing unit and RUP processing unit, as shown in the
following figure.
Figure 5-38 Configuring Integrated UC Board
5.5.3.2 IUB COM IP Address

Due to the integrated UC board in UR11.2 version, the common channel
processing module and control plane CMP module are processed in the
same board. The common channel should be allocated
allocated with an independent

72 © 2014ZTE
ZTE CORPORATION.
84
IP address (IUB COM IP address), which can be regarded as the special Iub
interface IP address.
Simply speaking, no matter how the IP address is planned, 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. In this situation, it is only required to configure
one more virtual IP in V3.11. This IP will be used to process the common
channel of integrated UC board in when the version is upgraded to V4 MO
version in future.
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
llocated to the Iub interface. When the IP is used by the integrated UC board,
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, one more IP should be planned. The IP is only provided for the
integrated UC board, and used as the service IP for common
common channel
establishment. This IP is only used on the Iub interface. If there is no router
on the Iub interface, it is not required to perform other operations on the
integrated NE.
Note:
Every three master CMP boards should be configured with one IUB COM IP.
IUB COM IP and Iub user plane IP are suggested to be planned in the same
subnet. It is convenient for the data communication engineer to configure the
route.
5.5.3.3 User Plane IP Allocation
When USP is used as the logical board RUP, because the number of port
Nos. supported by each slave is greatly increased, in the previous planning,
two RUB2 boards can share one IP; in the existing planning, one RUP board
needs two IP addresses.
Table 5-4 UDP Port No.
User-Plane Board
System Field Name UDP Port No.
Type
V4 UMTS IUB SBCJ 3968
V4 UMTS IUR SBCJ 1536
V4 UMTS IUCS SBCJ 1792
Refer to the following information for the detailed calculation method:
1. Calculation Method
Because user-planeplane addresses need to be allocated to different RUP boards,
the relation between the boards and the IP addresses should be made clear.
Use the following information to calculate the number of RUP boards
allocated with an IUX user-plane
user address:
The number of RUP boards supported by each IUX user-plane
user IP=
(Maximum number of port Nos. supported by RN RNC – Number of port Nos. for
other uses) / (Total number of UDPs occupied by IUX * Number of slaves
supported by each RUP board)
If the result is a decimal, round up value to get the number of the RUP boards
supported by each IUX user-plane
user IP.
2. Refer to the following description for the parameters related to the formula
85
i. Maximum number of port Nos. supported by RNC: It is the upper limit

UDP ports. The value should
should be 65535 as required by the protocol. However,
due to the round-up
round up calculation, the largest UDP Port No. should be set as
64999.
ii. Number of port Nos. for other uses: In RFC, the UDP port No. smaller
1024 has been registered. Therefore, in RNC equipment, the UDP port No.
smaller than 1024 should not be used. But the IUPS data contains the
nominated Port No. 2152, which is specified in the GTPU protocol, thus, do
nott use 2152 for UDP port No. of non-IUPS
non IUPS data. Considering the influence
on later RFC changes and expansion, do not use the UDP Nos. smaller than
5000. In this situation, the smallest UDP No. in RNC NE is 5000. The UDP
Port No. starts from 5000, that means 5000 can also be used. However, Port
Nos. from 1 to 4999 are not available.
iii. Total number of UDPs occupied by IUX: The following calculation
the number of UDP port Nos. of each slave on each interface of each board.
If the interface type is IUPS, the UDP port No. will not be occupied.
3. Calculation sample:
i. IP separation scenario on the IUX user plane:
For example, if one onsite resource shelf is configured with six RUP boards,
we can get the following result according to the formula mentioned above:
IUCS: (64999-4999)/(1792
4999)/(1792×15)=2.23, and the round-down
down result is 2. That is,
one IUCS user plane IP can be usedus by two RUP boards.
IUPS: One user plane IP can be used by the RUP boards in one shelf.
IUR: (64999-4999)/(1536
one IUR user plane address can be used by two RUP boards.
IUR: (64999-4999)/(3968
one IUB user plane address can be used by one RUP board.
ii. IP non-separation
separation scenario on the IUX user plane:
(64999-4999)/[(1792+1536+3968)
4999)/[(1792+1536+3968)×15]=0.55, that is, one IUX X user plane IP
can be used by 0.55 RUP board. Therefore, each RUP board needs two IUX
IP addresses.
5.5.3.4 User-Plane
Plane IP Configuration Rules
Rule 1:
All the configurations in this Guide are based on IP allocation by board,
instead of IP allocation by UDP port No. The system will allocate Port No.
automatically.
Rule 2:
When configuring the LOCIPADDR field, please separate the user-plane
user plane
addresses allocated to this board by semicolon in the same cell. It is not
necessary to consider the sequence of the addresses
addresses or the protocol
interface corresponding to each address.The system will associate them
automatically.
Rule 3:
In the “Slave or Dsp Service Config” sheet of the quick data configuration
template, the granularity of each line is board, and the IP of each line must
include four types of protocol interfaces (IUB/CS/PS/R). Do not fill in them in
separate lines.
5.6 PVC Configuration
nfiguration
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
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 5-39 Configuring PVC in V3 Version

74 © 2014ZTE
ZTE C
86
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 5-40 Configuring PVC in V4 Version
The relation of PVC traffic type, traffic parameter, and PVC service type is shown in the
following table:
Table 5-5 Relation of PVC Traffic Type, Traffic Parameter, and PVC Service Type
Servic
Traffic Type Para1 Para2 Para Para Para
Type
PCR0+
atmClpNoTaggingNoScr (3) PCR0
1
PCR0+
atmClpTaggingNoScr (4) PCR0
1
PCR0+
cbr atmNoClpNoScr (2)
1
PCR0+
atmClpTransparentNoScr (9) CDVT
1
PCR0+
atmNoClpNoScrCdvt (12) CDVT
1
PCR0+
atmNoClpNoScr(2)
1
PCR0+
atmClpNoTaggingNoScr(3) PCR0
1
PCR0+
atmClpTaggingNoScr(4) PCR0
1
PCR0+
atmClpNoTaggingScr(6) SCR0 MBS
1
atmClpNoTaggingScrCdvt(14 PCR0+ CDV
SCR0 MBS
rtVbr ) 1 T
ntrVbr 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
87
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+ CDV
ubr+ atmTrafficForUbr+(16) MCR MBS MFS
1 T
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:
1. For different PVC service types, only the corresponding traffic types in the above table
table can be used.
2. All the parameters in the above table should be filled with integer numbers.
3. In the running system, in order to modify PVC traffic parameters safely, block the
upper-level
level applications associated with PVC, such as AAL2PATH and ATMSIGLINK,
before modifying the parameters.
arameters. Otherwise, call loss may occur.
5.7 ATM Address Conversion
The format of the ATM address falls into three categories, as shown in Figure 5-41.
Figure 5-41 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
45 0-0-0-0-1F.
Since the last number “1” cannot
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.
69.144.83.37.0.0.0

76 © 2014ZTE
ZTE CORPORATION.
88
According to the values of AFI, there are four frequently-used

frequently used AESAs, as shown in
Table 5-6.
Table 5-6 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,d, 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.
5.8 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.
Configuration
Pay attention to the parameters in Table 5-7.
Table 5-7 1588 Clock Configuration Related Parameters
Parameter
arameter Name Value
Used Ethernet IP Interface(IPV4) Select the slot No. for EGBP in the
drop-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 5-42 and Figure 5-43:
Figure 5-42 1588 Clock Configuration
Configurati 1
Figure 5-43 1588 Clock Configuration 2
89
5.9 Shielding Alarms

Configuration Path: Managed Element > Equipment > Rack > Gate control’s
configuration.
Figure 5-44 Shielding Alarms
5.10 Rules of Configuring

C Master/Slave lave 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 situatio
situation.
5.10.1.1 Port Switch
There are three types of port switch under master-slave
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
peer end equipment
automatically according to the received packets. Besides monitoring the RX
physical signals, the master/slave ports collect the real-time
r 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 w 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
peer end equipment can detect the
master-slave
slave switchover
switchover process of the local equipment synchronously.

78 © 2014ZTE
ZTE CORPORATION.
90
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
master slave port
switchover automatically.
5.10.1.2 Application of Port Switch
Scenario 1
Usually, it is required that
th our GE interface board use 1+1 master-slaveslave mode.
In the integration with peer-end
peer end equipment (PTN or MSTP), if the peer-end
peer
uses L2 switch or there is the build-in
build in L2 switch function between the master
and slave ports, our default 1+1 master-slave
master policy can meet the
requirement of this scenario.(The default switch mode needs no
configuration).
Scenario 2:
If 1+1 master-slave
slave mode is required for our GE interface board, but the
peer-end
end equipment does not satisfy the above requirement, it is possible
thatt our equipment cannot coordinate with the peer-end
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
peer 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
master slave mode cannot be used normally.
5.10.1.3 Configuring Port Switch
There are five parameters, as shown in Table 5-8.
Table 5-8 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 5-45 Port Switch
Note:
For the master-slave
slave configuration:
91
1. If the optical port and the electrical port of EGPB are configured with
self-adaption,
adaption, it is not necessary to configure Switch Type.
2. If the optical port and the electrical port of EGPB are configured with the
th
forced mode, the Switch Type needs to be configured. Under this mode, our Tx
Tx transmission will be stopped and the peer-end
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 po
port),
provided the switchover mode of the interface board of all the member ports is
is consistent.
5.11 Rules of Configuring Slots for USP
In the design of UR13.1, if the USP board is not configured to a proper slot during the
upgrade from UR11.2 and UR12.1 to UR13.1, UR13.1, field engineers may need to adjust the
slot of the board manually. This will affect the field work.
In the upgrade from UR11.2 and UR12.1 to UR13.1, though the total number of USP
boards is fixed, some DMP and RUB boards may change to CMP and the CM CMP must
be in master/slave configuration, that is to say, the number of CMPs may increase after
the upgrade while the number of DMPs and RUBs may decrease.
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},
{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(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.
5.12 Iub-Interface
Interface Qos Planning Rules
There are two options for the Transport Qos Profile Type filed, i.e., “QOS According
ARP/THP/TC” and “QOS According to Service Type,” as shown in Error! Not a valid
bookmark self-reference.
reference..
Figure 5-46 Transport Qos Profile Type
Each option has several configuration

configuration templates. Each template has a fixed relation
with different IUB transmission.
5.12.1 QOS According to ARP/THP/TC
In most sites, this QOS configuration applies only to the single-path
single IP
transmission and is invalid to ATM transmission.
Path of selecting template: Managed Element > Local ManagementElement
information > Logical Iub Link > Used Transport Bearer Type Profile Related
Basic Priority.
Figure 5-47 Used Transport
T Bearer Type Profile Related to Basic Priority

80 © 2014ZTE
ZTE C
92
There are two templates in total. The relation between the templates and
transmission bearers is as shown in Table 5-9.
Table 5-9 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
5.12.2 QOS According to Service Type
When the IUb-interface
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.
Profile
Figure 5-48 Used Dedicated Service Transport Bearer Qos Profile
The relation
ation between the value of “Used Dedicated Service Transport Bearer Qos
Profile” and IUB-interface
interface transmission bearer is as shown in Table 5-10
10.
Table 5-10 IUB QOS Planning Rules – 2
No. Name Common Scenarios
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 IPoE1+IPoFE multi-path
path scenario
IPOFE Path
One ATM Path and One IP ATM+IP dual-stack, ATM+IP
Template 6
Path multi-path scenario
93
ZXUR 9000 UMTS (V4.11.20) Commissioning Gu
Guide
5.13 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 Figure 5-29.
Path: Managed Element > UMTS Logical Function Configuration > Link
IP Function Switch.
Figure 5-49 IP Function Switch

82 © 2014ZTE
ZTE CORPORATION.
94

ZXUR 9000 UMTS (V41120) Commissioning Guide-Quick Data Configuration - R14

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 (V41120) Commissioning Guide-Quick Data Configuration - R14

Uploaded by

Copyright:

Available Formats

A-PDF OFFICE TO PDF DEMO: Purchase from www.A-PDF.

com to remove the watermark

ZXUR 9000 UMTS (V4.11.20)

Copyright © 2014 ZTE CORPORAT

and are registered trademarks of ZTE CORPORATION. ZTE’s company name,

Address: Address: NO. 55

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. I

ZTE Confidential Proprietary

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. V

5.12.2 QOS According to Service Type 81

ZTE Confidential Proprietary

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. IX

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 1

2.1.2 Index Sheet

ZTE Confidential Proprietary

2.1.3 Attributes of Parameters

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 3

2.1.4.2 An Example of Filled Equipment Template

2.1.5 Transport Network Template

ZTE Confidential Proprietary

1. Sheets for IU/IUR and IUB

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 5

2.1.6 UMTS Radio Template

ZTE Confidential Proprietary

2.1.6.2 An Example of Filled UMTS Radio Template

UMTS Radio Quick

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 7

Step 4: Right-click ME and choose Import Quick Configuration Data..

ZTE Confidential Proprietary

Step 5: Click Choose,

Step 6: Click Execute to start loading template.

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 9

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 11

2.2.3 Check on Imported Quick Configuration Template

ZTE Confidential Proprietary

2. Global validity check: It is required this step be performed before data

3. License Center Check

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 13

2.2.5 Data Comparison Between Snapshot Area & Modify Area

ZTE Confidential Proprietary

Observe the value of Result. If it is Difference,, it means there is some difference

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 15

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 17

The value range:

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 19

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 21

ZTE Confidential Proprietary

Service IP Data Format:

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 23

ZTE Confidential Proprietary

It should be filled when Managed Element is

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 25

ZTE Confidential Proprietary

ZTE Confidential Proprietary © 2014 ZTE CORPORATION. All rights reserved. 27

ATM port long:[1..4] ATM Optical Port:[1..4] R-I

rtVBR and nrtVBR surpport:

ZTE Confidential Proprietary