Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
10)
Commissioning Guide
06 Quick Data Configuration
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following
terms. If you do not agree to the following terms, please notice that you are not allowed
to use this document.
Copyright 2016 ZTE CORPORATION. Any rights not expressly granted herein are
reserved. This document contains proprietary information of ZTE CORPORATION. Any
reproduction, transfer, distribution, use or disclosure of this document or any portion of
this document, in any form by any means, without the prior written consent of ZTE
CORPORATION is prohibited.
is the registered trademark of ZTE CORPORATION. ZTEs company name, logo and
product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be
trademarks or trade names of their respective owners. Without the prior written consent
of ZTE CORPORATION or the third party owner thereof, anyones access to this
document should not be construed as granting, by implication, estoppel or otherwise,
any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and
personal security. This product shall be stored, used or discarded in accordance with
product manual, relevant contract or laws and regulations in relevant country
(countries).
This document is provided as is and as available. Information contained in this
document is subject to continuous update without further notice due to improvement
and update of ZTE CORPORATIONs products and technologies.
ZTE CORPORATION
Addres
s:
Websit
e:
Email:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
http://support.zte.com.cn
800@zte.com.cn
Revision History
Product Version
V12.14.10
V12.14.10
Document Version
Serial Number
R1.0
First published
R1.1
Author
Date
Document Version
Prepared by
Reviewed by
Approved by
2015-05-20
R1.0
Hu Zhigang
Chen Taiming
Zhang Zhongqi
2015-08-10
R1.1
Hu Zhigang
Chen Taiming
Zhang Zhongqi
Intended audience: RNC commissioning engineers (from both ZTE and the
subcontractor)
II
Description
4 Specifications of Configuring
Equipment Template and Transport
Network Template
5 Specifications of Configuring
UMTS Radio Template
7 Special Subject
III
TABLE OF CONTENTS
1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
4
Template
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.1.7
4.1.8
4.1.9
4.1.10
4.1.11
4.1.12
4.1.13
4.1.14
4.1.15
4.1.16
4.1.17
4.1.18
4.1.19
4.2
4.2.1
4.2.2
4.2.3
IV
4.2.4
4.2.5
4.2.6
4.2.7
4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
4.2.13
4.2.14
4.2.15
4.2.16
4.2.17
4.2.18
4.2.19
4.2.20
4.2.21
4.2.22
4.2.23
4.2.24
4.2.25
4.2.26
4.2.27
4.2.28
4.2.29
4.2.30
4.2.31
4.2.32
IUB Office........................................................................................................
ATM Bearer(IUB Auto).....................................................................................
ATM Bearer(IUB).............................................................................................
SCTP Config(IUB-ABIS)..................................................................................
IP Bearer(IUB).................................................................................................
IPOE Bearer(IUB)............................................................................................
SCTP Config(ABIS)..........................................................................................
IP Bearer(ABIS)...............................................................................................
Adjacent Office(CN).........................................................................................
SCTP Config(CN)............................................................................................
M3uaAS Config(CN)........................................................................................
M3uaRoute......................................................................................................
M3uaRouteSet.................................................................................................
IP Path(CN)......................................................................................................
PVC Config(IU-IUR).........................................................................................
Mtp2Link..........................................................................................................
Mtp3Route.......................................................................................................
No.7 PCM........................................................................................................
Itc or BSC Office..............................................................................................
PCM(ITC-MSC)................................................................................................
MSC Office.......................................................................................................
SGSN Office....................................................................................................
Fr Gb................................................................................................................
Ip Gb................................................................................................................
Lucent Channel................................................................................................
SCTP Config(S1).............................................................................................
Dynamic Sctpac...............................................................................................
S1 Link.............................................................................................................
S1 TrPath.........................................................................................................
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
5.13
5.14
6
6.1
6.2
6.3
6.4
7
7.1
7.1.1
7.1.2
7.1.3
7.1.4
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.9.1
7.9.2
7.9.3
7.10
7.11
7.12
7.13
7.14
7.15
7.16
7.16.1
7.16.2
7.17
VI
Special Subject..............................................................................................97
ICM Data Configuration Flow (All-Parameter Configuration)............................97
ICM Initialization...............................................................................................
Exporting Optimization Template (All Parameters)...........................................
Data Import....................................................................................................102
Deleting Plan Area.........................................................................................118
Features of NodeB Auto-configuration...........................................................120
CMP Module No. Modification (Transmission)...............................................123
Overall Office Information Deletion................................................................124
Site Bearer Migration Function.......................................................................124
RNCID NODEBID CELLID Modification Tool.................................................125
Notes for All-data Synchronization & RNCID Modification..............................125
Adding User-plane IP (USP)..........................................................................125
Board Configuration.......................................................................................126
Slot Requirement for Master/Slave Boards....................................................126
Configuration Guide of ATM Interface Board Properties.................................126
Introduction of USP Board.............................................................................127
PVC Configuration.........................................................................................130
ATM Address Conversion...............................................................................133
1588 Clock Configuration...............................................................................134
Shielding Alarms............................................................................................135
Rules of Configuring Master/Slave EGPB......................................................136
Rules of Configuring Slots for USP................................................................138
Iub-Interface Qos Planning Rules..................................................................139
QOS According to ARP/THP/TC....................................................................139
QOS According to Service Type.....................................................................140
IP Function Switch.........................................................................................141
FIGURES
Figure 2-1 Template Importing Flow........................................................................................2
Figure 2-2 Template Info Sheet...............................................................................................3
Figure 2-3 Index Sheet........................................................................................................... 3
Figure 2-4 Attributes of Parameters........................................................................................4
Figure 2-5 V4_Template_Equipment......................................................................................5
Figure 2-6 V4_Template_TransportNetwork...........................................................................6
Figure 2-7 UMTS Radio Quick Configuration Template..........................................................7
Figure 2-8 UMTS Radio Template..........................................................................................7
Figure 2-9 Configuration Management...................................................................................8
Figure 2-10 Create Subnetwork..............................................................................................8
Figure 2-11 Create Management Element..............................................................................9
Figure 2-12 Import Quick Configuration Data.........................................................................9
Figure 2-13 Choose the Template to Be Loaded...................................................................10
Figure 2-14 Import Template.................................................................................................10
Figure 2-15 Template Importing Completed..........................................................................11
Figure 2-16 Query Importing Result......................................................................................11
Figure 2-17 Logs of Importing Result....................................................................................11
Figure 2-18 Export Quick Configuration Data.......................................................................12
Figure 2-19 Template Exporting Interface.............................................................................13
Figure 2-20 Template Importing Check.................................................................................14
Figure 2-21 Global Validity Check.........................................................................................15
Figure 2-22 Restore Modify Area from Snapshot Area..........................................................16
Figure 2-23 Restore Modify Area..........................................................................................16
Figure 2-24 Data Comparison...............................................................................................17
Figure 2-25 Comparison Result............................................................................................17
Figure 3-1 IP Number Calculating Tool.................................................................................18
Figure 6-1 Independent Board Configuration Online.............................................................90
Figure 6-2 Check the Link Status of an Independent Board..................................................91
Figure 6-3 Independent Board Configuration Online.............................................................92
Figure 6-4 Modify Parameters..............................................................................................94
Figure 6-5 Activate Data.......................................................................................................95
VII
VIII
TABLES
Table 1-1 Notices in Data Configuration..................................................................................1
Table 2-1 Parameter Attributes...............................................................................................4
Table 4-1 Basic Info..............................................................................................................20
Table 4-2 Plmn Config..........................................................................................................22
IX
XI
Contents
Description
Master/slave configuration,
alternate backup slots
PLMN ID
Configuration of integrated
CDR
IUBCOM
Netmask
OMCB gateway IP
Global check
2.1
2.1.1
templates. Therefore, the content of this sheet must be kept complete no matter which of
other sheets are selected.
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.
2.1.3
Attributes of Parameters
The fifth line of the template is parameter attributes, as shown in Figure 2 -4.
The attributes of the parameters fall into the following categories according to different
applications. Please refer to Table 2 -2 for the method of filling the parameters of
different attributes (Modifying this line is prohibited).
Meaning
Description
Read
Read only
R-W
R-I
R-W-I
Primary Key
R-M-I
Primary Key
Note:
Do not modify the first line and the fifth line of the template. Otherwise, template loading
error will occur.
2.1.4
Equipment Template
2.1.4.1
2.1.4.2
V4_Template_Equip
ment.xls
2.1.5
2.1.5.1
Filter the template according to radio type, transmission type, and special scene. The
principles are as shown below:
1.
Select a radio type. Only one mode can be selected here. The template generated
will display all configuration parameters of the specified radio mode.
2.
Select a combination of radio type and transmission type. The template generated
will display the configuration parameters involved in the specified radio mode and
transmission type. This applies to the scenario of initial commissioning.
3.
Select a combination of radio type and special scene. The template generated will
display the configuration parameters involved in the specified radio mode and
special scene. This applies to the scenario of transmission modification.
4.
Select no filtering condition. The template will not perform filtering and will display
the contents of all sheets.
2.1.5.2
V4_Template_Trans
portNetwork.xls
2.1.6
2.1.6.1
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.
2.1.6.2
2.2
Common Functions
2.2.1
Loading Templates
Step 1: Choose View > Configuration Management.
Step 2: Right-click and choose Create Subnetwork. Set Subnetwork ID and Set of
MCC according to the actual situation.
Step 5: Click Choose, select the template to be loaded, and click Open.
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.
If the number displayed in Result on the right is equal to the total number of records, it
means all records are loaded successfully. Otherwise, some records fail to be loaded.
10
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.
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.
Note:
There is only one loading method for V4 quick configuration, no matter whether it is for
Equipment template & Transport Network template or for UMTS Radio Quick Configuration
template.
2.2.2
Exporting Templates
Step 1: Right-click ME and choose Export Quick Configuration Data.
Step 2: Fill in the values for Choose Directory, File Name Prefix, and Export File
according to the actual situation, export the required template sheet by sheet, and click
Execute.
12
2.2.3
Template importing: In this process, OMM will check the validity, effectiveness, and
completeness of the format in the quick configuration template.
2.
14
3.
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
After the Batch NEs Operation window pops up on OMM, select the target NE, and
click Restore modify area from Snapshot Area to restore data from the snapshot area
to the modify area. If Copied is displayed in Status, it means the operation succeeds.
2.2.5
16
Select the target NE, click Run (the Fast comparison mode is used by default), and click
OK to start comparison.
Observe the value of Result. If it is identical, it means that the data in the snapshot
area is the same as that in the modify area.
In the Excel template, the values of the parameters are as shown below:
USPBOARDNUM: 0..42
USP2ABOARDNUM: 0..42
Restriction: If the numbers of USP and USP2a are both "0," an error will be prompted,
indicating it is necessary to fill in the number correctly.
18
The ratio of control plane for sharing CPU Resource: 20..67; default: 20; based on
the default value "20," we can get the upper limit for the number of IPs needed. In the
calculation process, it is recommended that "20" be used to work out the upper limit, so
that there are some redundant IPs.
IPINTFTYPE 1-5:
Bit0=1: 3G Iub interface
Bit1=1: 3G Iur interface
Bit2=1: 3G IuCS interface
Bit3=1: 3G IuPS interface
Bit4=1: 3G Iubprecfg interface
In the whole system, the interface types supported by the service IP of each Slave are
the same. The five IPINTFTYPE parameters show the interface types supported by the
service IPs allocated to each Slave and the corresponding interface combinations. Each
RNC occupies one record in the template.
Refer to the following examples:
1.
2.
IPINTFTYPE1=1,IPINTFTYPE2=10,IPINTFTYPE3=100,IPINTFTYPE4=1000,
IPINTFTYPE5=0: Each interface uses an independent IP and does not support the
pre-configuration of the Iub interface.
3.
IPINTFTYPE1=11,IPINTFTYPE2=0,IPINTFTYPE3=1100,IPINTFTYPE4=0,
IPINTFTYPE5=0: Iub and Iur share an IP, and IuCs and IuPs share an IP, and preconfiguration of iUb is not supported.
Restriction: Check whether the interface types involved are conflicted with each other,
i.e., after the AND operation is performed to every two of IPINTFTYPE1~ IPINTFTYPE5,
the value of the five bits should not be "1."
PLMNCOMBTYPE 1-5:
The PLMN combinations corresponding to IPINTFTYPE 1-5.
If different PLMNs use different IPs, separate the IPs with ";". If different PLMNs share
IPs, separate the IPs with @.
When filling in PLMNCOMBTYPE, fill in all the PLMN IDs supported by the NE.
Because an RNC supports four PLMNs at most, we use 1, 2, 3, and 4 to represent four
PLMN IDs respectively.
Suppose an NE supports four PLMNs, and PLMN 1 and PLMN 2 share an IP, PLMN 3
and PLMN 4 use two independent IPs, this parameter should be set to "1@2;3;4."
If this parameter is not configured, it means all PLMNs are supported.
If the system supports only one PLMN, fill in either the exact PLMNID or null.
Restriction: If the value of PLMNCOMBTYPE is not 0, either fill in null or fill in 1, 2, 3,
4" and make sure the PLMN IDs filled in are not repeated. For all non-0
PLMNCOMBTYPEs, the number of PLMNs must be consistent with PLMN IDs, but
PLMNID does not need to match PLMNCOMBTYPE.
Fill in the supported IP types, and click the Count the number of IP address button, and
then the Excel template will count the service IPs.
The Excel template has both Chinese and English versions, which are stored under the
\ums-clnt\tools\UCIUIpNum directory.
Specifications of Configuring
Equipment Template and Transport
Network Template
4.1
Equipment Template
4.1.1
Basic Info
Table 4-3 Basic Info
20
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,M,P
A:Add,
D:Delete,
M:Modify, P:Pass
Managed
Element ID
long:
[1..4095]
Primary
Key
Mode Type
long:[2..4]
2:UMTS
3:GSM
4:GU
R-I
Omp's omc
port ip
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
Omp's omc
port mask
length
long:[0..32]
R-W-I
Omp's omc
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
Description
Parameter
Name
Parameter
Value
port
gateway
Description
Remarks
IP address
of SNTP
server
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
OMCB
Agent IP
Address to
NODEB
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
OMCB
Server IP
Address
ipv4
eg:xxx.xxx.xxx.xxx
R-W-I
OMCB
Server IP
Mask
Length
long:[0..32]
R-W-I
ipv4
eg:xxx.xxx.xxx.xxx
It can be used when it
supports multipath
protection.
Otherwise, it is filled in
default value 0.0.0.0 .
R-W-I
long:[-720,660,-600,540,-480,420,-360,300,-240,180,-120,60,0,60,120
,180,240,30
0,360,420,4
80,540,600,
660,720,78
0]
R-W-I
OMCB
Inner Ip
Address
Time Zone
Daylight
Saving
long:[0,1]
0:Stop
1:Start
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
Time using
flag
4.1.2
Start time
of the
Daylight
Saving
Time(Mon/
Day/Hour/
Min)
string
eg:Mon/Day/Hour/Min
R-W
End time of
the Daylight
Saving
Time(Mon/
Day/Hour/
Min)
string
eg:Mon/Day/Hour/Min
R-W
Step of
Daylight
Saving
Time(minut
e)
long:
[0..33008]
60 is recommended value.
R-W
Plmn Config
Table 4-4 Plmn Config
22
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
User label
string
R-W
Managed
Element ID
long:
[1..4095]
Primary
Key
PLMN
Group
Object ID
long:
[0..429496
7295]
Primary
Key
Mobile
Country
Code
long:
[0..999]
R-W-I
Mobile
Network
Code
long:
[0..999]
R-W-I
MNC BCD
Code
Length
long:[2..3]
R-W-I
Description
4.1.3
Parameter
Name
Parameter
Value
Default
PLMN
Indicator
long:[0..1]
0:false
1:true
R-W-I
Is Local
Office's
PLMN
long:[0..1]
0:false
1:true
R-I
Description
Remarks
Filling
Instructions
Shelf Config
Table 4-5 Shelf Config
Parameter
Name
4.1.4
Parameter
Value
Description
Remarks
Filling
Instruction
s
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
Managed
Element ID
long:[1..4095]
Primary
Key
Rack No.
long:[1..1]
Primary
Key
Shelf No.
long:[1..3]
Primary
Key
Shelf Type
long:[33,34]
33:ETCA V1
34:ETCA V2
Primary
Key
Master Shelf
Flag
long:[0..1]
R-W-I
Board Config
Table 4-6 Board Config
Parameter
Name
Parameter
Value
Description
Remarks
Modification
Indication
A,D,P
A:Add, D:Delete,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
rack/shelf/slot
string
eg:1/2/7
Primary
Key
Physical
Board Type
string
eg:UMP
R-I
Filling
Instructions
Parameter
Name
Logical Board
Type
Remarks
Description
string
eg:OMP
R-I
Module No.
string
R-I
Backup Mode
long:[0,1,5]
0:No Backup
1:1+1 Backup
5:1TO1 Backup
R-I
long:[0..2]
0:PUBLIC
1:2G
2:3G
3:AG
R-I
long:[0..8]
0:INVALID
1:SDH-63E1
2:SDH-63T1
3:SDH-84T1
4:POS
5:ATM
6:E1
7:T1
8:Ethernet
R-I
Multiplex
structure of
the optical
port
long:[0..4]
0:INVALID
1:SDH AU-4
2:SDH AU-3
3:SONET STS-1
4:SONET STS-3C
R-I
PCM Map
Type
long:[0,1,255]
0:ITUT-G.707 type
1:Tributary type
255:Invalid
long:[0,1,4,6]
0:Multi-Frame
1:Double Frame
4:Multi-Frame with
checked
6:Forced MultiFrame(default value)
It can be empty.
E1
Impedance
long:[0,1,3]
0:75(default value of
Electric E1)
1:120
3:Invalid(default value
of Channelized E1)
It can be empty.
Cable Type of
Ethernet Port
long:[2,3]
2:Fiber(default value)
3:Cable
Mode Type
Port Type
E1 Frame
Type
Use Scene of
2G CRP
Board
24
Parameter
Value
long:[0,1,2]
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
1:TDMA
2:IPA
4.1.5
Global Info
Table 4-7 Global Info
Parameter
Name
Parameter
Value
Description
Modification
Indication
A,M,P
A:Add, M:Modify,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
IP Segment
ReAssemble
Default Unit
string
eg:rack/shelf/slot
R-W
The First IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Second
IP Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Third IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Fourth
IP Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Fifth IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Sixth IP
Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
The Seventh
IP Segment
ReAssemble
Unit
string
eg:rack/shelf/slot
R-W
4.1.6
Interface IP
Table 4-8 Interface IP
Parameter
Name
26
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User Label
string
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Interface
Board
string
eg:rack/shelf/slot
Primary
Key
Module No.
long:[1..127]
Primary
Key
Port Type
long:[0,1,2]
0:Interface
1:Loopback port
2:Virtual port
Primary
Key
Interface
Local Port
No.
long:[0..128]
0:invalid,
1~4:real port,
1~128:loop port
1~244Interface(ATM
port)
Primary
Key
VLAN
Sequence
long:[0..4095]
0 is invalid
Primary
Key
Vlan ID
long:[0..4095]
0 is invalid.
It is valid when it is sub
interface.
R-W-I
VPN ID of
sub port
long:[0..254]
0 is invalid
R-W-I
MAC
address
string
eg:
xx-xx-xx-xx-xx-xx
R-W
IP address of
interface
ipv4
eg:
xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
R-W-I
Mask Length
of interface
IP
long:[0..32]
eg:24;24
R-W-I
4.1.7
Service IP
Table 4-9 Service IP
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Service IP
ipv4
eg:
xxx.xxx.xxx.xxx
Primary
Key
string
Bit0=1:A Interface of
GSM Network
Bit1=1:Abis PS
Interface of GSM
Network
Bit2=1:Abis CS
Interface of GSM
Network
Bit3=1:Gb Interface of
GSM Network
string
Bit0=1:Iub Interface of
3G Network
Bit1=1: Iur Interface of
3G Network
Bit2=1: IuCS Interface
of 3GNetwork
Bit3=1: IuPS Interface
of 3G Network
Bit4=1:Iub Common
Interface of 3G
Network (for CCIU)
Bit5=1:Preconfiguratio
n IuB Interface of 3G
Network
string
Bit0=1:IuCS Interface
of HNB GW Network
Bit1=1:IuPS Interface
of HNB GW Network
Bit2=1:IuhCS Interface
of HNB GW Network
Bit3=1:IuhPS Interface
of HNB GW Network
Bit4=1:HenbS1
Interface of HeNB GW
Network
Bit5=1:MmeS1
Interface of HeNB GW
Network
Application
Type of IP
address(2G)
Application
Type of IP
address(3G)
Application
Type of IP
address(AG)
Parameter
Name
VPN ID of
sub port
PLMN info of
Service IP
4.1.8
Parameter
Value
Remarks
Description
long:[0..254]
0 is invalid
R-I
string
eg:
MCC1:MNC1;MCC2:M
NC3
or 65535:65535,
65535:65535 denotes
supporting all PLMN
R-W-I
Filling
Instructions
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,P
A:Add, D:Delete,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary
Key
string
Data Format(Iub
Common Interface):
xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
Primary
Key
string
Data Format(Iub
Preconfiguration):
xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
Primary
Key
Service IP
Address of
CCIU SLAVE
Service IP for
Preconfigurat
ion Iub
Interface
4.1.9
Parameter
Value
Description
Remarks
Modification
Indication
A,D,P
A:Add, D:Delete,
P:Pass
Managed
Element
Object ID
long:[1..4095]
Primary Key
string
Data Format:
binary mode, 5 bits
in total: xxxxx
Bit0=1:Iub Interface
of 3G Network
Primary Key
Interface
Type
Combination
1 of Service
IP
28
Parameter
Value
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Bit1=1:Iur Interface
of 3G Network
Bit2=1:IuCS
Interface of 3G
Network
Bit3=1:IuPS
Interface of 3G
Network
Bit4=1:Preconfigura
tion IuB Interface of
3G Network
The PLMN
Combination
for "Interface
Type
Combination
1 of Service
IP"
Interface
Type
Combination
2 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
2 of Service
IP"
Interface
Type
Combination
3 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
3 of Service
IP"
string
string
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
eg:
If this parameter is
not configured, it
means all PLMNs
are supported.
If the system
supports only one
PLMN, fill in either
the exact PLMNID
or nothing.
Data Format:
binary mode, 5 bits
in total: xxxxx
Primary Key
Primary Key
string
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Primary Key
string
Data Format:
binary mode, 5 bits
in total: xxxxx
Primary Key
string
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Primary Key
Filling
Instructions
Parameter
Name
Interface
Type
Combination
4 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
4 of Service
IP"
Interface
Type
Combination
5 of Service
IP
The PLMN
Combination
for "Interface
Type
Combination
5 of Service
IP"
Parameter
Value
string
string
string
string
Description
Remarks
Data Format:
binary mode, 5 bits
in total: xxxxx
Primary Key
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Data Format:
binary mode, 5 bits
in total: xxxxx
Data Format:
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx;xxx.xx
x.xxx.xxx;xxx.xxx.x
xx.xxx
Filling
Instructions
Primary Key
Primary Key
Primary Key
IPINTFTYPE 1-5:
The five IPINTFTYPE parameters show the interface types supported by the service IPs
allocated to each Slave and the corresponding interface combinations. Each RNC
occupies one record in the template.
Refer to the following examples:
1.
2.
IPINTFTYPE1=1,IPINTFTYPE2=10,IPINTFTYPE3=100,IPINTFTYPE4=1000,
IPINTFTYPE5=0: Each interface uses an independent IP and does not support the
pre-configuration of the Iub interface.
3.
IPINTFTYPE1=11,IPINTFTYPE2=0,IPINTFTYPE3=1100,IPINTFTYPE4=0,
IPINTFTYPE5=0: Iub and Iur share an IP, and IuCs and IuPs share an IP, and preconfiguration of iUb is not supported.
Restriction: Check whether the interface types involved are conflicted with each other,
i.e., after the AND operation is performed to every two of IPINTFTYPE1~ IPINTFTYPE5,
the value of the five bits should not be "1."
PLMNCOMBTYPE 1-5:
30
4.1.10
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,P
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
string
Data Format:
RACK/SHELF/SLOT,
2G: CRP or ETCB or EDTB
or ESDTB board,
3G: 0/0/0. Don't assign IP
resource by board for 3G.
Primary
Key
string
Data Format:
xxx.xxx.xxx.xxx;xxx.xxx.xxx
.xxx;xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
Primary
Key
Data Format(Iub
Preconfiguration):
Primary
Key
Board Info
Service IP
Address of
SLAVE
Service IP
for
string
Parameter
Name
Parameter
Value
Preconfigur
ation Iub
Interface
4.1.11
Remarks
Description
Filling
Instructions
xxx.xxx.xxx.xxx;xxx.xxx.xxx
.xxx
Channel Port
Table 4-13 Channel Port
Parameter
Name
4.1.12
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Channel
Group ID
long:[1..16]
Primary
Key
VLAN
Sequence
long:[0..4095]
0 is invalid
Primary
Key
Vlan ID
long:[0..4095]
0 is invalid.
It is valid when it is sub
interface.
R-W-I
Bound Mode
long:[3..5]
3:on Mode
4:backup Mode
5:802.3AD Mode
R-W-I
VPN ID of
sub port
long:[0..254]
0 is invalid
R-W-I
MAC
address
string
eg:
xx-xx-xx-xx-xx-xx
R-W
IP address of
interface
ipv4
eg:
xxx.xxx.xxx.xxx;xxx.xx
x.xxx.xxx
R-W-I
Mask Length
of interface
IP
long:[0..32]
eg:24;24
R-W-I
Member Port
Table 4-14 Member Port
Parameter
Name
Modification
32
Parameter
Value
A,D,M,P
Description
A:Add, D:Delete,
Remarks
Filling
Instructions
Parameter
Name
Parameter
Value
Indication
Remarks
Filling
Instructions
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Member port
ID of
Channel
Group
long:[1..128]
Primary
Key
Interface
Board
string
eg:rack/shelf/slot
R-I
Local port
No. of
member port
long:[1..4]
R-I
Channel
Group ID
long:[1..16]
R-I
Bounding
mode of
member port
long:[1..4]
1:active
2:passive
3:on
4:backup
R-W-I
System
Priority of
LACP
protocol
long:[1..65535]
R-W
long:[0..1]
0:long time,
1:short time,
The defaulte value is
0.
R-W
Timeout Type
of LACP
protocol
4.1.13
Description
Super Vlan
Table 4-15 Super Vlan
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Supervlan ID
long:[1..16]
Primary
Key
Switch of
inner-route
function
long:[0..1]
0:Closed
1:Open
R-W-I
Parameter
Name
MAC
address
4.1.14
Parameter
Value
Remarks
Description
string
eg:
xx-xx-xx-xx-xx-xx
R-W
IP address of
Super Vlan
Interface
ipv4
R-W-I
Mask Length
of interface
IP
long:[0..32]
eg:24;24
R-W-I
VPN ID of
port
long:[0..254]
0 is invalid
R-W-I
Filling
Instructions
Remarks
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
string
eg:rack/shelf/slot.
When Vlan Sub
Interface of Ethernet
Port joins to supervlan,
this parameter should
be filled in the EGPB
board.
When Vlan Sub
Interface of Channel
Group joins to
supervlan,
this parameter should
be filled in 0/0/0.
Primary
Key
Interface
Board
Real Port
No.
34
Parameter
Value
long:[1..16]
Filling
Instructions
Primary
Key
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Channel-group ID.
4.1.15
VLAN
Sequence
long:[1..4095]
Primary
Key
Supervlan
ID
long:[1..16]
R-I
DHCP Server
Table 4-17 DHCP Server
Parameter
Name
Parameter
Value
Description
Remarks
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
DHCP
Server
Object ID
long:[1..2800]
Unique in ME
Primary
Key
Type of
DHCP
Server
Address
long:[0..2]
0:DHCP Server IP
Address-Inner
Controller
1:DHCP Server IP
Address-Outer
Controller
2:DHCP Server BoardLogical Address
Module No.
long:[1..127]
It is valid if
DHCPSVRIPTYPE=2.
R-W
DHCP
Server IP
Address
ipv4
It is valid if
DHCPSVRIPTYPE=0
or 1.
R-W
Mask
Length of
DHCP
Server IP
Address
long:[0..32]
It is valid if
DHCPSVRIPTYPE=0
or 1.
R-W
VPN ID of
Port
long:[0..254]
It is valid if
DHCPSVRIPTYPE=0.
The default value is 0.
R-W
R-W-I
Filling
Instructions
4.1.16
DHCP Client
Table 4-18 DHCP Client
Parameter
Name
36
Parameter
Value
Remarks
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Client
Number
long:
[1..2800]
Unique in ME
String
R-W-I
Hardware
Address
String
eg:
xxx.xxx...xxx.xxxx(leng
th is 16)
R-W-I
Client
Identity
String
eg:
xxx.xxx...xxx.xxxx(leng
th is 16)
R-W-I
Client
Identity
ipv4
eg:
xxx.xxx.xxx.xxx
R-W-I
Mask Length
of DHCP
Client IP
Address
long:[0..32]
32 is recommended
R-W-I
DHCP Client
Host Name
String
1 to 128 characters of
ASCII, the same as
vendor class of Node
B
R-W
DHCP
Server
Object ID
long:
[1..2800]
DHCP
Server
Identity(Interf
ace IP)
ipv4
R-W-I
RNC OAM IP
Address to
NodeB
ipv4
eg:
xxx.xxx.xxx.xxx
R-W-I
DHCP
Gateway IP
Address
ipv4
eg:
xxx.xxx.xxx.xxx
R-W-I
Primary
Key
1 to 16 characters of
ASCII, the same as
vendor class of Node
B
Vendor Class
Identity of
DHCP Client
Filling
Instructions
R-W-I
4.1.17
DHCP Relay
Table 4-19 DHCP Relay
Parameter
Name
Parameter
Value
Description
Remarks
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
DHCP Relay
Object ID
long:[1..2800]
IP interface
board
Real Port
No.
Unique in ME
Primary
Key
string
eg:rack/shelf/slot
It must be EGPB
board info if DHCP
relay port is real port
or sub interface of real
port.
Others, it can be filled
in 0/0/0.
R-I
long:[0..4]
0 is invalid.
It is valid only if DHCP
relay port is real port
or sub interface of real
port.
R-I
0 is invalid.
Channel
Group ID
long:[0..16]
R-I
long:[0..4095]
0 is invalid.
It is valid only if DHCP
relay port is sub
interface of real port or
sub interface of
channel port.
R-I
Relay IP
Address
ipv4
R-W-I
Mask Length
of Relay IP
Address
long:[0..32]
R-W-I
VLAN
Sequence
Filling
Instructions
Parameter
Name
DHCP
Server
Object ID
4.1.18
Parameter
Value
Remarks
Description
long:[1..2800]
Filling
Instructions
R-W-I
38
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
VPN Name
string
no more than 30
characters
VPN ID of
Port
long:[1..254]
Route
Distinguisher
Type
long:[1,2]
1:ASN:nn format,
2:IP-address:nn format
R-W-I
Route
Distinguisher
Value
string
If the RD TYPE is
"ASN:nn", the format of
RD VALUE is (165535):(04294967295).
If the RD TYPE is "IPaddress:nn", the
format of RD VALUE is
(0.0.0.0255.255.255.255): (065535)
R-W-I
VRF
description
information
string
no more than 80
characters
R-W
R-W-I
Primary
Key
4.1.19
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
VPN Name
string
no more than 30
characters
VPN ID of
Port
long:[1..254]
Target-VPN
community
long:[2,3]
2:Export
3:Import
Primary
Key
VRF Route
Target Type
long:[1,2]
1:ASN:nn format,
2:IP-address:nn format
Primary
Key
string
If the RT TYPE is
"ASN:nn", the format
of RT VALUE is (165535):(04294967295).
If the RT TYPE is "IPaddress:nn", the
format of RT VALUE is
(0.0.0.0255.255.255.255): (065535)
Primary
Key
VRF Route
Target
Value
R
Primary
Key
4.2
TransportNetwork Template
4.2.1
Local Office
Table 4-22 Local office
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Parameter
Name
Parameter
Value
Description
Net type of
local office
long:[1..255]
Primary
Key
Whether to
enable
network
appearance
long:[1,2]
1:Enable
2:Disable
R-W-I
Network
appearance
long:
[0..42949672
95]
R-W
14-bit
signalling
point code
of local
office on
the net
long:
[0..16383]
This is an interconnection
parameter, so the peer
must be identical to the
local setting.
R-W-I
24-bit
signalling
point code
of local
office on
the net
long:
[0..16777215
]
This is an interconnection
parameter, so the peer
must be identical the local
setting.
R-W-I
Mode Type
long:[0,1]
0:2G
1:3G (UMTS, AG)
R-I
ATM
Address
string
20 Bytes, decimal.
This is an interconnection
parameter.
GSM doesn't need to
config.
R-W
Network
Resource
Identifier Bit
Num in CS
Domain
long:[0..10]
R-W
Network
Resource
Identifier Bit
Num in PS
Domain
long:[0..10]
R-W
BSC ID
40
long:
[1..4095]
Remarks
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
4.2.2
Static Route
Table 4-23 Static route
Parameter
Name
Parameter
Value
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Static
Route
Number
long:[1..5000]
Unique in ME
Primary
Key
ipv4
R-W-I
Static route
network
mask
length
long:[8..32]
R-W-I
Route next
hop
address
ipv4
R-W-I
VPN ID of
sub port
long:[0..254]
0 is invalid
R-W-I
long:[1..254]
R-W-I
Static route
network
prefix
Route
distance
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
4.2.3
long:[0..1]
0:unactived
1:actived
R-W-I
IP Path Group
Table 4-24 IP Path Group
Parameter
Name
Remarks
Description
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Path Group
Id
long:
[0..4095]
Unique in ME.
Father Path
Group Id
long:
[0..65535]
R-I
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
AG:3..31
Support to modify the
module No. of path group
for Iu interface.
R-W-I
Path Group
Bear Type
long:[2,5]
2:ETHERNET_NOVLAN
5:ETHERNET_VLANTAG
R-W-I
PLMN
Group
Object ID
sequence<lo
ng,4>
eg:1;2
R-I
Ratio of
occupied
private
bandwidth
of Path
Group by
operator
sequence<lo
ng,4>
0 to 1000
If more than one
MCC/MNC, separate
each value by ';'
R-W-I
long:
R-W-I
Forward
bandwidth(
42
Parameter
Value
Primary
Key
Parameter
Name
4.2.4
Parameter
Value
Description
kbps)
[0..4294967]
physical bandwidth.
Backward
bandwidth(
kbps)
long:
[0..4294967]
Remarks
Filling
Instructions
R-W-I
IUB Office
Table 4-25 IUB Office
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
A,D,M,S,P
A:Add, D:Delete,
M:Modify,
S:Swap,
P:Pass
User label
string
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
ATM/ATM+IP:101 to 999,
IP/IPOE:1001 to 3999
Primary
Key
Net
Element ID
long:
[1..65534]
R-I
sequence<lo
ng,4>
R-M-I
CMP
Module No.
long:[3..31]
R-W-I
Config for
Bear Type
of Service
in IUB
long:[0,1,2]
0: ATM
1: IP
2: ATM+IP
R-I
Modification
Indication
PLMN
Group
Object ID
Parameter
Name
Remarks
Description
Config for
Bear Type
of NBAP in
IUB
long:[0,1,2]
0: ATM
1: IP
2: ATM+IP
R-I
Config for
Bear Type
of
Common
Channel in
IUB
long:[0,1,2]
0: ATM
1: IP
2: ATM+IP
R-I
long:[0..2]
0: Protection OFF
1: Support multipath
protection
2: Support ATM+IP
protection
R-W-I
Transport
Qos Profile
Type
long:[1..2]
1: QoS(according to
ARP/THP/TC)
2: QoS(according to
service type)
The default value is 2 if
this parameter is empty.
R-W
Subsystem
of RUP
long:
[1,2,3,255]
R-W-I
ATM
address of
adjacent
office
string
20 Bytes, decimal
R-W
NodeB
Inner IP
ipv4
R-W-I
ipv4
It must be unique if it is
valid(not 0.0.0.0).
It can be configured under
multipath protection.
R-W-I
long:[1..255]
1:ATM+IP Transport,
2:Only IP Transport.
It cant be filled when it is
only ATM transport.
System will configure it
according office's bear
type when it is empty.
This parameter is valid if
UPQOSMAPTYPE= 1.
R-W
Switch of
IUB
multipath
protection
OMCB
Inner
Service Ip
Address
Profile ID of
Transport
Bearer
Type Profile
Related to
Basic
Priority
Transport
Qos Profile
parameter
Index
44
Parameter
Value
long:[1..32]
Filling
Instructions
R-W
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
4.2.5
Parameter
Value
Description
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:[1..4095]
Primary
Key
Destination
IP address
ipv4
R-W-I
Destination
IP Address
Mask
Length
long:[0..32]
R-W-I
OMCB Path
priority
long:[1..3]
It should be configured
when IUB office is
multipath production.
R-W
Path Group
long:[0..4095]
R-I
Parameter
Name
Parameter
Value
Id
Filling
Instructions
Atm
Interface
Board
string
R-W-I
E1 List
string
R-W-I
Iub Plan
long:[1..2]
1:Normal,
2:High load
R-I
long:[1..20]
R-W
The
number of
UBR Aal2
PVC
4.2.6
Remarks
Description
ATM Bearer(IUB)
Table 4-27 ATM Bearer(IUB)
Parameter
Name
46
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
User label
string
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
PVC ID
long:
[1..12600]
Primary
Key
Atm
Interface
Board
string
R-I
ATM
Optical Port
long:[1..4]
R-I
VPI on
High End
long:
[0..4095]
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
recommended to use a
value smaller than or equal
to 4.
VCI on
High End
long:
[32..65535]
PVC
Service
Type
long:[0,2,4]
0: AAL5 signal
2: AAL2 user data
4: OMCB
R-W-I
R-I
0:CBR
1:rtVBR
2:nrtVBR
4:UBR
CBR supports:
atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3),
atmNoClpNoScr(1)
atmClpTransparentNoScr(8
),
atmNoClpNoScrCdvt(11).
Service
Category
long:[0,1,2,4]
R-W-I
UBR supports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCdvt(11),
atmNoClpTaggingNoScr(10
).
Traffic Type
long:[0..15]
0: NOTRF
1: atmNoClpNoScr
2: atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
atmClpTransparentNoScr
9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
atmClpNoTaggingScrCdvt
14: atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell
rate for
CLP=0+1
(PCR0+1)
Peak cell
rate for
CLP=0
(PCR0)
Cell delay
variation
tolerance
(CDVT)
Sustainable
cell rate for
CLP=0
(SCR0)
Sustainable
cell rate for
CLP=0+1
(SCR0)
48
long:
[0..18210661
33]
Unit: Kbps.
This Traffic Para supports
all Service Category and all
Traffic Type.
R-W-I
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
CBR ,rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingNoScr(2),
atmClpTaggingNoScr(3).
R-W
long:
[0..42949672
95]
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
atmClpTransparentNoScr
(8),
atmNoClpNoScrCdvt (11),
atmClpTaggingScrCdvt(14),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpNoScrCdvt(13),
atmNoClpTaggingNoScr(10
).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt(
13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
R-W
Parameter
Name
Parameter
Value
Description
Remarks
atmNoClpScr(4).
Maximum
burst cell
number
(MBS)
long:
[0..42949672
95]
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt(
13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
Path Group
Id
long:
[0..4095]
TrPath ID
sequence<lo
ng,4>
AAL2 Path
ID intra
office
long:
[1..42949672
95]
As an interconnection
parameter, this number
must have the same
configuration as the peer
office.
long:[0..1]
0:Local End
1:Peer End
If Local Office is configured,
the AAL2 PATH ID will be
allocated in the ascending
order.
If Adjacent Office is
configured, the AAL2 PATH
ID will be allocated in the
descending order.
For two interconnected
RNCs, one end should be
configured as the Local
Office, while the other as
the Adjacent Office.
AAL2 Path
Ownership
AAL2 Path
Service
Type
long:[10..14]
10:RT
11: NRT1
12: NRT2
13: NRT3
14: MIX
RT: for bearing real-time
service,
NRT1: for bearing R99 nonreal-time service,
R-W
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
4.2.7
Application
Type of UNI
Link
long:[1..3]
1: ALCAP
2: NBAP(NCP)
3: NBAP(CCP)
Destination
IP address
ipv4
R-W
Destination
IP Address
Mask
Length
long:[0..32]
R-W
OMCB
Path
priority
long:[1..3]
It should be configured
when IUB office is multipath
production.
R-W
SCTP Config(IUB-ABIS)
Table 4-28 SCTP Config(IUB-ABIS)
Parameter
Name
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..65535]
Primary
Key
Association
ID
long:
[1..8400]
Primary
Key
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
R-I
Local port
50
Parameter
Value
long:
[1..65535]
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
ipv4
R-W-I
long:
[1..65535]
R-W-I
Remote IP
address
ipv4
R-W-I
SCTP
association
bearer
protocol
type
long:[15,21]
15:NBAP (3G)
21:IPABIS (2G)
R-I
Max
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:500
R-W
Min
Retransmis
sion
Timeout(10
millisecond)
long:
[10..1000]
default value:50
R-W
Initial
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:100
R-W
Heartbeat
Interval(10
millisecond)
long:
[10..6000]
default value:500
R-W
Delayack
interval(10
millisecond)
long:[0..20]
default value:20
R-W
Local IP
address
Remote
port
Filling
Instructions
4.2.8
IP Bearer(IUB)
Table 4-29 IP Bearer(IUB)
Parameter
Name
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
Primary
Key
TrPath ID
long:[0..7]
Primary
Key
Path Group
ID
long:
[0..4095]
PLMN
Group
Object ID
long:
[0..42949672
95]
Destination
IP address
ipv4
Destination
IP Address
Mask
Length
long:[0..32]
long:
[0..4294967]
R-W-I
long:
[0..4294967]
R-W-I
Path Tx
Band width
of Trpath
(kbps)
Path Rx
Band width
of Trpath
(kbps)
52
Parameter
Value
Parameter
Name
4.2.9
Parameter
Value
Remarks
Description
IP Domain
No.
long:
[0,21,22,23]
0:Invalid,
21:IP Domain No.1,
22:IP Domain No.2,
23:IP Domain No.3
It should be configured to
effective value (21,22,23)
when IUB office is
multipath production.
OMCB Path
priority
long:[1..3]
It should be configured
when IUB office is
multipath production.
R-W
R-W
Filling
Instructions
IPOE Bearer(IUB)
Table 4-30 IPOE Bearer(IUB)
Parameter
Name
Parameter Value
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,
P:Pass
User label
string
It contains no
more than 80
characters.
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:[1..4095]
Quote ANEID of
"IUB Office"
sheet.
Primary
Key
string
rack/shelf/slot
It must be the
EDTI or ESDTI
board info for
IPOE bear type.
R-W
MP Port
No.
long:[0..120]
0:ppp
[1..512]:Mp
When it is MultiPPP link,
LOCALPORT is
usually not filled,
can be auto
generated by
system.
E1/T1 List
string
Separated by ";"
R-W
E1/T1 TS
string
Separated by ";"
R-W
Board Info
of IPOE
Description
Remarks
Filling
Instructions
Parameter
Name
Description
Remarks
List
and "-"
Path Group
ID
long:[0..4095]
The
recommended
value is 1001 to
3999.
R-I
TrPath ID
sequence<long,4>
TrPath ID :[0..7]
eg:0;1
Primary
Key
Destination
IP address
ipv4
Depend on the
real situation.
R-W-I
long:[0..32]
It is the mask
length of the
destination IP
address.
R-W-I
long:[0,21,22,23]
0:Invalid,
21:IP Domain
No.1,
22:IP Domain
No.2,
23:IP Domain
No.3
It should be
configured to
effective value
(21,22,23) when
IUB office is
multipath
production.
R-W
long:[1..3]
It should be
configured when
IUB office is
multipath
production.
R-W
Destination
IP Address
Mask
Length
IP Domain
No.
OMCB Path
priority
4.2.10
Parameter Value
Filling
Instructions
SCTP Config(ABIS)
Related to GSM network.
4.2.11
IP Bearer(ABIS)
Related to GSM network.
54
4.2.12
Adjacent Office(CN)
Table 4-31 Adjacent Office(CN)
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]
R-I
Net
Element ID
sequence<lo
ng,8>
Mgw Id:[4096..65535],
Mscserver Id:[0..4095],
Sgsn Id:[0..4095],
Rnc Id[1..4095],
BSC Id:[1..4095],
SAS Id:[0..65535],
SMLC Id:[0..65535].
1)When the mode type is
UMTS or AG and the
office type is
MGW+MSCSERVER, the
number of NEID must be
double of the number of
PLMNID.
This parameter notes
NEID of MGW office and
NEID of MSCSERVER
office, such as
MgwId1;MscsId1;MgwId2;
MscsId2 .
When the mode type is
UMTS and the office type
is SAS, the number of
NEID must be 1.
Under other office type,
the number of NEID must
be equal to the number of
PLMNID.
2)When the mode type is
GSM, the number of NEID
must be 1.
R-I
PLMN
sequence<lo
R-M-I
Parameter
Name
Group
Object ID
ng,4>
Mode Type
long:[2,3,6]
Remarks
Description
2:UMTS
3:GSM
6:AG
R-I
long:
[16,32,64,51
2,576,1023,4
096,32768]
R-I
Bear type
long:[0..2]
0: ATM (3G)
1: IP
2: TDM (2G)
(Parameters can't be
modified)
When 2G office is
RNC,SRVBRSTYPE must
be 1.
R-I
Encode
type of
signalling
point
long:[14,24]
14:SPC 14 bits,
24:SPC 24 bits
R-W-I
Destination
point code
long:
[0..16777215
]
14 bits:0..16383
24 bits:0..16777215
R-W-I
SubService
Field
long:
[0,4,8,12]
Filling
Instructions
2G office:
32:RNC
64:MGW
576:MGW+MSCSERVER
1023:SMLC
3G office:
16:BSC
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
32768:SAS
AG Office:
64:MGW
512:MSCSERVER
576:MGW+MSCSERVER
4096:SGSN
Type of
adjacent
office
56
Parameter
Value
0: International SPC,
international network, with
a code of 0x00H in the
signaling.
4: Reserved international
SPC, reserved
international network, with
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
Connection
relationship
with local
signalling
point
long:[1..3]
1:Associated
2:Quasi-associated
3:No connection
This field identifies
whether the local office
and the adjacent office
are directly associated or
quasi-associated in terms
of signaling relation.
Associated Mode means
there are directly
connected signaling links
between the local office
and the adjacent office.
Quasi-associated Mode
means there is no directly
connected signaling link
between the local office
and the adjacent office,
and they need one
signaling transfer point or
more in between. If the
RNC and MSC are
connected through
transfer of the MGW,
Quasi-associated Mode
should be used.
Fill in this field according
to the real situation.
Whether to
support
broadband
properties
long:[0..1]
0:Not Support
1:Support
R-W-I
Protocol
type
long:[1..3]
1:CHINA
2:ITU
3:ANSI
R-W-I
ATM
address
string
R-W-I
R-W
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
MGW/MGW+MSC/MSC/S
GSN NE type and the
bear type is ATM.
And the ATM address
must be full 0 for
MSC/SGSN NE type.
It is invalid for GSM and
can be empty.
Default
Office Flag
Capacity
Weight in
CS/PS
Domain
Number of
Network
Resource
Identifier in
CS/PS
Domain
58
sequence<lo
ng,4>
R-W
sequence<lo
ng,4>
R-W
sequence<lo
ng,4>
R-W
Parameter
Name
Network
Resource
Identifier in
CS/PS
Domain
4.2.13
Parameter
Value
string
Description
The value range of one
Network Resource
Identifier is [0..1023].
If there are two PLMNs,
the NUMOFNRI of
PLMN1 is 2 and the
NUMOFNRI of PLMN2 is
3,then NRILIST is
10;11@100;101;103.
Valid in the case of
IUFLEX networking.
As an interconnection
parameter, this parameter
will appear in the
TMSI/PTMSI allocated to
the UE by the network.
It is invalid for GSM and
can be empty.
Remarks
Filling
Instructions
R-W
SCTP Config(CN)
Table 4-32 SCTP Config(CN)
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]
Primary
Key
Association
ID
long:
[1..3000]
2G:1..2048
3G:1..3000
AG:1..3000
The recommended value
for UMTS is
1 to 1000.
Primary
Key
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
AG:3..31
R-W-I
Application
type of
association
long:[1..2]
1:Server
2:Client
For the two ends
associated, at least one
R-W-I
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
long:
[1..65535]
R-W-I
ipv4
R-W-I
long:
[1..65535]
R-W-I
ipv4
R-W-I
ASP
Number
long:
[1..8400]
R-I
Max
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:500
R-W
Min
Retransmis
sion
Timeout(10
millisecond)
long:
[10..1000]
default value:50
R-W
Initial
Retransmis
sion
Timeout(10
millisecond)
long:
[10..3000]
default value:100
R-W
Heartbeat
Interval(10
millisecond)
long:
[10..6000]
default value:500
R-W
Delayack
interval(10
millisecond)
long:[0..20]
default value:20
R-W
Local port
Local IP
Address
Remote
port
Remote IP
Address
60
4.2.14
M3uaAS Config(CN)
Table 4-33 M3uaAS Config(CN)
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]
Primary
Key
AS Number
long:[1..640]
Primary
Key
ASP
Number
sequence<lo
ng,16>
R-W-I
long:[0..1]
0: FALSE
1: TRUE
Each group of values
indicates whether the
local end and the peer
end are configured with
routing context.
Select TRUE if one ASP
occurs to more than one
AS, or select FALSE
otherwise. In the
Controller, one ASP
usually occurs to one AS,
so it is unnecessary to
configure the routing
context ID.
R-W-I
long:
[0..4294967
295]
R-W-I
Whether
exists
routing
context
Routing
context ID
Whether
exists peer
routing
long:[0..1]
0: FALSE
1: TRUE
R-W
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
context
long:
[0..4294967
295]
4294967295 is invalid
R-W
AS property
long:[1..5]
1: SGP,
2: ASP,
3: IPSP SERVER,
4: IPSP CLIENT,
5: DOUBLE EXCHANGE
MODEL
This is an interconnection
parameter, so when the
IUR and IU are
interconnected, note that
the two ends should be
configured respectively as
the IPSP Server and IPSP
Client. Be sure to
negotiate with the peer
end for consistency to
avoid configuration of
both ends as the IPSP
Server.
If DOUBLE EXCHANGE
MODEL is configured, the
local end and the peer
end are allowed to have
different routing contexts.
R-W-I
AS traffic
mode
long:[1..2]
Peer routing
context ID
62
1: Override,
2: Loadshare
N+K load sharing means
the multiple ASPs in one
AS are simultaneously in
the service state, so that
the messages can be
transmitted through the
ASPs in turn. The N value
indicates the minimum
number of ASPs that must
be activated before the
AS can be activated. The
K value makes little sense
now. Override means only
one ASP is in the service
state at certain time in
one AS, while other ASPs
are standing by and will
substitute when the ASP
in service breaks down.
Select NO during normal
running, or otherwise
select YES for the test
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
purpose.
value of N
value of K
4.2.15
long:[0..16]
It is OK to select the
default value, or as
required, make the AS
available only when
multiple ASPs are
activated.
R-W-I
long:[0..16]
R-W-I
M3uaRoute
Table 4-34 M3uaRoute
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Route
Number
long:[1..640]
Unique in ME
Primary
Key
Route
range mode
long:[0..2]
0:natural sort
1:ikebana sort
2:handworked sort
R-W-I
AS1
Number
long:[1..640]
Quote AS Number of
"M3uaAS Config(CN)"
sheet.
R-W-I
AS2
Number
long:[0..640]
0 is valid
R-W-I
AS3
Number
long:[0..640]
0 is valid
R-W-I
AS4
Number
long:[0..640]
0 is valid
R-W-I
4.2.16
M3uaRouteSet
Table 4-35 M3uaRouteSet
Parameter
Name
4.2.17
Parameter
Value
Remarks
Description
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Adjacent
Office ID
long:[1..2048]
Primary
Key
Route ID 1
long:[1..640]
R-W-I
Route ID 2
long:[0..640]
0 is valid
R-W-I
IP Path(CN)
Table 4-36 IP Path(CN)
Parameter
Name
64
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Net
Element
Identifier
long:
[1..4095]
Primary
Key
Path ID
long:[0..7]
Primary
Key
Path Group
ID
long:
[0..4095]
Primary
Key
CMP
Module No.
long:[3..63]
2G:3..63
3G:3..31
AG:3..31
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
PLMN
Group
Object ID
long:
[0..42949672
95]
R-I
Destination
IP Address
ipv4
R-W-I
long:[0..32]
Destination
IP Address
Mask
Length
Forward
bandwidth(
kbps)
Backword
bandwidth(
kbps)
long:
[0..4294967]
long:
[0..4294967]
R-W-I
R-W-I
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Remarks
Filling
Instructions
4.2.18
PVC Config(IU-IUR)
Table 4-37 PVC Config(IU-IUR)
Parameter
Name
Description
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
Managed
Element
Object ID
long:
[1..4095]
Primary
Key
Adjacent
Office ID
long:
[1..2048]
Primary
Key
long:
[1..12600]
Primary
Key
Atm
Interface
Board
string
It must be the
EAPB/EDTA/ESDTA
board info.
eg:rack/shelf/slot
R-I
ATM port
long:[1..244]
R-I
E1 list
string
R-W
PVC ID
66
Parameter
Value
Parameter
Name
VPI on
High End
VCI on
High End
Parameter
Value
Description
Remarks
long:
[0..4095]
R-W-I
long:
[32..65535]
R-W-I
0: AAL5 Signal,
1: AAL5 Data,
2: AAL2 Data
PVC
Service
Type
long:[0..2]
PVC
interface
type
long:[2..4]
Service
Category
long:[0,1,2,4]
R-I
R-I
R-W-I
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14
),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
UBR supports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCdvt(11),
atmNoClpTaggingNoScr(1
0).
IU interface: CBR is
recommended.
IUR interface: CBR is
recommended for
signaling, while a
combination of CBR and
UBR is recommended for
service.
Traffic Type
long:[0..15]
0: NOTRF
1: atmNoClpNoScr
2:
atmClpNoTaggingNoScr
3: atmClpTaggingNoScr
4: atmNoClpScr
5: atmClpNoTaggingScr
6: atmClpTaggingScr
7: atmClpNoTaggingMcr
8:
atmClpTransparentNoScr
9: atmClpTransparentScr
10:
atmNoClpTaggingNoScr
11: atmNoClpNoScrCdvt
12: atmNoClpScrCdvt
13:
atmClpNoTaggingScrCdvt
14:
atmClpTaggingScrCdvt
15: atmTrafficForUbr+
Peak cell
rate for
CLP=0+1
(PCR0+1)
long:
[0..18210661
33]
Unit: Kbps.
This Traffic Para supports
all Service Category and
all Traffic Type.
Peak cell
rate for
CLP=0
(PCR0)
68
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
CBR ,rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingNoScr(2
R-W-I
R-W-I
R-W
Parameter
Name
Parameter
Value
Description
Remarks
),
atmClpTaggingNoScr(3).
long:
[0..42949672
95]
Unit: 0.1us.
Service Category:
CBR ,rtVBR, nrtVBR and
UBR.
Traffic Type:
atmClpTransparentNoScr
(8),
atmNoClpNoScrCdvt (11),
atmClpTaggingScrCdvt(14
),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpNoScrCdvt(13),
atmNoClpTaggingNoScr(1
0).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt
(13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14
).
R-W
long:
[0..18210661
33]
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
R-W
Maximum
burst cell
number
(MBS)
long:
[0..42949672
95]
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingScr(5),
atmClpNoTaggingScrCdvt
(13),
atmClpTaggingScr(6),
atmClpTaggingScrCdvt(14
),
atmClpTransparentScr(9),
atmNoClpScrCdvt(12),
atmNoClpScr(4).
R-W
Path Group
ID
long:
[0..4095]
Cell delay
variation
tolerance
(CDVT)
Sustainable
cell rate for
CLP=0
(SCR0)
Sustainable
cell rate for
CLP=0+1
(SCR0)
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
4001 to 4095.
TrPath ID
sequence<lo
ng,4>
AAL2
Attached
Module
long:[3..31]
R-W
AAL2 Path
ID intra
office
long:
[1..42949672
95]
As an interconnection
parameter, this number
must have the same
configuration as the peer
office.
long:[10..14]
10:RT
11: NRT1
12: NRT2
13: NRT3
14: MIX
RT: for bearing real-time
service,
NRT1: for bearing R99
non-real-time service,
NRT2: for bearing HS
non-real-time service,
MIX: for bearing all types
of service.
AAL2 Path
Ownership
long:[0..1]
0:Local End
1:Peer End
If Local Office is
configured, the AAL2
PATH ID will be allocated
in the ascending order.
If Adjacent Office is
configured, the AAL2
PATH ID will be allocated
in the descending order.
For two interconnected
RNCs, one end should be
configured as the Local
Office, while the other as
the Adjacent Office.
Signalling
link number
long:
[1..9000]
Unique in ME
Linkset
number
long:
[1..1024]
Unique in ME
long:[3..31]
R-W
AAL2 Path
Service
Type
Signalling
Link
Attached
Module
70
Parameter
Name
Signaling
Link Code
Destination
IP address
4.2.19
Parameter
Value
Description
Remarks
long:[0..15]
R-W
ipv4
R-W
Filling
Instructions
Mtp2Link
Related to GSM network.
4.2.20
Mtp3Route
Table 4-38 Mtp3Route
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify, P:Pass
User label
string
R-W
Managed
Element
Object ID
long:[1..4095]
Primary
Key
Route ID
long:[1..2000]
Unique in ME
Primary
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
Key
Used
Signalling
Linkset 1
long:[1..1024]
R-W-I
Used
Signalling
Linkset 2
long:[0..1024]
0:Invalid
R-W-I
long:[0..8]
0:Any arrangement
(default value)
1:According to SLS_bit0
choose routing groups
2:According to SLS_bit1
choose link groups
3:According to SLS_bit2
choose link groups
4:According to SLS_bit3
choose link groups
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:Floral sort
R-W
Permutation
of signalling
links
4.2.21
No.7 PCM
Related to GSM network.
4.2.22
4.2.23
PCM(ITC-MSC)
Related to GSM network.
4.2.24
MSC Office
Related to GSM network.
72
4.2.25
SGSN Office
Related to GSM network.
4.2.26
Fr Gb
Related to GSM network.
4.2.27
Ip Gb
Related to GSM network.
4.2.28
Lucent Channel
Related to GSM network.
4.2.29
SCTP Config(S1)
4.2.30
Dynamic Sctpac
Related to GSM network.
4.2.31
S1 Link
Related to GSM network.
4.2.32
S1 TrPath
Related to GSM network.
5.1
UTRAN Cell
Table 5-39 UTRAN Cell
Parameter
Name
Parameter Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
NodeB No
long:[0..65535]
R-W-I
Cell ID
long:[0..65534]
Primary
Key
Local Cell
Identity
long:
[0..268435455]
R-W-I
Frequency
Band
Indicator
0:Band I,1:Band
II,2:Band
III,3:Band
IV,4:Band
V,5:Band
VI,7:Band VIII
R-W-I
long:
[9612..9888,9262.
.9538,12,37,62,87
,112,137,162,187,
212,237,262,287,
937..1288,1312..1
513,1662,1687,17
12,1737,1762,178
7,1812,1837,1862
,4132..4233,782,7
87,807,812,837,8
62,4162..4188,81
2,837,2712..2863]
uarfcnUl is calculated
by uarfcnDl, should not
input any value.
{freqBandInd==0}
[9612..9888],
{freqBandInd==1}
[9262..9538][12][37]
[62][87][112][137][162]
[187][212][237][262]
[287],
{freqBandInd==2}
[937..1288],
{freqBandInd==3}
UUARFCN
74
Description
Parameter
Name
Parameter Value
Description
Remarks
[1312..1513][1662]
[1687][1712][1737]
[1762][1787][1812]
[1837][1862],
{freqBandInd==4}
[4132..4233][782][787]
[807][812][837][862],
{freqBandInd==5}
[4162..4188][812]
[837],
{freqBandInd==7}
[2712..2863]
DUARFCN
long:
[10562..10838,96
62..9938,412,437,
462,487,512,537,
562,587,612,637,
662,687,1162..15
13,1537..1738,18
87,1912,1937,196
2,1987,2012,2037
,2062,2087,4357..
4458,1007,1012,1
032,1037,1062,10
87,4387..4413,10
37,1062,2937..30
88]
{freqBandInd==0}
[10562..10838],
{freqBandInd==1}
[9662..9938][412][437]
[462][487][512][537]
[562][587][612][637]
[662][687],
{freqBandInd==2}
[1162..1513],
{freqBandInd==3}
[1537..1738][1887]
[1912][1937][1962]
[1987][2012][2037]
[2062][2087],
{freqBandInd==4}
[4357..4458][1007]
[1012][1032][1037]
[1062][1087],
{freqBandInd==5}
[4387..4413][1037]
[1062],
{freqBandInd==7}
[2937..3088]
R-W-I
Cell
Primary
Scrambling
Code
long:[0..511]
R-W-I
Location
Area Code
long:
[1..65533,65535]
R-W-I
Routing
Area Code
long:[0..255]
R-W-I
Service
Area Code
long:[0..65535]
R-W-I
URA
Identity
sequence<long,4
>
R-W-I
Service
Area Code
long:[0..65535]
R-W-I
Filling
Instructions
Parameter
Name
Parameter Value
Description
Remarks
Filling
Instructions
for BC
Domain
T_Cell
5.2
long:
[0..9],<default:0>
R-W-I
5.3
Parameter
Value
Description
Remarks
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
Mobile
Country
Code
long:[0..999]
Primary
Key
Mobile
Network
Code
long:[0..999]
Primary
Key
Cell ID
long:[0..65534]
Primary
Key
Common
PLMN
Indicator
0:False,1:True,
<default:1>
R-W-I
Filling
Instructions
76
Parameter
Value
Description
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
Parameter
Name
Parameter
Value
Description
Remarks
RNC ID
long:[0..4095]
Primary
Key
Cell Identity
of Adjacent
Cell
long:[0..65535]
Primary
Key
RNC
Identity of
Adjacent
RNC
long:[0..4095]
Primary
Key
Mobile
Country
Code
long:[0..999]
R-W-I
Mobile
Network
Code
long:[0..999]
R-W-I
Location
Area Code
long:
[1..65533,65535
]
R-W-I
Frequency
Band
Indicator
0:Band I,1:Band
II,2:Band
III,3:Band
IV,4:Band
V,5:Band
VI,7:Band VIII
R-W-I
long:
[9612..9888,926
2..9538,12,37,6
2,87,112,137,16
2,187,212,237,2
62,287,937..128
8,1312..1513,16
62,1687,1712,1
737,1762,1787,
1812,1837,1862
,4132..4233,782
,787,807,812,83
7,862,4162..418
8,812,837,2712.
.2863]
{freqBandInd==0}
[9612..9888],
{freqBandInd==1}
[9262..9538][12][37]
[62][87][112][137][162]
[187][212][237][262]
[287],
{freqBandInd==2}
[937..1288],
{freqBandInd==3}
[1312..1513][1662]
[1687][1712][1737]
[1762][1787][1812]
[1837][1862],
{freqBandInd==4}
[4132..4233][782][787]
[807][812][837][862],
{freqBandInd==5}
[4162..4188][812]
[837],
{freqBandInd==7}
[2712..2863]
long:
[10562..10838,9
662..9938,412,4
37,462,487,512,
{freqBandInd==0}
[10562..10838],
{freqBandInd==1}
[9662..9938][412][437]
UUARFCN
DUARFCN
R-W-I
Filling
Instructions
Parameter
Name
5.4
Parameter
Value
Remarks
Description
537,562,587,61
2,637,662,687,1
162..1513,1537.
.1738,1887,191
2,1937,1962,19
87,2012,2037,2
062,2087,4357..
4458,1007,1012
,1032,1037,106
2,1087,4387..44
13,1037,1062,2
937..3088]
[462][487][512][537]
[562][587][612][637]
[662][687],
{freqBandInd==2}
[1162..1513],
{freqBandInd==3}
[1537..1738][1887]
[1912][1937][1962]
[1987][2012][2037]
[2062][2087],
{freqBandInd==4}
[4357..4458][1007]
[1012][1032][1037]
[1062][1087],
{freqBandInd==5}
[4387..4413][1037]
[1062],
{freqBandInd==7}
[2937..3088]
Cell
Primary
Scrambling
Code
long:[0..511]
R-W-I
Service
Area Code
for CS and
PS Domain
long:[0..65535]
R-W-I
URA
Identity
sequence<long,
4>
R-W-I
Filling
Instructions
78
Parameter
Name
Parameter Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
Cell
long:[0..65535]
Primary
Description
Parameter
Name
Parameter Value
Description
Identifier of
Adjacent
GSM Cell
Remarks
Key
Location
Area Code
of Adjacent
GSM Cell
long:
[1..65533,65535]
Primary
Key
Band
Indicator
R-W-I
BCCH
ARFCN
long:
[512..885,512..81
2,0..124,955..102
3,259..293,306..3
40,438..511,128..
251]
{bandIndicator==0}
[512..885],
{bandIndicator==1}
[512..812],
{bandIndicator==2}
[0..124][955..1023],
{bandIndicator==3}
[259..293],
{bandIndicator==4}
[306..340],
{bandIndicator==5}
[438..511],
{bandIndicator==6}
[128..251]
R-W-I
Network
Colour
Code
long:[0..7]
R-W-I
Base
Station
Colour
Code
long:[0..7]
R-W-I
Mobile
Country
Code
long:[0..999]
R-W-I
Mobile
Network
Code
long:[0..999]
R-W-I
BSC
Identifier
long:[0..65535]
R-W-I
Filling
Instructions
5.5
UExternalENBFunction
Table 5-43 External ENodeB Function
5.6
Parameter
Name
Parameter Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:[1..4095]
Primary
Key
User Label
string:[0..80]
R-W
RNC ID
long:[0..4095]
Primary
Key
ENodeB ID
long:
[0..268435455]
Primary
Key
Rnc ID
Attached by
Eutran Cell
long:[0..4095]
R-W
ENodeB
Type
0:Macro
eNodeB,1:Home
eNodeB,<default:
0>
R-W
Description
Parameter
Value
Remarks
Filling
Instructions
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
eNodeB ID
long:
[0..2684354
55]
EUTRAN
Cell
Identity
long:
[0..255]
Primary
Key
long:
R-W-I
EUTRAN
Physical
80
Description
Primary
Key
Parameter
Name
Parameter
Value
Cell
Identity
[0..503]
Mobile
Country
Code
long:
[0..999]
R-W-I
Mobile
Network
Code
long:
[0..999]
R-W-I
Eutran
Frequency
Band
Indicator
0:Band
1,1:Band
2,2:Band
3,3:Band
4,4:Band
5,5:Band
6,6:Band
7,7:Band
8,8:Band
9,9:Band
10,10:Band
11,11:Band
12,12:Band
13,13:Band
14,16:Band
17,17:Band
18,18:Band
19,19:Band
20,20:Band
21,22:Band
23,23:Band
24,24:Band
25
R-W-I
{eutranFreqBandInd==0}
[0..599],
{eutranFreqBandInd==1}
[600..1199],
{eutranFreqBandInd==2}
[1200..1949],
{eutranFreqBandInd==3}
[1950..2399],
{eutranFreqBandInd==4}
[2400..2649],
{eutranFreqBandInd==5}
[2650..2749],
{eutranFreqBandInd==6}
[2750..3449],
{eutranFreqBandInd==7}
[3450..3799],
{eutranFreqBandInd==8}
[3800..4149],
{eutranFreqBandInd==9}
R-W-I
Downlink
EUTRAN
Absolute
Radio
Frequency
Channel
Number
long:
[0..65535]
Description
Remarks
Filling
Instructions
Parameter
Name
Parameter
Value
Remarks
Description
Filling
Instructions
[4150..4749],
{eutranFreqBandInd==10}
[4750..4999],
{eutranFreqBandInd==11}
[5000..5179],
{eutranFreqBandInd==12}
[5180..5279],
{eutranFreqBandInd==13}
[5280..5379],
{eutranFreqBandInd==16}
[5730..5849],
{eutranFreqBandInd==17}
[5850..5999],
{eutranFreqBandInd==18}
[6000..6149],
{eutranFreqBandInd==19}
[6150..6449],
{eutranFreqBandInd==20}
[6450..6599],
{eutranFreqBandInd==22}
[7500..7699],
{eutranFreqBandInd==23}
[7700..8039],
{eutranFreqBandInd==24}
[8040..8689]
Uplink
EUTRAN
Absolute
Radio
Frequency
Channel
Number
82
long:
[0..65535]
{eutranFreqBandInd==0}
[18000..18599],
{eutranFreqBandInd==1}
[18600..19199],
{eutranFreqBandInd==2}
[19200..19949],
{eutranFreqBandInd==3}
[19950..20399],
{eutranFreqBandInd==4}
[20400..20649],
{eutranFreqBandInd==5}
[20650..20749],
{eutranFreqBandInd==6}
[20750..21449],
{eutranFreqBandInd==7}
[21450..21799],
{eutranFreqBandInd==8}
[21800..22149],
{eutranFreqBandInd==9}
[22150..22749],
{eutranFreqBandInd==10}
[22750..22999],
{eutranFreqBandInd==11}
[23000..23179],
R-W-I
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
{eutranFreqBandInd==12}
[23180..23279],
{eutranFreqBandInd==13}
[23280..23379],
{eutranFreqBandInd==16}
[23730..23849],
{eutranFreqBandInd==17}
[23850..23999],
{eutranFreqBandInd==18}
[24000..24149],
{eutranFreqBandInd==19}
[24150..24449],
{eutranFreqBandInd==20}
[24450..24599],
{eutranFreqBandInd==22}
[25500..25699],
{eutranFreqBandInd==23}
[25700..26039],
{eutranFreqBandInd==24}
[26040..26689]
5.7
Tracking
Area Code
long:
[0..65535]
Location
Area Code
long:
[0..65533,6
5535]
R-W
Routing
Area Code
long:
[0..255]
R-W
MNC BCD
Code
Length
long:
[2,3],<defa
ult:2>
EUTRAN
Measurem
ent
Bandwidth
0:6,1:15,2:2
5,3:50,4:75,
5:100,<def
ault:0>
R-W-I
R-W
Parameter
Value
Modificatio
n Indication
A,D,M,P
[Managed
Element
Object ID]
long:
[1..4095]
Remarks
Filling
Instructions
A:Add, D:Delete,
M:Modify,P:Pass
Primary
Key
Description
Parameter
Name
Parameter
Value
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
eNodeB ID
long:
[0..2684354
55]
EUTRAN
Cell
Identity
long:
[0..255]
Primary
Key
EUTRAN
Physical
Cell
Identity
long:
[0..503]
R-W-I
Mobile
Country
Code
long:
[0..999]
R-W-I
Mobile
Network
Code
long:
[0..999]
R-W-I
Eutran
Frequency
Band
Indicator
32:Band
33,33:Band
34,34:Band
35,35:Band
36,36:Band
37,37:Band
38,38:Band
39,39:Band
40,40:Band
41,41:Band
42,42:Band
43
R-W-I
{eutranFreqBandInd==33}
[36200..36349],
{eutranFreqBandInd==34}
[36350..36949],
{eutranFreqBandInd==35}
[36950..37549],
{eutranFreqBandInd==36}
[37550..37749],
{eutranFreqBandInd==37}
[37750..38249],
{eutranFreqBandInd==38}
[38250..38649],
{eutranFreqBandInd==39 }
[38650..39649],
{eutranFreqBandInd==40}
[39650..41589],
{eutranFreqBandInd==41}
R-W-I
EUTRAN
Absolute
Radio
Frequency
Channel
Number
84
long:
[0..65535]
Remarks
Description
Filling
Instructions
Primary
Key
Parameter
Name
Parameter
Value
Description
Remarks
Filling
Instructions
[41590..43589],
{eutranFreqBandInd==42}
[43590..45589]
5.8
Tracking
Area Code
long:
[0..65535]
Location
Area Code
long:
[0..65533,6
5535]
R-W
Routing
Area Code
long:
[0..255]
R-W
MNC BCD
Code
Length
long:
[2,3],<defa
ult:2>
EUTRAN
Measurem
ent
Bandwidth
0:6,1:15,2:2
5,3:50,4:75,
5:100,<def
ault:0>
R-W-I
R-W
Neighbouring Cell
Table 5-46 Neighbouring Cell
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
Cell ID
long:
[0..65534]
Primary
Key
Target RNC
ID
long:
[0..4095]
Primary
Key
Target Cell
ID
long:
[0..65535]
Primary
Key
Description
5.9
5.10
Parameter
Name
Parameter
Value
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
Cell ID
long:
[0..65534]
Primary
Key
Location
Area Code
long:
[1..65533,6
5535]
Primary
Key
Cell
Identifier
long:
[0..65535]
Primary
Key
Description
86
Parameter
Name
Parameter
Value
Modificatio
n Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
Cell ID
long:
[0..65534]
Primary
Key
EUTRAN
Cell Type
0:EUTRAN
FDD,1:EUT
RAN TDD
eNodeB ID
long:
[0..2684354
55]
Primary
Key
EUTRAN
long:
Primary
Description
Remarks
Filling
Instructions
R-I
5.11
Parameter
Name
Parameter
Value
Cell Identity
[0..255]
Description
Remarks
Filling
Instructions
Key
5.12
Paramet
er Value
Description
Remarks
Filling
Instructions
Modification
Indication
A,D,M,P
A:Add, D:Delete,
M:Modify,P:Pass
[Managed
Element
Object ID]
long:
[1..4095]
Primary
Key
User Label
string:
[0..80]
R-W
RNC ID
long:
[0..4095]
Primary
Key
[User
Authorized
PLMN+SNA
C Information
Object ID]
long:
[0..42949
67295]
Primary
Key
MCC of
Shared
Network
sequence
<long,10>
R-W-I
MNC of
Shared
Network
sequence
<long,10>
R-W-I
The Imsi
Matched
Digits Num
long:
[1..15]
R-W-I
The Imsi
Matched
Digit
sequence
<long,15>
R-W-I
Number of
Shared
Network
Code
long:
[1..10],<d
efault:1>
MBMS Configuration
It is not necessary to configure this sheet at present.
R-W-I
5.13
5.14
6.1
2.
88
Click Link Status on the Independent Board Configuration Online window, and
check whether the link status of ECMM, EGBS, and EGFS is ON. Refer to the
ZXUR 9000 UMTS (V4.14.10) Commissioning Guide 04 Board Power-On to load
the software of the boards and make sure ECMM, EGBS, and EGFS are all in the
ON state.
6.2
Common parameter configuration: The configuration of DST has two formats, i.e.,
YY/MM/DD and the weekly mode. Either is OK, but the YY/MM/DD format is
recommended.
Parameter
Name
Descriptio
n
Remarks
R-W-I
Master
SNTP
server
address
ipv4
e.g.:
xxx.xxx.xxx.x
xx,
recommende
d
configuration:
129.0.100.10
0
SNTP
Synchroniz
ation cycle
millisecond
Recommend
ed value:
1800000.
long:[-720,660,-600,540,-480,-
The value
range:
-720:GMT-12
Time Zone
90
Parameter
Value
Filling
Instructio
ns
R-W-I
Common
Parameter
configuration
Parameter
Name
Parameter
Value
Descriptio
n
420,-360,300,-240,180,-120,60,0,60,120,
180,240,300,
360,420,480,
540,600,660,
720,780]
-660:GMT-11
-600:GMT-10
-540:GMT-9
-480:GMT-8
-420:GMT-7
-360:GMT-6
-300:GMT-5
-240:GMT-4
-180:GMT-3
-120:GMT-2
-60:GMT-1
0:GMT
60:GMT+1
120:GMT+2
180:GMT+3
240:GMT+4
300:GMT+5
360:GMT+6
420:GMT+7
480:GMT+8
540:GMT+9
600:GMT+10
660:GMT+11
720:GMT+12
780:GMT+13
Daylight
Saving
Time using
flag
long:[0,1]
0:Stop
1:Start
R-W-I
Start time
of the
Daylight
Saving
Time(Mon/
Day/Hour/M
in)
string
eg:Mon/Day/
Hour/Min
R-W
End time of
the Daylight
Saving
Time(Mon/
Day/Hour/M
in)
string
eg:Mon/Day/
Hour/Min
R-W
Step of
Daylight
Saving
Time(minut
e)
long:
[0..33008]
60 is
recommende
d value.
R-W
Remarks
Filling
Instructio
ns
6.3
2.
3.
Click Modify and then the corresponding button on the right to modify related
parameters.
2.
92
3.
6.4
2.
Click the icon in the red circle in the above figure, and the following operation result
appears.
94
Special Subject
7.1
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.
7.1.1
Plan Template: It is the quick configuration template on OMMR. The plan template
uses a simplified filling method, i.e., the values of the parameters not displayed in
the template will be calculated with the fixed method and will be generated
automatically. Plan template consists of three templates: Equipment template,
TransportNetwork, template, and UMTS Radio template. This template can be used
on both OMMR and ICM.
MO Template: It can only be operated through ICM and is similar to the OMMR MO
Template. It consists of two templates: Uni Ground template and UMTS Radio
template.
ICM Initialization
Open EMS client, choose Configuration > Plan Data Management, and open the Plan
Data Management window.
Click Live Data Area, and select the record of the target OMMR in the dialog box on the
right. Right-click the record and choose Synchronize to synchronize ICM live data area
and OMMR data and start manually the synchronization between the live data area and
OMMR.
96
Note:
ICM can only synchronize data with the snapshot area of the OMMR, because the snapshot
area is always consistent with RNC and the data can be used as the reference.
If the data in the snapshot area is changed (i.e., the data is synchronized from OMMR to
RNC) ICM will monitor this operation in real time and trigger data upload automatically.
This can make sure the data in the live data area of ICM is consistent with that in snapshot
area of OMMR, i.e., consistent with the RNC data.
If data upload cannot be triggered automatically, it is necessary to perform data upload
manually with the method mentioned above.
7.1.2
Select the type of the data to be exported in Data Type, e.g., UMTS Radio for UMTS
radio data and Uni_Ground for ground data, and click Next. In Figure 7 -40, UMTS
Radio is taken as the example.
Click Select and select the directory for the exported file. Click Save > Export.
98
The interface for the data exported successfully is as shown in Figure 7 -42. Click Quit
to exit the Query and Export window.
Note:
The Optimization Template can be exported from either Live Data Area or Plan Area, but
because the data in Live Data Area is consistent with the RNC data fixedly, it is
recommended to export the Optimization Template from Live Data Area.
7.1.3
Data Import
Data importing is based on Plan Area and is usually performed according the flow in
Figure 7 -43.
100
7.1.3.1
Configure User Label in the pop-up Create Plan Area dialog box, select the check box
of the corresponding subnet record, and click OK.
7.1.3.2
Importing Template
Right-click the target Plan_Area under Data Area, and choose Import to import data.
102
1.
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.
Right-click the imported file record and choose View Detail to view the details of the
imported file.
The importing result will be automatically saved under the path in the red box in the
figure below.
104
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.
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.
The process of importing Optimization Template is the same as that of importing Plan
Template. Check whether the number of successful records in Succeed/All Counts is
the same as the number of all records. If it is, the template is loaded successfully.
Note:
When importing the Optimization Template from ICM, pay attention to the following points:
1. In the Optimization template, the ME ID field must be configured. This is different
from the rules of filling in the Plan template.
2.
The Data Type selected should match with the template name, as shown below:
106
7.1.3.3
Validity Check
Right-click the target Plan_Area under Data Area, and choose Check to perform data
validity check.
In the pop-up Data Check-Validity window, click OK to start data validity check. By
default, Full Data and All Rules will not be selected, because the system will use the
most efficient way to perform the operation by default. If there is no special requirement,
do not select these two items.
After validity check is completed, observe the import result in the figure below. If Validity
is Pass, it means the validity check succeeds.
108
If there is some error found in the check process, the number of ERROR/WARN records
will be displayed in Result. If there are ERROR records, please check whether the data
is correct. Otherwise, the configuration cannot be activated. If there is only the WARN
record, the activation can be performed normally. This record will appear when the
optional global validity check fails to pass, and the detailed information is displayed in
the CSV file under the path in Detail.
7.1.3.4
Conflict Check
Choose the Conflict tab and click OK to start conflict check.
Before conflict check is started, the following dialog box will pop up. Confirm the live data
is synchronized and click OK.
If the Progress is 100%, the "Conflict" is No, the Result is Success, and the
Detail is Finished, this means the conflict check is finished and there is no conflict. In
this case, enter the Submit tab to perform the subsequent operations.
110
7.1.3.5
Data Submission
After the conflict check passes, choose the Submit tab, and click Submit to submit the
activation request.
Click Quit to quit the Check interface.
7.1.3.6
Data Activation
Choose Activate to display the Activation Management window.
112
Click the Add button to open the Activation task management tab, and add the plan
area to be activated to the Selected Plan Area. Fill in the Task Name and click OK.
Choose the task to be activated. Right-click the task and choose Compare to Get Delta
to create incremental data.
Observe the execution result in Status in the record and the Result in the log.
Observe the execution result in Status in the record and the Result in the log.
114
Observe the execution result in Status in the record and the Result in the log.
7.1.4
7.1.4.1
116
7.1.4.2
7.1.4.3
7.2
118
When the user uses commands to configure the objects like NodeB/cell, there is no
need to appoint the board of the object and the CU of control plane, which are
automatically allocated by ZXUR 9000. Therefore, the complexity of configuration is
reduced for the users and the operation and maintenance efficiency is improved.
In addition, the load of the CUs on different control planes is balanced, which helps
avoid the situation when the CUs of some control planes are overloaded (which may
result in access control) while the CUs of some other control planes are light-loaded. In
this way, the use rate of equipment and resources is improved and customers
satisfaction is promoted.
ZXUR 9000 provides the regular swap function and the immediate swap function to
dynamically adjust the NodeBs and cells deployed on the subnets of control planes. The
regular swap function can be performed automatically or manually.
1.
Module Restore: synchronize the module information configured for the site radio
resource in OMMR to RNC.
2.
Module Adjust: export the suggestions for module adjustment from RNC and adjust
the home module of radio resource accordingly.
120
7.3
7.4
7.5
Table 7-51 Sheets to Be Configured for Each Transmission Type of a New Site
No
.
IPoE1+IPoF
E
IPoFE
ATMoE1
ATM+IP
IUB Office
IUB Office
IUB Office
IUB Office
IUB Office
IUB Office
IP Bear(IUB)
IP
Bear(IUB)
IP
Bear(IUB)
ATM
Bearer(IU
B Auto)
IP
Bear(IUB)
ATM
Bearer(IUB)
SCTP Config
(IUB-ABIS)
SCTP
Config
(IUBABIS)
SCTP
Config
(IUBABIS)
SCTP
Config
(IUBABIS)
Static Route
Static
Route
Static
Route
Static
Route
IP Path
Group
IP Path
Group
IP Path
Group
IP Path
Group
122
ATMoSTM1
IPoE1
ATM
Bearer(IU
B Auto)
Load the IUB Office sheet first, and then load other sheets.
Note:
Make sure the IUB Office sheet is loaded before other sheets and they are loaded by two
separate templates.
7.6
7.7
7.8
2.
Service IP: Fill in the interface type supported by the user-plane IP added at step 1
(operation type A).
3.
UCIU IP Combination Type: Fill in the combination type of UCIU IP, which needs
only one record (operation type A).
After completing the above three sheets, import them into OMM to finish adding userplane IPs.
7.9
Board Configuration
Pay attention to the following new concepts and general cares in board configuration of
V4.
7.9.1
7.9.2
124
Board
Physic
al
Board
0: INVALID
0: INVALID
No sub-card
Not
supported
Not
supported
Not supported
EDTS_2/EDTS
_3
6:E1;
7:T1
0: INVALID
0: INVALID
ESDTA
ESDTS_2
1:SDH63E1;
2:SDH63T1;
3:SDH84T1
1:STM-1
1:SDH-AU-4;
2:SDH-AU-3;
3:SONET-STS-1
EAPB
EXIS
5:ATM
1:STM-1
1:SDH-AU-4;
4:SONET-STS3C
ESDTI
ESDHS
1:SDH63E1;
2:SDH63T1;
3:SDH84T1
1:STM-1
1:SDH-AU-4;
2:SDH-AU-3;
3:SONET-STS-1
EDTI
EDTS_3/EMDT
S
6:E1;
7:T1
0: INVALID
0: INVALID
EDTA
EMSI
7.9.3
Available
Optical Port
Multiplexing
Structure
(sdhtype)
6:E1;
7:T1
ASPB
EAPB_
2
Available
Port Type
(porttype)
Available
Optical Port
Speed
Mode
(speedmod
e)
Logical
Board Name
CDR
Function
Completes control-plane
protocol and user-plane
protocol processing of all
interfaces. It is equivalent to the
combination of CMP, DMP, and
RUP in RU12.
Configuration
Description
It is strongly
recommended that
master/slave
configuration be used
for this board. Each
master board should
be configured with
one CMP module No.
Physical
Board
Logical
Board Name
Configuration
Description
Function
If master/slave
configuration is not
used, the cells cannot
be allocated to the
CMPs of CDR.
USP2a
7.9.3.1
CDR
Completes control-plane
protocol and user-plane
protocol processing of all
interfaces. It is equivalent to the
combination of CMP, DMP, and
RUP in RU12.
It is strongly
recommended that
master/slave
configuration be used
for this board. Each
master board should
be configured with
one CMP module No.
If master/slave
configuration is not
used, the cells cannot
be allocated to the
CMPs of CDR.
126
CMP: Firstly, it provides service for NodeB/cell. The common NBAP protocols and
cell radio resource are processed in CMP. Each cell must be allocated to a certain
CMP. Secondly, CMP processes the connectionless messages on the IU/IUR
interfaces, such as paging, etc. Finally, CMP processes signaling transmission
protocols, such as SCCP/M3UA/ SCTP/ MTP3B/ALCAP, etc. This means
transmission bandwidth resources need to be taken into account for CMP.
DMP: It only processes the radio process related to UE, such as special
RRC/RANAP/RNSAP/NBAP processes and special radio resource algorithm. No
resource relation is configured in the DMP module.
RUP processes only the common services and dedicated services of the user
plane.
For V4.13 series and later versions, the processing units of the user plane are all
processed by the RUB unit of CDR, which is divided into two parts, i.e., UCIU
(processing special user plane service) and CCIU (processing common user plane
service).
UCIU: It is the DSP for the special UE calling service, and the user plane sub-unit
processing special service. In ZXUR 9000 UMTS, it is deployed in RUP of the CDR
board.
CCIU: It is the DSP resource required during CCH establishment, and the user
plane sub-unit processing cell and common transmission channel instances. In
ZXUR 9000 UMTS, it is deployed in the RUB of the CDR board.
7.9.3.2
If Iux IP separation is set on site, the source of the IP can be one IP allocated to the
Iub interface. When the IP is used by the integrated CDR board (IUB COM IP), it
cannot be used by the special part of the Iub interface as the service IP. Therefore,
an IP should be reserved for the Iub interface on site, which can be regarded as the
IP allocated to the Iub interface. If there is no router set on the Iub interface, the
If Iux IP separation is not set on site, Iux interfaces share the IP. In this condition,
the IP should be planned. This IP is only provided for the integrated CDR board
(IUB COM IP), and it is used as the service IP for common channel establishment.
This IP is only used on the Iub interface. If there is no router on the Iub interface,
the integrated NE is not required to be set with other devices.
Note:
If two shelves are configured, it is necessary to plan an IUB COM IP. If three shelves are
configured, it is necessary to plan two IUB COM IPs.
It is recommended that IUB COM IP and Iub user plane IP be planned in the same subnet. It
is convenient for the data communication engineer to configure the route.
7.9.3.3
7.10
Field Name
User-Plane Board
Type
V4 UMTS
IUB
SBCJ/SBCR
3200
V4 UMTS
IUR
SBCJ/SBCR
1152
V4 UMTS
IUCS
SBCJ/SBCR
1280
PVC Configuration
The PVC traffic parameters include L2HtrfType and L2HtrfPara1 to L2HtrfPara5 and the
corresponding high traffic to low traffic type and parameters, all of which are used to
define the traffic bandwidth and characters on both receiving and sending directions of
PVC.
In the quick configuration version in V3 series, only Para1 to Para5 are displayed based
on the above principle. For different traffic types, the same traffic parameter may have
different meanings.
128
From the V4 version, all the parameters related to traffic parameters are displayed. The
engineer can choose the corresponding parameters according to onsite situation.
The relation of PVC traffic type, traffic parameter, and PVC service type is shown in the
following table:
Table 7-55 Relation between PVC Traffic Type, Traffic Parameter, and PVC Service
Type
Servic
e Type
cbr
rtVbr
ntrVbr
Traffic Type
Para1
Para2
atmClpNoTaggingNoScr (3)
PCR0+
1
PCR0
atmClpTaggingNoScr (4)
PCR0+
1
PCR0
atmNoClpNoScr (2)
PCR0+
1
atmClpTransparentNoScr (9)
PCR0+
1
CDVT
atmNoClpNoScrCdvt (12)
PCR0+
1
CDVT
atmNoClpNoScr(2)
PCR0+
1
atmClpNoTaggingNoScr(3)
PCR0+
1
PCR0
atmClpTaggingNoScr(4)
PCR0+
1
PCR0
atmClpNoTaggingScr(6)
Para
3
PCR0+
1
SCR0
MBS
Para
4
Para5
Servic
e Type
abr
Para
3
Para
4
SCR0
MBS
CDV
T
PCR0+
1
SCR0
MBS
atmClpTaggingScrCdvt(15)
PCR0+
1
SCR0
MBS
CDV
T
atmClpTransparentScr(10)
PCR0+
1
SCR0+
1
MBS
CDV
T
atmNoClpScrCdvt(13)
PCR0+
1
SCR0+
1
MBS
CDV
T
atmNoClpScr(5)
PCR0+
1
SCR0+
1
MBS
atmClpNoTaggingMcr(8)
PCR0+
1
CDVT
MCR
Traffic Type
Para1
atmClpNoTaggingScrCdvt(14
)
PCR0+
1
atmClpTaggingScr(7)
Para2
Para5
atmNoTrafficDescriptor(1)
ubr
ubr+
atmNoClpNoScr(2)
PCR0+
1
atmNoClpNoScrCdvt(12)
PCR0+
1
CDVT
atmNoClpTaggingNoScr(11)
PCR0+
1
CDVT
atmTrafficForUbr+(16)
PCR0+
1
MCR
MBS
MFS
CDVT
Note:
For different PVC service types, only the corresponding traffic types in the above table can
be used.
130
All the parameters in the above table should be configured as integer numbers.
In the running system, in order to modify PVC traffic parameters safely, block the upperlevel applications associated with PVC, such as AAL2PATH and ATMSIGLINK, before
modifying the parameters. Otherwise, call loss may occur.
7.11
The ATM address provided by the operator is usually in the format of E164, that is, a
string of 15 decimal numbers. Our OMM supports two ways of configuration: E164 and
NSAP. By default, NSAP will be adopted. The conversion between the two ways is as
follows: Put 45 before 905325000000001, so we get 45905325000000001. Separate the
string of numbers and put every two numbers into a group: 45-90-53-25-0-0-0-0-1F.
Since the last number 1 cannot form a group by itself, the letter F is added here. It
should be noticed that 45 is hexadecimal, which becomes 69 in the decimal system.
Therefore, when the E164 format mentioned above is converted into the NSAP format, it
becomes 69.144.83.37.0.0.0.0.31.
According to the values of AFI, there are four frequently-used AESAs, as shown in Table
7 -56.
Format
0x39
0x47
0x45
0x49
At present, in the test environment, manufacturers use the E.164 format of AFI=0x45
most frequently.
For the address in the E.164 format, the IDI field is marked by an ISDN number. This
field has all together eight bytes, and it adopts the BCD (Binary Coded Decimal) coding
method. 15 digits of it will be used, and each digit is a semi octet. If the first semi octets
are not used, they should all be replaced by the number 0.The entered ISDN number will
work as a management organization and be responsible for the DSP coding.
Here is an example which shows how to convert the NSAP format to the E164 format.
For example, 101.101.101 in the NASP format can be converted to 0X 45+65 65 65 in
the E164 format.
7.12
Value
Enable
Step mode
One step
Port state
Master
Enable
The screenshots are as shown in Figure 7 -83 and Error: Reference source not found
132
7.13
Shielding Alarms
Configuration Path: Managed Element > Equipment > Rack > Gate controls
configuration.
7.14
7.14.1.1
Port Switch
There are three types of port switch under master-slave EGPB configuration.
1.
2.
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.
The system can make the switch decision according to the result monitored by the
IEEE802.3ah protocol of the master and slave ports. The master port at the RNC side
134
judges the link accessibility by the 802.3ah heartbeat detection. If there is a link fault, the
system will trigger master-slave port switchover automatically.
7.14.1.2
7.14.1.3
VALUE
Subsystem No.
0~19
Module No.
1~127
Unit No.
1~17
SubUnit No.
1~254
Switch Type
Note:
For the master-slave configuration:
1. If the optical port and the electrical port of EGPB are configured with self-adaption, it is
not necessary to configure Switch Type.
2. If the optical port and the electrical port of EGPB are configured with the forced mode,
the Switch Type needs to be configured. Under this mode, our Tx transmission will be
stopped and the peer-end will follow the switchover when our equipment has problems in Rx
and Tx transmission.
Besides 1+1 configuration, when the LACP of the Backup mode is used, the member ports of
the LACP group can use the above three fault detection and switchover modes (Follow the
way should be used in priority, i.e., perform switchover according to the statistics of the
packets received by the Rx port), provided the switchover mode of the interface board of all
the member ports is consistent.
7.15
136
7.16
Each option has several configuration templates. Each template has a fixed relation with
different IUB transmission.
7.16.1
Figure 7-88 Used Transport Bearer Type Profile Related to Basic Priority
There are two templates in total. The relation between the templates and transmission
bearers is as shown in Table 7 -59.
7.16.2
Name
Common Scenarios
Template 1
ATM+IP Transport
Template 2
Only IP Transport
The relation between the value of Used Dedicated Service Transport Bearer Qos
Profile and IUB-interface transmission bearer is as shown in Error: Reference source
not found.
138
Name
Template 1
Two IP Paths
Template 2
Three IP Paths
Template 3
Template 4
Common Scenarios
IPoFE and IPoE1 scenarios
ATMoE1 scenario
No.
7.17
Name
Common Scenarios
Template 5
Template 6
IP Function Switch
In the MO version and later versions, if IP transmission needs to be used on the IUX
interface, it is not only necessary to apply for the license but also necessary to enable
license control switches on OMM, as shown in Error: Reference source not found
Path: Managed Element > UMTS Logical Function Configuration > Link
Configuration > IP Function Switch.