ZXUR 9000 UMTS (V4.11.20) Commissioning Guide-Quick Data Configuration - R1.4

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
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.
are registered trademarks of ZTE CORPORATION. ZTEs company name,
and
logo and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyones access to this document should not be construed as
a 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
CORPORATIONs 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.
Revision History
Product Version
OMMRV12.11.40P02
OMMRV12.11.40P03
Document Version
R1.0
R1.1
OMMRV12.11.40P04
R1.2
OMMRV12.11.40P05
R1.3
OMMRV12.11.40P05
R1.4
Serial Number
Reason for Revision

First published
Some
ome contents added
Section
ection 5.5.3.4
User
User-Plane
IP
Configuration Rules is
added
The
he templates
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
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
Date
Document Version
2012-06-28
R1.0
2012-08-10
R1.1
2012-10-27
R1.2
2012-12-31
R1.3
2013-02-31
R1.4
II
Prepared
by
Cheng
Hao
Cheng
Hao
Cheng
Hao
Cheng
Hao
Cheng
Reviewed by
Chen Taiming, Hu
Zhigang
Chen Taiming, Hu
Zhigang
Chen Taiming, Hu
Zhigang
Chen Taiming, Hu
Zhigang
Chen Taiming, Hu
2014ZTE CORPORATION.
C
All rights reserved.
Approved by

Proprietary
Date
Document Version
Prepared
by
Hao
Reviewed by
Approved by
Zhigang
Intended audience: RNC commissioning engineer
About
Summary This Document
Chapter
1 Notices in Data Configuration
2 Introduction to Quick Data
Configuration
3 Specifications
cations of Configuring
Equipment Template & Transport
Network Template
4 Specifications of Configuring
UMTS Radio Template
5 Special Subject
Description
Notices in Data Configuration
Introduction to Quick Data Configuration
Specifications of Configuring Equipment Template &
Transport Network Template
Specifications of Configuring UMTS Radio Template
Special Subject
III
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
C

Proprietary
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 Specifications
ns 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
5.12.2 QOS According to Service Type

5.13 IP Function Switch 81
VI
81
C

Proprietary
FIGURES
Figure 2-1
1 Template Loading Flow
Figure 2-2
2
Figure 2-3
Figure 2-4
4
Figure 2-5
5
Figure 2-6
6
Figure 2-7
7
Figure 2-8
8
Figure 2-9
9
Figure 2-10
10
Figure 2-11
11
Figure 2-12
12
Figure 2-13
13
Figure 2-14
14
Figure 2-15
15
Figure 2-16
16
Figure 2-17
17
Figure 2-18
18
Figure 2-19
19
Figure 2-20
20
Figure 2-21
21
Figure 2-22
22
Figure 2-23
23
Figure 2-24
24
Figure 2-25
25
Figure 2-26
26
Figure 2-27
27
Figure 5-1
1
Figure 5-2
2
Figure 5-3
3
Figure 5-4
4
Figure 5-5
5
Figure 5-6
6
Figure 5-7
7
Figure 5-8
8
Figure 5-9
Figure 5-10
10
Figure 5-11
Figure 5-12
12
Figure 5-13
13
Figure 5-14
14
Figure 5-15
15
Figure 5-16
Figure 5-17
17
Figure 5-18
18
Figure 5-19
19
Figure 5-20
20
Figure 5-21
21
Figure 5-22
22
Figure 5-23
23
2
Template Info Sheet2
Index Sheet
3
Parameter Attributes
3
V4_Template_Equipment
4
V4_Template_TransportNetwork 4
UMTS Radio Quick Configuration Template 6
UMTS Radio Template 7
Configuration Management 7
Create Subnetwork
8
Create Management Element 8
Import Quick Configuration Data
8
Selecting the Template to Be Loaded
9
Executing Template Loading
9
Template Loaded Completely 10
Querying the Loading Result File
10
Loading Result
11
Export Quick Configuration Data
11
Template Exporting Interface 12
Check on Loaded Template12
Template
Global Check 13
Restoring Data from Snapshot Area to Modify Area
Restore Modify Area 14
Data Comparison 14
Select Compare Type 15
Comparison Result-1
Result
15
Comparison Result-2
Result
15
ICM Data Area 51
Plan Data Management 51
Live Data Area Synchronization 52
Exporting Optimization Template on ICM 52
Query and Export 53
Storage Path of Exported File
53
Data Exported Successfully 54
ICM Operation Flow 55
Creating Plan Area 55
Create Plan Area 55
Confirm 56
Importing Template
56
Importing Plan Template 57
Importing Optimization Template
58
Validity Check 59
Data Check-Validity
Validity
60
Check Result 60
Conflict Check 61
Confirm Live Data 62
Conflict Check Result 62
Submitting Data 63
Activating Data
63
Activating Task Management 64
13
VII
Figure 5-24
24
Figure 5-25
25
Figure 5-26
Figure 5-27
27
Figure 5-28
Figure 5-29
29
Figure 5-30
30
Figure 5-31
31
Figure 5-32
32
Figure 5-33
33
Figure 5-34
Figure 5-35
35
69
Figure 5-36
36
Figure 5-37
37
Figure 5-38
38
Figure 5-39
39
Figure 5-40
40
Figure 5-41
41
Figure 5-42
42
Figure 5-43
43
Figure 5-44
44
Figure 5-45
Figure 5-46
46
Figure 5-47
Figure 5-48
48
Figure 5-49
49
Compare to Get Delta 64

Compare Success 65
Download 65
Download Success
66
Activate 66
Activate Success 66
Deleting Activation Task
67
Switching Submit Status 67
Deleting Plan Area 68
Confirming Plan Area 68
CMP Module No. Modification 68
Office Information Deletion (Including Ground & Radio Resources)
Site Bearer Migration 69
Diagram of Master/Slave Board Slots
70
Configuring Integrated UC Board
72
Configuring PVC in V3 Version 74
Configuring PVC in V4 Version 75
ATM Address Format 76
1588 Clock Configuration 1 77
1588 Clock Configuration 2 77
Shielding Alarms 78
Port Switch 79
Transport Qos Profile Type 80
Used Transport
ransport Bearer Type Profile Related to Basic Priority 80
Used Dedicated Service Transport Bearer Qos Profile
81
IP Function Switch 82
TABLES
Table 1-1
1 Notices in Data Configuration 1
Table 2-1
1
Table 2-2
2
Table 2-3
3
Table 2-4
4
Table 3-1
Table 3-2
Table 3-3
Table 3-4
Table 3-5
Table 3-6
Table 3-7
Table 3-8
8
Table 3-9
9
Table 3-10
Table 3-11
Table 3-12
Table 3-13
Table 3-14
14
Table 3-15
15
Table 3-16
16
Table 3-17
17
Table 3-18
VIII
Parameter Attributes 3
Sheets to Be Configured for IU/IUR and IUB 5
Sheets to Be Configured for Different IUB-Interface
IUB
Bearers 5
Sheets to Be Configured for Different IU/IUR-Interface
IU/IUR Interface Bearers 6
Basic Info 17
Plmn Config 18
Shelf Config 19
Board Config
19
Global Info 20
Interface IP 21
Service IP 22
Slave or Dsp Service Config 22
CCIU Service Config 23
Channel Port 23
Member Port 23
Local Office
24
IUB Office 25
ATM Bearer (IUB Auto) 27
ATM Bearer (IUB) 27
IP Bearer (IUB) 30
SCTP Config (IUB-ABIS)
(IUB
31
Static Route 32
C
10

Proprietary
Table 3-19
19
Table 3-20
Table 3-21
21
Table 3-22
22
Table 3-23
23
Table 3-24
Table 3-25
25
Table 3-26
26
Table 3-27
Table 3-28
28
Table 4-1
Table 4-2
2
Table 4-3
3
Table 4-4
4
Table 4-5
5
Table 4-6
6
Table 5-1
1
69
Table 5-2
2
Table 5-3
3
Table 5-4
Table 5-5
5
75
Table 5-6
6
Table 5-7
7
Table 5-8
Table 5-9
9
Table 5-10
10
IP Path Group 32
IP Path (CN) 33
Adjacent Office (CN)
34
SCTP Config (CN) 36
M3uaAS Config (CN) 37
M3uaRoute
37
M3uaRouteSet 38
PVC Config (IU-IUR)
(IU
38
Mtp3Route 41
Mtp3RouteSet 42
UTRAN Cell 44
Logic Cell Configuration 45
External UTRAN Cell
46
External GSM Cell 47
Neighbouring Cell 49
GSM Neighbouring Cell 49
Sheets to Be Configured for Each Transmission Type of a New Site
Configuring Data of ATM Interface Board 70
Introduction of USP Board
71
UDP Port No. 73
Relation of PVC Traffic Type, Traffic Parameter, and PVC Service Type
AFI of ATM Address 77
1588 Clock Configuration Related Parameters 77
Port Switch 79
IUB QOS Planning Rules 1 81
IUB QOS Planning Rules 2
81
11
IX
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
Master/slave configuration,
1
alternate backup slots
PLMN ID
CMP Module No. for integrated UC

(CMP & UCIU)
IUBCOM
5
6
Signaling point code

Netmask
OMCB gateway IP
Global check
In the Slave or Dsp Service

Config sheet of the quick data
configuration template, the
granularity of each line is board.
10
The description of Default Office

Flag in the Adjacent Office (CN)
sheet is incorrect.
11
Matters for attention in ATM+IP

multipath protection
Description
(1,3), (2,4), (11,13), (12,14)
It is recommended to set PLMN ID
as a combination of MCC + MNC,
each composed of 3 digits, e.g., for
460/1, the PLMN ID should be set as
460001.
Each master CMP board needs to
be configured with four CMP
MP module
Nos.
It is an address that needs to be
added for IUB-interface OMM
planning. Every 3 master CMPs
should be configured with one
IUBCOM.
Set it as a decimal value.
Set it as a decimal value.
It must be configured on the virtual
port.
In the synchronization process, the
system will check both the required
items and the optional items by
default. Sometimes the optional
items may cause synchronization
failure and
d the check can be cleared
manually.
The IP of each line must include four
types of protocol interfaces
(IUB/CS/PS/R). Do not fill in them in
separate lines.
The correct description should be:
1:Is Default Office
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
successfully first and then load the
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.
13
2There
Introduction
to Quick
Data
are three V4 quick data configuration
templates,
i.e., V4_Template_Equipment,
V4_Template_TransportNetwork, and UMTS Radio Quick Configuration Template, which
can be loaded into OMM one by one.
Figure 2-1 Template 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)
2014ZTE
ZTE C
CORPORATION. All rights reserved.
14

Proprietary
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
2014ZTE
ZTE C
16

Proprietary
No.
1
2
3
4
5
6
7
8
9
10
11
12
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
IU/IUR
IUB
Local Office
IUB Office
Adjacent Office
IP Bear (IUB)
SCTP Config (CN
CN)
M3uaAS Config (CN)
ATM Bearer (IUB Auto)
M3uaRoute
ATM Bearer (IUB)
M3uaRouteSet
PVC Config (IU--IUR)
Mtp3Route
Mtp3RouteSet
IP Path(CN)
IP Path Group
IP Path Group
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
.
1
IPoE1+IPoF
E
IUB Office
IP Bear(IUB)
IPoE1
IPoFE
ATMoE1
ATM+IP
IUB Office
IUB Office
IUB Office
IP
Bear(IUB)
IP
Bear(IUB)
IUB Office
ATM
Bearer(IU
B Auto)
ATMoSTM
ATMoSTM1
IUB Office
IP
Bear(IUB)
ATM
Bearer(IUB)
SCTP
Config
(IUB-ABIS
ABIS
)
Static
Route
SCTP
Config
(IUB-ABIS
)
Static
Route
IP Path
Group
SCTP
Config
3
(IUB-ABIS
)
Static
4
Static Route
Route
IP Path
IP Path
5
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-IUR
IUR)
(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
SCTP Config
(IUB-ABIS)
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
2014ZTE
ZTE CORPORATION.
C
18

Proprietary
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
2014ZTE
ZTE CORPORATION.
C
20

Proprietary
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.
C
22

Proprietary
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
11
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.
C
24

Proprietary
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
13
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.
Comp
Figure 2-24 Data Comparison
14
2014ZTE
ZTE CORPORATION.
C
26

Proprietary
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
15
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

Proprietary
3ThisSpecifications
cations
of sheets
Configuring
Guide deals mainly
with the common
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
Name
Value
Modificatio
A:Add,
n
A,M,P
D:Delete,
M:Modify, P:Pass
Indication
Managed
long:[1..409
Element ID 5]
2:UMTS
Mode Type long:[2..4]
3:GSM
4:GU
Omp's
ipv4
eg:xxx.xxx.xxx.xxx
omc port ip
Omp's
omc port
long:[0..32]
mask
length
Omp's
eg:xxx.xxx.xxx.xxx
omc port
ipv4
UMTS It should be as same as the IP
UMTS:
gateway
address of bond2:1
IP address
of SNTP
ipv4
eg:xxx.xxx.xxx.xxx
server
SNTP
0:Not use NTP clock synchronization,
networking long:[0..2]
1:Connected by OMM server,
2:Connected by RPU
mode
OMCB
Agent IP
ipv4
eg:xxx.xxx.xxx.xxx
Address to
NODEB
OMCB
Server IP
ipv4
eg:xxx.xxx.xxx.xxx
Address
OMCB
Server IP
long:[0..32]
Mask
Length
eg:xxx.xxx.xxx.xxx
OMCB
It can be used when it supports multipath
Inner Ip
ipv4
protection.
Address
Other,it is filled in default value 0.0.0.0 .
Remark
Primary
Key
R-I
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
29
17
ZXUR 9000
00 UMTS (V4.11.20) Commissioning Guide
Time Zone
Daylight
Saving
Time using
flag
Start time
of the
Daylight
Saving
Time(Mon/
Day/Hour/
Min)
End time
of the
Daylight
Saving
Time(Mon/
Day/Hour/
Min)
Step of
Daylight
Saving
Time(minut
te)
3.1.2
long:[-720,-6
60,-600,-54
0,-480,-420,
-360,-300,-2
40,-180,-12
0,-60,0,60,1
20,180,240,
300,360,420
,480,540,60
0,660,720,7
80]
The value range:

-720:GMT-12
-660:GMT-11
-600:GMT-10
-540:GMT-9
-480:GMT-8
-420:GMT-7
-360:GMT-6
-300:GMT-5
-240:GMT-4
-180:GMT-3
-120:GMT-2
-60:GMT-1
0:GMT
60:GMT+1
120:GMT+2
180:GMT+3
240:GMT+4
300:GMT+5
360:GMT+6
420:GMT+7
480:GMT+8
540:GMT+9
600:GMT+10
660:GMT+11
720:GMT+12
780:GMT+13
R-W-II
long:[0,1]
0:Stop
0:
1:Start
R-W-II
string
eg:Mon/Day/Hour/Min
R-W
string
eg:Mon/Day/Hour/Min
R-W
long:[0..330
08]
60 is recommended value.
R-W
Plmn Config
Table 3-2 Plmn Config

Parameter Parameter
Name
Value
18
Description
2014ZTE
ZTE CORPORATION.
C
30
Remark

Proprietary
Modificatio
n Indication
User label
Managed
Element ID
PLMN
Group
Object ID
Mobile
Country
Code
Mobile
Network
Code
MNC BCD
Code
Length
Default
PLMN
Indicator
Is Local
Office's
PLMN
3.1.3
A,D,M,P
A:Add, D:Delete, M:Modify, P:Pass
String
long:[1..409
5]
R-W
Primary
Key
long:[0..429
4967295]
Primary
Key
long:[0..999
]
R-W-II
long:[0..999
]
R-W-II
long:[2..3]
R-W-II
long:[0..1]
0:false
1:true
R-W-II
long:[0..1]
0:false
1:true
R-I
Shelf Config
Table 3-3 Shelf Config

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
Managed
long:[1..4095]
Element ID
Rack No.
long:[1..1]
Shelf No.
long:[1..3]
Master
Shelf Flag
long:[0..1]
3.1.4
0:Not Master Shelf

1:Is Master Shelf
Remark
Primary
Key
Primary
Key
Primary
Key
R-W-I
Board Config
Table 3-4 Board Config

Parameter
Parameter
Description
Name
Value
Modification
A,D,P
A:Add, D:Delete, P:Pass
Indication
Managed
long:[1..4095]
Element
]
Object ID
Remark
Primary
Key
rack/shelf/slot
string
eg:1/2/7
Primary
Key
Physical
Board Type
string
eg:UMP
R-I
31
19
Logical Board
Type
string
Module No.
string
Backup Mode
long:[0,1,5]
Mode Type
long:[0..2]
Port Type
long:[0..8]
Sdh speed
mode
long:[0..4]
E1 Frame
Type
long:[0,1,4,6]
E1
Impedance
long:[0,1,3]
Cable Type of
of Ethernet
Port
long:[2,3]
2:Fiber(default value)
3:Cable
CS Slave
Number Per
RUP
long:[0..15]
It is valid for GSM mode type.

The default value is 6(SBCJ) for 2G
RUP board.
3.1.5
eg:OMP
R-I
It should be filled multi module No., if

there are multi modules on one board.
eg:3;4;5
0:No Backup
1:1+1 Backup
5:1TO1 Backup
0:PUBLIC
1:2G
2:3G
0:INVALID
1:SDH-63E1
2:SDH-63T1
3:SDH-84T1
4:POS
5:ATM
6:E1
7:T1
8:Ethernet
0:INVALID
1:SDH AU-4
2:SDH AU-3
3:SONET STS-1
4:SONET STS-3C
0:Multi-Frame
1:Double Frame
4:Multi-Frame with checked
6:Forced Multi-Frame(default value)
It can be empty.
0:75(default value of Electric E1)
1:120
3:Invalid(default value of Channelized
E1)
It can be empty.
R-I
R-I
R-I
R-I
Global Info
Table 3-5 Global Info

Parameter
Parameter
Description
Name
Value
Modification
A,M,P
A:Add, M:Modify, P:Pass
Indication
Managed
long:[1..4095]
Element
]
Object ID
IP Segment
eg:rack/shelf/slot
ReAssemble string
Default Unit
20
R-I
2014ZTE
ZTE CORPORATION.
C
32
Remark
Primary Key
R-W

Proprietary
The First IP
Segment
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
string
eg:rack/shelf/slot
R-W
string
eg:rack/shelf/slot
R-W
string
eg:rack/shelf/slot
R-W
string
eg:rack/shelf/slot
R-W
string
eg:rack/shelf/slot
R-W
string
eg:rack/shelf/slot
R-W
string
eg:rack/shelf/slot
R-W
Interface IP
Table 3-6 Interface IP

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User Label
string
Managed
Element
long:[1..4095]
Object ID
Interface
string
eg:rack/shelf/slot
Board
It should be filled when it is Virtual
Module No.
long:[1..127]
port. Other,it can be filled in 1.
0:Interface
Port Type
long:[0,1,2]
1:Loopback port
2:Virtual port
Interface
0:invalid,
long:[0..128]
Local Port
1~4:real port,
No.
1~128:loop port
VLAN
long:[0..4095] 0 is invalid
Sequence
0 is invalid.
Vlan ID
long:[0..4095]
It is valid when it is sub interface.
Remark
R-W
Primary Key
Primary Key
Primary Key
Primary Key
Primary Key
Primary Key
R-W-I
33
21
VPN ID of sub
sub port
MAC
address
IP address of
interface
Mask Length
of interface
IP
3.1.7
long:[0..254]
string
ipv4
long:[0..32]
0 is invalid
R-W-I
eg:
xx-xx-xx-xx-xx-xx
eg:
xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx
eg:24;24
3.1.8
R-W-I
R-W-I
Service IP
Table 3-7 Service IP

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
Managed
long:[1..4095]
Element
]
Object ID
eg:
Service IP
ipv4
xxx.xxx.xxx.xxx
Bit0=1:A Interface of GSM Network
Bit1=1:Abis PS Interface of GSM
Application
Network
string
Type of IP
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
Bit3=1: IuPS Interface of 3G Network
address(3G)
Bit4=1:Iub Common Interface of 3G
Network (for CCIU)
VPN ID of sub
long:[0..254]
0 is invalid
sub port
PLMN info of
Service IP
R-W
string
eg:
MCC1:MNC1;MCC2:MNC3
or 65535:65535,
65535:65535 denotes supporting all
PLMN
Remark
Primary Key
Primary Key
R-I
R-W-I
Slave or Dsp Service Config
Table 3-8 Slave or Dsp Service Config

Parameter Parameter
Description
Name
Value
Modificatio
A,D,P
n Indication
Managed
long:[1..409
Element
5]
Object ID
Data Format:
RACK/SHELF/SLOT,
Board Info
string
2G:RUP or ETCB or EDTB or ESDTB board
3G:RUP or DRP board
22
2014ZTE
ZTE CORPORATION.
C
34
Remark
Primary
Key
Primary
Key

Proprietary
Service IP
Address of
SLAVE
string
3.1.9
Data Format:
xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx;xxx.xxx.xxx
.xxx;xxx.xxx.xxx.xxx
Primary
Key
CCIU Service Config
Table 3-9 CCIU Service Config

Parameter Parameter
Description
Name
Value
Modification
A,D,P
Indication
Managed
long:[1..409
Element
5]
Object ID
Service IP
Address of
Data Format(Iub Common Interface):
string
CCIU
SLAVE
Remark
Primary
Key
Primary
Key
3.1.10 Channel Port

Table 3-10 Channel Port
Parameter Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Channel
long:[1..16]
Group ID
VLAN
Sequence
Vlan ID
Bound
Mode
long:[0..409
5]
long:[0..409
5]
long:[3..5]
VPN ID of
sub port
MAC
address
IP address
of interface
Mask
Length of
interface IP
long:[0..254
]
string
ipv4
long:[0..32]
0 is invalid
0 is invalid.
It is valid when it is sub interface.
3:on Mode
4:backup Mode
5:802.3AD Mode
0 is invalid
Remark
R-W
Primary
Key
Primary
Key
Primary
Key
R-W-II
R-W-II
R-W-II
eg:
xx
xx-xx-xx-xx-xx-xx
eg:
eg:24;24
R-W
R-W-II
R-W-II
3.1.11 Member Port

Table 3-11 Member Port
Parameter Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
Remark
R-W
35
23
Managed
Element
Object ID
Member
port ID of
Channel
long:[1..409
Primary
Key
5]
long:[1..128]
Primary
Key
Group
Interface
Board
string
eg:rack/shelf/slot
R-I
Local port
No. of
member port
port
Channel
Group ID
Bounding
mode of
member
port
System
Priority of
LACP
protocol
Timeout
Type of
LACP
protocol
long:[1..4]
R-I
long:[1..16]
R-I
long:[1..4]
long:[1..655
35]
long:[0..1]
1:active
2:passive
3:on
4:backup
R-W-II
The default value is 32768.
R-W
0:long time,
1:short time,
The default value is 0.
R-W
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
Template
Local Office
Table 3-12 Local Office

Parameter
Parameter
Name
Value
24
Description
2014ZTE
ZTE CORPORATION.
C
36
Remark

Proprietary
Modification
Indication
A,D,M,P
Managed
Element
Object ID
long:[1..4095
5]
Primary
Key
Net type of
local office
long:[1..255]
]
Primary
Key
Whether to
enable
network
appearance
long:[1,2]
1:Enable
2:Disable
R-W-I
Network
appearance
long:[0..4294
4967295]
Default value is 0 if this parameter cann't be

be configurated.
It is valid when NETAPPEARANCEFLAG=1.
NETAPPEARANCEFLAG=1.
R-W
14-bit
signalling point
point code of
local office on
on the net
long:[0..1638
83]
R-W-I
24-bit
signalling point
point code of
local office on
on the net
long:[0..1677
77215]
R-W-I
Mode Type
long:[0,1]
0:2G
1:3G
R-I
ATM address
string
20 Bytes, decimal.
GSM doesn't need to config.
R-W
Network
Resource
Identifier Bit
Num in CS
Domain
long:[0..10]
It is valid just for UMTS, and the default value is

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

value is 0.
R-W
BSC ID
long:[1..4095
5]
It should be filled when Managed Element is

is GU mode, and BSCID != MEID.
Other, it can be empty.
3.2.2
IUB Office
Table 3-13 IUB Office

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

Proprietary
Transport
Qos Profile
parameter
Index
3.2.3
long:[1..32]
1:Two IP Paths,
2:Three IP Paths,
3:One ATM Path and Two IP Paths,
4:Two ATM Paths,
5:One IPOE Path and One IPOFE Path,
6:One ATM Path and One IP Path.
This parameter is valid if
UPQOSMAPTYPE=2.It can be filled in any
value if it is invalid.
ATM Bearer(IUB Auto)
Table 3-14 ATM Bearer (IUB Auto)

Parameter
Parameter
Description
Name
Value
Modification
A,D,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent Net
long:[1..409
Element
5]
Identifier
Destination
ipv4
IP address
Destination
IP Address
long:[0..32]
Mask Length
OMCB Path
It should be configured when IUB office is
long:[1..3] multipath production.
priority
Path Group
long:[0..409
Id
5]
Atm Interface
string
rack/shelf/slot
Board
E1 List
string
e1 index, separated by ";"
3.2.4
R-W-I
Remark
R
Primary
Key
Primary
Key
R-I
R-I
R
R-I
R-I
R-I
ATM Bearer(IUB)
Table 3-15 ATM Bearer (IUB)

Parameter
Parameter
Name
Value
Description
Remark
Modification
Indication
A,D,M,P
User label
string
Managed
Element
Object ID
long:[1..4095
5]
Primary
Key
Adjacent Net
Element
Identifier
long:[1..4095
5]
PVC ID
long:[1..1200
00]
Primary
Key
Atm Interface
Board
string
rack/shelf/slot
R-I
39
27
ZXUR 9000 UMTS (V4.11.20)

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

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

Proprietary
Peak cell rate

for CLP=0+1
(PCR0+1)
Peak cell rate

for CLP=0
(PCR0)
Cell delay
variation
tolerance
(CDVT)
Sustainable
cell rate for
CLP=0 (SCR0)
(SCR0)
Sustainable
cell rate for
CLP=0+1
(SCR0)
long:[0..1821
1066133]
Unit: Kbps.
This Traffic Para surpports all Service Category
Category and all Traffic Type.
R-W-I
long:[0..1821
1066133]
Unit: Kbps.
Service Category:
CBR ,rtVBR and nrtVBR.
Traffic Type:
atmClpTaggingNoScr(3).
R-W
long:[0..4294
4967295]
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and UBR.
Traffic Type:
atmClpTransparentNoScr (8),
atmNoClpNoScrCdvt (11),
R-W
long:[0..1821
1066133]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpTaggingScrCdvt(14).
R-W
long:[0..1821
1066133]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmNoClpScr(4).
R-W
Maximum
burst cell
number (MBS)
(MBS)
long:[0..4294
4967295]
Path Group Id
Id
long:[0..4095
5]
TrPath ID
sequence<lo
ong,4>
AAL2 Path ID
intra office
long:[1..4294
4967295]
AAL2 Path
Ownership
long:[0..1]
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmNoClpScr(4).
R-W
R
For one PLMN, the value range of TrPath ID is
ID is [32..127].
R
R
0:Local End
1:Peer End
41
29
AAL2 Path
Service Type
long:[10..14]
]
10:RT
11: NRT1
12: NRT2
13: NRT3
14: MIX
Application
Type of UNI
Link
long:[1..3]
1: ALCAP
2: NBAP(NCP)
3: NBAP(CCP)
Destination IP
IP address
ipv4
R-W
Destination IP
IP Address
Mask Length
long:[0..32]
R-W
OMCB Path
priority
long:[1..3]
3.2.5

multipath production.
R-W
IP Bearer(IUB)
Table 3-16 IP Bearer (IUB)

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent Net
long:[1..409
Element
5]
Identifier
SCTP
long:[1..840
association
0]
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
4967]
maximum of one third of the minimum of
Trpath (kbps)
Tx bandwidth and the Rx bandwidth, and
64000bps.
Path Rx
long:[0..429 value, and the specific value is the
Band width of
4967]
Trpath (kbps)
64000bps.
Path Group
long:[0..409
ID
5]
Board Info of
string
rack/shelf/slot
IPOE
E1 List
string
Separated by ";"
E1 TS List
string
Separated by ";" and "-"
long:[0..120 0:ppp
MP Port No.
[1..120]:Mp
]
30
2014ZTE
ZTE C
42
Remark
R
Primary
Key
Primary
Key
Primary
Key
R-W
R-W
R
R-W
R-W
R-W
R

Proprietary
Ip Address of
MP or PPP
Port
ipv4
Ip Address
Mask Length
of MP or PPP
Port
long:[8..32]
IP Domain
No.
long:[21..23
]
OMCB Path
priority
long:[1..3]
3.2.6
If MPLINK>0, then filling the Ip address of

MP or port, else filling the Ip Address of
PPP or port.
It can be empty.
If MPLINK>0, then filling the Ip address
mask length of MP or port, else filling the
Ip address mask length of PPP or port.
It can be empty.
Default is 24.
21:IP Domain No.1,
22:IP Domain No.2,
23:IP Domain No.3
multipath production.
R-W
R-W
IP Bearer (ABIS)
Related to GSM network.
3.2.7
Table 3-17 SCTP Config (IUB-ABIS)

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Association
long:[1..840
0]
ID
CMP Module
2G:3..63
long:[3..63]
No.
3G:3..31
long:[1..655
Local port
35]
Primary
Key
Local IP
address
R-W-II
Remote port
Remote IP
address
SCTP
association
bearer
protocol type
Max
Retransmissi
on
Timeout(10m
illisecond)
Min
Retransmissi
on
Timeout(10m
illisecond)
ipv4
It can be filled in one IP address
long:[1..655
Remark
R-W
Primary
Key
R-I
R-W-II
R-W-II
35]
ipv4
It can be filled in one IP address
R-W-II
long:[15,21]
15:NBAP
21:IPABIS
R-I
long:[10..30
00]
default value:500
R-W
long:[10..10
00]
default value:50
R-W
43
31
Initial
Retransmissi
on
Timeout(10m
illisecond)
Heartbeat
Interval(10mil
lisecond)
Delayack
interval(10mil
lisecond)
long:[10..30
00]
default value:100
R-W
long:[10..60
00]
default value:500
R-W
long:[0..20]
default value:20
R-W
3.2.8
Static Route
Table 3-18 Static Route

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
Managed
long:[1..409
Element
5]
Object ID
Static Route
long:[1..500
0]
Number
Static route
eg:
network
ipv4
xxx.xxx.xxx.xxx
prefix
Static route
network
long:[8..32]
mask length
Route next
long:[0..0]
0:IP address
hop type
Route next
eg:
ipv4
hop address
xxx.xxx.xxx.xxx
VPN ID of sub long:[0..254
0 is invalid
sub port
]
Route
distance
The flag if bfd
is enabled
3.2.9
long:[1..254]
0:unactived
1:actived
Primary
Key
Primary
Key
R-W-II
R-W-II
R-I
R-W-II
R-W-II
R-W-II
IP Path Group
Table 3-19 IP Path Group

Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Path Group
long:[0..409
Id
5]
32
R-W
R-W-II
long:[0..1]
Remark
2014ZTE
ZTE C
44
Remark
R-W
Primary
Key
Primary
Key

Proprietary
ZXUR 9000 UMTS (V4.11.20) Commissioning Gu

Guide
Father Path
Group Id
long:[0..655
35]
CMP Module
No.
long:[3..63]
Path Group
Bear Type
PLMN Group
Object ID
Ratio of
occupied
private
bandwidth of
Path Group
by operator
Forward
bandwidth(kb
ps)
Backward
bandwidth(kb
ps)
long:[2,5]
65535 is invalid, other value must be in

[0..4095]
2G:3..63
3G:3..31
Support to modify the module No. of path
group for Iu interface.
2:ETHERNET_NOVLAN
5:ETHERNET_VLANTAG
R-I
R-W-II
R-W-II
sequence<l
ong,4>
eg:1;2
R-I
sequence<l
ong,4>
0 to 1000
If more than one MCC/MNC, separate
each value by ';'
R-W-II
long:[0..429
4967]
R-W-II
long:[0..429
4967]
R-W-II
3.2.10 IP Path (CN)

Table 3-20 IP Path (CN)
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent Net
long:[1..409
Element
5]
Identifier
Path ID
long:[0..7]
Path Group
ID
CMP Module
long:[0..409
5]
No.
PLMN Group
Object ID
Destination
IP Address
Destination
IP Address
Mask Length
long:[3..63]
Remark
R-W
Primary
Key
Primary
Key
Primary
Key
Primary
Key
2G:3..63
3G:3..31
R-W-II
long:[0..429
4967295]
R-I
ipv4
R-W-II
long:[0..32]
R-W-II
45
33
Forward
bandwidth(kb
ps)
long:[0..429
4967]
Backword
bandwidth(kb
ps)
long:[0..429
4967]

value, and the specific value is the
64000bps.
value, and the specific value is the
64000bps.
R-W-II
R-W-II
3.2.11 Adjacent Office (CN)

Table 3-21 Adjacent Office (CN)
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent Net
long:[1..409
Element
5]
Identifier
Adjacent
long:[1..204
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
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].
Object ID
ong,4>
eg:1;2
2:UMTS
Mode Type
long:[2..3]
3:GSM
34
2014ZTE
ZTE C
46
Remark
R-W
Primary
Key
Primary
Key
R-I
R-I
R-I
R-I

Proprietary
Type of
adjacent
office
long:[16,32,
64,512,576,
1023,4096,
32768]
Bear type
long:[0..2]
Encode type
of signalling
point
Destination
point code
long:[0..167
77215]
Sub-Service
Field
long:[0,4,8,
12]
Connection
relationship
with local
signalling
point
Whether to
support
broadband
properties
long:[14,24]
2G office:
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
1023:SMLC
3G office:
16:BSC
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
32768:SAS
0: ATM (3G)
1: IP
2: TDM (2G)
(Parameters can't be modified)
14:SPC 14 bits,
24:SPC 24 bits
14 bits:0..16383
24 bits:0..16777215
0: International SPC,
4: Reserved international SPC,
8: National SPC,
12: Reserved National SPC
R-I
R-I
R-W-II
R-W-II
R-W-II
long:[1..3]
1:Associated
2:Quasi-associated
3:No connection
R-W-II
long:[0..1]
0:Not Support
1:Support
R-W-II
Protocol type
long:[1..3]
ATM address
string
Default Office
Office Flag
sequence<l
ong,4>
Capacity
Weight in
CS/PS
Domain
sequence<l
ong,4>
1:CHINA
2:ITU
3:ANSI
20 bytes, separate each byte with ".",
decimal.
2G office dosen't congifg it
For one PLMN,
0:Is Default Office
1:Is Not Default Office,
eg:1;0
For one PLMN,the value range is [0..100].

eg:1;0
R-W-II
R-W
R-W
R-W
47
35
Number of
Network
Resource
Identifier in
CS/PS
Domain
Network
Resource
Identifier in
CS/PS
Domain
sequence<l
ong,4>
For one PLMN,the value range is [0..4].

eg:1;0
R-W
string
The value range of one Network Resource

Identifier is [0..1023].
If there are two PLMNs,the NUMOFNRI of
PLMN1 is 2 and the NUMOFNRI of
PLMN2 is 3,then NRILIST is
10;11@100;101;103
R-W
3.2.12 SCTP Config (CN)

Table 3-22 SCTP Config (CN)
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent
long:[1..204
Office ID
8]
Association
long:[1..300 2G:1..2048
ID
0]
3G:1..3000
CMP Module
2G:3..63
long:[3..63]
No.
3G:3..31
Application
1:Server
type of
long:[1..2]
2:Client
association
long:[1..655
Local port
35]
Local IP
It can be filled in four IP address at most,
ipv4
Address
such as xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx
long:[1..655
Remote port
35]
It can be filled in four IP address at
Remote IP
ipv4
most,such as
Address
long:[1..840
ASP Number
0]
Max
Retransmissi
long:[10..30
on
default value:500
00]
Timeout(10m
illisecond)
Min
Retransmissi
long:[10..10
on
default value:50
00]
Timeout(10m
illisecond)
36
2014ZTE
ZTE C
48
Remark
R-W
Primary
Key
Primary
Key
Primary
Key
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
R-W-II
R-I
R-W
R-W

Proprietary
Initial
Retransmissi
on
Timeout(10m
illisecond)
Heartbeat
Interval(10mil
lisecond)
Delayack
interval(10mil
lisecond)
long:[10..30
00]
default value:100
R-W
long:[10..60
00]
default value:500
R-W
long:[0..20]
default value:20
R-W
3.2.13 M3uaAS Config (CN)

Table 3-23 M3uaAS Config (CN)
Parameter
Parameter
Name
Value
Description
Remark
Modification
Indication
A,D,M,P
User label
string
Managed
Element
Object ID
long:[1..4095
5]
Primary
Key
Adjacent
Office ID
long:[1..2048
8]
Primary
Key
AS Number
long:[1..640]
]
Primary
Key
ASP Number
sequence<lo
ong,16>
The value range of ASP Number is 1..8400.

1..8400.
eg:1;2
R-W-I
Whether exists
exists routing
context
long:[0..1]
0: FALSE
1: TRUE
R-W-I
Routing
context ID
long:[0..4294
4967295]
4294967295 is invalid
R-W-I
Whether exists
exists peer
routing context
context
long:[0..1]
0: FALSE
1: TRUE
R-W
Peer routing
context ID
long:[0..4294
4967295]
4294967295 is invalid
R-W
AS property
long:[1..5]
1: SGP,
2: ASP,
3: IPSP SERVER,
4: IPSP CLIENT,
5: DOUBLE EXCHANGE MODEL
R-W-I
AS traffic
mode
long:[1..2]
1: Override,
2: Loadshare
R-W-I
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
Name
Value
Description
Remark
49
37
Modification
Indication
A,D,M,P
User label
string
R-W
Managed
Element
Object ID
long:[1..4095]
5]
Primary
Key
Route Number
Number
long:[1..640]
]
Primary
Key
Route range
mode
long:[0..2]
AS1 Number
long:[1..640]
]
R-W-I
AS2 Number
long:[0..640]
]
R-W-I
AS3 Number
long:[0..640]
]
R-W-I
AS4 Number
long:[0..640]
]
R-W-I
0:natural sort
1:ikebana sort
2:handworked sort
R-W-I
3.2.15 M3uaRouteSet
Table 3-25 M3uaRouteSet
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent
long:[1..204
8]
Office ID
long:[1..640]
Route ID 1
]
Route ID 2
long:[0..640]
Remark
R-W
Primary
Key
Primary
Key
R-W-II
R-W-II
3.2.16 PVC Config (IU-IUR)

Table 3-26 PVC Config (IU-IUR)
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent
long:[1..204
Office ID
8]
long:[1..120
PVC ID
00]
38
2014ZTE
ZTE C
50
Remark
R-W
Primary
Key
Primary
Key
Primary
Key

Proprietary
Atm
Interface
Board
string
ATM port
long:[1..244]
E1 list
string
VPI on High
End
VCI on High
End
long:[0..409
5]
long:[32..65
535]
rack/shelf/slot
ATM Optical Port:[1..4],
IMA Port:[5..244]
IMA port need to be configured.
Separated by ";"
R-W-II
R-I
R-W
R-W-II
R-W-II
0: AAL5 Signal,
1: AAL5 Data,
2: AAL2 Data
PVC Service
Type
long:[0..2]
PVC
interface
type
long:[2..4]
AAL5 Signal: the Signalling over ATM,

AAL5 Data: IUPS is the service over ATM,
AAL2 Data: IUCS or IUR is the service
over ATM.
2; IUR,
3: IUCS,
4: IUPS
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
R-I
R-I
CBR surpports:
atmNoClpNoScr(1)
atmClpTransparentNoScr(8),
atmNoClpNoScrCdvt(11).
Service
Category
long:[0,1,2,4
]
rtVBR and nrtVBR surpport:

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

Proprietary
Maximum
burst cell
number
(MBS)
Path Group
ID
TrPath ID
AAL2
Attached
Module
AAL2 Path
ID intra
office
AAL2 Path
Service Type
Type
AAL2 Path
Ownership
Signalling
link number
Signalling
Link
Attached
Module
Signalling
Link Code
Destination
IP address
long:[0..429
4967295]
long:[0..409
5]
sequence<l
ong,4>
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmNoClpScr(4).
R-W
R
For one PLMN,the value range of TrPath
ID is [32..127].
long:[3..31]
R-W
long:[1..429
4967295]
long:[10..14]
long:[0..1]
10: RT,
11: NRT1,
12: NRT2,
13: NRT3,
14: MIX
0:Local End
1:Peer End
long:[1..900
0]
long:[3..31]
R-W
long:[0..15]
R-W
ipv4
R-W
3.2.17 Mtp3Route
Table 3-27 Mtp3Route
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
long:[1..200
Route ID
0]
R-W
Adjacent
Office ID
long:[1..204
8]
It must be filled if LINKSET_1 is not filled.

It should be filled for 3G.
Remark
Primary
Key
Primary
Key
53
41
Link set 1
Link set 2
Permutation
of signalling
links
long:[1..102
4]
long:[1..102
4]
long:[0..8]
0:Any arrangement (default value)

1:According to SLS_bit0 choose routing
groups
2:According to SLS_bit1 choose link
groups
groups
groups
5:According to SLS_bit0 and SLS_bit1
choose link groups
choose link groups
choose link groups
8:Floral sort
R-W
3.2.18 Mtp3RouteSet
Table 3-28 Mtp3RouteSet
Parameter
Parameter
Description
Name
Value
Modification
A,D,M,P
Indication
User label
string
Managed
long:[1..409
Element
5]
Object ID
Adjacent
long:[1..204
8]
Office ID
long:[1..200
Route ID 1
0]
Route ID 2
Route ID 3
Route ID 4
long:[0..200
Remark
R-W
Primary Key
Primary Key
R-W-I
R-W-I
0]
long:[0..200
R-W-I
0]
long:[0..200
R-W-I
0]
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

Proprietary
3.2.26 Lucent Channel

3.2.27 iTC Office
55
43
ZXUR 9000 UMTS (V4.11.20) Commissioning

Commissioni Guide
4TheSpecifications
of
Configuring
UMTS
first six sheets are required, while
other
sheets are optional.
4.1
UTRAN Cell
Table 4-1 UTRAN Cell
Parameter
Name
Parameter
Value
Modification
n Indication
A,D,M,P
[Managed
Element
Object ID]
long:[1..4095
5]
User Label
string:[0..80]
]
RNC ID
long:[0..4095
5]
Primary
Key
NodeB No
long:[0..6553
35]
R-W
W-I
Cell ID
long:[0..6553
34]
Primary
Key
Local Cell
Identity
long:[0..2684
435455]
R-W
W-I
Frequency
Band
Indicator
0:Band
I,1:Band
II,2:Band
III,3:Band
IV,4:Band
V,5:Band
VI,7:Band
VIII
R-W
W-I
UUARFCN
44
long:[9612..9
9888,9262..9
9538,12,37,6
62,87,112,13
37,162,187,2
212,237,262,
2,287,937..1
1288,1312..1
1513,1662,1
1687,1712,1
1737,1762,1
1787,1812,1
1837,1862,4
4132..4233,7
782,787,807,
7,812,837,86
62,4162..418
88,812,837,2
2712..2863]
Description
Remark
A:Add, D:Delete, M:Modify,P:Pass

Primary
Key
Cannot use invalid character < > & ' "
R-W
W
uarfcnUl is calculated by uarfcnDl, should not input

input any value.
{freqBandInd==0} [9612..9888],
{freqBandInd==1}
[9262..9538][12][37][62][87][112][137][162][187][212
][212][237][262][287],
{freqBandInd==2} [937..1288],
{freqBandInd==3}
[1312..1513][1662][1687][1712][1737][1762][1787][1
87][1812][1837][1862],
{freqBandIn
{freqBandInd==4}
[4132..4233][782][787][807][812][837][862],
{freqBandInd==5} [4162..4188][812][837],
{freqBandInd==7} [2712..2863]
2014ZTE
ZTE C
56

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

separated by ";".
R-W
W-I
4.2 Logic Cell Configuration

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

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

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

separated by ";".
R-W
W-I
4.4 External GSM Cell

Table 4-4 External GSM Cell
Parameter Parameter
Name
Value
Description
Remark
59
47
Modification
n Indication
A,D,M,P
[Managed
Element
Object ID]
long:[1..4095
5]
Primary
Key
User Label
stirng:[0..80]
]
R-W
W
RNC ID
long:[0..4095
5]
Primary
Key
Cell Identifier
Identifier of
Adjacent
GSM Cell
long:[0..6553
35]
Primary
Key
Location
Area Code of
of Adjacent
GSM Cell
long:[1..6553
33,65535]
Primary
Key
Band
Indicator
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
Used,4:GSM
M 480 Band
Band
Used,5:GSM
M 750 Band
Band
Used,6:GSM
M 850 Band
Band
Used,<defau
ult:0>
R-W
W-I
BCCH
ARFCN
long:[512..88
85,512..812,
,0..124,955..
.1023,259..2
293,306..340
0,438..511,1
128..251]
Network
Colour Code
Code
long:[0..7]
R-W
W-I
Base Station
Station
Colour Code
Code
long:[0..7]
R-W
W-I
48
{bandIndicator==0} [512..885],
{bandIndicator==2} [0..124][955..1023],
{ba
{bandIndicator==4}
[306..340],
{bandIndicator==6} [128..251]
2014ZTE
ZTE C
60
R-W
W-I

Proprietary
Mobile
Country
Code
long:[0..999]
]
R-W
W-I
Mobile
Network
Code
long:[0..999]
]
R-W
W-I
BSC
Identifier
long:[0..6553
35]
R-W
W-I
4.5 Neighbouring Cell

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

Table 4-6 GSM Neighbouring Cell
Parameter Parameter
Name
Value
Description
Remark
Modification
n Indication
A,D,M,P
[Managed
Element
Object ID]
long:[1..4095
5]
Primary
Key
User Label
string[0..80]
R-W
RNC ID
long:[0..4095
5]
Primary
Key
Cell ID
long:[0..6553
34]
Primary
Key
Location
Area Code
long:[1..6553
33,65535]
Primary
Key
Cell Identifier
Identifier
long:[0..6553
35]
Primary
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
49
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

Proprietary
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: The
he 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 will
will be generated automatically.
Plan template consists of three templates: Equipment template, TransportNetwork,
template, and UMTS Radio template. This template can be used on both OMMR and
ICM.
MO Template: It can only be operated through ICM and is similar
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
51
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

Proprietary
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
53
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

Proprietary
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
55
Figure 5-11
5.1.3.2
C
Confirm
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.
C
68

Proprietary
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
57
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

Proprietary
The process of importing Optimization Template is the same as that of

importing Plan Template. Check whether the number of successful records in
Succeed/All
ucceed/All Counts is the same as the number of all records. If it is, the
template is loaded successfully.
Note:
When importing the Optimization Template from ICM, pay attention to the
following 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
59
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

Proprietary
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
61
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.
C
74

Proprietary
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
63
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.
C
76

Proprietary
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
65
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.
C
78

Proprietary
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
67
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.
C
80

Proprietary
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
ATMoSTMIPoE1
IPoFE
ATMoE1
ATM+IP
.
E
1
1
IUB Office
IUB Office IUB Office IUB Office IUB Office IUB Office
ATM
IP
IP
ATM
IP
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
69
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
5.5.2
Configuration Guide of ATM Interface Board Properties
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
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
etc.)
Board
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.
C
82

Proprietary
EDTS_2/EDTS_
3
EDTA
ESDTA
EAPB
ESDTS_2
EXIS
5:ATM
ESDTI
ESDHS
EDTI
EDTS_3/EMDTS
EMSI
5.5.3
6:E1;
7:T1
1:
SDH-63E1
;
2:
SDH-63T1
;
3:
SDH-84T1
1:
SDH-63E1
;
2:
SDH-63T1
;
3:
SDH-84T1
6: E1;
7: T1
0: INVALID
0: INVALID
1: STM-1
1: SDH-AU
AU-4;
2: SDH-AU
AU-3;
3:
SONET-STS
STS-1
1: STM-1
1: SDH-AU
AU-4;
4:
SONET-STS
STS-3
C
1: STM-1
1: SDH-AU
AU-4;
2: SDH-AU
AU-3;
3:
SONET-STS
STS-1
0: INVALID
0: INVALID
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
Function
Logical
Board
Description
Board
Must be configured in
the master/slave
Processes the common control
mode. Each master
plane
protocols
on
the
Iub
and
Iu
USP
CMP
board must be
interfaces.
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
71
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.
C
84

Proprietary
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-plane
plane 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
73
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)/(179215)=2.23, and the round-down
down result is 2. That is,
one IUCS user plane IP can be used
us 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

Proprietary
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
)
1
T
rtVbr
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
75
abr
atmClpNoTaggingMcr(8)
PCR0+
1
CDVT
MCR
atmNoTrafficDescriptor(1)
atmNoClpNoScr(2)
ubr
atmNoClpNoScrCdvt(12)
atmNoClpTaggingNoScr(11)
ubr+
atmTrafficForUbr+(16)
PCR0+
1
PCR0+
1
PCR0+
1
PCR0+
1
CDVT
CDVT
MCR
MBS
MFS
CDV
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.
C
88

Proprietary
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
77
5.9
Shielding Alarms
Configuration Path: Managed Element > Equipment > Rack > Gate controls
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.
C
90

Proprietary
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-slave
slave 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
79
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

Proprietary
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
81
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.
C
94

Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide-Quick Data Configuration - R1.4

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide-Quick Data Configuration - R1.4

Enviado por

Direitos autorais:

Formatos disponíveis

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

com to remove the watermark

ZXUR 9000 UMTS (V4.11.20)

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

Reason for Revision

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

Intended audience: RNC commissioning engineer

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

5.12.2 QOS According to Service Type

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

Compare to Get Delta 64

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Com

CMP Module No. for integrated UC

Signaling point code

In the Slave or Dsp Service

The description of Default Office

Matters for attention in ATM+IP

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

Introduction to the Equipment Template

Figure 2-5 shows the sheets included

An Example of Filled Equipment Template

Transport Network Template

Introduction to the Transport Network Template

Figure 2-6 shows the sheets included in the Transport

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

1. Sheets for IU/IUR and IUB

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

An Example of Filled Transport Network Template

The template is corresponding to OMMR V12.11.40P03.

UMTS Radio Template

Introduction to the UMTS Radio Template

ZTE Confidential Proprietary

ZXUR 9000 UMTS (V4.11.20) Commissioning Guide

An Example of Filled UMTS Radio Template