Professional Documents
Culture Documents
12)
Commissioning Guide
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you
do not agree to the following terms, please notice that you are not allowed to use this document.
Copyright 2015 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.
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).
ZTE CORPORATION
Email: TSM.Aftersales@zte.com.cn
Revision History
Author
Prepared
Date Document Version Reviewed by Approved by
by
2013-02-21 R1.0 Cheng Chen Taiming,
Chen Taiming
Hao Wang Wenqiong
Summary
Chapter Description
1 Notices in Data Configuration Notices in Data Configuration
2 Introduction to Quick Data Introduction to Quick Data Configuration
Configuration
3 Specifications of Configuring Specifications of Configuring Equipment Template &
Equipment Template & Transport Transport Network Template
Network Template
4 Specifications of Configuring Specifications of Configuring UMTS Radio Template
UMTS Radio Template
5 Special Subject Special Subject
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. III
ZXWR RNC (V3.12) Commissioning Guide
TABLE OF CONTENTS
FIGURES
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. VII
ZXWR RNC (V3.12) Commissioning Guide
TABLES
1.1.2 IP Planning
Recommended
No. Restrictions
Configuration/Description
At most 8 next-hop routes can be
1 configured to the same destination Static route
subnetwork.
A CMP (IU) supports 32 IU-interface
2
SCTPs at most.
The SCTP Local Port and SCTP Local IP
3 Only for ZTEs equipment
must be unique within the office.
The IP segments of each path within each
office on the IU interface shall not include
4 the IPs of each other. The IP segment of
the IUB interface must be configured with
the 32-bit mask.
1.1.3 Others
Recommended
No. Restrictions
Configuration/Description
Because multi-path
If multi-path is used, the NodeB ID cannot rectification may be
1
be set as 0 and 65535. performed later, do not set
NodeB ID as 0 or 65535.
If multi-PLMN policy is not
used in the field, the
If the IPAPPTYPE field in Service IP
MCC/MNC of all service IPs
2 contains the IUR interface, the MCC/MNC
must be set as
must be set as 65535.
65535/65535.(i.e., all
PLMNs can be accessed)
The IUCS interface, IUPS
interface, and IUB interface
Data configuration must be complete. should be configured with at
3 Otherwise, board power-up failure and least one office, and at least
repeated board restart fault will occur. one cell should be
configured with wireless
data.
All SPCs must be configured
In the configuration of MGW for the IUCS to the maximum value (i.e.,
4 office using IP bearer, SPC must be filled in 7.255.7 for format 3-8-3, and
the quick configuration template. 255.255.255 for format
8-8-8).
Recommended
No. Restrictions
Configuration/Description
For RNC V3.09.30, this
parameter is in NEINFO, and
can be configured by quick
NRI BIT NUM is an integration parameter of configuration.
the CN office for IU-flex transmission. If For RNC V3.11.10, this
5 IU-flex is used, this parameter should be parameter is in wireless
set to the same value for all CS offices.(The parameter management,
same for PS offices) and cannot be configured in
quick configuration. Instead,
it needs to be configured
manually.
The RCP uplink scrambling codes of
It is recommended that the
different RNCs should be different. The
uplink scrambling codes be
6 RCP uplink scrambling codes of adjacent
differentiated by the relation
RNCs using the IUR interface must be
of RNC ID.
different.
7 Subnet ID must be consistent with RNC ID.
8 Restrictions on CMP module No. allocation Refer to Chapter 0.
Each CMP supports 500 cells. Each DMP
9
processes 250ks BHCA.
In the PVC Config sheet,
each path group ID can only
For ATM bearer, each path group ID can be configured with one ATM
10
only be configured with one ATM PORT. PORT. Do not configure
more than one ATM PORT to
the same path group ID.
When ATM transmission is used for IUR
Configure one end as local
office, the owner of AAL2 channel at local
11 and the other end as
end should be configured differently with
adjacent.
that at the peer end.
42 DMP modules can be configured at
12
most, i.e., 21 boards.
The first sheet of all quick data configuration templates is the Template Info sheet,
which provides the basic template information for OMM. By this sheet, OMM can judge
whether the template matches with OMM and acquire the categorization information of
templates. Therefore, the content of this sheet must be kept complete no matter which of
other sheets are selected.
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.
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-1 for the method of filling the parameters of different
attributes (Modifying this line is prohibited).
Note:
Do not modify the first line and the fifth line of the template. Otherwise, template loading
error will occur.
Figure 2-5 shows the sheets included in the Equipment template, which can fulfill rack,
shelf, board, global information, and basic networking related data configuration.
All sheets in this template are related to UMTS network. Field engineers shall select the
sheets according to the actual application scenario.
V3_Template_Equip
ment.xls
Figure 2-6 shows the sheets included in the Transport Network template.
Transmission parameters on the IU/IUR/IUB interfaces and office integration parameters
are configured by this template.
Some sheets in this template are for UMTS data configuration and some are for GSM
data configuration. Field engineers shall select the sheets according to the actual
application scenario.
Select and fill in different sheets for the IU/IUR interface and IUB interface according to
the actual application scenario.
The application of the IUB interface involves multiple bearers. Different sheets should be
filled in for different bearers on the IUB interface. The basic rules of selecting the sheets
are as listed in Table 2-3.
The application of the IU/IUR interface involves multiple bearers. Different sheets should
be filled in for different bearers on the IUB interface. The basic rules of selecting the
sheets are as listed in Table 2-4.
V3_Template_Trans
portNetwork.xls
Figure 2-7 shows the sheets included in the UMTS Radio Quick Configuration Template.
The radio parameters on the Iub interface are configured with this template.
All sheets in this template are for UMTS data configuration. Six of the sheets are required.
Other sheets should be filled in according to the actual application scenario.
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.
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.
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 V3 quick configuration, no matter whether it is for
Equipment template & Transport Network template or for UMTS Radio Quick Configuration
template.
Step 2: Fill in the values for Choose Directory and File Name Prefix according to the
actual situation, load the template needed sheet by sheet, and click Execute.
The competed quick data configuration template can only be synchronized to RNC when
it meets the related restrictions on OMM and passes the validity check.
1. Template importing: In this process, OMM will check the validity, effectiveness, and
completeness of the format in the quick configuration template.
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.
After the Batch NEs Operation window pops up on OMM, select the target NE, and click
Restore modify area from Snapshot Area to restore data from the snapshot area to the
modify area. If Succeed in operating is displayed in Status, it means the operation
succeeds.
Select the target NE, and click run. After the Select Compare Type window pops up on
OMM, choose a comparison mode and click OK.
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.
Note:
Fast Compare: It is used to compare only the last modify time. The advantage of this mode
is its speed.
Full-text Compare: It is used to compare all parameters. The advantage is its preciseness.
3 Specifications of Configuring
Equipment Template & Transport
Network Template
This Guide deals mainly with the common sheets for UMTS products. For the sheets not
introduced in this Guide, please contact the chief engineers in the head office for
confirmation in advance.
OMCB
Server IPv4 ipv4 eg:xxx.xxx.xxx.xxx R-W-I
Address
OMCB
Server IPv4
long:[0..32] R-W-I
Mask
Length
eg:xxx.xxx.xxx.xxx
It can be used when it
OMCB
supports multipath
Inner Ip ipv4 R-W-I
protection.
Address
Other,it is filled in
default value 0.0.0.0 .
eg:
-720:GMT-12
-660:GMT-11
-600:GMT-10
-540:GMT-09
-480:GMT-08
-420:GMT-07
-360:GMT-06
-300:GMT-05
-240:GMT-04
-210:GMT-03.5
-180:GMT-03
long[-720,-660
-120:GMT-02
,-600,-540,-48
-60:GMT-01
0,-420,-360,-3
0:GMT
00,-240,-210,-
60:GMT+01
180,-120,-60,0
120:GMT+02
Time Zone ,60,120,180,21 R-W-I
180:GMT+03
0,240,270,300,
210:GMT+03.5
330,345,360,3
240:GMT+04
90,420,480,54
270:GMT+04.5
0,570,600,660,
300:GMT+05
720,780]
330:GMT+05.5
345:GMT+05.75
360:GMT+06
390:GMT+06.5
420:GMT+07
480:GMT+08
540:GMT+09
570:GMT+09.5
600:GMT+10
660:GMT+11
720:GMT+12
780:GMT+13
Daylight
Saving 0:Disable
long:[0..1] R-W-I
Time using 1:Enable
flag
Start time
of the
Daylight
Mon/Day/Hour/Min
Saving string R-W
eg:00/00/00/00
Time(Mon/
Day/Hour/
Min)
End time of
the Daylight
Saving Mon/Day/Hour/Min
string R-W
Time(Mon/ eg:00/00/00/00
Day/Hour/
Min)
Step of
Daylight long:[0..127,13
R-W
Saving 0..255]
Time
when the
MODULESEQ is
invalid,this filed filled
by 0;0.
0:No Backup
Backup 1:1+1 Backup
long:[0,1,2,5] R-I
Mode 5:1TO1 Backup
2:Load sharing
0:Invalid mode
1:FE
In,ATM/POS/MP/CST
M-1/E1/T1/E3/T3 Out
Channel
long:[0,1,2,3,4, 2:FE In,FE Out
Configurati R-I
5] 3:GE In,GE Out
on
4:FE In,GE Out
5:GE
In,ATM/POS/MP/CST
M-1/E1/T1/E3/T3 Out
0:NULL
1:SDH-63E1
2:SDH-63T1
3:SDH-84T1
4:POS
5:ATM
Port Type long:[0..11] R-I
6:E1
7:T1
8:GE
9:FE
10:E3
11:T3
0:E1 supported
1:T1 supported, T1 is
E1/T1 not full configured
long:[0..3] R-I
Config 2:T1 supported, T1 is
full configured
3:Reserved
0:NULL
1:SDH AU-4
Sdh speed long:[0,1,2,4,5, 2:SDH AU-3
R-I
mode 6] 4:SONET STS-3C
5:SDH Vc4-4c
6:SONET Sts-12c
0:Multi-frame
E1 Frame
long:[0,1,4] 1:Dual-frame R
Type
4:Forcible multi-frame
0:75OHM
E1
long:[0,1,2] 1:120/100OHM R
Impedance
2:Auto
0:CABLE PORT
1:OPTICAL PORT
2:Adaptive
Cable type long:[0,1,2,3] R
3:Invalid
This Parameter is valid
for Ethernet Port.
Managed
Primary
Element long:[1..4095]
Key
Object ID
Primary
Used Unit string eg:rack/shelf/slot
Key
Port
Primary
Number of long:[1..4,255]
Key
GLI
1:GE type
GLI
long:[1,3,4,255 3:2*GE type
Interface R-I
] 4:10GE type
type
255:Invalid
2:UIM connected with
Unit
UIM
connection long:[2..3] R-I
3:GLI connected with
type
UIM
connected
string eg:rack/shelf/slot R-I
Unit
Backup
string eg:rack/shelf/slot R
Unit
0 is invalid.
Vlan ID long:[0..4095] It is valid when it is sub R-W-I
interface.
Used VRF
Attributes
long:[0..254] 0 is invalid R-W-I
Configurati
on Object
eg:xx-xx-xx-xx-xx-xx
MAC Value range:
string R-W
address 00-19-C6-3E-30-10 ~
00-19-C6-4E-30-0F
eg:
Ip address ipv4 xxx.xxx.xxx.xxx;xxx.xx R-W
x.xxx.xxx
Subnet
long:[0..32] eg:24;24 R-W
mask
3.1.11 Service IP
eg:
MCC1:MNC1;MCC2:M
PLMN info
NC3
of Service string R-W-I
or 65535:65535,
IP
65535:65535 denotes
supporting all PLMN
Data Format:
Used Primary
string xxx.xxx.xxx.xxx;xxx.xx
Service IP Key
x.xxx.xxx;xxx.xxx.xxx.x
xx;xxx.xxx.xxx.xxx
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
Configure this sheet according to the specifications of the quick configuration template.
14-bit
signalling
point code long:[0..1638
R-W-I
of local 3]
office on
the net
24-bit
signalling
point code long:[0..1677
R-W-I
of local 7215]
office on
the net
Network
Resource It is valid just for
Identifier Bit long:[0..10] UMTS, and the R-W
Num in CS default value is 0.
Domain
Network
Resource It is valid just for
Identifier Bit long:[0..10] UMTS, and the R-W
Num in PS default value is 0.
Domain
ATM 20 Bytes, decimal.
address of string GSM doesn't need to R-W
local office config.
Used VRF
Attributes
long:[0..254] 0 is invalid R-W-I
Configurati
on Object
Route
long:[1..254] R-W-I
distance
0:close BFD/IPD
Route detection
BFD/IPD long:[0..2] 1:open BFD R-W-I
flag detection
2:open IPD detection
Forward
band width long:[0..4294
kbps R-W-I
of Path 967]
Group
Backward
band width long:[0..4294
kbps R-W-I
of Path 967]
Group
ATM
address of
string 20 Bytes,decimal R-W
adjacent
office
whether
0:off
support long:[0..1] R-W
1:on
Twin-IMA
0: Protection OFF
Switch of
1: Support multipath
IUB
long:[0..2] protection R-W
multipath
2: Support ATM+IP
protection
protection
1: QoS(according to
ARP/THP/TC)
Transport 2: QoS(according to
Qos Profile long:[1..2] service type) R-W
Type The default value is 2
if this parameter is
empty.
long:[1..255]
1:ATM+IP Transport
2:Only IP Transport
It cann't be filled
Profile ID of when it is only ATM
Transport transport.
Bearer System will
sequence<lo
Type Profile configurate it R-W
ng,4>
Related to according office's
Basic bear type when it is
Priority empty.
This parameter is
valid if
UPQOSMAPTYPE=
1.
long:[1..32]
1:Two IP Paths
2:Three IP Paths
3:One ATM Path and
Two IP Paths
4:Two ATM Paths
Transport
5:One IPOE Path
Qos Profile sequence<lo
and One IPOFE Path R-W
parameter ng,4>
6:One ATM Path and
Index
One IP Path
This parameter is
valid if
UPQOSMAPTYPE=2
.It can be filled in any
value if it is invalid.
NodeB
Inner IPv4 ipv4 R-W
Address
3.2.6 IP Path(IUB)
Parameter Parameter Filling
Description Remarks
Name Value Instructions
User label string R
Managed
Element long:[1..4095] Primary Key
Object ID
Adjacent
Net
long:[1..2047] Primary Key
Element
Identifier
TrPath ID long:[0..7] Primary Key
Path
long:[0..2047] R-I
Group ID
PLMN
long:[0..429496
Group R-I
7295]
Object ID
Destination
ipv4 R-W-I
IP Address
net mask
length for
long:[0..32] R-W-I
Destination
IP
Tx long:[0..429496
unit:kbps R-W-I
bandwidth 7]
Rx long:[0..429496
unit:kbps R-W-I
bandwidth 7]
0:Invalid,
21:IP Domain No.1,
22:IP Domain No.2,
23:IP Domain No.3
It should be
IP Domain
long:[0,21..23] configurated to R-W
No.
effective
value(21,22,23)
when IUB office is
multipath
protection.
It should be
OMCB configurated when
Path long:[1..3] IUB office is R-W
priority multipath
protection.
format
unitindex;e1index@
unitindex;e1index
unitindex:[1..17]
e1index:DTB/DTI[1.
.32],SDTB
[1..63],SDTI/SDTB2
[1..63,85..147]
Each E1 consists of
two parts,one is the
unitindex, another
E1 List string e1index R-W-I
The unitindex is a
unit that E1 belongs
e1index is the
number of E1 within
the unit
Unit number and E1
numbers separated
by ;(semicolons)
When to configure
More than one E1,
separated by @
Sperated by ";" and
E1 TS List string R-W
"-"
If LocalPort>190,
then filling the Ip
address of MP
Local Ip
ipv4 port,else filling the R-W
Address
Ip Address of PPP
port.
It can be empty.
If LocalPort>190,
then filling the Ip
address mask
Local Ip
length of MP
Address
long:[8..32] port,else filling the R-W
mask
Ip address mask
length
length of PPP port.
It can be empty.
Default is 24.
Path Group
long:[0..2047] R-I
ID
sequence<lon TrPath ID :[0..7]
TrPath ID Primary Key
g,4> eg:0;1
Destination
ipv4 R-W-I
IP address
net mask
length for
long:[0..32] R-W-I
Destination
IP
0:Invalid,
21:IP Domain No.1,
22:IP Domain No.2,
23:IP Domain No.3
It should be
IP Domain
long:[0,21..23] configurated to R-W
No.
effective
value(21,22,23)
when IUB office is
multipath
protection.
It should be
OMCB configurated when
Path long:[1..3] IUB office is R-W
priority multipath
protection.
format
unitindex;e1index@
unitindex;e1index
unitindex:[1..17]
e1index:DTB/DTA[1
..32],SDTB
[1..63],SDTA/SDTB
2[1..63,85..147],SD
TA2[1..63,64..126,1
27..189,190..246]
Each E1 consists of
two parts,one is the
E1 List string unitindex, another R-W-I
e1index
The unitindex is a
unit that E1 belongs
e1index is the
number of E1 within
the unit
Unit number and E1
numbers separated
by ;(semicolons)
When to configure
More than one E1,
separated by @
1:Normal,
Iub Plan long:[1..2] R-I
2:High load
0:CBR
1:rtVBR
2:nrtVBR
3:ABR
4:UBR
5:UBR+
CBR surpports:
atmClpNoTaggingN
oScr(2),
atmClpTaggingNoS
cr(3),
atmNoClpNoScr(1)
atmClpTransparent
NoScr(8),
atmNoClpNoScrCd
vt(11).
ABR surpport:
atmClpNoTaggingM
cr(7)
UBR surpports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCd
vt(11),
atmNoClpTaggingN
oScr(10).
UBR+ surpports:
atmTrafficForUbr+(
15)
0: NOTRF
1: atmNoClpNoScr
2:
atmClpNoTaggingN
oScr
3:
atmClpTaggingNoS
cr
4: atmNoClpScr
5:
atmClpNoTaggingS
cr
6:
atmClpTaggingScr
7:
atmClpNoTaggingM
cr
8:
atmClpTransparent
Traffic Type long:[0..15] NoScr R-W-I
9:
atmClpTransparent
Scr
10:
atmNoClpTaggingN
oScr
11:
atmNoClpNoScrCd
vt
12:
atmNoClpScrCdvt
13:
atmClpNoTaggingS
crCdvt
14:
atmClpTaggingScr
Cdvt
15:
atmTrafficForUbr+
Unit: Kbps.
Peak cell
This Traffic Para
rate for long:[0..18210
surpports all R-W-I
CLP=0+1 66133]
Service Category
(PCR0+1)
and all Traffic Type.
Unit: Kbps.
Service Category:
CBR ,rtVBR and
Peak cell
nrtVBR.
rate for long:[0..18210
Traffic Type: R-W
CLP=0 66133]
atmClpNoTaggingN
(PCR0)
oScr(2),
atmClpTaggingNoS
cr(3).
Unit: 0.1us.
Service Category:
CBR ,rtVBR,
nrtVBR and UBR.
Traffic Type:
atmClpTransparent
NoScr (8),
atmNoClpNoScrCd
Cell delay
vt (11),
variation long:[0..42949
atmClpTaggingScr R-W
tolerance 67295]
Cdvt(14),
(CDVT)
atmClpTransparent
Scr(9),
atmNoClpScrCdvt(
12),
atmNoClpNoScrCd
vt(13),
atmNoClpTaggingN
oScr(10).
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
Sustainable atmClpNoTaggingS
cell rate for long:[0..18210 cr(5),
R-W
CLP=0 66133] atmClpNoTaggingS
(SCR0) crCdvt(13),
atmClpTaggingScr(
6),
atmClpTaggingScr
Cdvt(14).
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Sustainable
Traffic Type:
cell rate for long:[0..18210
atmClpTransparent R-W
CLP=0+1 66133]
Scr(9),
(SCR0)
atmNoClpScrCdvt(
12),
atmNoClpScr(4).
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingS
cr(5),
atmClpNoTaggingS
Maximum
crCdvt(13),
burst cell long:[0..42949
atmClpTaggingScr( R-W
number 67295]
6),
(MBS)
atmClpTaggingScr
Cdvt(14),
atmClpTransparent
Scr(9),
atmNoClpScrCdvt(
12),
atmNoClpScr(4).
Unit: Kbps.
Service Category:
ABR and UBR+.
Minimum
long:[0..18210 Traffic Type:
cell rate R-W
66133] atmClpNoTaggingM
(MCR)
cr(7),
atmTrafficForUbr+(
15)
Unit: cell.
Service Category:
Maximum
long:[0..42949 UBR+.
frame size R-W
67295] Traffic Type:
(MFS)
atmTrafficForUbr+(
15)
Path Group
long:[0..2047] R
ID
sequence<lon TrPath ID :[32..127]
TrPath ID R
g,4> eg:32;33
AAL2 Path
long:[1..42949
ID intra R
67295]
office
AAL2 Path 0:Local End
long:[0..1] R-W
Ownership 1:Peer End
10:RT
AAL2 Path 11: NRT1
Service long:[10..14] 12: NRT2 R-W
Type 13: NRT3
14: MIX
Application 1: ALCAP
Type of UNI long:[1..3] 2: NBAP(NCP) R
Link 3: NBAP(CCP)
Destination
ipv4 R-W
IP address
Destination
IP address long:[0..32] R-W
mask
It should be
OMCB configurated when
Path long:[1..3] IUB office is R-W
priority multipath
protection.
Related to TD network.
PLMN
sequence<lon PLMN
Group R-I
g,4> ID:[0..4294967295].
Object ID
eg:1;2
2G office:
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSE
RVER
1023:SMLC
Type of long:[16,32,64,
3G office:
adjacent 512,576,1023, R-I
16:BSC
office 4096,32768]
32:RNC
64:MGW
512:MSCSERVER
576:MGW+MSCSE
RVER
4096:SGSN
32768:SAS
0: ATM (3G)
1: IP
Bear type long:[0..2] 2: TDM (2G) R-I
(Parameters can't
be modified)
Encode
type of 14:SPC 14 bits,
long:[14,24] R-W-I
signalling 24:SPC 24 bits
point
Destination long:[0..16777 14 bits:0..16383
R-W-I
point code 215] 24 bits:0..16777215
0: International
SPC,
4: Reserved
Sub-Servic
long:[0,4,8,12] international SPC, R-W-I
e Field
8: National SPC,
12: Reserved
National SPC
Connection
relationship 1:Associated
with local long:[1..3] 2:Quasi-associated R-W-I
signalling 3:No connection
point
support
0:Not Support
broadband long:[0..1] R-W-I
1:Support
properties
1:CHINA
Protocol
long:[1..3] 2:ITU R-W-I
type
3:ANSI
20 bytes, separate
ATM
each byte with ".",
address of
string decimal. R-W
adjacent
2G office dosen't
office
congifg it
Preference
For one PLMN,
CN Office
sequence<lon 0:NO
Flag in R-W
g,4> 1:YES
CS/PS
eg:1;0
Domain
For one PLMN,
Default
0:Is Not Default
Office Flag sequence<lon
Office R-W
in CS/PS g,4>
1:Is Default Office,
Domain
eg:1;0
Capacity For one PLMN,the
Weight in sequence<lon value range is
R-W
CS/PS g,4> [0..100].
Domain eg:1;0
Number of
Network For one PLMN,the
Resource sequence<lon value range is
R-W
Identifier in g,4> [0..4].
CS/PS eg:1;0
Domain
TD:[3..18]
UMTS:[3..31]
GSM:[3..12]
Used
long:[3..31] Support to modify R-W-I
Module
the module No. of
path group for Iu
interface.
Application
1:Server
type of long:[1..2] R-W-I
2:Client
association
Local port long:[1..65535] R-W-I
It can be filled in
four IP address at
Local Ip ipv4 most,such as R-W-I
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx
Remote
long:[1..65535] R-W-I
port
It can be filled in
four IP address at
Remote Ip ipv4 most,such as R-W-I
xxx.xxx.xxx.xxx;xxx
.xxx.xxx.xxx
ASP ID long:[1..3000] R-I
default value:500
RTO.Max long:[10..3000] R-W
unit 10millisecond
default value:50
RTO.Min long:[10..1000] R-W
unit 10millisecond
default value:100
RTO.Initial long:[10..3000] R-W
unit 10millisecond
default value:500
HB.interval long:[10..6000] R-W
unit 10millisecond
Delay ack default value:20
long:[0..20] R-W
interval unit 10millisecond
3.2.14 M3uaRoute
Managed
Element long:[1..4095] Primary Key
Object ID
Route
long:[1..640] Primary Key
Number
0:Ikebana Sort
Route
1:This Module
range long:[0..2] R-W-I
Priority
mode
2:Natural Sort
AS Number
long:[1..640] R-W-I
1
AS Number
long:[0..640] 0:Invalid R-W-I
2
3.2.15 M3uaRouteSet
3.2.16 IP Path(CN)
0:CBR
1:rtVBR
2:nrtVBR
3:ABR
4:UBR
5:UBR+
CBR surpports:
atmClpNoTaggingN
oScr(2),
atmClpTaggingNoS
cr(3),
atmNoClpNoScr(1)
atmClpTransparent
NoScr(8),
atmNoClpNoScrCd
vt(11).
ABR surpport:
atmClpNoTaggingM
cr(7)
UBR surpports:
NOTRF(0),
atmNoClpNoScr(1),
atmNoClpNoScrCd
vt(11),
atmNoClpTaggingN
oScr(10).
UBR+ surpports:
atmTrafficForUbr+(
15)
0: NOTRF
1: atmNoClpNoScr
2:
atmClpNoTaggingN
oScr
3:
atmClpTaggingNoS
cr
4: atmNoClpScr
5:
atmClpNoTaggingS
cr
6:
atmClpTaggingScr
7:
atmClpNoTaggingM
cr
8:
atmClpTransparent
Traffic Type long:[0..15] NoScr R-W-I
9:
atmClpTransparent
Scr
10:
atmNoClpTaggingN
oScr
11:
atmNoClpNoScrCd
vt
12:
atmNoClpScrCdvt
13:
atmClpNoTaggingS
crCdvt
14:
atmClpTaggingScr
Cdvt
15:
atmTrafficForUbr+
Unit: Kbps.
Peak cell
This Traffic Para
rate for long:[0..18210
surpports all R-W-I
CLP=0+1 66133]
Service Category
(PCR0+1)
and all Traffic Type.
Unit: Kbps.
Service Category:
CBR ,rtVBR and
Peak cell
nrtVBR.
rate for long:[0..18210
Traffic Type: R-W
CLP=0 66133]
atmClpNoTaggingN
(PCR0)
oScr(2),
atmClpTaggingNoS
cr(3).
Unit: 0.1us.
Service Category:
CBR ,rtVBR,
nrtVBR and UBR.
Traffic Type:
atmClpTransparent
NoScr (8),
atmNoClpNoScrCd
Cell delay
vt (11),
variation long:[0..42949
atmClpTaggingScr R-W
tolerance 67295]
Cdvt(14),
(CDVT)
atmClpTransparent
Scr(9),
atmNoClpScrCdvt(
12),
atmNoClpNoScrCd
vt(13),
atmNoClpTaggingN
oScr(10).
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
Sustainable atmClpNoTaggingS
cell rate for long:[0..18210 cr(5),
R-W
CLP=0 66133] atmClpNoTaggingS
(SCR0) crCdvt(13),
atmClpTaggingScr(
6),
atmClpTaggingScr
Cdvt(14).
Unit: Kbps.
Service Category:
rtVBR and nrtVBR.
Sustainable
Traffic Type:
cell rate for long:[0..18210
atmClpTransparent R-W
CLP=0+1 66133]
Scr(9),
(SCR0)
atmNoClpScrCdvt(
12),
atmNoClpScr(4).
Unit: cell.
Service Category:
rtVBR and nrtVBR.
Traffic Type:
atmClpNoTaggingS
cr(5),
atmClpNoTaggingS
Maximum
crCdvt(13),
burst cell long:[0..42949
atmClpTaggingScr( R-W
number 67295]
6),
(MBS)
atmClpTaggingScr
Cdvt(14),
atmClpTransparent
Scr(9),
atmNoClpScrCdvt(
12),
atmNoClpScr(4).
Unit: Kbps.
Service Category:
ABR and UBR+.
Minimum
long:[0..18210 Traffic Type:
cell rate R-W
66133] atmClpNoTaggingM
(MCR)
cr(7),
atmTrafficForUbr+(
15)
Unit: cell.
Service Category:
Maximum
long:[0..42949 UBR+.
frame size R-W
67295] Traffic Type:
(MFS)
atmTrafficForUbr+(
15)
Path Group
long:[0..2047] R
ID
sequence<lon TrPath ID :[32..127]
TrPath ID R
g,4> eg:32;33
AAL2
TD:[3..18]
Attached long:[3..31] R-W
UMTS:[3..31]
Module
AAL2 Path
long:[1..42949
ID intra R
67295]
office
10: RT,
AAL2 Path 11: NRT1,
Service long:[10..14] 12: NRT2, R-W
Type 13: NRT3,
14: MIX
AAL2 Path 0:Local End
long:[0..1] R-W
Ownership 1:Peer End
Signalling
long:[1..9000] R
link number
Linkset
long:[1..1024] R
number
Signalling
Link TD:[3..18]
long:[3..31] R-W
Attached UMTS:[3..31]
Module
Signalling
long:[0..15] R-W
Link Code
Destination
ipv4 R-W
IP address
3.2.18 Mtp2Link
3.2.19 Mtp3Route
0:Any arrangement
1:According to
SLS_bit0 choose
routing groups
2:According to
SLS_bit1 choose
link groups
3:According to
SLS_bit2 choose
link groups
4:According to
SLS_bit3 choose
Permutation
link groups
of signalling long:[0..8] R-W-I
5:According to
links
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
3.2.20 Mtp3RouteSet
Signalling
route long:[0..2000] 0:Invalid R-W-I
number 4
3.2.22 IP Bearer(ABIS)
3.2.25 PCM(ITC-MSC)
3.2.28 Fr Gb
3.2.29 Ip Gb
uarfcnUl is
calculated by
uarfcnDl, should
not input any
value.
long:[9612..9 {freqBandInd==0}
888,9262..95 [9612..9888],
38,12,37,62, {freqBandInd==1}
87,112,137,1 [9262..9538][12][3
62,187,212,2 7][62][87][112][13
37,262,287,9 7][162][187][212][
37..1288,131 237][262][287],
2..1513,1662 {freqBandInd==2}
,1687,1712,1 [937..1288],
UUARFCN R
737,1762,17 {freqBandInd==3}
87,1812,183 [1312..1513][1662
7,1862,4132. ][1687][1712][173
.4233,782,78 7][1762][1787][18
7,807,812,83 12][1837][1862],
7,862,4162.. {freqBandInd==4}
4188,812,83 [4132..4233][782][
7,2712..2863 787][807][812][83
] 7][862],
{freqBandInd==5}
[4162..4188][812][
837],
{freqBandInd==7}
[2712..2863]
{freqBandInd==0}
[10562..10838],
{freqBandInd==1}
long:[10562..
[9662..9938][412][
10838,9662..
437][462][487][51
9938,412,43
2][537][562][587][
7,462,487,51
612][637][662][68
2,537,562,58
7],
7,612,637,66
{freqBandInd==2}
2,687,1162..
[1162..1513],
1513,1537..1
{freqBandInd==3}
738,1887,19
[1537..1738][1887
DUARFCN 12,1937,196 R-W-I
][1912][1937][196
2,1987,2012,
2][1987][2012][20
2037,2062,2
37][2062][2087],
087,4357..44
{freqBandInd==4}
58,1007,101
[4357..4458][1007
2,1032,1037,
][1012][1032][103
1062,1087,4
7][1062][1087],
387..4413,10
{freqBandInd==5}
37,1062,293
[4387..4413][1037
7..3088]
][1062],
{freqBandInd==7}
[2937..3088]
Cell
Primary
long:[0..511] R-W-I
Scrambling
Code
Location long:[1..6553
R-W-I
Area Code 3,65535]
Routing
long:[0..255] R-W-I
Area Code
Service long:[0..6553
R-W-I
Area Code 5]
Element Data
URA sequence<lo Range in Array is
R-W-I
Identity ng,4> [0..65535],and
seperated by ";".
Service
Area Code long:[0..6553
R-W
for BC 5]
Domain
long:[0..9],<d
T_Cell R-W-I
efault:0>
5 Special Subject
ICM can also compare the existing network data, history data, plan data, and the backup
data in the plan area, providing a necessary reference for planning configuration data.
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.
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.
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.
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.
Select the type of the data to be exported in Data Type, e.g., UMTS Radio for UMTS
radio data and Uni_Ground for ground data, and click Next. In Figure 5-5, UMTS Radio
is taken as the example.
Click Select and select the directory for the exported file. Click Save > Export.
The interface for the data exported successfully is as shown in Figure 5-7. 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.
Data importing is based on Plan Area and is usually performed according the flow in
Figure 5-8.
Choose Live Data Area, right-click the record of the target OMMR subnet and choose
Create Plan Area.
Configure User Label in the pop-up Create Plan Area dialog box, select the check box
of the corresponding subnet record, and click OK.
Right-click the target Plan_Area under Data Area, and choose Import to import data.
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.
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:
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.
The process of importing Optimization Template is the same as that of importing Plan
Template. Check whether the number of successful records in Succeed/All Counts is
the same as the number of all records. If it is, the template is loaded successfully.
Note:
When importing the Optimization Template from ICM, pay attention to the following two
points:
In the Optimization template, the ME ID field must be configured. This is different from the
rules of filling in the Plan template.
The Data Type selected should match with the template name, as shown below:
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.
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.
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.
After the conflict check passes, choose the Submit tab, and click Submit to submit the
activation request.
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.
Observe the execution result in Status in the record and the Result in the log.
In the Activation Management window, observe whether there is some activation task
that is related to the Plan Area to be deleted. If there is, choose the activation task to be
deleted, click Delete, and click Yes in the pop-up Confirm dialog box.
Right-click the Plan Area to be deleted, and choose Check. Choose the Submit tab in
the pop-up dialog box, and observe whether the status is Editing. If it is, it is necessary
to click To Edit and switch the status to Editing.
After the above two checks are completed, the Plan Area can be deleted.
Note:
In the in-depth integration version of EMS and ICM, only two plan areas are available to
users by default. Too many plan areas will lead to resource waste and will greatly affect the
execution efficiency of other plan areas. Therefore, after the use of the plan area is finished,
the plan area needs to be deleted timely.
Figure 5-35 Overall Office Information Deletion (Including Ground & Radio Resources)
Acquire V3_Template_TransportNetwork, and fill in the data of the new site according to
Table 5-1.
Table 5-1 Sheets to Be Configured for Each Transmission Type of a New Site
No. IPoE1+IPoFE IPoE1 IPoFE ATMoE1 ATM+IP ATMoSTM-1
IUB IUB IUB
1 IUB Office IUB Office IUB Office
Office Office Office
UMTS
SCTP SCTP ATM SCTP
SCTP Config ATM
2 Config Config Bearer Config
(IUB) Bearer(IUB)
(IUB) (IUB) (IUB (IUB)
Auto)
IPOE IP
IP Bearer IP Bearer
3 Bearer Bearer
(IUB) (IUB)
(IUB) (IUB)
IPOE Bearer Static Static
4 Static Route
(IUB) Route Route
IP Path IP Path
5 Static Route
Group Group
UMTS
ATM
IP Path
6 Bearer
Group
(IUB
Auto)
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.
In the quick configuration version in V3 non-MO series, only Para1 to Para5 are
displayed based on the above principle. For different traffic types, the same traffic
parameter may have different meanings.
From the V3 MO version, all the parameters related to traffic parameters are displayed.
The engineer can choose the corresponding parameters according to onsite situation.
The relation of PVC traffic type, traffic parameter, and PVC service type is shown in the
following table:
Table 5-2 Relation of PVC Traffic Type, Traffic Parameter, and PVC Service Type
Service Para Para Para
Traffic Type Para1 Para2
Type 3 4 5
PCR0+
atmClpNoTaggingNoScr (3) PCR0
1
PCR0+
atmClpTaggingNoScr (4) PCR0
1
atmNoClpNoScr (2) PCR0+
cbr
1
atmClpTransparentNoScr PCR0+
CDVT
(9) 1
PCR0+
atmNoClpNoScrCdvt (12) CDVT
1
PCR0+
atmNoClpNoScr(2)
rtVbr 1
ntrVbr PCR0+
atmClpNoTaggingNoScr(3) PCR0
1
PCR0+
atmClpTaggingNoScr(4) PCR0
1
PCR0+
atmClpNoTaggingScr(6) SCR0 MBS
1
atmClpNoTaggingScrCdvt(1 PCR0+ CDV
SCR0 MBS
4) 1 T
PCR0+
atmClpTaggingScr(7) SCR0 MBS
1
PCR0+ CDV
atmClpTaggingScrCdvt(15) SCR0 MBS
1 T
PCR0+ SCR0+ CDV
atmClpTransparentScr(10) MBS
1 1 T
PCR0+ SCR0+ CDV
atmNoClpScrCdvt(13) MBS
1 1 T
PCR0+ SCR0+
atmNoClpScr(5) MBS
1 1
PCR0+
abr atmClpNoTaggingMcr(8) CDVT MCR
1
atmNoTrafficDescriptor(1)
PCR0+
atmNoClpNoScr(2)
1
ubr PCR0+
atmNoClpNoScrCdvt(12) CDVT
1
PCR0+
atmNoClpTaggingNoScr(11) CDVT
1
PCR0+ CDV
ubr+ atmTrafficForUbr+(16) MCR MBS MFS
1 T
Note:
For different PVC service types, only the corresponding traffic types in the above table can
be used.
All the parameters in the above table should be configured as integer numbers.
In the running system, in order to modify PVC traffic parameters safely, block the
upper-level applications associated with PVC, such as AAL2PATH and ATMSIGLINK,
before modifying the parameters. Otherwise, call loss may occur.
The ATM address provided by the operator is usually in the format of E164, that is, a
string of 15 decimal numbers. Our OMM supports two ways of configuration: E164 and
NSAP. By default, NSAP will be adopted. The conversion between the two ways is as
follows: Put 45 before 905325000000001, so we get 45905325000000001. Separate the
string of numbers and put every two numbers into a group: 45-90-53-25-0-0-0-0-1F.
Since the last number 1 cannot form a group by itself, the letter F is added here. It
should be noticed that 45 is hexadecimal, which becomes 69 in the decimal system.
Therefore, when the E164 format mentioned above is converted into the NSAP format, it
becomes 69.144.83.37.0.0.0.0.31.
According to the values of AFI, there are four frequently-used AESAs, as shown in Table
5-3.
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.
For the old RNC V3.10 version that does not support separated user-plane IPs, the
rules are:
2. If separated user-plane IP addresses are not used in the new U9.3 version, the
above rules can still be used. If separated user-plane IP addresses are required, the
following formula should be used to guide the configuration.
(Maximum number of port Nos. supported by RNC Number of port Nos. for other uses) / (Total
number of UDPs occupied by IUX * Number of DSPs supported by each RUB board)
If the result is a decimal, please round up the value to get the number of the RUB boards
supported by each IUX user-plane IP.
It is the upper limit for UDP ports. The value should be 65535, but considering the
round-up calculation, the largest UDP Port No. is defined as 64999 in RNC.
In RFC, it is clearly specified that the UDP port Nos. smaller than 1024 are all
registered. Therefore, do not use these UDP Port Nos. in RNC equipment.
Because the IUPS data contains the nominated Port No. 2152, which is specified in
the GTPU protocol, do not use 2152 for UDP port No. for non-IUPS data. Besides,
considering the influence of later RFC changes and expansion over the equipment,
do not use the UDP Nos. smaller than 5000. Therefore, the smallest UDP No. in
RNC is 5000. The UDP Port No. starts from 5000, which means 5000 can also be
used. Therefore, Port Nos. from 1 to 4999 are excluded.
Table 5-4 shows the values of the UDP port Nos. on different interfaces. This is for
each DSP on the RUB board. IUPS type is not related to the number of UDP ports
for service IP. For the service IP with mixed types, the number of UDP ports is the
sum of UDP ports in each type.
Modified Number of Port Nos.: 1. Number of CS users on VTCD2 increased to 400; 2. Take the 2/3 of the calculated
value; 3. Make sure the number of ports occupied on VTCD is an integer multiple of that occupied on VTCD2.
Note:
Suppose every resource shelf is configured with six RUB2 boards, we can get the following
result according to the above formula:
One IUCS user IP can be provided to (64999-4999)/(53415)=7.49 RUB2 boards for use,
which is rounded down to 7, i.e. 7 RUB2 boards.
One IUPS user IP can serve one board in the resource shelf.
One IUR user IP can be provided to (64999-4999)/(31815)=12.57 RUB2 boards for use,
which is rounded down to 12, i.e. 12 RUB2 boards.
One IUB user IP can be provided to (64999-4999)/(111915)=3.57 RUB2 boards for use,
which is rounded down to 3, i.e. 3 RUB2 boards.
There are 6 RUB2 boards in each resource shelf, the number of addresses needed by each
resource shelf is:
Configure 1 for IUCS, 1 for IUPS, 1 for IUR, and 2 for IUB. When configuring DSP IP, use
the first IUB address for the first three boards and use the second IUB address for the last
three boards.
For RNC, there are two boards that need to be allocated with Module No., i.e., ROMB
and RCB. The Module No. ranges from 1 to 127.
For RNC V3.11 and later versions, two modules of RCB are changed a little, i.e., SMP is
deleted, and DMP is added, but this is not a function replacement. Instead, the function of
SMP is integrated into CMP, and DMP processes the calls of UE users alone. The range
of CMP module No. is 3-18. DMP module No. is from 32 to 127. Both CMP module No.
and DMP module No. are allocated starting from small numbers (e.g., CMP module No. is
allocated from 3, and DMP module No. from 32).
The first four CMP module Nos., i.e., 3, 4, 5, and 6, are allocated to the Iu interface
according the function specifications. The other 12 Nos., from 7 to 18, are allocated to the
Iub interface. When there are enough module Nos., do not use the CMP module No. of
the Iu interface as that of the Iub interface, and vice versa. (e.g., the CMP module No. of
the IU interface must be allocated from 3, and the CMP module No. of the IUB interface
must be allocated from 7).
Function Module
Basic Configuration Rules
Unit No.
All boards (except ROMB/RCB) must be allocated to ROMP
ROMP 1
Module 1.
RPU 2 The virtual address should be configured on RPU Module 2.
It is used to process the IU-interface signaling and CN-office
path/path group.
CMP(IU) 36 Each module supports 32 IU-interface SCTP links at most.
The association links must be allocated evenly among the
modules.
It is used to process cells.
CMP(IUB) 7 18 All objects of the same NodeB must be allocated to the same
module No., and the NodeBs must be allocated evenly among
the modules.
It is necessary to select the module Nos. when creating
DMP 32 127
boards, and there is nothing else to be configured.
Note:
1. DMP/CMP on the same board is prohibited (the 2 modules on an RCB must be either
CMP or DMP).
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. 101
ZXWR RNC (V3.12) Commissioning Guide
2. The RCB of CMP must be in master/slave configuration. The RCB of DMP must be set
as NONE, and all DMPs should act as a resource pool by default.
Table 5-7 provides the allocation proportion rule for the D/C module No. of a
newly-commissioned site, and it does not cover all scenarios. Instead, it is only a
reference for quick data planning.
Table 5-7 Recommended D/C Module No. Planning for Newly-Commissioned Sites
Total
Number CMPNotIub CMPIub DMP Site Cell BHCA(K) OL(K)
of RCBs
4 1 1 2 250 500 1000 9
6 1 3 2 750 1500 1000 12
8 1 3 4 750 1500 2000 24
10 1 3 6 750 1500 3000 27
12 1 5 6 1250 2500 3000 36
14 1 5 8 1250 2500 4000 45
16 1 7 8 1750 3500 4000 48
18 2 6 10 1500 3000 5000 54
20 2 8 10 2000 4000 5000 60
22 2 8 12 2000 4000 6000 72
24 2 8 14 2000 4000 7000 72
26 2 10 14 2500 5000 7000 84
28 2 10 16 2500 5000 8000 90
30 2 10 18 2500 5000 9000 90
32 2 12 18 3000 6000 9000 108
34 2 12 20 3000 6000 10000 108
37 3 13 21 3250 6500 10500 117
Tip:
The CMPNotIub and "CMPIub (number) in Table 5-7 refer to the number of master CMP
modules. Both should be in 1+1 master/slave configuration and thus the number of master
CMP modules should be the same as the number of boards.
The DMP in the above table refers to the number of DMPs. Each board has two DMP
modules.
Take 20 as an example for Total Number of RCBs. It can be learnt from the above table
that it is necessary to configure two CMPNotIub modules and eight CMPIub modules, i.e., 10
master CMP modules in total. Because each board has two modules, five master CMPs are
needed, and therefore 10 CMP boards are needed for master/slave CMP configuration.
According to the above table, the number of DMPs is 10, and therefore the number of
DMPs to be configured is 10*2=20.
The BFD session based on static route is the implicit BFD function. Under this
configuration, the user does not need to configure any session parameters, and the
system will use the default value. No certification policy will be used for the
establishment of BFD session.
If the default parameters are used, the parameters should be configured the same at
the CE side.
5.10.1 E1 Bearer
The quantity of PVC and the bandwidth, which are generated by the quick data
configuration tool for RNC or SDR, are based on the results in the bandwidth
configuration tool.
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. 103
ZXWR RNC (V3.12) Commissioning Guide
When load-sharing mode is used, both GIPI boards will work simultaneously all the time
and share the transmission work of the IP network together. The maximum traffic of the
interface is the sum of the traffic on all load-sharing ports. Under master-slave
configuration, only one GIBI works normally at one time. The traffic of the interface is only
the traffic of a single port, i.e., half of the traffic for load-sharing mode.
The two boards of the load-sharing mode are independent from each other. Thus, we can
switch boards or change the configuration flexibly to meet some special rectification
requirements. If master-slave configuration is used, the two boards must be operated
simultaneously, such as, rectifications, swaps, and other major operations. In this case,
the service protection solution will be less flexible.
The two boards of the load-sharing mode are configured separately, it is not necessary to
monitor the status of the peer port (i.e., no matter whether the peer port is down or not,
our equipment can receive packets as long as there is one port sending packets).But this
is not the case for the master-slave mode. If the peer-end equipment (PTN or MSTP) is
not an L2 switch or there is no build-in L2 switching function between the master and
slave ports, by default, our 1+1 master-slave policy cannot work with the peer-end
equipment. In this case, it is necessary to perform relative configuration (Port Switch) to
monitor the peer port status. Make sure our master port can synchronize with the
peer-end and switch services to the new master port (original slave port) immediately,
when there is a fault on the master port of the peer end.
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.
The system can make the switch decision according to the result monitored by the
IEEE802.3ah protocol of the master and slave ports. The master port at the RNC side
judges the link accessibility by the 802.3ah heartbeat detection. If there is a link fault, the
system will trigger master-slave port switchover automatically.
Scenario 1
Usually, it is required that our GE interface board use 1+1 master-slave mode. In the
integration with peer-end equipment (PTN or MSTP), if the peer-end uses L2 switch or
there is the build-in L2 switch function between the master and slave ports, our default
1+1 master-slave policy can meet the requirement of this scenario.(The default switch
mode needs no configuration).
Scenario 2:
If 1+1 master-slave mode is required for our GE interface board, but the peer-end
equipment does not satisfy the above requirement, it is possible that our equipment
cannot coordinate with the peer-end equipment. To guarantee interoperability, please
select AH function based on or Follow the way according to the actual
situation.(Configure Port Switch).
Scenario 3:
If the networking of the peer-end equipment cannot satisfy the requirement of Scenario 1
and its switchover system cannot coordinate with or satisfy the requirement of Scenario 2,
the master-slave mode cannot be used normally.
Port switch is configured on the attribute configuration interface of the GIPI board, as
shown in Figure 5-40.
ZTE Confidential Proprietary 2015 ZTE CORPORATION. All rights reserved. 105
ZXWR RNC (V3.12) Commissioning Guide
Note:
1. If the optical port and the electrical port of GIPI/GIPI3/GIPI4 are configured with
self-adaption, it is not necessary to configure Switch Type.
2. If the optical port and the electrical port of GIPI/GIPI3/GIPI4 are configured with the
forced mode, the Switch Type needs to be configured. Under this mode, our Tx
transmission will be stopped and the peer-end will follow the switchover when our
equipment has problems in Rx and Tx transmission.
MNIC_2 provides an optical port. If there is some problem with the optical port, board
switchover will be performed.
MNIC_3 provides two external optical ports. When both ports are abnormal, board
switchover will be performed.
Besides 1+1 configuration, when the LACP of the Backup mode is used, the member ports
of the LACP group can use the above three fault detection and switchover modes (Follow
the way should be used in priority, i.e., perform switchover according to the statistics of the
packets received by the Rx port), provided the switchover mode of the interface board of all
the member ports is consistent.