ZTE Quick Commissioning Guidelines

1 Notices in Data Configuration
1.1 Restrictions on Configuration Planning

1.1.1 Boards & Slots
1.1.2 IP Planning
1.1.3 Others
2 Introduction to Quick Data Configuration

2.1 Overview of Plan Templates
2.1.1 Template Info Sheet
2.1.2 Index Sheet
2.1.3 Attributes of Parameters
2.1.4 Equipment Template
2.1.5 Transport Network Template
2.1.6 UMTS Radio Template
2.2 Common Functions
2.2.1 Loading Templates
2.2.2 Exporting Templates
2.2.3 Check on Imported Quick Configuration Template
2.2.4 Restoring Modify Area from Snapshot Area
2.2.5 Data Comparison Between Snapshot Area & Modify Area
3 Equipment Template and Transport Network Template Configuration

Specifications
3.1 Equipment Template
3.1.1 Basic Info
3.1.2 Plmn Config
3.1.3 Shelf Config
3.1.4 Board Config
3.1.5 Board Warehouse
3.1.6 Unit Connection
3.1.7 Global Info
3.1.8 Interface IP
3.1.9 Service IP
3.1.10 User Plane Service
3.1.11 Channel Port
3.1.12 Member Port
3.1.13 Super Vlan
3.1.14 Super Vlan Member
3.1.15 DHCP Server
3.1.16 DHCP Client
3.1.17 DHCP Relay
3.1.18 VRF Base Info
3.1.19 VRF Route Target
3.1.20 LAPD Config
3.2 TransportNetwork Template
3.2.1 Local Office
3.2.2 Static Route
3.2.3 IP Path Group
3.2.4 IUB Office
3.2.5 SCTP Config(IUB)
3.2.6 IP Bearer(IUB)
3.2.7 IPOE Bearer(IUB)
3.2.8 UMTS ATM Bearer(IUB Auto)
3.2.9 TD ATM Bearer(IUB Auto)
3.2.10 ATM Bearer(IUB)
3.2.11 IP Bearer(ABIS)
3.2.12 Adjacent Office(CN)
3.2.13 SCTP Config(CN)
3.2.14 M3uaAS Config
3.2.15 M3uaRoute
3.2.16 M3uaRouteSet
3.2.17 IP Path(CN)
3.2.18 PVC Config(IU-IUR)
3.2.19 Mtp2Link
3.2.20 Mtp3Route
3.2.21 Mtp3RouteSet
3.2.22 Dynamic Sctp
3.2.23 No.7 PCM
3.2.24 MSC Office
3.2.25 SGSN Office
3.2.26 Fr Gb
3.2.27 Ip Gb
3.2.28 Lucent Channel
3.2.29 PCM(ITC-MSC)
3.2.30 iTC or BSC Office
4 UMTS Radio Template Configuration Specifications

4.1 UTRAN Cell FDD
4.2 ULogicalCell
4.3 UExternalUtranCellFDD
4.4 UExternalGSMCell
4.5 UExternalENodeBFunction
4.6 UExternalEUTRANCellFDD
4.7 UExternalEUTRANCellTDD
4.8 UUtranRelation
4.9 UGSMRelation
4.10 UEUtranRelation
4.11 UImsiSnacFilter
4.12 UMbms
4.13 UMbmsSa
4.14 UMbmsFreq
5 Special Subject
5.1 ICM Data Configuration Flow (All-Parameter Configuration)
5.1.1 ICM Initialization
5.1.2 Exporting Optimization Template (All Parameters)
5.1.3 Data Import
5.1.4 Deleting Plan Area
5.2 CMP Module No. Modification
5.3 Overall Office Information Deletion (Including Ground & Radio Resources)
5.4 Site Bearer Migration Function
5.5 PVC Configuration
5.6 ATM Address Conversion
5.7 Special Subjects About Separated User-Plane IPs
5.7.1 Mapping between RUB Board Quantity & Service IP
5.8 Special Subject About Module No.
5.8.1 Introduction to CMP/DMP
5.8.2 D/C Module No. Planning Solution for Newly-Commissioned Sites
5.9 Implicit BFD
5.10 Configuration of the IUB Bandwidth
5.10.1 E1 Bearer
5.11 Special Subject About GIPI/GIPI3/GIPI4 Board Backup
5.11.1 Comparison Between Load-Sharing Backup & Master-Slave Backup
5.11.2 Notices in Master-Slave Configuration
1 Notices in Data Configuration

In the data configuration process, please pay close attention to the parameters that may be
configured improperly, as detailed in Table 1-1.
1.1 Restrictions on Configuration Planning
1.1.1 Boards & Slots
Table 1-1 Restrictions on Boards & Slots
No. Board Type Restrictions

The GIPI3/4 board should be plugged in Slots 5-8 in
priority. If it is plugged in other slots, the total
throughput will be decreased by half.
1 GIPI3/4
Slots 15-17 cannot provide external electrical port. And
the base station cannot extract clock reference from the
boards of these two slots.
Slots 15-16 cannot provide external electrical port. And
2 GIPI the base station cannot extract clock reference from the
boards of these two slots.
For 1+1 backup: Slots 1/2, 3/4, 5/6, 7/8, 11/12, 13/14
can only use master/slave board configuration.
3 IMAB/EIPI
For other backup mode other than 1+1 backup: Only 1,
3, 5, 7, 11, 13 or 2, 4, 6, 8, 12, 14 can be configured.
Do not plug the RUB2 board in slot 17.
4 RUB/RUB2 Considering heat dissipation, do not plug the
RUB/RUB2 board in slots 1 & 17.
The number of E1 trunks at slot 17 is decreased from
5 SDTB
63 to 32.
The number of E1 trunks at slot 17 is decreased from
6 SDTB2
126 to 64.
SDTA/SDTA2 can only use Slots 15-16: clock reference
7 SDTA/SDTA2
cannot be extracted from these two slots.
The CMP module and the DMP module should not be
configured on the same RCB board.
RCB (CMP/CMP) must be configured as the “master-
8 RCB
slave” mode.
RCB (DMP/DMP) must be configured as the “NONE”
mode.
1.1.2 IP Planning
Table 1-2 IP Planning Related Restrictions
Recommended
No. Restrictions
Configuration/Description
At most 8 next-hop routes can be
1 configured to the same destination Static route
subnetwork.
A CMP (IU) supports 32 IU-interface
2
SCTPs at most.
The SCTP Local Port and SCTP Local IP
3 Applies only to ZTE RNC.
must be unique within the office.
The IP segments of each path within each
office on the IU interface shall not include
4 the IPs of each other. The IP segment of
the IUB interface must be configured with
the 32-bit mask.
1.1.3 Others
Table 1-3 Other Constraints
Recommended
No. Restrictions
Because multi-path
If multi-path is used, the NodeB ID cannot rectification may be
1
be set as “0” and “65535.” performed later, do not set
NodeB ID as “0” or “65535.”
If multi-PLMN policy is not
used in the field, the
If the IPAPPTYPE field in Service IP
MCC/MNC of all service IPs
2 contains the IUR interface, the MCC/MNC
must be set as
must be set as “65535.”
“65535/65535.”(i.e., all
PLMNs can be accessed)
The IUCS interface, IUPS
interface, and IUB interface
Data configuration must be complete. should be configured with at
3 Otherwise, board power-up failure and least one office, and at least
repeated board restart fault will occur. one cell should be
configured with wireless
data.
All SPCs must be configured
In the configuration of MGW for the IUCS to the maximum value (i.e.,
4 office using IP bearer, SPC must be filled 7.255.7 for format 3-8-3, and
in the quick configuration template. 255.255.255 for format 8-8-
8).
Recommended
No. Restrictions
NRI BIT NUM is an integration parameter
of the CN office for IU-flex transmission. If
5 IU-flex is used, this parameter should be
set to the same value for all CS offices.
(The same for PS offices)
The RCP uplink scrambling codes of
It is recommended that the
different RNCs should be different. The
uplink scrambling codes be
6 RCP uplink scrambling codes of adjacent
differentiated by the relation
RNCs using the IUR interface must be
of RNC ID.
different.
7 Subnet ID must be consistent with RNC ID.
8 Restrictions on CMP module No. allocation Refer to Chapter 0.
Each CMP supports 500 cells. Each DMP
9
processes 250k’s BHCA.
In the PVC Config sheet,
each path group ID can only
For ATM bearer, each path group ID can be configured with one ATM
10
only be configured with one ATM PORT. PORT. Do not configure
more than one ATM PORT
to the same path group ID.
When ATM transmission is used for IUR
Configure one end as “local”
office, the owner of AAL2 channel at local
11 and the other end as
end should be configured differently with
“adjacent.”
that at the peer end.
42 DMP modules can be configured at
12
most, i.e., 21 boards.

2 Introduction to Quick Data Configuration

There are three MO quick data configuration templates:
1. V3_Template_Equipment
2. V3_Template_TransportNetwork
3. UMTS Radio Quick Configuration Template

They can be loaded into OMM one by one.
Figure 2-1 Template Importing Flow
2.1 Overview of Plan Templates
2.1.1 Template Info Sheet
The first sheet of all quick data configuration templates is the “Template Info” sheet, which
provides the basic template information for OMM. By this sheet, OMM can judge whether
the template matches with OMM and acquire the categorization information of templates.
Therefore, the content of this sheet must be kept complete no matter which of other sheets
are selected.
Figure 2-2 Template Info Sheet
2.1.2 Index Sheet
The second sheet of all templates is the “Index” sheet. It provides the overall information
about the content of the template and the categorization (UMTS/GSM) of the sheets for the
user. It also provides hyperlinks, and the user can click the corresponding link to go to the
target sheet.
Figure 2-3 Index Sheet
2.1.3 Attributes of Parameters
The fifth line of the template is parameter attributes, as shown in Figure 2-4.

Figure 2-4 Attributes of Parameters
The attributes of the parameters fall into the following categories according to different
applications. Please refer to Table 2-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

The exported template is
Read only.
R Read No need to fill the
parameter in the template
created.
R-W Read and Write Read, write, or null
The exported template is
Read only.
R-I Read and Initial This parameter must be
filled in the template
created.
The exported template
has the Read-Write
attribute.
R-W-I Read, Write and Initial
This parameter must be
filled in the template
created.
This parameter must be
Primary Key Primary Key filled in the template
created.
Note:
Do not modify the first line and the fifth line of the template. Otherwise, template loading error will occur.
2.1.4 Equipment Template
2.1.4.1 Introduction to Equipment Template
Figure 2-5 shows the sheets included in the “Equipment” template, which can fulfill rack,
shelf, board, global information, and basic networking related data configuration.
All sheets in this template are related to UMTS network. Field engineers shall select the
sheets according to the actual application scenario.
Figure 2-5 V3_Template_Equipment
2.1.4.2 An Example of Filled Equipment Template
The template is corresponding to OMMR V12.13.15.

V3_Template_Equipment
2.1.5 Transport Network Template
2.1.5.1 Introduction to 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 V3_Template_TransportNetwork
1. Sheets for IU/IUR and IUB

Select and fill in different sheets for the IU/IUR interface and IUB interface according to the
actual application scenario.
Table 2-2 Sheets to Be Configured for IU/IUR and IUB
No. IU/IUR IUB

1 Local Office IUB Office
2 Adjacent Office (CN) SCTP Config (IUB)
3 SCTP Config (CN) IP Bearer (IUB)
4 M3uaAS Config IPOE Bearer (IUB)
5 M3uaRoute UMTS ATM Bearer (IUB Auto)
6 M3uaRouteSet ATM Bearer (IUB)
7 IP Path(CN)
8 PVC Config (IU-IUR)
9 Mtp3Route
10 Mtp3RouteSet
11 IP Path Group IP Path Group
12 Static Route Static Route
2. Sheets for different bearers on the IUB interface
The application of the IUB interface involves multiple bearers. Different sheets should be
filled in for different 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 Bearers
No IPoE1+IPoF ATMoSTM
IPoE1 IPoFE ATMoE1 ATM+IP
. E -1
1 IUB Office IUB Office IUB Office IUB Office IUB Office IUB Office
UMTS
SCTP SCTP SCTP ATM
SCTP ATM
2 Config(IUB Config Config(IUB Bearer(IU
Config (IUB) Bearer(IU
) (IUB) ) B)
B Auto)
IPOE IP IP
IP
3 Bearer(IU Bearer(IU Bearer(IU
Bearer(IUB)
B) B) B)
IPOE Static Static Static
4
Bearer(IUB) Route Route Route
IP Path IP Path
5 Static Route
Group Group
UMTS
IP Path ATM
6
Group 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 Bearers
No. IUCS/R(ATM) IUCS/PS/R(IP) IUPS(IPOA)

1 Local Office Local Office Local Office
Adjacent Office
2 Adjacent Office (CN) Adjacent Office (CN)
(CN)
3 SCTP Config (CN)
4 M3uaAS Config
5 M3uaRoute
6 M3uaRouteSet
7 IP Path(CN) IP Path(CN)
PVC Config (IU-
8 PVC Config (IU-IUR)
IUR)
9 Mtp3Route Mtp3Route
10 Mtp3RouteSet Mtp3RouteSet
11 IP Path Group IP Path Group
12 Static Route
2.1.5.2 An Example of Filled Equipment Template
V3_Template_TransportNetwork
2.1.6 UMTS Radio Template
2.1.6.1 Introduction to UMTS Radio Template
Figure 2-7 shows the sheets included in the UMTS Radio Quick Configuration Template.
The radio parameters on the Iub interface are configured with this template.
All sheets in this template are for UMTS data configuration. Six of the sheets are required.
Other sheets should be filled in according to the actual application scenario.
Figure 2-7 UMTS Radio Quick Configuration Template
The parameters in red in the first line must be filled in. This is similar to the yellow areas in
the V3 non-MO templates.
Figure 2-8 UMTS Radio Template
2.1.6.2 An Example of Filled UMTS Radio Template
UMTS Radio Quick Configuration
2.2 Common Functions
2.2.1 Loading Templates
Step 1: Choose View > Configuration Management.

Figure 2-9 Configuration Management
Step 2: Right-click and choose Create Subnetwork. Set Subnetwork ID and Set of

MCC according to the actual situation.
Figure 2-10 Create Subnetwork
Step 3: Right-click SubNetwork, choose Create Management Element, and

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

actual situation, load the template needed sheet by sheet, and clickExecute.
Figure 2-19 Template Exporting Interface
2.2.3 Check on Imported Quick Configuration Template
The competed quick data configuration template can only be synchronized to RNC when it
meets the related restrictions on OMM and passes the validity check.
1. Template importing: In this process, OMM will check the validity, effectiveness,
and completeness of the format in the quick configuration template.
Figure 2-20 Template Importing Check
2. Global validity check: It is required this step be performed before data

synchronization. It aims to check whether the OMM data is valid and meets the
restrictions completely.
This step can also be performed manually, as shown in Figure 2-21.
Figure 2-21 Global Validity Check
3. License Center Check

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

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

Modify Area.
Figure 2-24 Data Comparison
Select the target NE, and click run. After the Select Compare Type window pops up on
OMM, choose a comparison mode and click OK.
Figure 2-25 Select Compare Type
Observe the value of Result. If it is “identical,” it means that the data in the snapshot area
is the same as that in the modify area.
Figure 2-26 Comparison Result
Note:
There are two modes for comparing data:
Fast Compare: It is used to compare only the “last modify time.” The advantage of this mode is its speed.
Full-text Compare: It is used to compare all parameters. The advantage is its preciseness.

3 Equipment Template and Transport

Network Template Configuration
Specifications
This Guide deals mainly with the common sheets 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.1 Equipment Template
3.1.1 Basic Info
Table 3-1 Basic Info
Re
Parameter Descrip
Parameter Value ma
Name tion
rks
Pri
Managed mar
long:[1..4095]
Element ID y
Key
0:GSM
1:UMT
Mode Type long:[0,1,32768] S R-I
32768:
TD
1 is
Bureau R-
long:[1..253] recomm
Number W-I
ended
eg:xxx.x
xx.xxx.x
xx
UMTS:I
t should
Omp's be as R-
ipv4
omc port ip same W-I
as the
IP
address
of
bond2:4
Omp's
Omc Port R-
long:[0..32]
Mask W-I
Length
MacAdd
r:00-19-
C6-3E-
30-10 to
00-19-
C6-4E-
30-0F
eg:
xx-xx-
xx-xx-
Omp's
xx-xx R-
omc MAC string
Should W-I
address
be
same
with the
label of
ROMB
board,
can't be
blank in
add
mode.
eg:xxx.x
xx.xxx.x
xx
This IP
address
is
usually
configur
IP address ed to
R-
of SNTP ipv4 the IP
W-I
server address
of the
OMM
server,
which is
set as
the
SNTP
server.
OMCB
eg:xxx.x
Agent IPv4 R-
ipv4 xx.xxx.x
Address to W-I
xx
NODEB
OMCB
eg:xxx.x
Server R-
ipv4 xx.xxx.x
IPv4 W-I
xx
Address
OMCB
Server R-
long:[0..32]
IPv4 Mask W-I
Length
eg:xxx.x
xx.xxx.x
xx
It can
be used
when it
support
s
OMCB multipat
R-
Inner Ip ipv4 h
W-I
Address protecti
on.
Other,it
is filled
in
default
value
0.0.0.0
.
Time Zone long[-720,-660,-600,-540,-480,-420,- eg: R-
360,-300,-270,-240,-210,-180,-120,- - W-I
60,0,60,120,180,210,240,270,300,330,3 720:GM
45,360,390,420,480,540,570,600,660,7 T-12
20,780] -
660:GM
T-11
-
600:GM
T-10
-
540:GM
T-09
-
480:GM
T-08
-
420:GM
T-07
-
360:GM
T-06
-
300:GM
T-05
-
270:GM
T-04.5
-
240:GM
T-04
-
210:GM
T-03.5
-
180:GM
T-03
-
120:GM
T-02
-
60:GMT
-01
0:GMT
60:GM
T+01
120:G
MT+02
180:G
MT+03
210:G
MT+03.
5
240:G
MT+04
270:G
MT+04.
5
300:G
MT+05
330:G
MT+05.
5
345:G
MT+05.
75
360:G
MT+06
390:G
MT+06.
5
420:G
MT+07
480:G
MT+08
540:G
MT+09
570:G
MT+09.
5
600:G
MT+10
660:G
MT+11
720:G
MT+12
780:G
MT+13
Daylight 0:Disabl
Saving e R-
long:[0..1]
Time using 1:Enabl W-I
flag e
Start time
of the Mon/Da
Daylight y/Hour/
R-
Saving string Min
W
Time(Mon/ eg:00/0
Day/Hour/ 0/00/00
Min)
End time
of the Mon/Da
Daylight y/Hour/
R-
Saving string Min
W
Time(Mon/ eg:00/0
Day/Hour/ 0/00/00
Min)
Step of Unit:5
Daylight Min R-
long:[-127..-2,0,2..127]
Saving Default W
Time Value:0
3.1.2 Plmn Config
Table 3-2 Plmn Config
Paramete Remark
Parameter Value Description
r Name s
It contains no more
User label string R-W
than 80 characters.
Managed
Primary
Element long:[1..4095]
Key
ID
PLMN
long: Primary
Group
[0..4294967295] Key
Object ID
Mobile
Country long:[0..999] R-W-I
Code
When
Mobile
MNCBCDCODELE
Network long:[0..999] R-W-I
N is 2, range of
Code
MNC is [0..99].
MNC BCD
Code long:[2..3] R-W-I
Length
Default
0:false
PLMN long:[0..1] R-W-I
1:true
Indicator
Is Local
0:false
Office's long:[0..1] R-I
1:true
PLMN
3.1.3 Shelf Config
Table 3-3 Shelf Config
Parameter Parameter
Description Remarks
Name Value
Managed Primary
long:[1..4095]
Element ID Key
Primary
Rack No. long:[1..5]
Key
Primary
Shelf No. long:[1..4]
Key
1:BCTC
3:BPSN
Shelf type long:[1,3,4,7,8] 4:BUSN R-I
7:BPSNE
8:BGSN
3.1.4 Board Config
Table 3-4 Board Config
Para Parame Re
meter ter Description mar
Name Value ks
Mana
ged Pri
long:
Eleme mar
[1..4095
nt y
]
Object Key
ID
Pri
rack/s
mar
helf/sl string eg:1/2/11
y
ot
Key
Physic
This Parameter is associated with the
al
string PHYBRDTYPE of the Board Warehouse, R-I
Board
eg:ROMB2
Type
Logica
This Parameter is associated with the
l
string LOGICBRDTYPE of the Board R-I
Board
Warehouse, eg:OMP
Type
Modul string when the PhyBrdType is the following: R
e ROMB_X86
Seque ROMB
nce ROMB2
RCB_X86
RCB
RCB2
The MODULESEQ is valid,
the OMP Module No is 1;
the RPU Module No is 2;
The TD CCMP module value range is
[3..18]
The UMTS CCMP module value range is
[3..31]
The GSM CCMP module value range is
[3..12]
The DCMP module value range is
[32..127]
Each Board consists of two
Modules,Modules separated by ;
(semicolons)
eg:1;2
when the MODULESEQ is invalid,this

filed filled by 0;0.
0:No Backup
Backu
long: 1:1+1 Backup
p R-I
[0,1,2,5] 5:1TO1 Backup
Mode
2:Load sharing
Chann long: 0:Invalid mode R
el [0,1,2,3, 1:FE In,ATM/POS/MP/CSTM-
Config 4,5] 1/E1/T1/E3/T3 Out
uratio 2:FE In,FE Out
n 3:GE In,GE Out
4:FE In,GE Out
5:GE In,ATM/POS/MP/CSTM-
1/E1/T1/E3/T3 Out
When PHYBRDTYPE is GIPI,

CHANNELCONFIG is 3(shelf type is
BUSN and slot is 1 or 2, or shelf type is
BGSN) or 2 or 4. default value is 2(shelf
type is BUSN) or 3(shelf type is BGSN).
When PHYBRDTYPE is GIPI3 or GIPI4,
BGSN). default value is 3.
When PHYBRDTYPE is DTA or SDTA or
SDTA2 or SDTA3, CHANNELCONFIG is
5. default value is 5.
When PHYBRDTYPE is APBE2_85XX or
ET3A or APBI, CHANNELCONFIG is
5(shelf type is BGSN) or 1(shelf type is
BUSN). default value is 5(shelf type is
BGSN) or 1(shelf type is BUSN).
When PHYBRDTYPE is DTI or SDTI or
ET3I or POSI or EIPI or EIPI4,
BGSN) or 1. default value is 5(shelf type
is BGSN) or 1(shelf type is BUSN).
When PHYBRDTYPE is BIPI,
BUSN). default value is 2.
When PHYBRDTYPE is BIPI4,
CHANNELCONFIG is 2. default value is
2.
When PHYBRDTYPE is other value,
CHANNELCONFIG is 0. default value is
0.
Port long: 0:NULL R
Type [0..11] 1:SDH-63E1
2:SDH-63T1
3:SDH-84T1
4:POS
5:ATM
6:E1
7:T1
8:GE
9:FE
10:E3
11:T3
When PHYBRDTYPE is SDTA or

SDTA3, EXTPORTTYPE is 1 or
When PHYBRDTYPE is SDTA2 or SDTB
or SDTB2 or SDTI or ESDT or ESDT2 or
SDTB3 or SDTI2 or ESDT3,
EXTPORTTYPE is 1 or 2 or 3. default
value is 1.
When PHYBRDTYPE is POSI,
EXTPORTTYPE is 4. default value is 4.
When PHYBRDTYPE is APBE_755 or
APBE_85XX or APBE2_85XX,
When PHYBRDTYPE is APBI,
EXTPORTTYPE is 5 or 0. When Backup
Mode is No Backup or 1TO1 Backup,
default value is 5. When Backup Mode is
1+1 Backup, default value is 0.
When PHYBRDTYPE is DTB or DTA or
DTI or SPB or SPB2 or SPB2_85XX or
SPB or SPB2 or SPB2_85XX or SPB or
SPB2 or SPB2_85XX or DTEC or DTB3
or SPB3 or DTEC3, EXTPORTTYPE is 6
or 7. default value is 6.
When PHYBRDTYPE is GIPI or GIPI3 or
GIPI4, EXTPORTTYPE is 8. default
value is 8.
When PHYBRDTYPE is GIPI or BIPI or
BIPI4, EXTPORTTYPE is 9. default value
is 9.
When PHYBRDTYPE is ET3A or ET3I,
EXTPORTTYPE is 10. default value is
10.
0:E1 supported
1:T1 supported, T1 is not full configured
2:T1 supported, T1 is full configured
3:Reserved
When PHYBRDTYPE is IMAB_755 or

IMAB_85XX or DTA or SDTA or DTB or
DTI or EIPI or SPB or SPB2 or
SPB2_85XX or DTEC or EIPI4 or SDTA3
or DTB3 or SPB3 or DTEC3, E1T1CFG is
E1/T1 long: 0 or 1. default value is 0.
R
Config [0..3] When PHYBRDTYPE is APBI, E1T1CFG
is 0 or 1 or 3. When Backup Mode is No
Backup or 1+1 Backup, default value is 0.
When Backup Mode is 1TO1 Backup,
default value is 3.
When PHYBRDTYPE is SDTA2 or SDTB
or SDTB2 or SDTI or ESDT or ESDT2 or
SDTB3 or SDTI2, E1T1CFG is 0 or 1 or
E1T1CFG is 3. default value is 3.
Sdh long: 0:NULL R
speed [0,1,2,4, 1:SDH AU-4
mode 5,6] 2:SDH AU-3
4:SONET STS-3C
5:SDH Vc4-4c
6:SONET Sts-12c
When PHYBRDTYPE is SDTA or SDTA2

or SDTB or SDTB2 or SDTI or ESDT or
ESDT2 or SDTA3 or SDTB3 or SDTI2 or
ESDT3, SDHPORTMUXMODE is 1 or 2.
default value is 1.
When PHYBRDTYPE is APBE_755 or
APBE_85XX or APBE2_85XX,
SDHPORTMUXMODE is 1 or 4. default
value is 1.
When PHYBRDTYPE is APBI,
SDHPORTMUXMODE is 1 or 4 or 0.
When Backup Mode is No Backup or
1TO1 Backup, default value is 1. When
Backup Mode is 1+1 Backup, default
value is 0.
When PHYBRDTYPE is
POSI,SDHPORTMUXMODE is 1 or 4 or 5
or 6. default value is 1.
SDHPORTMUXMODE is 0. default value
is 0.
0:ITUT-G.707 type
1:Tributary type
When PHYBRDTYPE is
PCM SDTA,SDTA2,SDTB,SDTB2,SDTI,ESDT,
long:
Map ESDT2,SDTA3,SDTI2,SDTB3,ESDT3, R
[0,1]
Type PCMMAPTYPE is 0 or 1. default value is
0.
PCMMAPTYPE is 0. default value is 0.
0:Multi-frame
E1
long: 1:Dual-frame
Frame R
[0,1,4] 4:Forcible multi-frame
Type
This Parameter is valid for GSM.
0:75 OHM
E1
long: 1:120/100 OHM
Imped R
[0,1,2] 2:Auto
ance
This Parameter is valid for GSM.
0:CABLE PORT
1:OPTICAL PORT
Cable long:
2:Adaptive R
type [0,1,2,3]
3:Invalid
This Parameter is valid for Ethernet Port.
3.1.5 Board Warehouse
It is not necessary to fill in this sheet.

3.1.6 Unit Connection
Table 3-5 Unit Connection
Parameter Parameter
Description Remarks
Name Value
It contains no more
User Label string R-W
than 80 characters.
Managed
Element long:[1..4095] Primary Key
Object ID
UIMU, GUIM, GLI,
Used Unit string GSC board, Primary Key
eg:rack/shelf/slot
1 or 2 or 3 or 4 is
selected when the
GLI is connected
with the UIMU,1 or 3
is selected when the
GLI is connected
with the GUIM,
255 is selected
when the UIMs are
Port
interconnected, 1 or
Number of long:[1..22,255] Primary Key
3 or 5 or 7 or 9 or 11
GLI
or 13 or 15 or 17 or
19 or 21 is selected
when the GSC is
connected with the
UIMU,1 or 5 or 9 or
13 or 17 is selected
when the GSC is
connected with the
GUIM.
1:GE type(when the
GLI or GSC is
connected with the
UIMU)
3:2*GE type(when
the GLI or GSC is
GLI
connected with the
Interface long:[1,3,4,255] R-I
GUIM)
type
4:10GE type(when
the GUIMs are
interconnected)
255:Invalid(when the
GUIMs or UIMUs are
interconnected)
2:UIM connected
with UIM
Unit
3:GLI connected
connection long:[2..3,10] R-I
with UIM
type
10:GSC connected
with UIM
connected UIMU, GUIM board,
string R-I
Unit eg:rack/shelf/slot
3.1.7 Global Info
Table 3-6 Global Info
Parameter Parameter
Description Remarks
Name Value
Managed
Object ID
IP Segment
RUIB,POSI,ET3P,
ReAssembl
string EUIP board, R-W
e Default
eg:rack/shelf/slot
Unit
The First IP
RUIB,POSI,ET3P,
Segment
ReAssembl
eg:rack/shelf/slot
e Unit
The Second
RUIB,POSI,ET3P,
IP Segment
ReAssembl
eg:rack/shelf/slot
e Unit
The Third IP
RUIB,POSI,ET3P,
Segment
ReAssembl
eg:rack/shelf/slot
e Unit
The Fourth
RUIB,POSI,ET3P,
IP Segment
ReAssembl
eg:rack/shelf/slot
e Unit
The Fifth IP
RUIB,POSI,ET3P,
Segment
ReAssembl
eg:rack/shelf/slot
e Unit
The Sixth IP
RUIB,POSI,ET3P,
Segment
ReAssembl
eg:rack/shelf/slot
e Unit
The
Seventh IP RUIB,POSI,ET3P,
Segment string EUIP board, R-W
ReAssembl eg:rack/shelf/slot
e Unit
3.1.8 Interface IP
Table 3-7 Interface IP
Paramete Parameter Remark

Description
r Name Value s
User It contains no more than 80
string R-W
Label characters.
Managed
long: Primary
Element
[1..4095] Key
Object ID
RUIB, APBE, IMAB board,
eg:rack/shelf/slot
Interface When PORTTPE is Loopback Primary
string
Board port or Virtual port, Key
BOARDINFO is filled with
0/0/0.
TD:[1..18]
UMTS:[1..31]
GSM:[1..12]
When PORTTPE is Interface,
Module NO 1 should be used.
Module When PORTTPE is Loopback Primary
long:[1..31]
No. port, Module NO 2 should be Key
used.
When PORTTPE is Virtual
port, except to Module NO 1
and Module NO 2, other
modules should be used.
0:Interface
Primary
Port Type long:[0,1,2] 1:Loopback port
Key
2:Virtual port
Interface(real port):[1..4]
Interface
Interface(ATM port):[1..240] Primary
Local Port long:[0..240]
Loopback port:[1..128] Key
No.
Virtual port:0
0 is invalid
VLAN long: Primary
It is valid when it is sub
Sequence [0..1023] Key
interface.
0 is invalid.
long:
Vlan ID It is valid when it is sub R-W-I
[0..4095]
interface.
VPN ID of
long:[0..254] 0 is invalid R-W-I
sub port
eg:xx-xx-xx-xx-xx-xx
Value range: 00-19-C6-3E-
MAC
string 30-10~00-19-C6-4E-30-0F, R-W
address
00-D0-D0-A0-00-00~00-D0-
D0-A0-9F-FF
IP ipv4 eg: R-W-I
address of xxx.xxx.xxx.xxx;xxx.xxx.xxx.x
interface xx
Mask
Length of
long:[0..32] eg:24;24 R-W-I
Interface
IP
3.1.9 Service IP
Table 3-8 Service IP
Parameter Parameter Remark

Description
Name Value s
Managed
long: Primary
Element
[1..4095] Key
Object ID
Service IP eg: Primary
ipv4
address xxx.xxx.xxx.xxx Key
Used VRF
Attributes
Configuratio
n Object
Bit0=1:A Interface of GSM
Network
Bit1=1:Abis PS Interface of
Application
GSM Network
Type of IP string R-W
Bit2=1:Abis CS Interface of
address(2G)
GSM Network
Bit3=1:Gb Interface of
GSM Network
Bit0=1:Iub Interface of 3G
Network
Bit1=1: Iur Interface of 3G
Application
Network
Type of IP string R-W
Bit2=1: IuCS Interface of
address(3G)
3GNetwork
Bit3=1: IuPS Interface of
3G Network
eg:
MCC1:MNC1;MCC2:MNC
PLMN info of 3
string R-W-I
Service IP or 65535:65535,
65535:65535 denotes
supporting all PLMN
3.1.10 User Plane Service
Table 3-9 User Plane Service
Parame
Paramet Rem
ter Description
er Name arks
Value
Managed long: Prim
Element [1..4095 ary
Object ID ] Key
Data Prim
Used Unit string Format:rack/shelf/slot ary
Key
Used Prim
Data Format:
Service string ary
xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx;xxx.xxx
IP Key
.xxx.xxx;xxx.xxx.xxx.xxx
Service
IP for
Data Format:
Preconfig
string xxx.xxx.xxx.xxx;xxx.xxx.xxx.xxx;xxx.xxx R
uration
.xxx.xxx;xxx.xxx.xxx.xxx
Iub
Interface
3.1.11 Channel Port
Configure this sheet according to the specifications of the quick configuration template.
3.1.12 Member Port
3.1.13 Super Vlan
3.1.14 Super Vlan Member
3.1.15 DHCP Server
3.1.16 DHCP Client
3.1.17 DHCP Relay
3.1.18 VRF Base Info
3.1.19 VRF Route Target
3.1.20 LAPD Config
3.2 TransportNetwork Template
3.2.1 Local Office
Table 3-10 Local Office
Paramete Remark
r Name s
Managed
Primary
Key
Object ID
Net type
Primary
of local long:[1..255]
Key
office
flag field
of network 1:Enable
long:[1,2] R-W-I
appearan 2:Disable
ce
Default value is 0 if this
parameter cann't be
Network
long: configured.
appearan R-W
[0..4294967295] It is valid when
ce
NETAPPEARANCEFLAG
=1.
14-bit
signalling
point code
long:[0..16383] R-W-I
of local
office on
the net
24-bit
signalling
point code
long:[0..16777215] R-W-I
of local
office on
the net
Network
Resource
Identifier It is valid just for UMTS,
long:[0..10] R-W
Bit Num in and the default value is 0.
CS
Domain
Network
Resource
Identifier It is valid just for UMTS,
long:[0..10] R-W
Bit Num in and the default value is 0.
PS
Domain
ATM
20 Bytes, decimal.
address
string GSM doesn't need to R-W
of local
config.
office
3.2.2 Static Route
Table 3-11 Static Route
Parameter Parameter
Description Remarks
Name Value
User label R-W
Managed
Object ID
TD:[1..5120]
Route
long:[1..5120] UMTS:[1..5120] Primary Key
number
GSM:[1..4096]
eg:
Route prefix ipv4 R-W-I
xxx.xxx.xxx.xxx
Subnet mask long:[0..32] R-W-I
Route next eg:
ipv4 R-W-I
hop address xxx.xxx.xxx.xxx
Used VRF
Attributes
Configuration
Object
Route
long:[1..254] R-W-I
distance
0:close BFD/IPD
detection
Route 1:open BFD
long:[0..2] R-W-I
BFD/IPD flag detection
2:open IPD
detection
3.2.3 IP Path Group
Table 3-12 IP Path Group
Paramete Remark
r Name s
Managed
Primary
Key
Object ID
Path Primary
long:[0..2047]
Group Id Key
Father 65535 is invalid,other
Path long:[0..65535] value must be in R-I
Group [0..2047]
TD:[3..18]
UMTS:[3..31]
Used GSM:[3..12]
long:[3..31] R-W-I
Module Support to modify the
module No. of path
group for Iu interface.
Path 2:ETHERNET_NOVLAN
Group long:[2,5] 5:ETHERNET_VLANTA R-W-I
Bear Type G
PLMN
sequence<long,4
Group eg:1;2 R-W-I
>
Object ID
Ratio of
occupied
0 to 1000
private
sequence<long,4 If more than one
bandwidth R-W-I
> MCC/MNC, separate
of Path
each value by ';'
Group by
operator
Forward
band
width of long:[0..4294967] kbps R-W-I
Path
Group
Backward
band
width of long:[0..4294967] kbps R-W-I
Path
Group
3.2.4 IUB Office
Table 3-13 IUB Office
Parameter Remark
Name s
It contains no more than
80 characters.
Managed
Primary
Key
Object ID
Adjacent
Net Primary
long:[1..2047]
Element Key
Identifier
Net UMTS:[1..65534]
long:[0..65535] R-I
Element ID TD:[0..65535]
PLMN sequence<long,4 PLMN ID: R-W-I
Group > [0..4294967295],eg:1;2
Object ID
Module TD:[3..18]
long:[3..31] R-W-I
Sequence UMTS:[3..31]
Config for
0: ATM
Bear Type
long:[0,1,2] 1: IP R-I
of Service
2: ATM+IP
in IUB
Config for
0: ATM
Bear Type
long:[0,1,2] 1: IP R-I
of NBAP in
2: ATM+IP
IUB
Config for
Bear Type 0: ATM
of Commo long:[0,1,2] 1: IP R-I
n Channel 2: ATM+IP
in IUB
Subsystem The recommended value
long:[1..20,255] R-W-I
of RUP is 255.
ATM
address of
string 20 Bytes,decimal R-W
adjacent
office
whether
0:off
support long:[0..1] R-W
1:on
Twin-IMA
0: Protection OFF
Switch of
1: Support multipath
IUB
long:[0..2] protection R-W
multipath
2: Support ATM+IP
protection
protection
1: QoS(according to
ARP/THP/TC)
Transport
2: QoS(according to
Qos Profile long:[1..2] R-W
service type)
Type
The default value is 2 if
this parameter is empty.
Profile ID
long:[1..255]
of
1:ATM+IP Transport
Transport
2:Only IP Transport
Bearer
sequence<long,4 System will configure it
Type R-W
> according office's bear
Profile
type when it is empty.
Related to
This parameter is valid if
Basic
UPQOSMAPTYPE= 1.
Priority
Transport sequence<long,4 long:[1..48] R-W
Qos Profile > 1:One or Two IP Paths,
parameter 2:Three IP Paths,
Index 3:One ATM Path and
Two IP Paths,
4:ATM Paths,
5:One IPOE Path and
One IP Path,
6:One ATM and One IP
Path.
This parameter is valid if
UPQOSMAPTYPE=2.
Single Path Scene:
1)ATM, default valued is
4;
2)IPoFE, default valued
is 1;
3)IPoE1, default valued
is 1.
Multi Path Scene:
1)ATM Multi Path,
default valued is 4;
2)IP Multi Path, default
valued is 5;
3)ATM+IP, default
valued is 6;
4)IPoE1+IPoFE, default
valued is 5.
3.2.5 SCTP Config(IUB)
Table 3-14 SCTP Config(IUB)
Parameter Parameter
Description Remarks
Name Value
It contains no more
User label string R
than 80 characters.
Managed
Object ID
Adjacent Net
Identifier
Association
long:[1..3000] Primary Key
ID
Local port long:[1..65535] R-W-I
It can be filled in
Local Ip ipv4 R-W-I
one IP address
Remote port long:[1..65535] R-W-I
It can be filled in
Remote Ip ipv4 R-W-I
one IP address
default value:500
RTO.Max long:[10..3000] R-W
unit 10millisecond
default value:50
RTO.Min long:[10..1000] R-W
unit 10millisecond
default value:100
RTO.Initial long:[10..3000] R-W
unit 10millisecond
default value:500
HB.interval long:[10..6000] R-W
unit 10millisecond
Delay ack default value:20
long:[0..20] R-W
interval unit 10millisecond
1:Server
Application 2:Client
type of long:[1..2] If it is not filled, R-W
association default value is
1:Server.
3.2.6 IP Bearer(IUB)
Table 3-15 IP Bearer(IUB)
Parameter
Parameter Value Description Remarks
Name
It contains no
User label string more than 80 R
characters.
Managed
Primary
Key
Object ID
Adjacent
Primary
Net Element long:[1..2047]
Key
Identifier
Primary
TrPath ID long:[0..7]
Key
Path Group
long:[0..2047] R-I
ID
PLMN
Group long:[0..4294967295] R-I
Object ID
Destination
ipv4 R-W-I
IP Address
net mask
length for
long:[0..32] R-W-I
Destination
IP
Tx
long:[0..4294967295] unit:kbps R-W-I
bandwidth
Rx
bandwidth
IP Domain long:[0,21..23] 0:Invalid, R-W
No. 21:IP Domain
No.1,
22:IP Domain
No.2,
23:IP Domain
No.3
It should be
configured to
effective
value(21,22,23)
when IUB office
is multipath
protection.
It should be
configured when
OMCB Path
long:[1..3] IUB office is R-W
priority
multipath
protection.
3.2.7 IPOE Bearer(IUB)
Table 3-16 IPOE Bearer(IUB)
Para
mete Re
Paramet
r Description mar
er Value
Nam ks
e
User
string It contains no more than 80 characters. R
label
Man
aged
Prim
Elem long:
ary
ent [1..4095]
Key
Obje
ct ID
Adja
cent
Net Prim
long:
Elem ary
[1..2047]
ent Key
Identi
fier
Boar
d
R-
Info string EUIP board rack/shelf/slot
W-I
of
IPOE
MP long: 0:ppp R
Port [0,191..2 [191..254]:Mp
No. 54] When it is Multi-PPP link,LOCALPORT is
usually not filled, can be auto generated by
system.
format
unitindex;e1index@unitindex;e1index
unitindex:[1..17]
e1index:DTB/DTI/DTB3[1..32],SDTB
[1..63],SDTI/SDTB2/SDTB3[1..63,85..147],
SDTI2[1..63,64..126,127..189,190..246]
Each E1 consists of two parts,one is the
E1/T R-
string unitindex, another e1index
1 List W-I
The unitindex is a unit that E1 belongs
e1index is the number of E1 within the unit
Unit number and E1 numbers separated
by ;(semicolons)
When to configure More than one E1,
separated by @
eg, 5;1@5;1@6;1@6;2
E1/T
1 TS string Sperated by ";" and "-" R-W
List
Path
long:
Grou R-I
[0..2047]
p ID
sequenc Prim
TrPat TrPath ID :[0..7]
e<long,4 ary
h ID eg:0;1
> Key
Desti
natio
R-
n IP ipv4
W-I
addr
ess
net
mask
lengt
long: R-
h for
[0..32] W-I
Desti
natio
n IP
0:Invalid,
21:IP Domain No.1,
IP
22:IP Domain No.2,
Dom long:
23:IP Domain No.3 R-W
ain [0,21..23]
It should be configured to effective
No.
value(21,22,23) when IUB office is
multipath protection.
OMC
B
long: It should be configured when IUB office is
Path R-W
[1..3] multipath protection.
priori
ty
3.2.8 UMTS ATM Bearer(IUB Auto)
Table 3-17 UMTS ATM Bearer(IUB Auto)
Para
mete Para Re
r meter Description mar
Nam Value ks
e
User
label
Man
aged Pri
long:
Elem mar
[1..40
ent y
95]
Obje Key
ct ID
Adja
cent
Pri
Net long:
mar
Elem [1..20
y
ent 47]
Key
Ident
ifier
Desti
natio
R-
n IP ipv4
W-I
addr
ess
Mas
k
lengt
h of
long: R-
Desti
[0..32] W-I
natio
n IP
addr
ess
OMC
B
long: It should be configured when IUB office is R-
Path
[1..3] multipath protection. W
priori
ty
Path long:
Grou [0..20 R-I
p Id 47]
Atm
Interf
R-
ace string APBE, IMAB board rack/shelf/slot
W-I
Boar
d
format unitindex;e1index@unitindex;e1index
unitindex:[1..17]
e1index:DTB/DTA/DTB3[1..32],SDTB
[1..63],SDTA/SDTB2/SDTA3/SDTB3[1..63,85..
147],SDTA2[1..63,64..126,127..189,190..246]
E1 unitindex, another e1index R-
string
List The unitindex is a unit that E1 belongs W-I
Unit number and E1 numbers separated by ;
(semicolons)
separated by @
eg,5;1@5;1@6;1@6;2
Iub long: 1:Normal, R-
Plan [1..2] 2:High load W-I
The
num If this parameter is empty, it will be configured
ber by the default template.
long: R-
of The number of UBR Aal2 PVC by user defined
[1..20] W
UBR cannot be less than the number of default
Aal2 template.
PVC
3.2.9 TD ATM Bearer(IUB Auto)
This sheet is related to TD. No need to fill in this template.
3.2.10 ATM Bearer(IUB)
Table 3-18 ATM Bearer(IUB)1.1 　
Paramet Remar
er Name ks
User It contains no more than
string R
label 80 characters.
Managed
Primary
Key
Object ID
Adjacent
Net
long:[1..2047] R
Element
Identifier
PVC Primary
long:[1..12600]
Indicate Key
Atm
APBE, IMAB
Interface string R-I
board, rack/shelf/slot
Board
ATM port long:[1..4] R-I
VPI on
long:[0..4095] R-W-I
high port
VCI on
long:[32..65534] R-W-I
high port
PVC 0: AAL5 signal
Service long:[0,2,4] 2: AAL2 user data R-I
Type 4: OMCB
0:CBR
1:rtVBR
2:nrtVBR
3:ABR
4:UBR
5:UBR+
CBR surpports:
atmClpNoTaggingNoScr(2
),
atmClpTaggingNoScr(3),
atmNoClpNoScr(1)
atmClpTransparentNoScr(
8),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR

surpport:
atmNoClpNoScr(1),
),
Service atmClpTaggingNoScr(3),
long:[0..5] R-W-I
Category atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt(
13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14
),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
ABR surpport:
atmClpNoTaggingMcr(7)
UBR surpports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCdvt(11),
atmNoClpTaggingNoScr(1
0).
UBR+ surpports:
atmTrafficForUbr+(15)
Traffic long:[0..15] 0: NOTRF R-W-I
1: atmNoClpNoScr
2: atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
atmClpTransparentNoScr
Type 9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
atmClpNoTaggingScrCdvt
14:
atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell Unit: Kbps.
rate for long: This Traffic Para surpports
R-W-I
CLP=0+1 [0..1821066133] all Service Category and
(PCR0+1) all Traffic Type.
Unit: Kbps.
Service Category:
Peak cell
CBR ,rtVBR and nrtVBR.
rate for long:
Traffic Type: R-W
CLP=0 [0..1821066133]
(PCR0)
),
atmClpTaggingNoScr(3).
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
atmClpTransparentNoScr
Cell delay
(8),
variation long:
atmNoClpNoScrCdvt (11), R-W
tolerance [0..4294967295]
(CDVT)
),
atmNoClpTaggingNoScr(1
0).
Sustainab long: Unit: Kbps. R-W
le cell [0..1821066133] Service Category:
rate for rtVBR and nrtVBR.
CLP=0 Traffic Type:
(SCR0) atmClpNoTaggingScr(5),
13),
).
Unit: Kbps.
Sustainab Service Category:
le cell rtVBR and nrtVBR.
long:
rate for Traffic Type: R-W
[0..1821066133]
CLP=0+1 atmClpTransparentScr(9),
(SCR0) atmNoClpScrCdvt(12),
atmNoClpScr(4).
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingScr(5),
Maximum
burst cell long:
13), R-W
number [0..4294967295]
(MBS)
),
atmNoClpScr(4).
Unit: Kbps.
Service Category:
Minimum
long: ABR and UBR+.
cell rate R-W
[0..1821066133] Traffic Type:
(MCR)
atmClpNoTaggingMcr(7),
Unit: cell.
Maximum
Service Category:
frame long:
UBR+. R-W
size [0..4294967295]
Traffic Type:
(MFS)
Path
long:[0..2047] R
Group ID
sequence<long,4 TrPath ID :[32..127]
TrPath ID R
> eg:32;33
AAL2
Path ID long:
R
intra [1..4294967295]
office
AAL2
Path 0:Local End
long:[0..1] R-W
Ownershi 1:Peer End
p
10:RT
AAL2
11: NRT1
Path
long:[10..14] 12: NRT2 R-W
Service
13: NRT3
Type
14: MIX
Applicatio long:[1..3] 1: ALCAP R
n Type of 2: NBAP(NCP)
UNI Link 3: NBAP(CCP)
Destinatio
n IP ipv4 R-W
address
Mask
length of
Destinatio long:[0..32] R-W
n IP
address
OMCB It should be configured
Path long:[1..3] when IUB office is R-W
priority multipath protection.
3.2.11 IP Bearer(ABIS)
Related to GSM network.
3.2.12 Adjacent Office(CN)
Table 3-19 Adjacent Office(CN)
Param
Rema
eter Parameter Value Description
rks
Name
It contains no
User
string more than 80 R-W
label
characters.
Manag
ed
Prima
Elemen long:[1..4095]
ry Key
t Object
ID
Adjace
nt Net
Elemen Prima
long:[1..2047]
t ry Key
Identifi
er
The
recommended
Adjace
value for
nt
UMTS/TD is the
Office long:[1..2048] R-I
same as ANEID.
Numbe
The value range
r
of OFFICEID for
GSM is [1..64].
Net sequence<long,4> Mgw Id: R-W-I
Elemen [4096..65535],
Mscserver Id:
[0..4095],
MGW+MSCSER
VER Id:[0..4095],
Sgsn Id:[0..4095],
Rnc Id[0..4095],
BSC Id:[1..4095],
SAS Id:
t ID
[0..65535],
SMLC Id:
[0..65535].
2G office only fill
one NEID. NEID
of 2G office
cannot be
modified.
PLMN
PLMN ID:
Group
sequence<long,4> [0..4294967295]. R-W-I
Object
eg:1;2
ID
2G office:
32:RNC
64:MGW
576:MGW+MSCS
ERVER
1023:SMLC
Type of 3G office:
long:
adjace 16:BSC
[16,32,64,512,576,1023,4096 R-I
nt 32:RNC
,32768]
office 64:MGW
512:MSCSERVE
R
576:MGW+MSCS
ERVER
4096:SGSN
32768:SAS
0: ATM (3G)
1: IP
2: TDM (2G)
Bear (Parameters can't
long:[0..2] R-I
type be modified)
When 2G office is
RNC,SRVBRSTY
PE must be 1.
Encode
14:SPC 14 bits,
type of
24:SPC 24 bits
signalli long:[14,24] R-W-I
Depend on the
ng
real situation.
point
Destina long:[0..16777215] 14 bits:0..16383 R-W-I
tion 24
point bits:0..16777215
code This is an
interconnection
parameter, which
must remain the
same as the peer
setting.
0: International
SPC,
4: Reserved
Sub-
international
Service long:[0,4,8,12] R-W-I
SPC,
Field
8: National SPC,
12: Reserved
National SPC
Connec
tion
relation
1:Associated
ship
2:Quasi-
with long:[1..3] R-W-I
associated
local
3:No connection
signalli
ng
point
0:Not Support
1:Support
For UMTS or TD
mode type,the
recommended
value of
BandFlag is 1.
For GSM mode
support
type, the value of
broadb
BandFlag must
and long:[0..1] R-W-I
be 0 if the office
properti
configures MTP3
es
links,
and the
recommended
value of
BandFlag is 1 if
the office
configures M3UA
links.
1:CHINA
Protoco
long:[1..3] 2:ITU R-W-I
l type
3:ANSI
ATM 20 bytes,
addres separate each
s of byte with ".",
string R-W
adjace decimal.
nt 2G office doesn't
office configure it
Prefere sequence<long,4> For one PLMN, R-W
nce CN 0:NO
Office
Flag in 1:YES
CS/PS eg:1;0
Domain
For one PLMN,
Default
0:Is Not Default
Office
Office
Flag in sequence<long,4> R-W
1:Is Default
CS/PS
Office,
Domain
eg:1;0
Capacit
y For one
Weight PLMN,the value
sequence<long,4> R-W
in range is [0..100].
CS/PS eg:1;0
Domain
Numbe
r of
Networ
k For one
Resour PLMN,the value
sequence<long,4> R-W
ce range is [0..4].
Identifi eg:1;0
er in
CS/PS
Domain
Networ string Value Range of R-W
k one Network
Resour Resource
ce Identifier is
Identifi [0..1023].
er in Network
CS/PS resources
Domain identified as two-
dimensional
array,
the first-
dimensional array
of length
determined by the
array length of
PLMNID,
the length of the
array in each
PLMN is
determined by the
number of
network resource
identifier for each
PLmn
format
x;x;x;x@x;x;x;x
Network resource
identifier
separated by ;
(semicolons) in
the same PLMN,
When to
configure More
than one PLMN,
Network resource
identifier
separated by @
betwwen PLMN
Such
as:1;2;3;4@5;6;7;
8
3.2.13 SCTP Config(CN)
Table 3-20 SCTP Config (CN)
Paramete Parameter Remark

Description
r Name Value s
It contains no more than 80
User label string R
characters.
Managed
Primary
Key
Object ID
Adjacent
Office long:[1..2048] R-I
Number
Associatio Primary
long:[1..3000] GSM:long:[1..2000]
n ID Key
TD:[3..18]
UMTS:[3..31]
Used GSM:[3..12]
long:[3..31] R-W-I
Module Support to modify the module
No. of path group for Iu
interface.
Applicatio
n type of 1:Server
long:[1..2] R-W-I
associatio 2:Client
n
long:
Local port R-W-I
[1..65535]
It can be filled in four IP
address at most,such as
Local Ip ipv4 R-W-I
xxx.xxx.xxx.xxx;xxx.xxx.xxx.x
xx
Remote long:
R-W-I
port [1..65535]
Remote Ip ipv4 It can be filled in four IP R-W-I
address at most,such as
xxx.xxx.xxx.xxx;xxx.xxx.xxx.x
xx
ASP ID long:[1..3000] R-I
long: default value:500
RTO.Max R-W
[10..3000] unit 10millisecond
RTO.Min R-W
RTO.Initial R-W
HB.interva long: default value:500
R-W
l [10..6000] unit 10millisecond
Delay ack default value:20
long:[0..20] R-W
interval unit 10millisecond
3.2.14 M3uaAS Config
Table 3-21 M3uaAS Config
Parameter
Name
It contains no
characters.
Managed
Primary
Element Object long:[1..4095]
Key
ID
Adjacent Office
long:[1..2048] R-I
Number
Primary
AS Number long:[1..640]
Key
The value
range of ASP
ASP ID sequence<long,16> Number is R-W-I
1..3000.
eg:1;2
Whether exists 0: FALSE
long:[0..1] R-W-I
routing context 1: TRUE
Routing 4294967295
long:[0..4294967295] R-W-I
context ID is invalid
Whether exists
0: FALSE
peer routing long:[0..1] R-W
1: TRUE
context
Peer routing 4294967295
long:[0..4294967295] R-W
context ID is invalid
AS property long:[1..5] 1: SGP, R-W-I
2: ASP,
3: IPSP
SERVER,
4: IPSP
CLIENT,
5: DOUBLE
EXCHANGE
MODEL
1: Override,
AS traffic mode long:[1..2] R-W-I
2: Loadshare
value of N
which is
effective only
long:[0..16] R-W
under overload
participation
mode
value of K
which is
effective only
long:[0..16] R-W
under overload
participation
mode
3.2.15 M3uaRoute
Table 3-22 M3uaRoute
Parameter
Name
It contains no more
User label string than 80 R-W
characters.
Managed
Primary
Key
Object ID
Route Primary
long:[1..640]
Number Key
0:Ikebana Sort
Route
1:This Module
range long:[0..2] R-W-I
Priority
mode
2:Natural Sort
AS
long:[1..640] R-W-I
Number 1
AS
long:[0..640] 0:Invalid R-W-I
Number 2
3.2.16 M3uaRouteSet
Table 3-23 M3uaRouteSet
Parameter
Name
It contains no more
User label string than 80 R
characters.
Managed
Primary
Key
Object ID
Adjacent
Primary
Office long:[1..2048]
Key
Number
Route
long:[1..640] R-W-I
Number 1
Route
Number 2
3.2.17 IP Path(CN)
Table 3-24 IP Path (CN)
Parameter
Name
It contains no
characters.
Managed
Primary
Key
Object ID
Adjacent Net
Primary
Key
Identifier
Primary
TrPath ID long:[0..7]
Key
Path Group Primary
long:[0..2047]
ID Key
PLMN
Group long:[0..4294967295] R-I
Object ID
Destination
ipv4 R-W-I
IP Address
net mask long:[0..32] R-W-I
length for
Destination
IP
Tx
bandwidth
Rx
bandwidth
3.2.18 PVC Config(IU-IUR)
Table 3-25 PVC Config(IU-IUR)
Para
met Re
Paramet
er Description mar
er Value
Nam ks
e
User
label
Man
aged Pri
Elem long: mar
ent [1..4095] y
Obje Key
ct ID
Adja
cent
Offic long:
R
e [1..2048]
Num
ber
Pri
PVC long:
mar
Indic [1..12600
y
ate ]
Key
Atm
Interf
APBE, IMAB board
ace string R-I
rack/shelf/slot
Boar
d
ATM long: ATM Optical Port:[1..4],
R-I
port [1..240] IMA Port:[1..240]
E1 string IMA port need to be configured. R-
list format unitindex;e1index@unitindex;e1index W
unitindex:[1..17]
e1index:DTB/DTA/DTB3[1..32],SDTB
[1..63],SDTA/SDTB2/SDTA3/SDTB3[1..63,8
5..147],SDTA2[1..63,64..126,127..189,190..
246]
unitindex, another e1index
The unitindex is a unit that E1 belongs
Unit number and E1 numbers separated by ;
(semicolons)
separated by @
eg,5;1@5;1@6;1@6;2
VPI
on long: R-
high [0..4095] W-I
port
VCI
long:
on R-
[32..6553
high W-I
4]
port
0: AAL5 Signal,
1: AAL5 Data,
PVC 2: AAL2 Data
Servi long:
R-I
ce [0..2] AAL5 Signal: the Signalling over ATM,
Type AAL5 Data: IUPS is the service over ATM,
AAL2 Data: IUCS or IUR is the service over
ATM.
Servi long: 0:CBR R-
ce [0..5] 1:rtVBR W-I
Cate 2:nrtVBR
gory 3:ABR
4:UBR
5:UBR+
CBR surpports:
atmClpNoTaggingNoScr(2),
atmNoClpNoScr(1)
atmClpTransparentNoScr(8),
atmNoClpNoScrCdvt(11).
rtVBR and nrtVBR surpport:

atmNoClpNoScr(1),
atmClpNoTaggingNoScr(2),
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt(13),
atmClpTaggingScrCdvt(14),
atmNoClpScr(4).
ABR surpport:
atmClpNoTaggingMcr(7)
UBR surpports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpTaggingNoScr(10).
UBR+ surpports:
0: NOTRF
1: atmNoClpNoScr
2: atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
6: atmClpTaggingScr
Traffi
long: 7: atmClpNoTaggingMcr R-
c
[0..15] 8: atmClpTransparentNoScr W-I
Type
9: atmClpTransparentScr
10: atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13: atmClpNoTaggingScrCdvt
14: atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak
cell
rate
for long: Unit: Kbps.
R-
CLP [0..18210 This Traffic Para surpports all Service
W-I
=0+1 66133] Category and all Traffic Type.
(PC
R0+
1)
Peak
cell Unit: Kbps.
rate Service Category:
long:
for CBR ,rtVBR and nrtVBR. R-
[0..18210
CLP Traffic Type: W
66133]
=0 atmClpNoTaggingNoScr(2),
(PC atmClpTaggingNoScr(3).
R0)
Unit: 0.1us.
Cell Service Category:
dela CBR ,rtVBR, nrtVBR and UBR.
y Traffic Type:
varia long: atmClpTransparentNoScr (8),
R-
tion [0..42949 atmNoClpNoScrCdvt (11),
W
toler 67295] atmClpTaggingScrCdvt(14),
ance atmClpTransparentScr(9),
(CD atmNoClpScrCdvt(12),
VT) atmNoClpNoScrCdvt(13),
atmNoClpTaggingNoScr(10).
Sust long: Unit: Kbps. R-
aina [0..18210 Service Category: W
ble 66133] rtVBR and nrtVBR.
cell
rate Traffic Type:
for atmClpNoTaggingScr(5),
CLP atmClpNoTaggingScrCdvt(13),
=0 atmClpTaggingScr(6),
(SC atmClpTaggingScrCdvt(14).
R0)
Sust
aina
Unit: Kbps.
ble
Service Category:
cell
long: rtVBR and nrtVBR.
rate R-
[0..18210 Traffic Type:
for W
66133] atmClpTransparentScr(9),
CLP
=0+1
atmNoClpScr(4).
(SC
R0)
Unit: cell.
Service Category:
Maxi
rtVBR and nrtVBR.
mum
Traffic Type:
burst
long: atmClpNoTaggingScr(5),
cell R-
[0..42949 atmClpNoTaggingScrCdvt(13),
num W
67295] atmClpTaggingScr(6),
ber
atmClpTaggingScrCdvt(14),
(MB
S)
atmNoClpScr(4).
Mini Unit: Kbps.
mum Service Category:
long:
cell ABR and UBR+. R-
[0..18210
rate Traffic Type: W
66133]
(MC atmClpNoTaggingMcr(7),
R) atmTrafficForUbr+(15)
Maxi
mum Unit: cell.
fram long: Service Category:
R-
e [0..42949 UBR+.
W
size 67295] Traffic Type:
(MF atmTrafficForUbr+(15)
S)
Path
long:
Grou R
[0..2047]
p ID
PLM
PLMN ID:[0..4294967295], eg:1;2.
N
It should be filled when creating or modifying
Grou sequence R-
trpath.
p <long,4> W
This parameter must be consistent with the
Obje
PLMN info of Office.
ct ID
TrPa sequence TrPath ID :[32..127] R-
th ID <long,4> eg:32;33 W
AAL
2
Attac long: TD:[3..18] R-
hed [3..31] UMTS:[3..31] W
Mod
ule
AAL
2
Path long:
ID [1..42949 R
intra 67295]
offic
e
AAL
10: RT,
2
11: NRT1,
Path long: R-
12: NRT2,
Servi [10..14] W
13: NRT3,
ce
14: MIX
Type
AAL
2
Path long: 0:Local End R-
Own [0..1] 1:Peer End W
ershi
p
Sign
allin
g long:
R
link [1..9000]
num
ber
Link
set long:
R
num [1..1024]
ber
Sign
allin
g
Link long: TD:[3..18] R-
Attac [3..31] UMTS:[3..31] W
hed
Mod
ule
Sign
allin
g long: R-
Link [0..15] W
Cod
e
Desti ipv4 R-
natio W
n IP
addr
ess
3.2.19 Mtp2Link

3.2.20 Mtp3Route
Table 3-26 Mtp3Route
Parameter
Name
It contains no
User label string more than 80 R-W
characters.
Managed
Primary
Element Object long:[1..4095]
Key
ID
Signalling route Primary
long:[1..2000]
number Key
Used Signalling
long:[1..1024] R-W-I
Linkset 1
Used Signalling
Linkset 2
0:Any
arrangement
1:According to
SLS_bit0
choose routing
groups
2:According to
SLS_bit1
choose link
groups
3:According to
SLS_bit2
choose link
groups
4:According to
SLS_bit3
choose link
Permutation of
long:[0..8] groups R-W-I
signalling links
5:According to
SLS_bit0 and
SLS_bit1
choose link
groups
6:According to
SLS_bit1
and SLS_bit2
choose link
groups
7:According to
SLS_bit2
and SLS_bit3
choose link
groups
8:Ikebana
Arrangement
3.2.21 Mtp3RouteSet
Table 3-27 Mtp3RouteSet
Parameter
Name
It contains no
characters.
Managed
Primary
Key
Object ID
Adjacent Office Primary
long:[1..2048]
Number Key
Signalling
long:[1..2000] R-W-I
route number 1
Signalling
route number 2
Signalling
route number 3
Signalling
route number 4
3.2.22 Dynamic Sctp
3.2.23 No.7 PCM
3.2.24 MSC Office
3.2.25 SGSN Office
3.2.26 Fr Gb

3.2.27 Ip Gb
3.2.28 Lucent Channel
3.2.29 PCM(ITC-MSC)
3.2.30 iTC or BSC Office

4 UMTS Radio Template Configuration

Specifications
The sheets in Sections 0, 4.2, 4.3, and 4.8 must be configured, while other sheets are
optional.
4.1 UTRAN Cell FDD
Table 4-1 UTRAN Cell FDD
R
Par
e
am
m
ete
Parameter Value Description a
r
r
Na
k
me
s
[Ma P
nag ri
ed m
Ele a
me long:[1..4095] r
nt y
Obj K
ect e
ID] y
Cannot use
Use
invalid R
r
string:[0..80] character -
Lab
&,'"<>#%/\? W
el
@
P
ri
m
RN a
C long:[0..4095] r
ID y
K
e
y
R
No -
deB long:[0..65535] W
No -
I
P
ri
m
a
Cell
long:[0..65534] r
ID
y
K
e
y
Loc
R
al
-
Cell
long:[0..268435455] W
Ide
-
ntit
I
y
Fre
que
R
ncy
-
Ban 0:Band I,1:Band II,2:Band III,3:Band
W
d IV,4:Band V,5:Band VI,7:Band VIII
-
Indi
I
cat
or
UU long: uarfcnUl is R
AR [9612..9888,9262..9538,12,37,62,87,112,13 calculated by
FC 7,162,187,212,237,262,287,937..1288,1312. uarfcnDl,
N .1513,1662,1687,1712,1737,1762,1787,181 should not
2,1837,1862,4132..4233,782,787,807,812,8 input any
37,862,4162..4188,812,837,2712..2863] value.
{freqBandInd
==0}
[9612..9888],
{freqBandInd
==1}
[9262..9538]
[12][37][62]
[87][112]
[137][162]
[187][212]
[237][262]
[287],
{freqBandInd
==2}
[937..1288],
{freqBandInd
==3}
[1312..1513]
[1662][1687]
[1712][1737]
[1762][1787]
[1812][1837]
[1862],
{freqBandInd
==4}
[4132..4233]
[782][787]
[807][812]
[837][862],
{freqBandInd
==5}
[4162..4188]
[812][837],
{freqBandInd
==7}
[2712..2863]
{freqBandInd
==0}
[10562..1083
8],
{freqBandInd
==1}
[9662..9938]
[412][437]
[462][487]
[512][537]
[562][587]
[612][637]
[662][687],
{freqBandInd
==2}
long: [1162..1513],
[10562..10838,9662..9938,412,437,462,487, {freqBandInd R
DU
512,537,562,587,612,637,662,687,1162..15 ==3} -
AR
13,1537..1738,1887,1912,1937,1962,1987,2 [1537..1738] W
FC
012,2037,2062,2087,4357..4458,1007,1012, [1887][1912] -
N
1032,1037,1062,1087,4387..4413,1037,106 [1937][1962] I
2,2937..3088] [1987][2012]
[2037][2062]
[2087],
{freqBandInd
==4}
[4357..4458]
[1007][1012]
[1032][1037]
[1062][1087],
{freqBandInd
==5}
[4387..4413]
[1037][1062],
{freqBandInd
==7}
[2937..3088]
Cell long:[0..511] R
Pri -
mar W
y -
Scr I
am
blin
g
Co
de
Loc
atio R
n -
Are long:[1..65533,65535] W
a -
Co I
de
Ro
utin R
g -
Are long:[0..255] W
a -
Co I
de
Ser
R
vice
-
Are
long:[0..65535] W
a
-
Co
I
de
Element
UR R
Data Range
A -
in Array is
Ide sequence<long,4> W
[0..65535],an
ntit -
d separated
y I
by ";".
Ser
vice
Are
a
Co R
de long:[0..65535] -
for W
BC
Do
mai
n
R
-
T_
long:[0..9],<default:0> W
Cell
-
I
Sec
tor R
Ide long:[1..255],<default:1> -
ntit W
y
Cell long:[0..1806627],<default:10000> R
Ra -
diu
W
s
Mo
bilit
y
Co 0:Outdoor Scene,1:High-Mobility Outdoor R
nfig Scene,2:Indoor Scene,3:Subway/ tunnel -
urat Scene,<default:0> W
ion
Sce
ne
[UD
piA
ppS
rvP R
rofil long:[0..4294967295],<default:0> -
e W
Obj
ect
ID]
Cell
Ma
xim
um
Tra R
ns double:[0..50],<default:43>,step:0.1 -
mis W
sio
n
Po
wer
PIC
R
H
long:[-10..5],<default:-7> -
Po
W
wer
P-
CPI R
CH double:[-10..50],<default:33>,step:0.1 -
Po W
wer
Pri
mar
y R
SC double:[-35..15],<default:-5>,step:0.1 -
H W
Po
wer
Sec double:[-35..15],<default:-5>,step:0.1 R
ond -
ary W
SC
H
Po
wer
BC
R
H
double:[-35..15],<default:-4>,step:0.1 -
Po
W
wer
AIC
R
H
long:[-22..5],<default:-7> -
Po
W
wer
PC
R
H
double:[-35..15],<default:-3>,step:0.1 -
Po
W
wer
HS
0:Not Support HSUPA and
PA
HSDPA,1:Support HSDPA and R
Sup
DCH,2:Support HSDPA only,3:Support -
port
HSUPA, HSDPA and DCH,4:Support W
Met
HSUPA and HSDPA,<default:0>
hod
Ma
xim
um
Nu
mb
er R
of long:[0..65535],<default:16> -
Use W
rs
on
HS-
DS
CH
Ma
xim
um
Nu
mb
er R
of long:[0..65535],<default:16> -
Use W
rs
on
E-
DC
H
Prio long:[0..255],<default:0> R
rity -
of W
Fre
que
ncy
Swi
tch
Off
Min
imu
m
Re
quir
ed
Qu
ality R
Lev long:[-24..0],<default:-18> -
el W
in
the
Cell
(Qq
ual
min
)
Min
imu
m
Re
quir
ed
Rec
eiv
R
ed
long:[-115..-25],<default:-115>,step:2 -
Lev
W
el
in
the
Cell
(Qr
xlev
min
)
Incr long:[-4..-2],<default:-2>,step:2 R
em -
ent W
to
the
Min
imu
m
Re
quir
ed
Rec
eiv
ed
Lev
el
in
the
Cell
(De
lta
Qrx
lev
min
)
Cell
Res
erv
ed R
for 0:Reserved,1:Not Reserved,<default:1> -
Op W
erat
or
Use
ST
TD
Sup R
port 0:Supported,1:Not Supported,<default:1> -
Indi W
cat
or
Clo
sed
Loo
p
Mo
R
de
0:Supported,1:Not Supported,<default:1> -
1
W
Sup
port
Indi
cat
or
Cell
Indi
R
vid
double:[-10..10],<default:0>,step:0.5 -
ual
W
Off
set
HC
R
S_
long:[0..7],<default:0> -
PRI
W
O
Qu double:[-24..0],<default:-12>,step:0.5 R
ality -
Thr W
esh
old
Lev
el
for
App
lyin
g
Prio
ritis
ed
Hie
rarc
hic
al
Cell
Res
ele
ctio
n
(Q
Hcs
)
Wh
en
Me
asu
rem
ent
Qu
anti
ty is
CPI
CH
Ec/
No
Qu long:[-115..-26],<default:-92> R
ality -
Thr W
esh
old
Lev
el
for
App
lyin
g
Prio
ritis
ed
Hie
rarc
hic
al
Cell
Res
ele
ctio
n(Q
Hcs
)
Wh
en
Me
asu
rem
ent
Qu
anti
ty is
CPI
CH
RS
CP
Incr
em
ent
to
the
Min
imu
m
Re
quir
ed
R
Rec
0:False,1:True,<default:0> -
eiv
W
ed
Lev
el
in
the
Cell
Co
nfig
urat
ion
Tag
[UN
bC
om
Me
R
asP
long:[0..4294967295],<default:0> -
rofil
W
e
Obj
ect
ID]
[UT long:[0..4294967295],<default:0> R
rvM -
eas W
Pro
file
Obj
ect
ID]
[UU
eInt
Me
asP R
e W
Obj
ect
ID]
Pat
hlo
R
ss 0:Dense City Zone,1:Generic City
-
Sce Zone,2:Suburb,3:Country,<default:0>
W
nari
o
Cell
Des
R
crip 0:Center Point with Altitude and Cell
-
tion Radius,1:Polygon,2:Arc,<default:0>
W
Typ
e
MB
MS
Sup R
0:Not Support,1:Support MBMS and not
port -
MBMS,2:Only Support MBMS,<default:0>
Indi W
cat
or
Mul
ti-
Use
r
Det
R
ecti
0:Not Support,1:Support,<default:0> -
on
W
Sup
port
Indi
cat
or
TU 0:Not Supported,1:Supported,<default:0> R
TR -
AN- W
GP
S
Me
asu
rem
ent
Sup
port
Indi
cat
or
CS
Traf
fic
Pre R
0:CS No Preferred,1:CS
ferr -
Preferred,<default:1>
ed W
Indi
cat
or
R9
9
PS
Traf
fic R
0:R99 PS No Preferred,1:R99 PS
Pre -
Preferred,<default:1>
ferr W
ed
Indi
cat
or
HS
PS
Traf
fic
R
Pre 0:HS PS No Preferred,1:HS PS
-
ferr Preferred,<default:1>
W
ed
Indi
cat
or
Use
of
HC
S in R
Cell 1:Not Used,2:Used,<default:1> -
Res W
ele
ctio
n
UE 0:Off,1:On,<default:0> R
Tx -
Po W
wer
Swi
tch
for
Ha
ndo
ver
UL
BL
ER
Swi R
tch 0:Off,1:On,<default:0> -
for W
Ha
ndo
ver
DL
Tx
Po
wer
R
Swi
0:Off,1:On,<default:0> -
tch
W
for
Ha
ndo
ver
SIB
12 R
Indi 0:False,1:True,<default:0> -
cat W
or
HS
DP
A
R
Fun
0:Inactive,1:Active,<default:1> -
ctio
W
n
Stat
us
HS
UP
A
R
Fun
0:Inactive,1:Active,<default:1> -
ctio
W
n
Stat
us
MB
MS
Fun R
ctio 0:Inactive,1:Active,<default:0> -
n W
Stat
us
[UI long:[0..4294967295],<default:0> Configured R
ntra for general -
Me user W
asP
rofil
e
Obj
ect
ID]
[UI
ntra
Me
asP R
Configured
for VIP user
e W
Obj
ect
ID]
[UI
nter
Me
asP R
e W
Obj
ect
ID]
[UR
atM
eas
R
Pro
long:[0..4294967295],<default:0> -
file
W
Obj
ect
ID]
Cell R
0:Macro Cell,1:Normal Cell,2:Micro
Typ -
Cell,<default:1>
e W
Bac
kgr
oun
d
Noi
se
Aut 0:Normal Scene,1:Easy Adjustment R
om Scene,2:Difficult adjustment -
atic Scene,<default:0> W
Adj
ust
me
nt
Sce
ne
Cla 0:False,1:True,<default:0> R
ssifi -
ed W
Zon
e
Indi
cat
or
[US
rvP
cPr
R
ofil
long:[0..4294967295],<default:0> -
e
W
Obj
ect
ID]
PR
0:One PRACH Channel of R99,1:One
AC
PRACH Channel of R99 and One
H
PRACH Channel of Enhanced Uplink Fach
Co R
with the Same Preamble Scrambling
nfig -
Codes,2:One PRACH Channel of R99 and
urat W
One PRACH Channel of Enhanced Uplink
ion
Fach with the Different Preamble Scrambling
Sce
Codes,<default:0>
ne
DB
DC-
HS
DP
R
A
0:Not Supported,1:Supported,<default:0> -
Sup
W
port
Indi
cat
or
Sce
nari R
o string:[0..40] -
Typ W
e
Nu
mb
er
of
the
Co
des
with R
SF long:[0..30],<default:0> -
=12 W
8
Ord
ere
d
for
OC
NS
Co
de
No
de
Nu Element
mb Data Range
R
er in Array is
sequence<long,30> -
with [1..127],and
W
SF separated by
=12 ";".
8
for
OC
NS
Swi
tch
of
CS
64k R
bps 0:Off,1:On,<default:1> -
Est W
abli
sh
me
nt
Cell
F-
DP
CH R
Sup 0:Not Support,1:Support,<default:0> -
port W
Indi
cat
or
Cell
Enh
anc
ed
F-
R
DP
CH
W
Sup
port
Indi
cat
or
Cell 0:Not Support,1:Support,<default:0> R
64 -
QA W
M
Sup
port
Indi
cat
or
Cell
MI
MO
R
Sup
port
W
Indi
cat
or
Cell
CP
C
R
Sup
port
W
Indi
cat
or
Cell
HS
UP
A
2m
R
s
TTI
W
Sup
port
Indi
cat
or
Cell
MI
MO
and
DL
64
QA
M
Co R
mbi 0:Not Support,1:Support,<default:0> -
ned W
Ca
pab
ility
Sup
port
Indi
cat
or
Du 0:Not Support,1:Support,<default:0> R
al- -
Cell W
HS-
DS
CH
Sup
port
Indi
cati
on
Prio
r 0:Off,1:Prior to Inter-Frequency, secondly to
Re Inter-RAT (Prior to GSM Cell),2:Prior to
dire Inter-Frequency, Secondly to Inter-RAT (PS
R
ct prior to E-UTRA, CS Prior to GSM),3:Prior to
-
RA Inter-RAT (Prior to GSM), Secondly to Inter-
W
T Frequency,4:Prior to Inter-RAT (PS prior to
Indi E-UTRA, CS Prior to GSM), Secondly to
cat Inter-Frequency,<default:3>
or
Wai
t
Tim
e
for
RR
C
Co R
nne long:[0..15],<default:5> -
ctio W
n
Re
est
abli
sh
me
nt
Do
wnli
nk
Enh
anc
ed
CE R
LL_ 0:Not Support,1:Support,<default:0> -
FA W
CH
Sup
port
Indi
cat
or
Upli 0:Not Support,1:Support,<default:0> R
nk -
Enh W
anc
ed
CE
LL_
FA
CH
Sup
port
Indi
cat
or
Cell
Du
al
Cell
+MI R
MO 0:Not Support,1:Support,<default:0> -
Sup W
port
Indi
cat
or
Ra
dio
Ca R
pac long:[0..65535],<default:1> -
ity W
of
Cell
Cell
Loa R
0:Normal Load Cell,1:High Load
d -
Cell,<default:0>
Sce W
ne
Loa
d
Bal R
0:Close Load Balance,1:Open Load
anc -
Balance,<default:0>
e W
Sce
ne
0:2 SCCPCHs are Configured, not
Supporting MBMS, not Supporting CBS,1:2
SCCPCHs are Configured, not Supporting
SC MBMS, Supporting CBS,2:1 SCCPCH is
CP Configured, not Supporting MBMS, not
CH Supporting CBS,3:1 SCCPCH is Configured,
Co not Supporting MBMS, Supporting CBS,4:2 R
nfig SCCPCHs are Configured, Supporting -
urat MBMS, not Supporting CBS,5:2 SCCPCHs W
ion are Configured, Supporting MBMS,
Sce Supporting CBS,6:3 SCCPCHs are
ne Configured, Supporting MBMS, not
Supporting CBS,7:3 SCCPCHs are
Configured, Supporting MBMS, Supporting
CBS,<default:0>
Cell
Ra
0:[0~5]km,1:[5~10]km,2:[10~40]km,3: R
diu
[40~80]km,4:[80~200]km,5: -
s
[200~Infinity]km,<default:0> W
Sce
ne
Swi
tch
of
Def
erre
d R
SIB 0:Off,1:Opened,<default:0> -
11/ W
11b
is/1
2
Sup
port
[UB
Pri
Ac
R
Pro
long:[0..4294967295],<default:0> -
file
W
Obj
ect
ID]
[US
chP
riM
app
R
ing
long:[0..4294967295],<default:0> -
Pro
W
file
Obj
ect
ID]
[UA
ppP
riM
app
R
ing
long:[0..4294967295],<default:0> -
Pro
W
file
Obj
ect
ID]
[UA long:[0..4294967295],<default:0> R
ppP -
riM W
app
ing
Pro
file
Obj
ect
ID]
Pol
ygo
n
R
Poi
long:[3..15],<defalut:3> -
nt
W
Nu
mb
er
Pol
ygo Element
n Data Range
Poi in Array is
R
nt [0..1]
sequence<long,15>,<default:[0,0,0]> -
Lati (0:North,1:So
W
tud uth),and
e separated by
Sig ";".
n
De
gre
e of
Element
Pol
Data Range
ygo R
sequence<double,15>,<default: in Array is
n -
[0,0,0]>,step:0.00001 [0..90],and
Poi W
separated by
nt
";".
Lati
tud
e
De
gre
es
of Element
Pol Data Range
R
ygo sequence<double,15>,<default: in Array is [-
-
n [0,0,0]>,step:0.00001 180..180],an
W
Poi d separated
nt by ";".
Lon
gitu
de
Lati 0:North,1:South,<defalut:0> R
tud -
e W
Sig
n
for
Cell
Ce
nter
De
gre
e of
Lati
R
tud
double:[0..90],<defalut:0>,step:0.00001 -
e
W
for
Cell
Ce
nter
De
gre
es
of
Lon R
gitu double:[-180..180],<defalut:0>,step:0.00001 -
de W
for
Cell
Ce
nter
Cell
Altit
ude R
for long:[0..32767],<defalut:0> -
Cell W
Ce
nter
Dir
ecti
on
of
R
Altit
0:Height,1:Depth,<defalut:0> -
ude
W
for
Cell
Ce
nter
Altit
ude R
acc long:[0..990],<defalut:0> -
ura W
cy
Co
R
nfid
enc
W
e
Ge 0:Ellipsoid Point,1:Ellipsoid Point with R
ogr Uncertainty Circle,2:Ellipsoid Point with -
aph Uncertainty Ellipse,3:Ellipsoid Point with W
ical Altitude,4:Ellipsoid Point with Altitude and
Are
a
Re Uncertainty Ellipsoid,5:List of Ellipsoid
port Points,6:Ellipsoid Arc,<defalut:0>
Typ
e
Ant
enn R
0:Omni
a -
Antenna,1:Beam Antenna,<defalut:0>
Typ W
e
Ant
enn
aLa R
titu 0:North,1:South,<defalut:0> -
de W
Sig
n
De
gre
e of
Ant R
enn double:[0..90],<defalut:0>,step:0.00001 -
a W
Lati
tud
e
De
gre
es
of
R
Ant
double:[-180..180],<defalut:0>,step:0.00001 -
enn
W
a
Lon
gitu
de
Ant
enn R
a long:[0..32767],<defalut:0> -
Altit W
ude
Dir
ecti
on
of R
Ant 0:Height,1:Depth,<defalut:0> -
enn W
a
Altit
ude
Off long:[0..360],<defalut:0> R
set
-
Ang
W
le
Inn
R
er
Ang
W
le
Du
al
Cell
HS
UP R
A 0:Not Supported,1:Supported,<default:0> -
Sup W
port
Indi
cati
on
[U
MP
OPr
R
ofil
long:[0..4294967295],<default:0> -
e
W
Obj
ect
ID]
Cell
Du
al
Ban
d
Du
al R
Cell 0:Not Supported,1:Supported,<default:0> -
+MI W
MO
Sup
port
Indi
cat
or
The
Cell
ID R
of long:[0..65535],<default:65535> -
Bac W
kup
Cell
Cell 0:Not Supported,1:Supported,<default:0> R
DB- -
MC W
+MI
MO
Sup
port
Indi
cat
or
Cell
SB-
MC
+MI
R
MO
Sup
W
port
Indi
cat
or
HS
DP
A3
or 4
Car
R
rier
Sup
W
port
ed
Indi
cati
on
Swi
tch
of
Fas
t
Ret
urn
to
Eut
ran R
wh 0:Off,1:On,<default:0> -
en W
Eut
ran
CS
FB
CS
is
rele
ase
d
Swi 0:Off,1:On,<default:0> R
tch -
of W
Fas
t
Ret
urn
to
Eut
ran
wh
en
Eut
ran
SR
VC
C
CS
is
rele
ase
d
The
Nu
mb
er
of
UE
Sig
nalli
ng
Tra
ce
Dat
R
a
Coll
W
ecti
on
Co
nfig
urat
ion
Ind
ex
Rel
ate
d to
Cell
[US
Element
ign
Data Range
alTr
in Array is R
ace
sequence<long,20> [0..42949672 -
Cfg
95],and W
Obj
separated by
ect
";".
ID]
4.2 ULogicalCell
Table 4-2 ULogicalCell
Parameter Rema
Name rks
[Managed
Prima
ry Key
Object ID]
Cannot use
invalid
User Label string:[0..80] R-W
character
&,'"<>#%/\?@
Prima
RNC ID long:[0..4095]
ry Key
Mobile Prima
long:[0..999]
Country Code ry Key
Mobile Prima
long:[0..999]
Network Code ry Key
can not repeat
Prima
Cell ID long:[0..65534] in the same
ry Key
PLMN.
Common
PLMN 0:False,1:True,<default:1> R-I
Indicator
Add for
network
planning and
optimization,
only exporting
NodeB No long:[0..65535] supports this R
parameter.
Importing
should ignore
this
parameter.
Element Data
CS Domain
Range in
Specific
Array is [0..1]
Access Class sequence<long,16>,<defau
(0:Barred,1:N R-W
N Barred lt:1>
ot Barred),and
Indicator
separated by
(N=0…15)
";".
Element Data
PS Domain
Range in
Specific
Array is [0..1]
Access Class sequence<long,16>,<defau
(0:Barred,1:N R-W
N Barred lt:1>
ot Barred),and
Indicator
separated by
(N=0…15)
";".
Access
Percent of the
PLMN for Non- long:[0..100],<default:25> R-W
Supporting
UEs
0:Switch Off CS Domain
DSAR by OMCR,1:Switch
On CS Domain DSAR by
OMCR,2:RNC Controls
Dynamically CS Domain
Switch of CS DSAR According to
R-W
Domain DSAR Accessibility of Iu,3:RNC
Controls Dynamically CS
Domain DSAR According
to Load of Iu or
Accessibility of
Iu,<default:0>
0:Switch Off PS Domain
DSAR by OMCR,
1:Switch On PS Domain
DSAR by OMCR,
2:RNC Controls
Dynamically PS Domain
Switch of PS
DSAR According to R-W
Domain DSAR
Accessibility of Iu,
3:RNC Controls
Dynamically PS Domain
DSAR According to Load
of Iu or Accessibility of
Iu,<default:0>
0:Allow UEs to Respond to
Paging Message and
Initiate the
Location/Registration,1:Re
strict UEs from Responding
to Paging Message and
Allow UEs to Initiate the
Switch of
Location/Registration,2:Allo
Paging and
w UEs to Respond to
Location/Regis R-W
Paging Message and
tration
Restrict UEs from Initiating
Restriction
the
Location/Registration,3:Re
strict UEs from Responding
to Paging Message and
Initiating the
Location/Registration,<defa
ult:0>
Switch of 0:Not
Polling in CS Polling,1:Polling,<default:0 R-W
Domain DSAR >
Switch of 0:Not R-W
Polling in PS Polling,1:Polling,<default:0
Domain DSAR >
Number of
Barred AC in long:[1..10],<default:2> R-W
CS Domain
Number of
Barred AC in long:[1..10],<default:2> R-W
PS Domain
Dpch Code double:
Ratio of PLMN [0..100],<default:100>,step: R-W
Code sharing 0.1
R99 Power
double:
Ratio when
[0..100],<default:100>,step: R-W
Carrier
0.1
Sharing
4.3 UExternalUtranCellFDD
Table 4-3 UExtrenalUtranCellFDD
P
ar
R
a
e
m
m
et
Parameter Value Description a
er
r
N
k
a
s
m
e
[
M
a
n
a
P
g
r
e
i
d
m
El
a
e long:[1..4095]
r
m
y
e
K
nt
e
O
y
bj
e
ct
ID
]
U string:[0..80] Cannot use R
s invalid -
er
L character
a &,'"<>#%/\? W
b @
el
P
r
i
R m
N a
long:[0..4095]
C r
ID y
K
e
y
C
ell
Id
P
e
r
nt
i
ity
m
of
a
A long:[0..65535]
r
dj
y
a
K
c
e
e
y
nt
C
ell
R
N
C
Id P
e r
nt i
ity m
of a
long:[0..4095]
A r
dj y
a K
c e
e y
nt
c
ell
M long:[0..999] R
o -
bil W
e -
C I
o
u
nt
ry
C
o
d
e
M
o
bil
e
N R
et -
w long:[0..999] W
or -
k I
C
o
d
e
L
o
c
at
io R
n -
Ar long:[1..65533,65535] W
e -
a I
C
o
d
e
Fr
e
q
u
e
n
R
cy
-
B 0:Band I,1:Band II,2:Band III,3:Band
W
a IV,4:Band V,5:Band VI,7:Band VIII
-
n
I
d
In
di
c
at
or
U long: {freqBandInd R
U [9612..9888,9262..9538,12,37,62,87,112,13 ==0}
A 7,162,187,212,237,262,287,937..1288,1312 [9612..9888]
R ..1513,1662,1687,1712,1737,1762,1787,18 ,
F 12,1837,1862,4132..4233,782,787,807,812, {freqBandInd
C 837,862,4162..4188,812,837,2712..2863] ==1}
N [9262..9538]
[12][37][62]
[87][112]
[137][162]
[187][212]
[237][262]
[287],
{freqBandInd
==2}
[937..1288],
{freqBandInd
==3}
[1312..1513]
[1662][1687]
[1712][1737]
[1762][1787]
[1812][1837]
[1862],
{freqBandInd
==4}
[4132..4233]
[782][787]
[807][812]
[837][862],
{freqBandInd
==5}
[4162..4188]
[812][837],
{freqBandInd
==7}
[2712..2863]
D long: {freqBandInd R
U [10562..10838,9662..9938,412,437,462,487 ==0} -
A ,512,537,562,587,612,637,662,687,1162..1 [10562..108 W
R 513,1537..1738,1887,1912,1937,1962,1987 38], -
F ,2012,2037,2062,2087,4357..4458,1007,10 {freqBandInd I
C 12,1032,1037,1062,1087,4387..4413,1037, ==1}
N 1062,2937..3088] [9662..9938]
[412][437]
[462][487]
[512][537]
[562][587]
[612][637]
[662][687],
{freqBandInd
==2}
[1162..1513]
,
{freqBandInd
==3}
[1537..1738]
[1887][1912]
[1937][1962]
[1987][2012]
[2037][2062]
[2087],
{freqBandInd
==4}
[4357..4458]
[1007][1012]
[1032][1037]
[1062]
[1087],
{freqBandInd
==5}
[4387..4413]
[1037]
[1062],
{freqBandInd
==7}
[2937..3088]
C
ell
Pr
i
m
ar
y
R
S
-
cr
long:[0..511] W
a
-
m
I
bli
n
g
C
o
d
e
S long:[0..65535] R
er -
vi W
c -
e I
Ar
e
a
C
o
d
e
fo
r
C
S
a
n
d
P
S
D
o
m
ai
n
U Element
R Data Range R
A in Array is -
Id sequence<long,4> [0..65535],a W
e nd -
nt separated by I
ity ";".
C
ell
R R
a long:[0..1806627],<default:10000> -
di W
u
s
P
ol
y
g
o
n
R
P
oi
W
nt
N
u
m
b
er
P
ol
y
g
o
n Element
P Data Range
oi in Array is
R
nt [0..1]
sequence<long,15>,<default:[0,0,0]> -
L (0:North,1:S
W
at outh),and
it separated by
u ";".
d
e
Si
g
n
D sequence<double,15>,<default: Element R
e [0,0,0]>,step:0.00001 Data Range -
gr in Array is W
e
e
of
P
ol
y
g
o
[0..90],and
n
separated by
P
";".
oi
nt
L
at
it
u
d
e
D
e
gr
e
e
s
of
P
ol
Element
y
Data Range
g R
sequence<double,15>,<default: in Array is [-
o -
[0,0,0]>,step:0.00001 180..180],an
n W
d separated
P
by ";".
oi
nt
L
o
n
gi
tu
d
e
L 0:North,1:South,<default:0> R
at -
it W
u
d
e
Si
g
n
fo
r
C
ell
C
e
nt
er
D
e
gr
e
e
of
L
at
it
R
u
double:[0..90],<default:0>,step:0.00001 -
d
W
e
fo
r
C
ell
C
e
nt
er
D
e
gr
e
e
s
of
L
o
n
R
gi
tu
W
d
e
fo
r
C
ell
C
e
nt
er
C long:[0..32767],<default:0> R
ell -
Al W
tit
u
d
e
fo
r
C
ell
C
e
nt
er
Di
re
cti
o
n
of
Al
tit
u R
d 0:Height,1:Depth,<default:0> -
e W
fo
r
C
ell
C
e
nt
er
Al
tit
u
d
R
e
a
W
cc
ur
a
cy
C
o
nf
R
id
e
W
n
c
e
A
nt
e
n
R
n 0:Omni
-
a Antenna,1:Beam Antenna,<default:0>
W
T
y
p
e
A
nt
e
n
n
a
L R
at 0:North,1:South,<default:0> -
it W
u
d
e
Si
g
n
D
e
gr
e
e
of
A
nt
R
e
double:[0..90],<default:0>,step:0.00001 -
n
W
n
a
L
at
it
u
d
e
D
e
gr
e
e
s
of
A
nt
R
e
n
W
n
a
L
o
n
gi
tu
d
e
A long:[0..32767],<default:0> R
nt
e
n
n
a -
Al W
tit
u
d
e
Di
re
cti
o
n
of
A
nt R
e 0:Height,1:Depth,<default:0> -
n W
n
a
Al
tit
u
d
e
O
ff
s
R
et
A
W
n
gl
e
In
n
er R
A long:[0..360],<default:0> -
n W
gl
e
G 0:Ellipsoid Point,1:Ellipsoid Point with R
e Uncertainty Circle,2:Ellipsoid Point with -
o Uncertainty Ellipse,3:Ellipsoid Point with W
gr Altitude,4:Ellipsoid Point with Altitude and
a Uncertainty Ellipsoid,5:List of Ellipsoid
p Points,6:Ellipsoid Arc,<default:0>
hi
c
al
Ar
e
a
R
e
p
or
t
T
y
p
e
R
o
ut
in
g
R
Ar
e
W
a
C
o
d
e
H
C
S R
_ long:[0..7],<default:0> -
P W
RI
O
R
A
C
H
M
a
xi
m
u
m
Al R
lo long:[-50..33],<default:24> -
w W
e
d
U
L
T
X
P
o
w
er
Pr double:[-10..50],<default:33>,step:0.1 R
i -
m W
ar
y
C
PI
C
H
P
o
w
er
Q
rx
le
v
m R
in long:[-115..-25],<default:-115>,step:2 -
in W
SI
B
1
1
D
el
ta
Q
rx
le
R
v
long:[-4..-2],<default:-2>,step:2 -
m
W
in
in
SI
B
1
1
Q
q
u
al
m R
in long:[-24..0],<default:-18> -
in W
SI
B
1
1
S 0:Supported,1:Not Supported,<default:1> R
T -
T W
D
S
u
p
p
or
t
In
di
c
at
or
Cl
o
s
e
d
L
o
o
p
M
o
d R
e 0:Supported,1:Not Supported,<default:1> -
1 W
S
u
p
p
or
t
In
di
c
at
or
M
N
C
B
C
D
C R
o long:[2,3],<default:2> -
d W
e
L
e
n
gt
h
S sequence<long,3> Element R
h Data Range -
ar in Array is W
in [0..999],and
g separated by
M ";".
o
bil
e
C
o
u
nt
ry
C
o
d
e
S
h
ar
in
g
M
o Element
bil Data Range
R
e in Array is
sequence<long,3> -
N [0..999],and
W
et separated by
w ";".
or
k
C
o
d
e
s
h
ar
in Element
g Data Range
M in Array is R
N sequence<long,3> [2..3],<defau -
C lt:2>,and W
L separated by
e ";".
n
gt
h
S long:[0..4],<default:0> R
h -
ar W
e
d
N
et
w
or
k
Ar
e
a
C
o
d
e
N
u
m
b
er
S
h
ar
e
d
N Element
et Data Range
w in Array is R
or sequence<long,4> [0..65535],a -
k nd W
Ar separated by
e ";".
a
C
o
d
e
H
S
P
A
S
u
0:Not Support HSUPA and
p R
HSDPA,1:Support HSDPA and
p -
DCH,3:Support HSUPA, HSDPA and
or W
DCH,<default:3>
t
M
et
h
o
d
F- 0:Supported,1:Not Supported,<default:1> R
D -
P W
C
H
S
u
p
p
or
t
In
di
c
at
or
N
ei
g
h
b
or
in
g
C
ell
E
n
h
a
n
c
R
e
0:Supported,1:Not Supported,<default:1> -
d
W
F-
D
P
C
H
S
u
p
p
or
t
In
di
c
at
or
M
I
M
O
S
u
p R
p 0:Not Supported,1:Supported,<default:0> -
or W
t
In
di
c
at
or
M 0:Not Supported,1:Supported,<default:0> R
i
m
o
6
4
Q
a
m
S
-
u
W
p
p
or
t
In
di
c
at
or
6
4
Q
A
M
D
L
S
R
u
p
W
p
or
t
In
di
c
at
or
A 0:Not Supported,1:Supported,<default:0> R
dj -
a W
c
e
nt
C
ell
U
pli
n
k
E
n
h
a
n
c
e
d
L
a
y
er
2
S
u
p
p
or
t
In
di
c
at
or
Fl
e
xi
bl
e
M
A
C
-d
P
D
U
R
Si
z
W
e
S
u
p
p
or
t
In
di
c
at
or
D 0:Not Supported,1:Supported,<default:0> R
u -
al W
-
C
ell
H
S-
D
S
C
H
S
u
p
p
or
t
In
di
c
at
io
n
Pr
i
m
ar
y
C
PI
C
H
P
o
R
w
0:False,1:True,<default:0> -
er
W
C
o
nf
ig
ur
at
io
n
T
a
g
C
ell
D
e
sc
ri R
0:Center Point with Altitude and Cell
pt -
Radius,1:Polygon,2:Arc,<default:0>
io W
n
T
y
p
e
S 0:Off,1:On,<default:1> R
wi -
tc W
h
of
C
S
6
4
k
b
p
s
E
st
a
bli
s
h
m
e
nt
fo
r
E
xt
er
n
al
U
T
R
A
N
C
ell
D 0:False,1:True,<default:0> R
el -
ta W
Q
rx
le
v
m
in
in
SI
B
1
1
C
o
nf
ig
ur
at
io
n
T
a
g
T
U
T
R
A
N
-
G
P
S
M
e
a
s
R
ur
e
W
m
e
nt
S
u
p
p
or
t
In
di
c
at
or
2
m
s
E-
T
TI
S
u R
p W
or
t
In
di
c
at
or
E- 0:SF8,1:SF4,2:2SF4,3:2SF2,4:2SF2 and R
D 2SF4,<default:4> -
C W
H
S
F
C
a
p
a
bil
ity
E-
D
C
H
H
A
R
Q
C
o 0:IR Combining Capable,1:Combining R
m Capable,2:IR and Chase Combining -
bi Capable,<default:2> W
ni
n
g
C
a
p
a
bil
ity
M
a
x
U
E R
0:5,1:10,2:20,3:40,4:64,5:80,6:128,7:160,<d
D -
efault:7>
T W
X
C
yc
le
C 0:Not Supported,1:Supported,<default:1> R
P -
C W
D
T
X-
D
R
X
S
u
p
p
or
t
In
di
c
at
or
C
P
C
H
S-
S
C
C
H
le
R
ss
S
W
u
p
p
or
t
In
di
c
at
or
Tr
a
n
s
p
or
R
t
0:20ms,1:100ms,2:400ms,<default:0> -
Ti
W
m
e
D
el
a
y
Tr long:[0..100],<default:5> R
a -
n W
s
p
or
t
Ti
m
e
D
el
a
y
Jit
te
r
E
xt
er
n
al
U
T
R
A
N
C
ell
D
u
al
C R
ell 0:Not Supported,1:Supported,<default:0> -
+ W
M
I
M
O
S
u
p
p
or
t
In
di
c
at
or
Si 0:Not Supported,1:Supported,<default:0> R
xt -
e W
e
n
Q
A
M
U
L
S
u
p
p
or
t
In
di
c
at
or
E-
D
P
C
C
H
P
o
w
er
B
o
o R
sti 0:Not Supported,1:Supported,<default:0> -
n W
g
S
u
p
p
or
t
In
di
c
at
or
C 0:Not Supported,1:Supported,<default:0> R
ell -
M W
I
M
O
Pr
e
c
o
di
n
g
W
ei
g
ht
S
et
R
e
st
ri
cti
o
n
S
u
p
p
or
t
In
di
c
at
or
Cl
a
ss
ifi
e
d
Z R
o 0:False,1:True,<default:0> -
n W
e
In
di
c
at
or
D
B
D
C
-
H
S
D
P
A
S
u R
p W
or
t
In
di
c
at
or
o
n
Iu
r
N long:[0..10],<default:0> R
u -
m
b
er
of
D
B
S
e
c
o
n W
d
ar
y
S
er
vi
n
g
C
ell
[D
B
S
e
c
o
n Element
d Data Range
ar in Array is R
y sequence<long,10>,<default:null> [0..65535],a -
S nd W
er separated by
vi ";".
n
g
C
ell
ID
]
D
R
N
C
R
C
0:Macro Cell,1:Micro Cell,<default:0> -
ell
W
T
y
p
e
E 0:Not Supported,1:Supported,<default:0> R
xt -
er W
n
al
U
T
R
A
N
C
ell
D
u
al
B
a
n
d
D
u
al
C
ell
+
M
I
M
O
S
u
p
p
or
t
In
di
c
at
or
D 0:Not Supported,1:Supported,<default:0> R
C -
- W
H
S
U
P
A
S
u
p
p
or
t
In
di
c
at
or
o
n
Iu
r
S
e
p
ar
at
e
Iu
r
Tr
a
n
s
p
or
R
t
B
W
e
ar
er
S
u
p
p
or
t
In
di
c
at
or
E- 0:Not Supported,1:Supported,<default:0> R
D -
C W
H
U
L
Fl
o
w
M
ul
ti
pl
e
xi
n
g
S
u
p
p
or
t
In
di
c
at
or
M
a
x
N
u
m
b
er
of
H
S-
D
S
C
H
S
e R
c long:[0..10],<default:0> -
o W
n
d
ar
y
S
er
vi
n
g
C
ell
o
v
er
Iu
r
P sequence<long,10>,<default:null> Element R
o Data Range -
ss in Array is W
ibl [0..65535],a
e nd
S separated by
e ";".
c
o
n
d
ar
y
S
er
vi
n
g
C
ell
ID
Li
st
o
v
er
Iu
r
M
ul
tic
ell
E-
D
C
Element
H
Data Range
R
in Array is R
e
sequence<long,10>,<default:null> [0: FALSE,1: -
st
TRUE],and W
ri
separated by
cti
";".
o
n
o
v
er
Iu
r
4.4 UExternalGSMCell
4.5 UExternalENodeBFunction
4.6 UExternalEUTRANCellFDD
4.7 UExternalEUTRANCellTDD
4.8 UUtranRelation
Table 4-4 UUtranRelation
Desc Re
Parameter
Parameter Value riptio ma
Name
n rks
Pri
[Managed ma
Element Object long:[1..4095] ry
ID] Ke
y
Cann
ot
use
invali
d
R-
User Label string:[0..80] chara
W
cter
&,'"<
>#
%/\?
@
Pri
ma
RNC ID long:[0..4095] ry
Ke
y
Pri
ma
Cell ID long:[0..65534] ry
Ke
y
Target RNC ID long:[0..4095] Pri
ma
ry
Ke
y
Pri
ma
Target Cell ID long:[0..65535] ry
Ke
y
Measurement
R-
Priority of long:[0..2],<default:0>
W
Neighboring Cell
Share Cover 0:Neighbor,1:Overlap,2:Covers,3: R-
Indication Contained in,<default:0> W
UE State
0:Cell Selection/Reselection
Indicator Used
Only,1:Handover only,2:Cell R-
for UTRAN
Selection/Reselection and W
Neighboring Cell
Handover,<default:2>
Configuration
Cell Individual double:[- R-
Offset 10..10],<default:0>,step:0.5 W
Broadcast in
R-
either SIB11 or 0:SIB11,1:SIB11bis,<default:0>
W
SIB11bis
Use of HCS in R-
1:Not Used,2:Used,<default:1>
Cell Reselection W
Quality Offset 1
Between
Serving Cell and
R-
Neighbouring long:[-50..50],<default:0>
W
Cell
Broadcasted in
SIB11
Quality
Threshold
Level(Qhcs) of
R-
Neighbouring long:[-50..50],<default:0>
W
Cell
Broadcasted in
SIB11
Quality
Threshold Level
for Applying
Prioritised
Hierarchical Cell
Reselection
(Qhcs) of double:[-24..0],<default:- R-
Neighbouring 10>,step:0.5 W
Cell When
Measurement
Quantity is
CPICH Ec/No
Broadcasted in
SIB11
Quality
Threshold Level
for Applying
Prioritised
Hierarchical Cell
Reselection
(Qhcs) of R-
long:[-115..-26],<default:-90>
Neighbouring W
Cell When
Measurement
Quantity is
CPICH RSCP
Broadcasted in
SIB11
Quality
Threshold Level
for Applying
Prioritised
Hierarchical Cell
Reselection
(Qhcs) of double:[-24..0],<default:- R-
Neighbouring 10>,step:0.5 W
Cell When
Measurement
Quantity is
CPICH Ec/No
Broadcasted in
SIB12
Quality
Threshold Level
for Applying
Prioritised
Hierarchical Cell
Reselection
(Qhcs) of R-
long:[-115..-26],<default:-90>
Neighbouring W
Cell When
Measurement
Quantity is
CPICH RSCP
Broadcasted in
SIB12
1:Not Used(Not
Penalty Time in Used),2:10(10),3:20(20),4:30(30), R-
SIB11 5:40(40),6:50(50),7:60(60),<defau W
lt:1>
Temporary 0:3(3),1:6(6),2:9(9),3:12(12),4:15( R-
Offset When 15),5:18(18),6:21(21),7:inf(inf),<d W
Measurement efault:0>
Quantity is
CPICH
RSCP(Temporar
y_offset1)
Broadcasted in
SIB11
Temporary
Offset When
Measurement
Quantity is 0:2(2),1:3(3),2:4(4),3:6(6),4:8(8),5
R-
CPICH :10(10),6:12(12),7:inf(inf),<default
W
Ec/No(Temporar :0>
y_offset2)
Broadcasted in
SIB11
Quality Offset 1
(Qoffset1s,n)
Between
Serving Cell and R-
long:[-50..50],<default:0>
Neighbouring W
Cell
Broadcasted in
SIB12
Quality Offset 2
(Qoffset2s,n)
Between
Serving Cell and R-
long:[-50..50],<default:0>
Neighbouring W
Cell
Broadcasted in
SIB12
1:Not Used(Not
Penalty Time in Used),2:10(10),3:20(20),4:30(30), R-
SIB12 5:40(40),6:50(50),7:60(60),<defau W
lt:1>
Temporary_offs
et(Temporary_of
0:3(3),1:6(6),2:9(9),3:12(12),4:15(
fset1) for CPICH R-
15),5:18(18),6:21(21),7:inf(inf),<d
RSCP W
efault:0>
Broadcasted in
SIB12
Temporary_offs
et(Temporary_of
0:2(2),1:3(3),2:4(4),3:6(6),4:8(8),5
fset2) for CPICH R-
:10(10),6:12(12),7:inf(inf),<default
EC/No W
:0>
Broadcasted in
SIB12
White List Cell R-
0:False,1:True,<default:0>
Indicator W
Black List Cell R-
0:False,1:True,<default:0>
Indicator W
4.9 UGSMRelation
4.10 UEUtranRelation
4.11 UImsiSnacFilter
4.12 UMbms
4.13 UMbmsSa
4.14 UMbmsFreq

5 Special Subject
5.1 ICM Data Configuration Flow (All-Parameter

Configuration)
ICM (Integrated Configuration & Management) is tool used for configuration data storage,
management, analysis, and conversion. It can be used to configure and optimize the data
of the whole network. It can import the configuration data obtained from CNO or after
manual modification.
ICM can also compare the existing network data, history data, plan data, and the backup
data in the plan area, providing a necessary reference for planning configuration data.
Figure 5-1 ICM Data Area
Description of different ICM data areas:
 Live Data Area: ICM synchronizes the configuration data running in the existing network
from OMMR to Live Data Area. This data is used as a reference for data modification.
 Live Data: The latest configuration data under the current node in the Live Data Area.
 History data: The backed-up configuration data under the node in Live Data Area
(usually named as AutoBackup).
 Plan Data Area: To make sure multiple users can operate on ICM at the same time.
Data importing, exporting, and activation can be performed Plan Data Area by Plan
Data Area.
 When a Plan Area is created, the Live Data of the NEs in the subnetwork selected will
be copied to the Plan Data and Reference Data of the Plan Area.
 Plan Data: The data that can be modified in Plan Area. Copy the master plan data from
the Live Data Area and create slave plan data manually. The Import, Export, and
Activate operations are for master plan data.
ICM supports two types of template configuration:
 Plan Template: It is the quick configuration template on OMMR. The plan template uses
a simplified filling method, i.e., the values of the parameters not displayed in the
template will be calculated with the fixed method and will be generated automatically.
Plan template consists of three templates: Equipment template, TransportNetwork,
template, and UMTS Radio template. This template can be used on both OMMR and
ICM.
 MO Template: It can only be operated through ICM and is similar to the OMMR MO
Template. It consists of two templates: Uni Ground template and UMTS Radio
template.
5.1.1 ICM Initialization
Open EMS client, choose Configuration > Plan Data Management, and open

the Plan Data Management window.
Figure 5-2 Plan Data Management
Click Live Data Area, and select the record of the target OMMR in the dialog box on the
right. Right-click the record and choose Synchronize to synchronize ICM live data area
and OMMR data and start manually the synchronization between the live data area and
OMMR.
Figure 5-3 Live Data Area Synchronization
Note:
ICM can only synchronize data with the snapshot area of the OMMR, because the snapshot area is always
consistent with RNC and the data can be used as the reference.
If the data in the snapshot area is changed (i.e., the data is synchronized from OMMR to RNC) ICM will
monitor this operation in real time and trigger data upload automatically. This can make sure the data in the
live data area of ICM is consistent with that in snapshot area of OMMR, i.e., consistent with the RNC data.
If data upload cannot be triggered automatically, it is necessary to perform data upload manually with the
method mentioned above.
5.1.2 Exporting Optimization Template (All Parameters)
Choose Live Data Area, right-click the target OMMR subnet and choose Export to export
all parameters.
Figure 5-4 Exporting Optimization Template on ICM
Select the type of the data to be exported in Data Type, e.g., UMTS Radio for UMTS radio
data and Uni_Ground for ground data, and click Next. InFigure 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.

Figure 5-6 Storage Path of Exported File
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, but because the data in
Live Data Area is consistent with the RNC data fixedly, it is recommended to export the Optimization
Template from Live Data Area.
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, right-click the record of the target OMMR subnet and
choose Create Plan 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 Plan Area
Figure 5-11 Confirm Message Box
5.1.3.2 Importing Template
Right-click the target Plan_Area under Data Area, and choose Import to import data.
Figure 5-12 Import Template
1. Importing Plan Template

In the Data Import window, choose Plan, and modify Data Type to the type of the data to
be imported, such as, Uni_Ground/Uni_Office for ground data, and UMTS Radio for radio
data.
Figure 5-13 Import Plan Template
Right-click the imported file record and choose View Detail to view the details of the
imported file.
The importing result will be automatically saved under the path in the red box in the figure
below.
Note:
When importing the Plan Template from ICM, pay attention to the following two points:
In the Plan template, the ME ID field can be left un-configured. This is different from the rules of OMMR.
The Data Type selected should match with the template name, as shown below:
Uni_Ground for V3_Template_Equipment.xls
Uni_Office for V3_Template_TransportNetwork.xls
UMTS Radio for UMTS Radio Quick Configuration Template.xls
2. Importing Optimization Template

In the Data Import window, choose Optimization, and modify Data Type to the type of the
data to be imported, such as, Uni_Ground for ground data, and UMTS Radio for radio data.
Click Import to import the template.
Figure 5-14 Import Optimization Template
The process of importing Optimization Template is the same as that of importing Plan
Template. Check whether the number of successful records in Succeed/All Counts is the
same as the number of all records. If it is, the template is loaded successfully.
Note:
When importing the Optimization Template from ICM, pay attention to the following 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:
Uni_Ground for 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 the target Plan_Area under Data Area, and choose Check to perform data

validity check.
Figure 5-15 Check
In the pop-up Data Check-Validity window, click OK to start data validity check. By
default, “Full Data” and “All Rules” will not be selected, because the system will use the
most efficient way to perform the operation by default. If there is no special
requirement, do not select these two items.
Figure 5-16 Data Check-Validity
After validity check is completed, observe the import result in the figure below. If Validity is
“Pass,” it means the validity check succeeds.
Figure 5-17 Check Result
If there is some error found in the check process, the number of ERROR/WARN records
will be displayed in Result. If there are ERROR records, please check whether the data is
correct. Otherwise, the configuration cannot be activated. If there is only the WARN record,
the activation can be performed normally. This record will appear when the optional global
validity check fails to pass, and the detailed information is displayed in the CSV file under
the path in Detail.
5.1.3.4 Conflict Check
Choose the Conflict tab and click OK to start conflict check.
Figure 5-18 Conflict
Before conflict check is started, the following dialog box will pop up. Confirm the live data is
synchronized and click OK.
Figure 5-19 Confirming 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
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 Data
5.1.3.6 Data Activation
Choose Activate to display the Activation Management window.
Figure 5-22 Activating Data
Click the Add button to open the Activation task management tab, and add the plan area
to be activated to the Selected Plan Area. Fill in the Task Name and click OK.
Figure 5-23 Activating Task Management
Choose the task to be activated. Right-click the task and choose Compare to Get Delta to
create incremental data.
Figure 5-24 Compare to Get Delta
Observe the execution result in Status in the record and the Result in the log.
Figure 5-25 Compare Success
Right-click the task and choose Download to download data.
Figure 5-26 Download
Figure 5-27 Download Success
Right-click the task and choose Activate to activate data.
Figure 5-28 Activating Data
Figure 5-29 Activate Success
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. 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 the Plan Area to be deleted, and choose Check. Choose the Submit tab in the
pop-up dialog box, and observe whether the status is “Editing.” If it is, it is necessary to
click To Edit and switch the status to “Editing.”
Figure 5-31 Switching Submit Status
5.1.4.3 Deleting Plan Area
After the above two checks are completed, the Plan Area can be deleted.
Right-click the Plan Area to be deleted and choose Delete.
Figure 5-32 Deleting Plan Area
Click OK to confirm the delete operation.
Figure 5-33 Confirming Plan Area Deletion
Note:
In the in-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.
5.2 CMP Module No. Modification

Get the V3_Template_TransportNetwork template, open the IUB Office sheet, modify the
value of MODIND to “M,” and fill in a proper value for Primary Key and Module respectively
to import the quick configuration template. The system will modify the home module No. of
Iub link, Association, and Transmission Path Group accordingly.
Figure 5-34 CMP Module No. Modification
5.3 Overall Office Information Deletion (Including

Ground & Radio Resources)
Acquire the “V3_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 Overall 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 V3_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
ATMoSTM-
No. IPoE1+IPoFE IPoE1 IPoFE ATMoE1 ATM+IP
1
IUB IUB IUB
1 IUB Office IUB Office IUB Office
Office Office Office
UMTS
SCTP ATM SCTP
SCTP Config SCTP ATM
2 Config Bearer Config
(IUB) Config (IUB) Bearer(IUB)
(IUB) (IUB (IUB)
Auto)
IP
IP Bearer IPOE IP Bearer
3 Bearer
(IUB) Bearer (IUB) (IUB)
(IUB)
IPOE Bearer Static Static
4 Static Route
(IUB) Route Route
IP Path IP Path
5 Static Route
Group Group
UMTS
ATM
IP Path
6 Bearer
Group
(IUB
Auto)
Modify the value of MODIND in the IUB Office sheet to “S.”
Figure 5-36 Site Bearer Migration
Load the IUB Office sheet first, and then load other sheets.
Note:
Make sure the IUB Office sheet is loaded before other sheets and they are loaded by two separate templates.
5.5 PVC Configuration

The PVC traffic parameters include L2HtrfType and L2HtrfPara1 to L2HtrfPara5 and the
corresponding high traffic to low traffic type and parameters, all of which are used to define
the traffic bandwidth and characters on both receiving and sending directions of PVC.
In the quick configuration version in V3 non-MO 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-37 Configuring PVC in V3 Non-MO Version
From the V3 MO version, all the parameters related to traffic parameters are displayed. The
engineer can choose the corresponding parameters according to onsite situation.
Figure 5-38 Configuring PVC in V3 MO Version
The relation of PVC traffic type, traffic parameter, and PVC service type is shown in the
following table:
Table 5-2 Relation of PVC Traffic Type, Traffic Parameter, and PVC Service Type
Servic Para Para Para

Traffic Type Para1 Para2
e Type 3 4 5
PCR0+
atmClpNoTaggingNoScr (3) PCR0
1
PCR0+
atmClpTaggingNoScr (4) PCR0
1
PCR0+
cbr atmNoClpNoScr (2)
1
PCR0+
atmClpTransparentNoScr (9) CDVT
1
PCR0+
atmNoClpNoScrCdvt (12) CDVT
1
PCR0+
atmNoClpNoScr(2)
1
PCR0+
atmClpNoTaggingNoScr(3) PCR0
1
PCR0+
atmClpTaggingNoScr(4) PCR0
1
PCR0+
atmClpNoTaggingScr(6) SCR0 MBS
1
atmClpNoTaggingScrCdvt(14 PCR0+ CDV
SCR0 MBS
rtVbr ) 1 T
ntrVbr PCR0+
atmClpTaggingScr(7) SCR0 MBS
1
PCR0+ CDV
atmClpTaggingScrCdvt(15) SCR0 MBS
1 T
PCR0+ SCR0+ CDV
atmClpTransparentScr(10) MBS
1 1 T
PCR0+ SCR0+ CDV
atmNoClpScrCdvt(13) MBS
1 1 T
PCR0+ SCR0+
atmNoClpScr(5) MBS
1 1
PCR0+
abr atmClpNoTaggingMcr(8) CDVT MCR
1
ubr atmNoTrafficDescriptor(1)
PCR0+
atmNoClpNoScr(2)
1
atmNoClpNoScrCdvt(12) PCR0+ CDVT
1
PCR0+
atmNoClpTaggingNoScr(11) CDVT
1
PCR0+ CDV
ubr+ atmTrafficForUbr+(16) MCR MBS MFS
1 T
PCR0+1: Peak cell rate for CLP=0+1
PCR0: Peak cell rate for CLP=0
CDVT: Cell delay variation tolerance
SCR0: Sustainable cell rate for CLP=0
SCR0+1: Sustainable cell rate for CLP=0+1
MBS: Maximum burst cell number
MCR: Minimum cell rate
MFS: Maximum frame size
Note:
For different PVC service types, only the corresponding traffic types in the above table can be used.
All the parameters in the above table should be configured as integer numbers.
In the running system, in order to modify PVC traffic parameters safely, block the upper-level applications
associated with PVC, such as AAL2PATH and ATMSIGLINK, before modifying the parameters. Otherwise,
call loss may occur.
5.6 ATM Address Conversion

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

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

Starting from 310P, the RNC system supports scenarios where the user-plane IP
addresses are separated according to the protocol interfaces (IUB/CS/PS/R). The
configuration for different interfaces is different.
5.7.1 Mapping between RUB Board Quantity & Service IP
5.7.1.1 Calculation Method
1. The user-plane addresses need to be allocated to different RUB boards, so there

is a mapping relation between the boards and the IP addresses, such as, how many
RUB boards need to be allocated with one IUX user-plane address.
For the old RNC V3.10 version that does not support separated user-plane IPs, the
rules are:
 One IP for every five RUB boards;
 One IP for every two RUB2 boards;
2. If separated user-plane IP addresses are not used in the new U9.3 version, the
above rules can still be used. If separated user-plane IP addresses are required, the
following formula should be used to guide the configuration.
The number of RUB boards supported by each IUX user-plane IP=
(Maximum number of port Nos. supported by RNC – Number of port Nos. for other uses) / (Total
number of UDPs occupied by IUX * Number of DSPs supported by each RUB board)
If the result is a decimal, please round up the value to get the number of the RUB boards
supported by each IUX user-plane IP.
5.7.1.2 Description of Calculation Formula Related Parameters
1. Max. number of port Nos. supported by RNC:

It is the upper limit for UDP ports. The value should be 65535, but considering the
round-up calculation, the largest UDP Port No. is defined as 64999 in RNC.
2. Number of port Nos. for other uses:

In RFC, it is clearly specified that the UDP port Nos. smaller than 1024 are all
registered. Therefore, do not use these UDP Port Nos. in RNC equipment. Because
the IUPS data contains the nominated Port No. 2152, which is specified in the GTPU
protocol, do not use 2152 for UDP port No. for non-IUPS data. Besides, considering
the influence of later RFC changes and expansion over the equipment, do not use the
UDP Nos. smaller than 5000. Therefore, the smallest UDP No. in RNC is 5000. The
UDP Port No. starts from 5000, which means 5000 can also be used. Therefore, Port
Nos. from 1 to 4999 are excluded.
3. Number of UDPs occupied by IUX:

Table 5-4 shows the values of the UDP port Nos. on different interfaces. This is for
each DSP on the RUB board. IUPS type is not related to the number of UDP ports for
service IP. For the service IP with mixed types, the number of UDP ports is the sum of
UDP ports in each type.
Table 5-4 UDP Port No. Allocation
User-plane Processing Modified Number of

Interface Type
Board Type Port Nos.
IUB VTCD 373
VTCD2 1119
IUR VTCD 106
VTCD2 318
IUCS VTCD 178
VTCD2 534
Total VTCD 657
VTCD2 1971
User-plane Processing Board Type: 80 CS users on VTCD, 80 instances; 160 CS
users on VTCD2, 400 instances; 500 CS users on SBCJ, 1320 instances.
Modified Number of Port Nos.: 1. Number of CS users on VTCD2 increased to 400;

2. Take the 2/3 of the calculated value; 3. Make sure the number of ports occupied on
VTCD is an integer multiple of that occupied on VTCD2.
Note:
Suppose every resource shelf is configured with six RUB2 boards, we can get the following result according to
the above formula:
One IUCS user IP can be provided to (64999-4999)/(534×15)=7.49 RUB2 boards for use, which is rounded
down to 7, i.e. 7 RUB2 boards.
One IUPS user IP can serve one board in the resource shelf.
One IUR user IP can be provided to (64999-4999)/(318×15)=12.57 RUB2 boards for use, which is rounded
One IUB user IP can be provided to (64999-4999)/(1119×15)=3.57 RUB2 boards for use, which is rounded
There are 6 RUB2 boards in each resource shelf, the number of addresses needed by each resource shelf is:
Configure 1 for IUCS, 1 for IUPS, 1 for IUR, and 2 for IUB. When configuring DSP IP, use the first IUB
address for the first three boards and use the second IUB address for the last three boards.
5.8 Special Subject About Module No.
5.8.1 Introduction to CMP/DMP
For RNC, there are two boards that need to be allocated with Module No., i.e., ROMB and
RCB. The Module No. ranges from 1 to 127.
For RNC V3.11 and later versions, two modules of RCB are changed a little, i.e., SMP is
deleted, and DMP is added, but this is not a function replacement. Instead, the function of
SMP is integrated into CMP, and DMP processes the calls of UE users alone. The range of
CMP module No. is 3-18. DMP module No. is from 32 to 127. Both CMP module No. and
DMP module No. are allocated starting from small numbers (e.g., CMP module No. is
allocated from 3, and DMP module No. from 32).
Table 5-5 Value Range of Module No.
Function Unit Module No.

ROMP 1
RPU 2
CMP 3 – 18
DMP 32 – 127
The first four CMP module Nos., i.e., 3, 4, 5, and 6, are allocated to the Iu interface
according the function specifications. The other 12 Nos., from 7 to 18, are allocated to the
Iub interface. When there are enough module Nos., do not use the CMP module No. of the
Iu interface as that of the Iub interface, and vice versa. (e.g., the CMP module No. of the IU
interface must be allocated from 3, and the CMP module No. of the IUB interface must be
allocated from 7).
The rules of configuring module No. are as shown in Table 5-6.
Table 5-6 Rules of Configuring Module No.
Function Module
Basic Configuration Rules
Unit No.
All boards (except ROMB/RCB) must be allocated to ROMP
ROMP 1
Module 1.
RPU 2 The virtual address should be configured on RPU Module 2.
It is used to process the IU-interface signaling and CN-office
path/path group.
CMP(IU) 3–6 Each module supports 32 IU-interface SCTP links at most.
The association links must be allocated evenly among the
modules.
It is used to process cells.
CMP(IUB) 7 – 18 All objects of the same NodeB must be allocated to the same
module No., and the NodeBs must be allocated evenly among
the modules.
32 – It is necessary to select the module Nos. when creating
DMP
127 boards, and there is nothing else to be configured.
Note:
1. DMP/CMP on the same board is prohibited (the 2 modules on an RCB must be either CMP or DMP).
2. The RCB of CMP must be in master/slave configuration. The RCB of DMP must be set as “NONE,” and
all DMPs should act as a resource pool by default.
5.8.2 D/C Module No. Planning Solution for Newly-Commissioned Sites
Table 5-7 provides the allocation proportion rule for the D/C module No. of a newly-
commissioned site, and it does not cover all scenarios. Instead, it is only a reference for
quick data planning.
Table 5-7 Recommended D/C Module No. Planning for Newly-Commissioned Sites
Total
Number CMPNotIub CMPIub DMP Site Cell BHCA(K) OL(K)
of RCBs
4 1 1 2 250 500 1000 9
6 1 3 2 750 1500 1000 12
8 1 3 4 750 1500 2000 24
10 1 3 6 750 1500 3000 27
12 1 5 6 1250 2500 3000 36
14 1 5 8 1250 2500 4000 45
16 1 7 8 1750 3500 4000 48
18 2 6 10 1500 3000 5000 54
20 2 8 10 2000 4000 5000 60
22 2 8 12 2000 4000 6000 72
24 2 8 14 2000 4000 7000 72
26 2 10 14 2500 5000 7000 84
28 2 10 16 2500 5000 8000 90
30 2 10 18 2500 5000 9000 90
32 2 12 18 3000 6000 9000 108
34 2 12 20 3000 6000 10000 108
37 3 13 21 3250 6500 10500 117
 Tip:
The “CMPNotIub” and "CMPIub” (number) in Table 5-7 refer to the number of master CMP modules. Both should
be in 1+1 master/slave configuration and thus the number of master CMP modules should be the same as the
number of boards.
The “DMP” in the above table refers to the number of DMPs. Each board has two DMP modules.
Take “20” as an example for “Total Number of RCBs.” It can be learnt from the above table that it is necessary
to configure two CMPNotIub modules and eight CMPIub modules, i.e., 10 master CMP modules in total. Because
each board has two modules, five master CMPs are needed, and therefore 10 CMP boards are needed for
master/slave CMP configuration. According to the above table, the number of DMPs is “10,” and therefore the
number of DMPs to be configured is “10*2=20.”
5.9 Implicit BFD

RNC supports static route configuration. For each destination IP, at most eight routes
can be configured. The RNC is connected directly to every next-hop IP. If the BFD
auto-detection function (configuration parameter: BFDFLG) is enabled in static route
configuration, the system will bind and create the BFD detection instance for every
next-hopping path described by the static route and start the real-time detection
function, once the user configures static route.
The BFD session based on static route is the implicit BFD function. Under this
configuration, the user does not need to configure any session parameters, and the
system will use the default value. No certification policy will be used for the
establishment of BFD session.
If the default parameters are used, the parameters should be configured the same at
the CE side.
Table 5-8 Default Parameters of Implicit BFD
PARAMETER NAME VALUE

BFD Mode: Asynchronous mode
Authentication Type not authenticated
Minimum Transmitting Interval (ms) 200 milliseconds
Minimum Received Interval (ms) 200 milliseconds
Detection Time Multiplier 2
Hop Mode Single-hop
5.10 Configuration of the IUB Bandwidth
5.10.1 E1 Bearer
The quantity of PVC and the bandwidth, which are generated by the quick data
configuration tool for RNC or SDR, are based on the results in the bandwidth configuration
tool.
5.11 Special Subject About GIPI/GIPI3/GIPI4 Board

Backup
There are two kinds of backup for GIPI boards: load-sharing (NONE) and Master-Slave.
5.11.1 Comparison Between Load-Sharing Backup & Master-Slave Backup
Load-sharing backup mode is recommended for on-site planning & configuration because
of the following four points:
When load-sharing mode is used, both GIPI boards will work simultaneously all the time
and share the transmission work of the IP network together. The maximum traffic of the
interface is the sum of the traffic on all load-sharing ports. Under master-slave
configuration, only one GIBI works normally at one time. The traffic of the interface is only
the traffic of a single port, i.e., half of the traffic for load-sharing mode.
The load-sharing mode used by our company is a routing-realized multi-channel
transmission path. Therefore, when there is some fault on one board, the load-sharing
mode is the same as the dual-Rx mode. In this sense, its capacity of protecting service
from being interrupted is better than that of the master-slave mode.
The two boards of the load-sharing mode are independent from each other. Thus, we can
switch boards or change the configuration flexibly to meet some special rectification
requirements. If master-slave configuration is used, the two boards must be operated
simultaneously, such as, rectifications, swaps, and other major operations. In this case, the
service protection solution will be less flexible.
The two boards of the load-sharing mode are configured separately, it is not necessary to
monitor the status of the peer port (i.e., no matter whether the peer port is down or not, our
equipment can receive packets as long as there is one port sending packets).But this is not
the case for the master-slave mode. If the peer-end equipment (PTN or MSTP) is not an L2
switch or there is no build-in L2 switching function between the master and slave ports, by
default, our 1+1 master-slave policy cannot work with the peer-end equipment. In this case,
it is necessary to perform relative configuration (Port Switch) to monitor the peer port
status. Make sure our master port can synchronize with the peer-end and switch services to
the new master port (original slave port) immediately, when there is a fault on the master
port of the peer end.
5.11.2 Notices in Master-Slave Configuration
5.11.2.1 Port Switch
There are three types of port switch under master-slave configuration.
1. Default: Switch triggered by the changes in the RX signal strength.
2. Follow the way:

The system can detect and follow the switchover of the peer-end equipment automatically
according to the received packets. Besides monitoring the RX physical signals, the
master/slave ports collect the real-time statistics of the packets received, including the
statistics of the packets received on the slave port but not received on the master port when
there is no fault on the physical port. The system will trigger master/slave port switchover,
and the working port will be transferred to the original slave port. After the switchover
finishes, the new slave port will be closed temporarily and stops transmitting physical
signals for 10 seconds, so that the peer-end equipment can detect the master-slave
switchover process of the local equipment synchronously.
3. AH function based on:

The system can make the switch decision according to the result monitored by the
IEEE802.3ah protocol of the master and slave ports. The master port at the RNC side
judges the link accessibility by the 802.3ah heartbeat detection. If there is a link fault, the
system will trigger master-slave port switchover automatically.
5.11.2.2 Application of Port Switch
Scenario 1
Usually, it is required that our GE interface board use 1+1 master-slave mode. In the
integration with peer-end equipment (PTN or MSTP), if the peer-end uses L2 switch or
there is the build-in L2 switch function between the master and slave ports, our default 1+1
master-slave policy can meet the requirement of this scenario.(The default switch mode
needs no configuration).
Scenario 2:
If 1+1 master-slave mode is required for our GE interface board, but the peer-end
equipment does not satisfy the above requirement, it is possible that our equipment cannot
coordinate with the peer-end equipment. To guarantee interoperability, please select “AH
function based on” or “Follow the way” according to the actual situation.(Configure Port
Switch).
Scenario 3:
If the networking of the peer-end equipment cannot satisfy the requirement of Scenario 1
and its switchover system cannot coordinate with or satisfy the requirement of Scenario 2,
the master-slave mode cannot be used normally.
5.11.2.3 Configuring Port Switch
Port switch is configured on the attribute configuration interface of the GIPI board, as
shown in Figure 5-40.
Figure 5-40 Port Switch
Note:
For the master-slave configuration:
1. If the optical port and the electrical port of GIPI/GIPI3/GIPI4 are configured with self-
adaption, it is not necessary to configure Switch Type.
2. If the optical port and the electrical port of GIPI/GIPI3/GIPI4 are configured with the
forced mode, the Switch Type needs to be configured. Under this mode, our Tx
transmission will be stopped and the peer-end will follow the switchover when our
equipment has problems in Rx and Tx transmission.
MNIC_2 provides an optical port. If there is some problem with the optical port, board switchover will be
performed.
MNIC_3 provides two external optical ports. When both ports are abnormal, board switchover will be
performed.
Besides 1+1 configuration, when the LACP of the Backup mode is used, the member ports of the LACP group
can use the above three fault detection and switchover modes (“Follow the way” should be used in priority,
i.e., perform switchover according to the statistics of the packets received by the Rx port), provided the
switchover mode of the interface board of all the member ports is consistent.

ZTE Quick Commissioning Guidelines

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZTE Quick Commissioning Guidelines

Hochgeladen von

Copyright:

Verfügbare Formate

1 Notices in Data Configuration

1.1 Restrictions on Configuration Planning

2 Introduction to Quick Data Configuration

3 Equipment Template and Transport Network Template Configuration

4 UMTS Radio Template Configuration Specifications

1 Notices in Data Configuration

1.1.1 Boards & Slots

Table 1-1 Restrictions on Boards & Slots

No. Board Type Restrictions

Table 1-2 IP Planning Related Restrictions

2 Introduction to Quick Data Configuration

3. UMTS Radio Quick Configuration Template

Figure 2-1 Template Importing Flow

2.1 Overview of Plan Templates

2.1.1 Template Info Sheet

Figure 2-2 Template Info Sheet

The fifth line of the template is parameter attributes, as shown in Figure 2-4.

Parameter Attributes Meaning Description

2.1.4.1 Introduction to Equipment Template

2.1.4.2 An Example of Filled Equipment Template

The template is corresponding to OMMR V12.13.15.

2.1.5 Transport Network Template

2.1.5.1 Introduction to Transport Network Template

Figure 2-6 shows the sheets included in the “Transport Network” template. Transmission

1. Sheets for IU/IUR and IUB

Table 2-2 Sheets to Be Configured for IU/IUR and IUB

No. IU/IUR IUB

Table 2-3 Sheets to Be Configured for Different IUB-Interface Bearers

3. Sheets for different bearers on the IU/IUR interface

Table 2-4 Sheets to Be Configured for Different IU/IUR-Interface Bearers

No. IUCS/R(ATM) IUCS/PS/R(IP) IUPS(IPOA)

2.1.5.2 An Example of Filled Equipment Template

The template is corresponding to OMMR V12.13.15.

2.1.6 UMTS Radio Template

2.1.6.1 Introduction to UMTS Radio Template

Figure 2-7 UMTS Radio Quick Configuration Template

Figure 2-8 UMTS Radio Template

2.1.6.2 An Example of Filled UMTS Radio Template

The template is corresponding to OMMR V12.13.15.

UMTS Radio Quick Configuration

2.2 Common Functions

Step 1: Choose View > Configuration Management.

Step 2: Right-click and choose Create Subnetwork. Set Subnetwork ID and Set of

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

Figure 2-11 Create Management Element

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

Figure 2-12 Import Quick Configuration Data

Step 5: Click Choose, select the template to be loaded, and click Open.

Figure 2-13 Choosing the Template to Be Loaded

Figure 2-15 Template Importing Completed

Figure 2-16 Querying Importing Result

Figure 2-17 Logs of Importing Result

Step 1: Right-click ME and choose Export Quick Configuration Data.

Figure 2-18 Export Quick Configuration Data

Step 2: Fill in the values for Choose Directory and File Name Prefix according to the

Figure 2-19 Template Exporting Interface

2.2.3 Check on Imported Quick Configuration Template

Figure 2-20 Template Importing Check

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

Figure 2-21 Global Validity Check

3. License Center Check

2.2.4 Restoring Modify Area from Snapshot Area

Click Configuration Management > Batch NEs Operation.